Managing WireGuard access for a fleet from OPNsense
Handing out WireGuard configurations by hand stops scaling quickly. Managed Paart moves that work into the OPNsense interface you already run.
The problem: WireGuard does not scale by hand
WireGuard is small, fast and pleasant to run for one person. Running it for thirty is a different job.
Every new user means generating a key pair, writing a peer block into the firewall configuration, assembling a client configuration, and getting it to the right device without emailing a private key. Every departure means finding that peer block again and removing it. Every replaced laptop means doing both.
None of that is difficult. It is simply manual, repetitive, and exactly the kind of work where an entry gets forgotten — and a forgotten peer block is access that nobody revoked.
What the firewall already knows
The firewall is where the tunnel terminates, so it already holds the peers, the addresses and the routes. What it does not have is a way to talk about users and devices rather than about configuration blocks.
That is the gap Managed Paart fills: a management interface inside the OPNsense admin UI, so that users and their WireGuard access are managed where the tunnel already lives, without editing configuration files by hand.
What that changes
- Create the user, assign the device. Configurations are deployed from the firewall, and when one of them changes, the update is pushed to the device.
- Revoke from the firewall. A lost device or a departure is handled remotely, without waiting for anyone to touch the device.
- Keys never travel. Each device generates its own and keeps it in its own secure storage. Someone with a laptop and a phone has two, and revoking one leaves the other intact. Keys can be renewed manually or on a schedule.
- Your infrastructure, not ours. There is no Paart cloud and no SaaS in this: the plugin runs on your own OPNsense, and the tunnels go from the device to your firewall.
Where this stands today
Managed Paart is in Early Access, and there is no official release date or final pricing yet. It is not an idea on a roadmap — the system works and has been tested in the lab, and the current Paart client is already compatible with it — but the OPNsense plugin is not in the official repository yet.
If that is the shape of problem you have, Managed Paart explains what it is and how to get in touch about testing it.
If someone already gave you a connection
You do not need any of this to use a configuration your organisation issued you: it is an ordinary WireGuard configuration, and it is imported like any other. See Managed Paart on the help side, and adding your first connection.