// Migration Guide · 2026
Migrate from CapRover to Runsite
CapRover gives you a self-hosted PaaS on Docker Swarm — and the duty to keep that Swarm healthy. Runsite runs the same Docker-based apps fully managed in Frankfurt, with no instance to maintain.
- ~15 min
- typical migration
- No Swarm to maintain
- keep your workflow
- Keep CapRover running
- until you cut over
// the mental model
Every CapRover concept has a Runsite home
CapRover deploys from a captain-definition (a Dockerfile pointer) onto your own server. Runsite builds the same container for you, removing the Swarm and host upkeep.
{
"schemaVersion": 2,
"dockerfilePath": "./Dockerfile"
}- →captain-definitioncaproverWeb service from your Dockerfile autoRunsite builds the same container — no Swarm runner
- →One-click app: PostgrescaproverManaged PostgreSQL you doReplace the self-managed app with managed Postgres
- →One-click app: RediscaproverManaged Redis you doReplace with a managed Redis instance
- →Docker Swarm hostcaproverFully managed infra autoNo Swarm health, no host patching, no backups to script
- →App environment varscaproverEnvironment variables autoNon-secret vars imported; secrets pasted once
// step by step
From CapRover to live in the EU
Six steps. Most of them take seconds. CapRover keeps serving traffic until you flip your DNS.
- 1
Create a Runsite project
~30 secSign in at runsite.app and create an empty project. No credit card, no sales call.
- 2
Connect your Git repo
GitHub · GitLab · BitbucketAuthorize GitHub, GitLab or Bitbucket. Runsite scans the selected branch for your captain-definition and detects the stack automatically.
- 3
Review the detected setup
Full preview before provisioningRunsite lists every service, database and env var it found and how each maps onto a Runsite resource. Tweak build or start commands inline. Nothing is created yet.
- 4
Provision in Frankfurt
One click · eu-centralCreate the whole stack in one step. Cross-resource env vars are wired up for you, and you get fresh database and Redis credentials in the EU.
- 5
Drop in your secrets
Secrets stay out of GitSecret values are never read from your repo. Paste API keys and tokens once in the dashboard; they're encrypted at rest and never logged.
- 6
Push to go live
Live in < 2 mingit push and your app builds and deploys in the EU in under two minutes. Point your custom domain when ready. CapRover keeps running until you cut over.
// no surprises
What moves on its own — and what you touch
Honest about the boundaries. The supported stack is recreated in one click; a short list needs a human, and Runsite flags every item.
Imported automatically
- ✓ Container builds from your Dockerfile
- ✓ Ports and health checks
- ✓ Non-secret environment variables
- ✓ Auto-deploy on git push
You handle once
- → One-click database apps — move to managed PostgreSQL
- → One-click Redis — move to managed Redis
- → Persistent volumes — confirm size & mount after import
- → Secret environment variables — paste once after import
// caprover problems → runsite solutions
Common CapRover frustrations — sound familiar?
Every CapRover frustration, solved.
CapRover problem
"My CapRover main node crashed"
CapRover's main node holds all SSL certs and config. If it goes down, every app behind it goes offline.
Runsite solution
No single point of failure
Managed multi-node infrastructure with auto-failover. Your apps stay online even when individual nodes fail.
CapRover problem
"One-click apps are outdated"
Many CapRover marketplace apps haven't been updated in months. You inherit unmaintained Docker images.
Runsite solution
Deploy from your own Git repo
Push your code, we build and deploy it. No dependency on community-maintained templates.
CapRover problem
"I need a VPS just to run CapRover"
Before deploying anything, you need a VPS, Docker, CapRover CLI, DNS setup, and SSL configuration.
Runsite solution
No VPS, no setup
Connect your GitHub repo, pick a region, deploy. Two minutes, zero infrastructure setup.
// comparison
Runsite vs CapRover
Side-by-side. No marketing fluff — just facts.
| Feature | Runsite | CapRover |
|---|---|---|
| Server Management | ✓ Fully managed | ✗ You manage the VPS |
| Setup Time | ✓ 2 minutes | 30-60 min (VPS + Docker + CapRover) |
| High Availability | ✓ Multi-node, auto-failover | ✗ Main node = single point of failure |
| GDPR Compliance | ✓ EU entity, full compliance | Depends on your VPS provider |
| Managed PostgreSQL | ✓ From €5/mo, auto-backups | One-click app, you manage backups |
| Web Dashboard | ✓ | ✓ Full web UI |
| One-Click Apps | Templates available | ✓ Large marketplace |
| Cost (small apps) | €5/mo | VPS $5-10/mo + your time |
// migration questions
Migrating from CapRover, answered
Do I have to maintain Docker Swarm with Runsite?
No. CapRover runs on a Docker Swarm host you keep healthy yourself. Runsite is fully managed — there is no Swarm to monitor, no host to patch and no backups to script.
Can Runsite build my captain-definition app?
Yes. Your captain-definition points at a Dockerfile, and Runsite builds that same Dockerfile, so your container deploys without changes.
What about CapRover one-click databases?
Replace CapRover's one-click Postgres and Redis apps with Runsite's managed PostgreSQL and Redis in Frankfurt. Export your data and import it once; connection strings are auto-wired.
Is migrating from CapRover risky?
No. Your CapRover instance keeps running while you verify on Runsite, then you cut over with DNS — and you remove the risk of a self-hosted server going down.
Why migrate from CapRover to Runsite?
You keep Docker-based deploys but drop self-hosting, gaining an EU Frankfurt region for GDPR, predictable EUR pricing with hard spending caps and a permanent free tier.
Leave CapRover behind
Bring your captain-definition. We'll handle the rest — in Frankfurt.
Start your migration →