| What you control | A server in your own account, in the region you pick: your languages, your database, workers and cron jobs side by side. | What the platform offers: its runtimes, its add-ons and its regions. |
|---|
| Leaving later | Everything is a plain file in your repository: infrastructure code, workflows and a runbook. Delete OpsCrew and the deployment keeps working, and OpsCrew can move a live app to another provider with its data. | Your code usually moves easily. The platform’s own settings, functions and add-ons are what you rebuild elsewhere. |
|---|
| Your effort | About ten minutes to set up, plus your review. After that, each change is a pull request or a plan you approve, and the server installs security updates by itself. | Connect the repository and push. The platform runs and patches the servers for you. |
|---|
| Security | OpsCrew hardens the server (key-only SSH, a firewall, fail2ban) and checks it again whenever you ask. The account and its keys are yours to guard. | The platform secures and patches its machines. Your app, its settings and its secrets stay yours to get right. |
|---|
| Growing | Your app runs on one server per environment, and a service can get a server of its own. A bigger server is a plan you approve. Nothing scales out on its own. | More instances with a setting, and on some plans automatically. |
|---|
| Database backups | Hetzner’s and DigitalOcean (opens in a new tab)’s server backups, at their price. On a server you already have, backups are yours to set up. | Depends on the database plan you pick. |
|---|
| Help when stuck | The docs, GitHub (opens in a new tab) issues, and your provider’s support for the server. OpsCrew is open source and in alpha. | The platform’s own support, with paid tiers and, on some plans, an SLA. |
|---|