Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

Render alternative for PHP hosting

Created

Reviewedbyfl

Markdown ↓

🎨

fortrabbit vs Render.

fortrabbit is a Render alternative — a PHP-focused PaaS with native MySQL, EU data residency, 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 card

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 response around an hour. There is no phone line and it is not 24/7, but the platform is monitored around the clock.

#

Different by design

A platform purpose-built for PHP. More than the sum of its parts.

Pay in arrears

Daily prorated, post-paid billing. No upfront payment, no yearly commitment.

Modular pricing

Pay per component and scale each one from xs to 2xl on its own.

No dark patterns

No vendor lock-in, no upselling, no misleading messages.

Humans in support

Eye-level developer chat over the support bubble. No sales calls.

Developer-first

Git-push deploy, SSH access, bring your own code. No 1-click bloat.

Managed platform

A hardened, service-oriented PHP stack. Deploy code, skip the server admin.