Same push-to-deploy you already know, running on a machine you already pay for. No Docker. No SSH. No invoice.
The boring operational parts are already handled. You just have to pick what to deploy.
Deplo has a clean, intuitive UI that helps you understand what’s happening, without wasting time.
Your coding agent can deploy, read logs and roll back for you, with the same access a teammate gets.
Deplo knows. Every action has a name and a time on it, and you decide who's allowed to do what in the first place.
Your hardware, your network, your data. Open source, no lock-in, and no pricing page to keep an eye on.
Deploys, backups, logs, metrics and TLS, already on. Nothing to buy on top, nothing to hunt down.
Deplo ships a native MCP server. Point Claude, Cursor or any MCP client at your instance and it can deploy, read logs and roll back in plain language, under a token you mint and revoke. Same permission checks as the dashboard, so an agent can never do what you can't. Off by default.
Connect GitHub, GitLab, Bitbucket or Gitea once. Every push to your production branch goes live, every pull request gets its own preview URL that disappears when it closes, and a bad release rolls back to the exact image that worked. No CI pipeline to own.
Deplo is built for a team, not for one operator with root. 46 fine-grained Capabilities let you say "can deploy, cannot delete", and per-folder grants hand a member exactly one corner of the fleet. The Activity trail answers who did what and when, in the UI. Nobody has to look in a database.
Connect the repo and you get a live URL with HTTPS on it. deplo works out the framework and builds it for you, so there's no Dockerfile to write, no SSH, nothing to hand-edit. Postgres or Redis sits next to your app in two clicks. Same stack you ran on the cloud. Only the bill changed.
If it ships as a Docker image, it runs on Deplo. Every one of the hundred-plus templates is deployed and checked first: a hundred that work beat a thousand that might.
Nobody moves off a cloud bill this happily without looking for one. Here are six questions worth asking.
Correct. Deplo runs Docker underneath, but you deploy from a repo or a template and the platform does the container part. There's a terminal and a compose escape hatch if you want one, and it stays out of your way if you don't.
That’s exactly what we’re trying to avoid. Deplo is built to be intuitive from the start, so you can understand what’s happening without spending hours learning another complicated interface.
Deplo is free and open source. You pay your server provider, and that's the whole bill: no per-seat pricing, no bandwidth surprises, no charge for the tenth environment.
Deplo is currently in beta, with the stable release targeted for Q4 2026. That said, people are already using it for real workloads today. The beta is an opportunity to use Deplo, see how it fits into your workflow, and help us make the product even better before the stable release.
Your apps are standard Docker containers on a server you own, and deplo is AGPLv3, so nobody can take it away or reprice it. Leaving means moving containers, not rebuilding on someone else's proprietary primitives.
You get the same push-to-deploy experience here, on a machine that is yours. Usually faster, since the resources are dedicated instead of shared and metered. More flexible, since anything that runs in a container runs. Cheaper, since you pay the server and nobody in between. And there is nothing proprietary to unpick the day you move it somewhere else.
Install takes one command on a server you already pay for. What you do with the money you get back is your business.
