DigitalOcean CapRover: Self-hosted PaaS with automatic HTTPS, deploy apps in minutes

If you've ever wasted an afternoon wrestling with nginx configs, SSL certificates, and Docker Compose files just to get a side project online, you already know why people keep searching for "digitalocean caprover." It's the combination that turns a fresh Linux server into something that feels suspiciously close to Heroku or Vercel — except you own the box, you own the data, and you're not paying per-deploy markup.

Let's walk through what CapRover actually is, why pairing it with a DigitalOcean Droplet is the path most people recommend, and what you should pick when you're staring at that droplet-size picker for the first time.

What CapRover brings to the table

CapRover is a free, open-source, self-hosted PaaS built on top of Docker, Docker Swarm, nginx, and Let's Encrypt. The pitch is simple: you bring code in any language that runs in a container — Node.js, Python, PHP, Java, Ruby, .NET, whatever — and CapRover handles the build, the routing, the HTTPS, and the ongoing management from a web dashboard.

A few things make it stand out from the DIY-Docker-on-a-VPS route:

• One-click apps: there's a sizable library of pre-configured templates for WordPress, MySQL, MongoDB, Postgres, monitoring tools, and dozens of other popular services. You click, it deploys.

• Automatic HTTPS: Let's Encrypt certificates are issued and renewed for you, with one-click HTTP-to-HTTPS redirects. No more certbot cron jobs you forget about.

• Flexible deploys: push from the dashboard, the caprover CLI, a webhook, or your existing Git workflow.

• Cluster-ready: when one node isn't enough, you add nodes to the Docker Swarm cluster and CapRover handles load balancing.

• No vendor lock-in: it's open source and runs on any Linux box with Docker, so you're never trapped.

The official CapRover docs themselves note that the recommended install path is the DigitalOcean one-click app — which is a pretty strong hint about which combination the maintainers actually use day to day.

Why DigitalOcean is the natural home for CapRover

You can run CapRover on any provider, but there's a reason "digitalocean caprover" is the search people type rather than "random-VPS-provider caprover." DigitalOcean lists CapRover as a Marketplace 1-Click App, currently built on Ubuntu 24.04 with CapRover version 1.15.1. That means the entire install — OS, Docker, CapRover, nginx, Swarm setup — happens in the time it takes the droplet to provision. You don't SSH in and run a setup script; you click once.

A couple of pricing notes worth knowing before you spin one up:

• As of January 1, 2026, DigitalOcean moved Droplets to per-second billing with a 60-second minimum (or $0.01, whichever is higher). That's genuinely useful for CapRover testing — you can stand up a droplet, poke at a deploy, destroy it, and pay pennies instead of a full month.

• New accounts currently receive a $5 credit valid for 90 days, which is enough to run a small CapRover instance for a few weeks of evaluation without touching your card.

If you want to grab that credit and launch the one-click, here's the door:

👉 Get started with DigitalOcean and claim your new-user credit

Picking the right Droplet size for CapRover

This is the part where most people overthink it. CapRover's own getting-started guide says it's tested on Ubuntu 24.04 with Docker 25+ and that most providers' $5-ish/1GB instance works as a floor. The basic Droplet lineup currently looks like this — pick based on how many apps you plan to cram onto one box, not on speculation.

512 MiB / 1 vCPU — $4/month

The absolute floor. 10 GiB SSD, 500 GiB outbound transfer. Technically CapRover can install here, but in practice you'll be swapping the moment you stack a database next to a web app. Fine for one tiny static-ish site or a throwaway experiment, painful for anything real.

1 GiB / 1 vCPU — $6/month

25 GiB SSD, 1,000 GiB transfer. This is roughly the "minimum recommended" tier CapRover's docs hint at. Good for a single small app plus one of the lighter one-click services. If you're just learning CapRover, start here.

👉 Launch a 1 GiB Droplet and install the CapRover 1-Click

2 GiB / 1 vCPU — $12/month

50 GiB SSD, 2,000 GiB transfer. Comfortable for a small portfolio: a couple of web apps, a Postgres or MySQL instance, maybe a WordPress site. The sweet spot for personal projects.

2 GiB / 2 vCPUs — $18/month

