Cookies ahead

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

Docs

Examples

These examples show the costs for different real life setups including apps with multiple environments and different software stacks.

Docs

fortrabbit / supported software

from $6.5/mo

©

Symfony hosting

Composer and Git deploys, SSH access, and components that scale on demand.

Symfony is not only a set of PHP components. It's a web application framework, a philosophy and a community — all working together in harmony. The predictable release cycle and the LTS are unique in our fast moving industry.

The fortrabbit hosting environment works smoothly with the Symfony framework and with many Symfony based projects. Installing Symfony on fortrabbit is straightforward: a git push deploys the code, and Composer runs as part of the build. We love it too and use it a lot. Some of our backend services are based on Symfony and API Platform. That's why we can give you good support for it. fortrabbit has a track record for fast, reliable and secure hosting. It's less expensive than some more enterprise solutions.

A deploy is a git push. The build runs composer install --no-dev, then whatever the project declares as build commands — cache:warmup, assets:install, importmap:install on an AssetMapper project, or a Webpack Encore production build where the front end needs one. The finished release is swapped in atomically, so a half-written var/cache never serves a request. A failed build stops before the swap and the previous release keeps running.

Configuration stays out of the repository. APP_ENV, APP_SECRET and the rest are environment variables set in the dashboard, and the platform injects the credentials of the MySQL component, so Doctrine reaches the database without a secret committed to .env. Migrations run over SSH like any other console command. messenger:consume and the Symfony scheduler run on the jobs component as worker or cron jobs, in their own processes, away from the web front-end.

Scaling happens per component. A Symfony API answering JSON has a different shape from a Symfony site rendering Twig with a heavy back office behind it, and PHP, MySQL, jobs and storage are sized separately — each one moves without touching the others. That also keeps the LTS route affordable: an app pinned to an older Symfony release and a matching PHP version costs the same as one tracking the newest.

The Symfony guide in the docs covers the install, the environment variables and the tuning end to end. if something in a specific setup does not line up — the answer comes from people who deploy Symfony here too.

Different by design

Frequently asked

How do I deploy a Symfony app to fortrabbit?
Git push

Git push - Push the repository; the deploy runs Composer, then build steps like cache:clear and assets:install, and swaps in the new release atomically. Set APP_ENV and secrets as env vars in the dashboard. fortrabbit runs Symfony in its own backend, so the setup is well-trodden.

#
Can I host an older or LTS version of Symfony?
Yes

Yes - Symfony's predictable release cycle is one of its strengths, and the composer.json decides the version. Pair an LTS release with a matching PHP version and run it as long as needed; the upgrade happens when it suits the project.

#
Do Messenger workers and the scheduler run here?
Yes

Yes - The Symfony scheduler and messenger:consume run from cron jobs, and full SSH access covers console commands, migrations, and debugging as usual.

#
Can I try Symfony hosting before paying?
Yes

Yes - New apps start as a free trial — seven days, no credit card — enough to deploy a real Symfony project and check the response times.

#
Which database does Symfony use on fortrabbit?
MySQL

MySQL - Add a MySQL component and point Doctrine at it via the database env vars. It is the standard relational database here for a Symfony app.

#
Do AssetMapper and Webpack Encore builds run on deploy?
Both do

Both do - Node is available during the build, so importmap:install for AssetMapper and an Encore production build both run as build commands. The compiled assets ship inside the release, which keeps the swap atomic and the runtime free of a build step.

#
Where do uploaded files go on a Symfony app?
Persistent storage

Persistent storage - The release directory is replaced on every deploy, so anything written at runtime belongs in the mounted storage directory. Point the upload path there — VichUploader, Flysystem or plain move_uploaded_file all work the same way.

#

What customers say

I just wanted to say that the documentation that you guys have and the service you provided me while I was initially setting everything up was probably the best I've encountered in my 20-ish years of front-end web development. Your dashboard is super simple and it has all of the right things for someone like me, and none of the fluff that isn't necessary.

Scott Cooper

Scott Cooper

Front-end developer

2023 — Customer support

As a design and development studio, managing and maintaining servers used to take a big chunk of our time, especially when things went wrong or major updates were needed. Passing that responsibility to fortrabbit, who are absolute experts and have a specialist team, was a game changer. The service is faultlessly stable, support is always fantastic & prompt and it scales with the click of a button. The whole experience is so scarily smooth! The time they have saved us could not be more valuable.

Josh Attwood

Josh Attwood

Creative director at Josh Attwood Studio

2026 — Direct feedback

I've been a fortrabbit customer for seven years, and I continue to appreciate its simplicity and reliability. Deploying Laravel applications is incredibly fast and intuitive: projects are online in just a few steps, without wasting time managing infrastructure. Support is always quick, knowledgeable, and practical. fortrabbit lets me focus on development, knowing everything else is in excellent hands.

AS

Andrea Spotorno

2026 — Direct feedback

More