Deploy Bridge FAQ

Limits, ownership and the agent's boundaries.

Straight answers about the server you bring, what happens at a ceiling, what a downgrade changes and what the remediation agent is permitted to do.

FAQ

Deploy Bridge questions

Do I need my own server to use Deploy Bridge?

Yes. Deploy Bridge deploys to a machine you provide and connect over SSH, from any provider you like. We do not resell compute, so the hosting bill stays between you and your provider.

What happens when I hit a plan limit?

The action that would exceed the ceiling is refused and you are told which limit you reached. Nothing already running is stopped or deleted, and deployment and agent-fix counts reset when your next billing period begins.

What happens if I downgrade?

Nothing is removed. Servers, projects and domains above the new ceiling become read-only, with the oldest ones up to the limit staying writable, and you cannot add more until you are back under it. Upgrading again restores everything with no repair step.

Can the AI agent run commands on my server without asking?

Yes, but only commands on a fixed allowlist of low-risk operations: inspecting files and the state of the machine, creating a directory, pulling and restarting containers through Compose, and testing or reloading nginx. Anything the allowlist does not recognise is classified destructive and stops for your approval. Either way the action is recorded against the deployment.

Is there a free tier?

Yes, and it does not need a card. Free covers one connected server, two projects, one domain, ten deployments a month and five agent fixes a month.

What do I lose if I cancel?

The orchestration, the agent and the deployment history. What you keep is everything that matters operationally: the server is yours, the containers carry on running, and your data never left your machine.

See the ceilings side by side.

Every plan includes every feature. Compare the six usage limits and start on the free tier without a card.