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.
Why move from Heroku to fortrabbit for PHP?
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.
Start a free trial — no credit card# FAQ
How do I migrate my Laravel app from Heroku to fortrabbit?
Most Laravel migrations off Heroku take a day. Set up the fortrabbit app, add a MySQL component, dump and import your JawsDB or ClearDB database via the SSH tunnel, copy your Heroku config vars over as environment variables, and re-point your repo at the fortrabbit app for git-push deploys. Uploaded files in an S3 add-on get rsynced into the app's persistent storage — no separate bucket service to wire up.
#Why is fortrabbit cheaper than Heroku for a small PHP app?
Heroku bills you per dyno-hour, with the managed database and Redis as separate add-ons that each carry their own monthly minimum. A small PHP app on Heroku quickly lands at $20-25 a month before traffic. The same app on fortrabbit is a single per-app plan with the MySQL component included, starting at roughly €5 a month. There are no usage meters in the middle and no surprise bill at the end of the month.
#Does fortrabbit support Heroku-style buildpacks for PHP?
No, and that is intentional. fortrabbit runs your PHP code directly with Composer at build time — no buildpack indirection, no proprietary install layer between your repo and the deployed app. PHP version, extensions, opcache, and Composer cache are configurable per environment via the dashboard, not by editing a buildpack URL.
#How is fortrabbit's PHP support different from Heroku's?
Heroku is a polyglot PaaS — PHP is one supported language among many, and the runtime defaults reflect that. fortrabbit has only ever hosted PHP, since 2012. PHP version pinning, opcache tuning, MySQL integration, and Composer behavior are the platform's main concerns. When you open a support chat about a PHP-specific issue, you reach engineers who think about PHP all day.
#