Deploy, orchestrate & monitor Docker across all your servers

InstallOne container, SQLite inside

SecretsAES-256-GCM at rest

ConnectSSH or Docker socket

LicenseApache-2.0, open source

Capabilities

Everything between git push and production

Deploy to every server

Define a service once — image, env, health checks — and roll it out to any number of servers over SSH or the Docker socket. Existing containers are discovered and adopted in place.

See the workflow

Config & secrets

AES-256-GCM encrypted secrets and templated config files, synced atomically to your servers.

Out of .env files

Monitoring & health

Server, container, and database metrics plus four kinds of health checks — no Prometheus stack to run.

Watch everything

CI/CD & deployment plans

CI pushes an image, a signed webhook triggers a health-gated rollout — with automatic rollback.

Ship on git push

Notifications & topology

Alerts where your team lives, plus a live diagram of servers, services, databases, and dependencies.

See the whole picture

Automate everything

Every screen in the UI is a stable REST API underneath — with a Go SDK, a CLI, a Terraform provider, and an MCP server for AI agents.

Explore the API

Browse all use cases

Up and running

From zero to deployed in three steps

1. 01

   Run the container

   One docker run — SQLite is embedded, so there's no external database to stand up.

   docker run -d --name bridgeport \
     -p 3000:3000 -v bridgeport-data:/data \
     -e MASTER_KEY=$(openssl rand -base64 32) \
     -e JWT_SECRET=$(openssl rand -base64 32) \
     -e [email protected] \
     -e ADMIN_PASSWORD=changeme123 \
     ghcr.io/bridgeinpt/bridgeport:latest

   Copy
2. 02

   Connect your servers

   Point BridgePort at your machines over SSH or the Docker socket. It discovers running containers and brings them under management — nothing to reinstall.

   Adding servers
3. 03

   Deploy & monitor

   Ship services from the image catalog, wire up health checks and alerts, and let deployment plans handle ordering and rollback.

   Getting started guide

Where it fits

More than Compose. Less than Kubernetes.

SSH + docker compose

Great for one box. Past a couple of servers you're hand-rolling deploys, scattering .env files, and tailing logs over SSH — no audit trail, no rollback, no overview.

The sweet spot

BridgePort

One self-hosted control plane for the whole fleet: central deploys, encrypted secrets, health checks, and plans that roll back on failure. Still plain Docker underneath — no lock-in, leave anytime.

Kubernetes

The right call for elastic, cluster-scale platforms with a team to run them. For a fleet of long-lived servers, it's a lot of machinery you don't need.

Full comparisons: Kubernetes · Docker Compose · Portainer · Coolify · Dokploy · CapRover — or read the FAQ

Run your fleet like a port authority

Install one container, connect your servers, and ship with confidence — your infrastructure, your data, your rules.

Get startedRead the concepts

Self-hosted · single container · Apache-2.0