Bring your own machine
Any server you can reach over SSH. We do not resell compute, so there is no margin for us in where you run and no reason to steer you.
Ownership
It is your machine. We never pretend otherwise.
Deploy Bridge is not a host. You bring a server from whoever you like, we connect to it over SSH, and everything we do is something you could have typed yourself.
Capabilities
Root stays with you
You are not handed a restricted tenant on somebody else’s box. You keep the credentials, and you can log in beside us at any time.
Ordinary containers underneath
Projects run as containers described by ordinary files on your disk. There is no proprietary runtime that stops working when you stop paying.
Leaving is a decision, not a migration
Cancel and the machine keeps running exactly as it was. The worst case is that you go back to deploying it by hand.
01
The lock-in question, answered honestly
Most platforms answer "can I leave?" with a migration guide. The honest version is simpler: if the thing you deploy to is already yours, leaving is not a migration at all. Your containers keep running on your server whether or not you have an account with us.
That constrains what we can build — we cannot invent a proprietary layer and charge you for access to it — and we think that is the right constraint. What you pay for is the orchestration, the agent and the audit trail, not custody of your own infrastructure.
02
What we hold, and what we do not
We hold the connection details needed to reach your machine, the history of what was deployed and when, and the record of who approved what. That is the material the product is made of.
We do not hold your data, your database contents, or the only copy of anything. If our service is unavailable, your applications carry on serving traffic, because they are running on your server and not on ours.
The complete product starts on Free.
Every plan includes every Deploy Bridge capability. Paid plans raise usage ceilings; they do not unlock this feature.