Heroku alternative for PHP hosting
🎸
fortrabbit vs Heroku.
fortrabbit is the modern, PHP-focused Heroku alternative — managed deployments, integrated MySQL, EU data residency, and human support.
Heroku alternative for PHP at a glance
fortrabbit is a managed PaaS built exclusively for PHP. Since 2012 we've been running git-push deployments, integrated MySQL, atomic releases, and zero-downtime restarts for freelancers, agencies, and startups. Heroku invented the modern PaaS but its PHP support has always been bolt-on, and since the Salesforce acquisition the platform has lost focus — free tier gone, prices up, PHP-specific features stagnant.
If you're moving off Heroku for PHP — whether Laravel, Symfony, Statamic, Craft CMS, Kirby, or plain PHP — fortrabbit gives you the same git-push workflow, but with native PHP tuning, an integrated managed MySQL component (Heroku has none), EU data residency, and direct support from the engineers who run the platform. Plans start at €2.50 per month, and pricing scales with app size rather than dyno-hours.
Heroku vs fortrabbit — feature comparison
| Feature | Heroku | fortrabbit |
|---|---|---|
| PHP focus | Polyglot | PHP only |
| Deployment | git push | git push, atomic |
| Managed MySQL | Add-on (JawsDB, ClearDB) | Native |
| Managed Redis | Add-on | Native |
| File storage | S3 add-on | Persistent app storage |
| SSH access | One-off dynos | Full SFTP + SSH |
| Pricing model | Per-dyno, hourly | Per-app, monthly |
| Free tier | Removed 2022 | 30-day trial, no card |
| Support | Tiered, paid for fast | Human chat, all plans |
| Region | US default; EU paid | EU, German data centers |
| Company | Salesforce | Independent, bootstrapped |
Pricing comparison
| Use case | Heroku (Basic dyno + add-ons) | fortrabbit |
|---|---|---|
| Small site / dev | ~$7 dyno + ~$15 DB add-on ≈ $22 / mo | €5 / mo |
| Production app | ~$25 dyno + ~$50 DB + Redis ≈ $80+ / mo | €30 / mo |
| Scaled app | Standard-2X + Premium DB ≈ $200+ / mo | €60–€120 / mo depending on tier |
Numbers are illustrative — exact Heroku pricing varies with region, dyno hours, and add-on choice. See fortrabbit pricing for the current matrix.
Migrating from Heroku to fortrabbit
The move is usually a one-day job for a small app, a weekend for a larger one. Most of the work is data migration; the deployment workflow stays the same.
- 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. Heroku users coming from JawsDB or ClearDB can
mysqldumpthe source database and import via the SSH tunnel — see MySQL import guide. - 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. Heroku config vars map 1:1 to fortrabbit's environment variables — set them in the dashboard or via the CLI.
- Move uploads and assets. If you used Heroku's S3 add-on, rsync (or
aws s3 syncthen upload) the bucket contents into your fortrabbit app's persistent storage via SFTP / SSH — no separate bucket service needed. - Cut over DNS. Add the domain in the fortrabbit dashboard, update the CNAME, and watch the certificate issue automatically via Let's Encrypt.
For framework-specific notes see the install guides — particularly Laravel and Statamic, which are the most common migrations.
Start the migration with a free trial