// Migration Guide · 2026
Migrate from Coolify to Runsite
Coolify is self-hosted PaaS — powerful, but you babysit the underlying server, updates and backups. Runsite gives you the same Docker-based deploys fully managed in Frankfurt, so there's no VPS to maintain.
- ~15 min
- typical migration
- No server to babysit
- keep your workflow
- Keep Coolify running
- until you cut over
// the mental model
Every Coolify concept has a Runsite home
Coolify deploys from a Dockerfile or docker-compose on your own server. Runsite runs the same containers managed for you, so the ops burden disappears.
services:
app:
build: .
ports:
- "3000:3000"
environment:
- DATABASE_URL=${DATABASE_URL}
db:
image: postgres:16
cache:
image: redis:7- →Dockerfile / compose buildcoolifyWeb service from your repo autoRunsite builds your container — no self-hosted runner
- →compose postgres servicecoolifyManaged PostgreSQL you doReplace the self-managed container with managed Postgres 16
- →compose redis servicecoolifyManaged Redis you doReplace the container with a managed Redis instance
- →Server / VPS upkeepcoolifyFully managed infra autoNo OS patching, no Docker upkeep, no backup scripts
- →Environment variablescoolifyEnvironment variables autoNon-secret vars imported; secrets pasted once
// step by step
From Coolify to live in the EU
Six steps. Most of them take seconds. Coolify 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 docker-compose.yml 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. Coolify 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 Dockerfile or compose
- ✓ Ports and health checks
- ✓ Non-secret environment variables
- ✓ Auto-deploy on git push
You handle once
- → Database containers — move to managed PostgreSQL
- → Redis containers — move to managed Redis
- → Persistent volumes — confirm size & mount after import
- → Secret environment variables — paste once after import
// coolify problems → runsite solutions
Common Coolify frustrations — sound familiar?
Every Coolify frustration, solved.
Coolify problem
"I spend hours maintaining the server"
Coolify runs on your VPS. You're responsible for OS updates, security patches, backups, and uptime.
Runsite solution
Fully managed infrastructure
99.9% uptime SLA. Auto-updates. Automated backups. Focus on building, not maintaining.
Coolify problem
"Setup took an hour"
Provision a VPS, install Docker, install Coolify, configure DNS, set up SSL — before deploying anything.
Runsite solution
Deploy in 2 minutes
Connect GitHub. Pick a region. Deploy. SSL and DNS handled automatically.
Coolify problem
"My Coolify server went down at 3am"
Self-hosted means self-monitored. Server crashes, disk full, or OOM — it's your problem.
Runsite solution
24/7 monitoring + auto-recovery
We monitor, restart, and scale your apps. You sleep through the night.
// comparison
Runsite vs Coolify
Side-by-side. No marketing fluff — just facts.
| Feature | Runsite | Coolify |
|---|---|---|
| Server Management | ✓ Fully managed | ✗ Self-hosted, you manage |
| Setup Time | ✓ 2 minutes | 30-60 min (VPS + install) |
| Uptime & Maintenance | ✓ 99.9% SLA, auto-updates | You handle updates & backups |
| GDPR Compliance | ✓ EU entity | Depends on your VPS provider |
| Cost (small apps) | €5/mo | VPS $5-10/mo + time |
| Cost (large scale) | Usage-based pricing | ✓ Cheaper at scale |
| Open Source | Closed source | ✓ Fully open source |
// migration questions
Migrating from Coolify, answered
Do I still need to maintain a server with Runsite?
No. Coolify runs on a VPS you patch, update and back up yourself. Runsite is fully managed — there is no operating system to maintain, no Docker daemon to upgrade and no backup scripts to write.
Can Runsite build my existing Dockerfile?
Yes. Runsite builds directly from your Dockerfile or docker-compose, the same artifacts Coolify uses, so you don't rewrite anything to deploy.
What happens to my database and Redis containers?
Replace the self-managed Postgres and Redis containers with Runsite's managed PostgreSQL and Redis in Frankfurt. Export your data and import it once; the connection strings are auto-wired.
Is migrating from Coolify risky?
No. Your Coolify instance keeps running while you verify on Runsite, then you cut over with DNS. Because Runsite is managed, you also remove the risk of a self-hosted server going down.
Why move from Coolify to Runsite?
You keep Coolify's Docker-based simplicity but drop the self-hosting burden, gain an EU Frankfurt region with GDPR compliance, predictable EUR pricing, hard spending caps and a permanent free tier.
Leave Coolify behind
Bring your docker-compose.yml. We'll handle the rest — in Frankfurt.
Start your migration →