One stack across many small customers.
Twenty customers with fifteen users each is a worse problem than one customer with three hundred: the same work, twenty times, on twenty budgets that cannot each afford an enterprise licence.
The situation
Per-seat pricing punishes exactly this shape. So does per-tenant infrastructure, when the tenant is a dental practice with a NAS in the back office.
The alternative — a different tool per customer, whatever they already had — means every incident starts with remembering which stack this one is.
What MeshHold does about it
No per-seat licence to work around
AGPL-3.0. What you deploy costs what the hardware costs, which makes the fifteen-user customer viable at all.
One thing to learn, many places to run it
The same single binary on a NAS, a mini PC, a VPS or a router. One set of habits across the whole book of customers.
Reach every site without opening it up
Tunnels and port forwards get you to a customer's web UI or an internal service without publishing anything or standing up a jump host per site.
Their data stays theirs
Each customer's mesh is separate, with its own swarm key. You operate it; you are not a party to it, which is a much easier conversation about liability.
Where it does not fit
Every page like this one is a sales pitch. Here is the part that is not.
- There is no multi-tenant control plane. Twenty customers are twenty meshes, and the fleet dashboard that would make that one screen is Business-tier work that has not shipped.
- No white-labelling. It says MeshHold in the interface.
- You are the first line of support for your customers — see the partner programme, where that is stated as a requirement rather than a hope.
Talk to us about it
There is one person on the other end, so a conversation is a conversation and not a discovery call.