Render alternative for PHP hosting
Created
Reviewedbyfl
🎨
fortrabbit vs Render.
fortrabbit is a Render alternative — a PHP-focused PaaS with native MySQL, EU hosting (AWS Ireland), and predictable per-app pricing.
Why pick fortrabbit over Render for PHP hosting?
fortrabbit is a managed PaaS built exclusively for PHP. Render is a polyglot PaaS with a beautiful UI and reasonable defaults for Node, Python, Go and Docker — PHP works, but as a generic Docker workload, not a first-class environment. Persistent disks are paid-only, build timings can be slow, and pricing leans toward larger apps.
If you're hosting PHP — Laravel, Symfony, Statamic, Craft CMS, Kirby, or plain PHP — fortrabbit gives you the same git-push workflow without the Docker step in the middle. PHP versions, opcache, Composer, atomic deploys, and integrated MySQL just work. Hosting is in EU data centers, and pricing is per-app and predictable. Plans start at €2.50 per month; the trial doesn't require a credit card.
Start a free trial — no credit cardHow does fortrabbit compare to Render?
| Feature | Render | fortrabbit |
|---|---|---|
| Focus | Polyglot, Docker | PHP only |
| Deployment | git + Dockerfile | git push, no Docker |
| Managed MySQL | — | Native |
| Managed Postgres | Yes | — |
| Persistent disks | Paid plans only | Included |
| SSH access | Limited | Full SFTP + SSH |
| Region | US, EU, Asia | EU (Ireland) |
| Pricing model | Per-service hourly | Per-app, monthly |
| Free tier | Cold starts | 7-day trial, no card |
| Support | Community, paid fast | Human chat, all plans |
| Company | Venture-backed | Independent, bootstrapped |
Pricing comparison
| Use case | Render | fortrabbit |
|---|---|---|
| Small site / dev | Starter $7 + DB $7 ≈ $14 / mo | €5 / mo |
| Production app | Standard $25 + DB $20 + disk ≈ $50+ / mo | €30 / mo |
| Scaled app | Pro $85+ DB $90+ ≈ $175+ / mo | €60–€120 / mo depending on tier |
Numbers are illustrative — exact Render pricing varies with region, instance size, and add-on choice. See fortrabbit pricing for the current matrix.
Migrating from Render 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 Render Postgres, plan a schema port; if you brought your own MySQL externally,
mysqldumpand import via fortrabbit's SSH tunnel — see MySQL import guide. - Drop the Dockerfile. fortrabbit deploys PHP source via git push; you don't need to maintain a container image.
- 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. Render env vars map 1:1 to fortrabbit env vars — set in the dashboard or via the CLI.
- Move persistent files. rsync from the Render disk 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 Docker overhead. Push PHP source, not container images.
- PHP-first ergonomics. Composer, OPcache tuning, PHP version pinning, integrated MySQL.
- Predictable bills. Per-app monthly pricing, no per-service stacking.
- Owner-run support. You talk to the engineers who run the platform.
For background on Render itself, see our hosting guide entry.
# Frequently asked
Can I deploy PHP to fortrabbit without a Dockerfile, like Render requires for PHP?Yes
Yes - Push a PHP repo to fortrabbit and Composer runs as part of the build — no Dockerfile in the middle. Render supports PHP as a generic Docker workload, which means a faster cold start of features for languages it treats as first-class, and PHP teams writing their own Dockerfile. fortrabbit treats PHP as first-class out of the box.
#Does fortrabbit charge separately for persistent disk like Render does?No
No - fortrabbit's per-app plan includes persistent storage sized for the app, with the option to scale storage as a separate component if you need more. Render bills persistent disks as a paid add-on on top of the service plan, and the smallest disk has its own monthly cost. For PHP apps that need user uploads or a SQLite database on disk, that adds up.
#How do I move a PHP site from Render to fortrabbit?Self-service
Self-service - Migration is a few steps: push the repo to the new fortrabbit app for git-push deploys, transfer environment variables, and import the database from a dump via the SSH tunnel into the MySQL component. Files on a Render persistent disk move into fortrabbit's persistent storage via rsync. Build time for the same project is usually shorter without the Docker step.
#Is fortrabbit a good Render alternative for EU hosting?Yes
Yes - fortrabbit runs on AWS EU (Ireland) by default and the company is registered in Berlin, so EU jurisdiction is built in rather than a region toggle. Render runs in multiple cloud regions including the EU, but the company is US-based. For projects where the operational entity matters as much as the data center, fortrabbit is the simpler answer.
#Does fortrabbit offer human support like a person to chat with?Yes
Yes - Support is direct chat with the engineers who run the platform, during CET business hours, with a median first response under two hours. There is no phone line and it is not 24/7, but the platform is monitored around the clock.
#