Built from running real servers.

Why it exists

Running apps for a team and for clients meant a server here, a cheaper one there and one in an office, each with its own dashboard. Two problems kept coming back.

Every app wanted its own address. Testing an app against a payment provider or a sign-in service needs a real HTTPS address. Tools that give each machine a name made a second app on the same machine a fight over ports.

Reaching a client's database safely was awkward. The choices were to open it to the internet, or to put the server and everyone who needs it on one private network, one machine at a time.

Both have one cause: the network knows machines, and people care about apps. Meshploy runs the apps and the private network together, so each app can have its own address, private or public, and each person can be given exactly the apps they need.

What we believe

• Your machines, your data. Apps run on servers you choose. The platform is open source, and leaving means moving your apps, not rebuilding them.
• Plain words. You should not need to learn Kubernetes to put an app online, or to know what a mesh is to share one.
• Tested on real servers. Every feature is run on real machines, upgrades and reboots included, before it is called done.