Documentation

Deploy Bridge, documented

How the deployment platform works: connecting a server, shipping a build, managing secrets and domains, and the limits on what the build agent is permitted to do on your machine.

About the product

Getting started

What Deploy Bridge is

Deploy Bridge turns source code into a recorded deployment on a Linux server supplied by the account holder. It combines source analysis, container deployment, optional database provisioning and Cloudflare-backed routing.

4 min read

Connecting your first server

Register a reachable Linux server, verify the SSH connection and provision the toolchain used by Deploy Bridge. Connection secrets are encrypted and the first observed host key is pinned.

4 min read

Deploying a project from Git

Connect an HTTPS Git repository, review the analysed deployment blueprint and start a tracked run against a registered server. Private repositories may use an encrypted personal access token.

4 min read

Configuration

Environment variables and secrets

Deploy Bridge derives an environment template during analysis and writes resolved values beside the remote Compose file. Generated database credentials override stale template values.

4 min read

Domains and certificates

Deploy Bridge currently publishes domains through Cloudflare and Nginx. Adding a domain records intent; DNS, Origin CA and proxy configuration are applied when that domain is selected for deployment.

4 min read

Databases and provisioning

Deploy Bridge can detect and provision PostgreSQL, MySQL, MongoDB and Redis as server-local containers. Credentials and named volumes are scoped to a project, server and database engine.

4 min read

The build agent

How the agent proposes a fix

After a deployment step fails, the agent receives bounded operational context and proposes one structured remediation. The proposal is schema-validated and risk-classified before anything can run.

4 min read

Approvals and what the agent may run

Unattended remediation is restricted by a fixed allowlist and content-specific checks. Anything unrecognised or able to reach wider host state pauses the deployment for a recorded decision.

4 min read

Operations

Plans, limits and what happens at a ceiling

Plans meter six dimensions: servers, projects, domains, deployments, agent fixes and team members. Actions that exceed a ceiling are refused without removing resources already in place.

5 min read

Troubleshooting a failed deployment

Begin with the first failed step and its terminal output, then inspect the corresponding server, blueprint or external integration. Later steps are skipped after a failure and should not be diagnosed as independent faults.

4 min read

Something the docs do not cover?

If the platform is not behaving the way this documentation describes, that is a bug in one of the two. Tell us which page and what you saw.

Start a conversation Deploy Bridge