Fly.io alternative for PHP hosting
✈️
fortrabbit vs Fly.io.
fortrabbit is a Fly.io alternative — a managed PHP PaaS without the CLI-and-Docker overhead, with native MySQL and persistent storage.
Fly.io alternative for PHP at a glance
fortrabbit is a managed PaaS built exclusively for PHP. Fly.io runs Firecracker microVMs in regions around the world — powerful infrastructure if you need global edge distribution, but everything is configured through the flyctl CLI and a Dockerfile you maintain. For most PHP teams, that's lower-level than they want.
If you don't need a global edge fleet — most PHP sites and applications don't — fortrabbit gives you the upper layer of abstraction: git push deploys, atomic releases, integrated MySQL, PHP-tuned runtime defaults (opcache, version pinning, Composer), and a dashboard instead of a CLI. Hosting is in EU data centers; support comes from the engineers who run the platform. Plans start at €2.50 per month; the trial doesn't require a credit card.
Fly.io vs fortrabbit — feature comparison
| Feature | Fly.io | fortrabbit |
|---|---|---|
| Focus | Polyglot, microVMs | PHP only |
| Abstraction | Dockerfile required | Push PHP source |
| Deployment | flyctl, Dockerfile | git push, atomic |
| Managed MySQL | — | Native |
| Managed Postgres | Yes | — |
| Edge regions | 30+ worldwide | EU (Germany) |
| SSH access | flyctl ssh, ephemeral | Full SFTP + SSH |
| Pricing model | Per-machine + bandwidth | Per-app, monthly |
| Free tier | Limited allowance | 30-day trial, no card |
| Support | Community, paid fast | Human chat, all plans |
| Company | Venture-backed | Independent, bootstrapped |
Pricing comparison
| Use case | Fly.io | fortrabbit |
|---|---|---|
| Small site / dev | shared-cpu-1x + small Postgres ≈ $5–$10 / mo | €5 / mo |
| Production app | dedicated 2x + Postgres + bandwidth ≈ $50+ / mo | €30 / mo |
| Scaled app | Multi-region machines + DB ≈ $150+ / mo | €60–€120 / mo depending on tier |
Numbers are illustrative — exact Fly.io pricing varies with machine size, region count, and egress. See fortrabbit pricing for the current matrix.
Migrating from Fly.io to fortrabbit
- Provision the app on fortrabbit. Pick a region (EU) and a plan. The free trial is enough to validate the move.
- Add the MySQL component. If you were on Fly Postgres, plan a schema port; if you brought your own MySQL,
mysqldumpand import via fortrabbit's SSH tunnel — see MySQL import guide. - Drop the Dockerfile and fly.toml. fortrabbit deploys PHP source via git push; no container image or app config file to maintain.
- Connect your git provider. Install the fortrabbit GitHub App (or connect GitLab / Bitbucket) and link your existing repo to the new fortrabbit app — see deployment intro. Pushes to your branch trigger an automatic deploy; Composer install runs as part of it.
- Move environment variables and secrets.
flyctl secrets list→ fortrabbit env vars. Set in the dashboard or via the CLI. - Move persistent volumes. rsync from Fly volumes into your fortrabbit app's persistent storage via SFTP / SSH.
- Cut over DNS. Add the domain in the fortrabbit dashboard, update the CNAME, and watch the certificate issue automatically via Let's Encrypt.
Why teams switch
- No Dockerfile, no flyctl. Push PHP source, use a dashboard.
- PHP-first ergonomics. Composer, OPcache, version pinning, integrated MySQL — all defaults.
- Predictable bills. Per-app monthly pricing, no per-machine or egress surprises.
- Owner-run support. You talk to the engineers who run the platform.
For background on Fly.io itself, see our hosting guide entry.
Start a free trial — no credit card