Been slowly stabilizing my new project I’m calling (for lack of a better name at the moment) Webmesh and hitting the rounds on some social networks.
It’s yet another mechanism for configuring WireGuard networks, with the core difference from others being that it uses raft-consensus to maintain state between connected instances. This allows for any node to optionally be a “controller server” on top of being a spoke in the network. There is more information in the Github - but tons more documentation is needed for sure.
I’m building a plugin architecture around it as well as potentially looking to build a saas or some other type of offering. Been actively looking for another developer or two who may be interested in embarking on the adventure with me. Feel free to reach out if interested. Also happy to hear any feedback :)
You must log in or register to comment.
Something like this would solve a lot of my hesitations in using a mesh network setup, since central access isn’t always available and I hate having to rely on one . Looking forward to see where this goes and potentially using it, especially in a production environment (where support can potentially come along with it! 💸)
Thanks for the kind words :)