BridgePort vs Dokploy

Fleet control plane vs self-hosted PaaS

Dokploy is a self-hosted platform-as-a-service in the same family as Coolify: connect a git repository, and it builds your app, wires routing and TLS through its built-in Traefik proxy, and runs it — with one-click databases, backups, and app templates included. For multi-server setups it builds on Docker Swarm.

BridgePort is not a PaaS. It assumes CI builds your images and picks up from there: a control plane that deploys cataloged images as services across plain Docker servers, syncs encrypted secrets and templated config files, orchestrates multi-service rollout plans with automatic rollback, and monitors servers, services, and databases. It also adopts infrastructure that already exists rather than expecting to have created it.

At a glance

DimensionBridgePortDokploy

PhilosophyOps control plane for image-based services on your fleetSelf-hosted PaaS: git push → build → run behind its proxy

Builds from sourceBring images from any registry — CI owns the buildBuilds from git (Dockerfile, Nixpacks, buildpacks) with app templates

Multi-server modelPlain Docker hosts over SSH or socket — no cluster layerMulti-node setups lean on Docker Swarm and remote server support

Adopting existing serversDiscovers and manages containers already running on your hostsManages what it deploys; pre-existing workloads stay outside its model

Reverse proxy & TLSBring your own (Caddy, Traefik, nginx) — managed as services like everything elseBuilt-in Traefik with automatic HTTPS

Multi-service orchestrationDeployment plans: dependency ordering, health gates, automatic rollbackPer-app deploys and compose stacks; cross-app ordering is not the model

Secrets & configAES-256-GCM secrets + templated config files and fragments synced to serversPer-app and shared environment variables

MonitoringServer/service/database metrics, URL/TCP/TLS checks, alert notificationsContainer/server monitoring and notifications, PaaS-scoped

Infrastructure as codeTerraform provider, REST API, Go SDK, CLI, MCP serverREST API and CLI

License & costApache-2.0, one edition, all featuresOpen source and free to self-host, with an optional paid cloud

Dokploy is a fast-moving project — verify specifics against its current documentation for your version. Comparison last reviewed July 2026.

Choose BridgePort if…

CI already builds and pushes images, and you want deployment + operations from there.
You operate an existing fleet — proxies, databases, and containers you set up yourself.
You need coordinated multi-service rollouts with health gates and rollback.
You want to avoid a Swarm layer and keep servers as plain Docker hosts.

Choose Dokploy if…

You want git-push-to-deploy with builds, routing, and TLS handled for you.
You like one-click databases, backups, and a template marketplace.
A Vercel/Heroku-style app workflow on your own hardware is the goal.

Frequently asked questions

Is BridgePort a Dokploy alternative?

They overlap on "run containers on my own servers" but optimize different workflows. Dokploy is a PaaS: it builds apps from git and runs them behind its built-in proxy. BridgePort is an operations control plane for image-based services across a fleet — deployment plans, encrypted secrets, config sync, and monitoring for infrastructure you already run.

Does BridgePort use Docker Swarm for multiple servers?

No. BridgePort manages each server as a plain Docker host over SSH or the Docker socket — there is no cluster or Swarm layer, which keeps servers independent and easy to reason about.

Does BridgePort build my app from a git repository like Dokploy?

No, by design. Your CI builds and pushes the image; an HMAC-signed webhook then triggers BridgePort to roll it out, optionally through a deployment plan with automatic rollback.

Can I use both?

Yes — some teams host small apps on a PaaS while running core infrastructure through BridgePort. Since BridgePort only needs SSH or socket access, it can also monitor servers a PaaS manages.