Bring your own server

Forge-grade control,
without the fragility.

Sproobo runs your apps and databases as plain Docker containers on Linux servers you own. Builds happen off your server, every deploy goes through a health gate, and the agent only ever dials out.

Free for one server.
cp.sproobo.com · a push with a bug in itrolled back · nothing shipped

Real recording, 2.5× speed. The new container never passes the health gate, so the deploy rolls back on its own.Watch the full 79 s with sound

How it is built

What runs on your server, and how it gets there.

Three decisions carry the rest. Each one is visible on the box: open a shell and check.

Plain Docker, on a server you own.

Apps and databases run as pinned containers. Postgres, MySQL, MariaDB, Redis and MongoDB change version when you change them. Data sits on host paths under /var/lib/sproobo that you can open, back up and take with you. If you ever leave, everything is still there.

The agent only dials out, on port 8443.

One command installs Docker, the agent, a firewall baseline and the Caddy proxy. You do not open a single inbound port for Sproobo, and it works behind NAT. SSH stays open the whole time and Sproobo cannot close it. Logs and metrics are read live from the box when you open them; Sproobo stores none of it.

Every deploy goes through the same gate.

The build runs on Sproobo's builder, never on your server. The new container starts next to the old one, and traffic only moves once it passes your health check. If it never passes, the deploy rolls back on its own and the failed container's log tail is pinned to the deployment. The same path runs whether a person, the CLI or an AI agent pushed the button.

Sproobo deployment page: the health gate failed, the previous release kept serving, and the crashed container's log tail is shown on the deployment itself.
The gate fails. The previous release keeps serving and the crashed container's logs are on the deployment page, not in an SSH session.
Sproobo app overview after a passing deploy: health gate passed, the release is live on its domain with a valid certificate.
The gate passes. Traffic switches to the new release on its domain, with a certificate Caddy got and renews.
Coming from Forge, Ploi or Coolify

Same control surface. Different foundation.

Migrate one server at a time. The short version is below; the full matrix also covers Dokploy and Vercel.

Sproobo compared with Forge, Ploi and Coolify
 SprooboForgePloiCoolify
Apps & services in DockerEverythingNativeNativeYes
Pinned service versionsApps + DBsHost-tiedHost-tiedPartial
Data on inspectable host pathsYesOn hostOn hostVolumes
Outbound-only agent (no open ports)YesSSH inSSH inSSH in
AI connectors (claude.ai / ChatGPT)Built-inNoNoNo
See the full comparison
Pricing

Free for one server. Flat per organization after that.

Prices in EUR, billed through Stripe as Merchant of Record. Your servers come from any host or bare metal and are never on our bill. Plan details and what every plan includes.

Free

Kick the tires on one real server.

€0 / org / mo
  • Servers1
  • Apps3
  • Databases & services2
  • Team seats2
  • Releases kept per app1
  • PR preview deploymentsNone
Start free

Pro

For a builder running real workloads.

€19 / org / mo
  • Servers3
  • AppsUnlimited
  • Databases & services10
  • Team seats5
  • Releases kept per app5
  • PR preview deployments3 per app
Start with Pro

Team

Unlimited fleet, whole team on board.

€29 / org / mo
  • ServersUnlimited
  • AppsUnlimited
  • Databases & servicesUnlimited
  • Team seatsUnlimited
  • Releases kept per app10
  • PR preview deployments3 per app
Start with Team

Enterprise

Security review, DPA, SLA. Let's talk.

Custom
  • ServersUnlimited
  • AppsUnlimited
  • Databases & servicesUnlimited
  • Team seatsUnlimited
  • Releases kept per app10
  • PR preview deployments3 per app
Contact us