60 GiB SSD, 3,000 GiB transfer. Same memory as above but two shared cores, which matters when a build is running at the same time as traffic hits your live app. Good for a small team's staging environment.

4 GiB / 2 vCPUs — $24/month

80 GiB SSD, 4,000 GiB transfer. This is the size DigitalOcean itself uses in its CapRover marketplace API example, and it's the configuration most "I run my side business on this" people land on. Enough headroom for several apps, a database, and a monitoring stack without constant anxiety.

👉 Provision a 4 GiB / 2 vCPU Droplet with CapRover preinstalled

8 GiB / 4 vCPUs — $48/month and up

160 GiB SSD, 5,000 GiB transfer. Once you're here you're running real production load, multiple tenants, or you've started attaching Swarm worker nodes. Above this, the 16 GiB / 8 vCPU at $96/month is the next obvious step before you start thinking about CPU-Optimized or General Purpose droplets for dedicated cores.

For most people reading a "digitalocean caprover" guide, the honest answer is: start at $6, move to $12 the moment you add a database, jump to $24 when something is paying for itself. Per-second billing means the upgrade path costs you almost nothing to test.

How a CapRover deploy actually flows

The part the marketing pages gloss over is what happens under the hood, and it's worth understanding because it's the difference between "it just works" and "it just works until it doesn't."

When you run caprover deploy from the CLI (or trigger the same flow from the dashboard), CapRover detects your source, builds a Docker image, pushes it to its internal registry, schedules the container on the Swarm, wires up the nginx routing for whatever domain you pointed at it, and requests a Let's Encrypt certificate if HTTPS is enabled. The whole thing is one command and a few seconds of output. The first time you watch it happen, the appeal of self-hosted PaaS clicks into place — you get the Heroku-shaped experience without the Heroku-shaped bill scaling.

The catch is that you're still the operator. If the droplet runs out of RAM, the kernel OOM-killer decides what dies, not CapRover. If Let's Encrypt rate-limits you because you redeployed a dozen subdomains in an hour, that's on you. The trade is: less monthly spend, more operational awareness. For the audience that searches "digitalocean caprover," that trade is usually the whole point.

CapRover vs the other self-hosted PaaS options

You'll see Coolify, Dokku, and Dokploy mentioned in the same breath, and they're all worth a look, but the short version:

• Dokku is the minimalist's choice — smaller, leaner, less hand-holding, closer to "git push to a server" with a plugin ecosystem. Great if you enjoy reading docs.

• Coolify has the more polished dashboard and smoother Git-connected builds, scales more comfortably, but uses noticeably more RAM at idle. If your droplet is small, that matters.

• Dokploy leans into the full deployment lifecycle with Nixpacks and Docker Compose support, better for monorepos.

• CapRover sits in the middle: more one-click templates than Coolify, a stable if slightly older-looking dashboard, lower idle footprint, and the most documented "works on a cheap DigitalOcean droplet" path of the bunch.

For someone whose goal is "one-click install on a $6–$24 droplet and stop thinking about it," CapRover is still the most friction-free answer, and the fact that it's the one DigitalOcean chose for its Marketplace tells you something.

Getting your first app live

The flow once your droplet is up:

1. Point a root domain or wildcard subdomain's DNS at your droplet's public IP.

2. SSH in, run the CapRover setup, set a root domain and a dashboard password.

3. Open the dashboard, create a new app, and either pick a one-click template or connect your Git repo / push via CLI.

4. Toggle HTTPS on. Let's Encrypt does the rest.

CapRover's own estimate is that your first deployment is about ten minutes away from a fresh server. That's roughly accurate if your DNS has already propagated; add a coffee break otherwise.

When you're ready to actually do it instead of reading about it:

👉 Create a DigitalOcean account and spin up the CapRover 1-Click App

The takeaway

The "digitalocean caprover" pairing endures for a boring, good reason: it's the cheapest reliable way to get Heroku-style deploys on infrastructure you control, and the one-click marketplace install removes the only part that used to be annoying. Start on a 1 GiB droplet for $6, use the new-user credit to kick the tires for free, and scale up the moment you've got something you'd be sad to lose. The PaaS is free; the server is the only thing you're paying for, and thanks to per-second billing, even that's almost negotiable.