Deplo

Deplo

Deplo is an open-source alternative to Vercel, Railway and Cloudflare: push a repo, pick a server, get a deployment, on your own infrastructure.

The Deplo dashboard

Deplo is still in beta

Rough edges are expected. The official 1.0 release is planned for Q4 2026.

Why Deplo

Push, and it's live: on hardware you own, a bill you control.

A VPS and a domain is enough

Builds, routing, TLS, backups, monitoring, rollbacks.

No per-seat pricing, no lock-in

You pay your host, not Deplo.

Deploy from anything

A Git repo, an image, a Dockerfile, Compose, or a plain upload.

The shell is optional

An escape hatch for experts, never a requirement.

Familiar by design

Shaped by a dedicated UX/UI team, not reinvented.

A free URL from the first deploy

Before you even own a domain.

Popular features

The parts people reach for first.

How it works

Two programs, one rule: the control plane decides, the agent executes.

The control plane decides

Renders the Compose file and the routing, resolves secrets, never touches Docker directly.

The server agent executes

One Go binary per host, the only thing that runs Docker, reached over mutual TLS.

Traefik routes and issues certificates

Automatic HTTPS for every domain you add.

Postgres remembers

The single source of truth for the whole control plane.

The box running Deplo itself is just another server in the fleet, no special shortcut.

What Deplo is not

  • Not a hosting provider. You bring the server. Deplo never bills you for compute, seats or build minutes.
  • Not a DNS provider. You keep your registrar. Deplo tells you which record to create and checks that it resolves.
  • Not Kubernetes. The unit is a Docker container on a host you picked, not a scheduled pod. There is no cluster to operate.
  • Not a black box. The rendered Compose file, the routing labels and the build logs are all readable from the dashboard.

Explore the rest

  • Getting Started: install Deplo and deploy your first app.
  • Concepts: how Deplo works, under the hood.
  • Guides: every day-to-day task.
  • Advanced: Compose apps, build servers, custom certificates.
  • Operations: upgrade, back up and administer your instance.
  • Reference: glossary, environment variables, the API.
  • Troubleshooting: fix deploys, domains, servers and access.

Did this page help you?