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 / use cases

🔌

One backend, many front ends.

API backend hosting

One PHP service, many clients. The backend answers JSON from one environment; the front ends ship wherever they live — app stores, CDNs, other hosts.

Try for freeSee pricing

Built with

Laravel
Canonical PHP framework by Taylor
Symfony
French PHP framework by Fabien
Tempest
An ORM that embraces modern PHP

All software →

Built by

🚀
Startup
Ship an MVP without a DevOps hire.
🧘🧘🏾🧘‍♂️
Agency
Hosting that maps how agencies work.
🚢
You
See if the fortrabbit platform might be for you.

All solutions →

A PHP service that answers JSON, consumed by clients it doesn't control and can't deploy. No templates, no session cookies — only routes that take a request and return data. Deploys go by git push: the build runs Composer in a separate deploy container, and only a finished package syncs into the web space. Migrations and console commands run over SSH.

Work that isn't a response

Sending mail, generating exports, and calling third parties that time out have no business inside a request. The jobs component runs workers and cron jobs in a container isolated from the web layer, sharing the code base, database, and env vars — a webhook handler that writes a row and returns immediately survives a spike that a synchronous one won't. Jobs scale by memory and job count, separately from PHP.

Persistent connections aren't supported, so APIs that need to push do it by polling or by calling webhooks back out.

Trust

An honest account.

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.

Frequently asked

Can one API serve a website, a mobile app and a SPA at once?
Yes

Yes - That is the usual arrangement. The backend exposes one set of endpoints and stays unaware of who calls them. Clients release on their own schedule — an app store review does not require a deployment here, and a deployment here does not wait for one.

#
Are queue workers and scheduled jobs supported?
Yes

Yes - The jobs component runs worker and cron jobs in a separate runtime container, with access to the same file system, database, and env vars as the web layer. Laravel's `database` queue driver works with the MySQL component out of the box, and `php artisan schedule:run` fires from a cron job every minute. Each deployment restarts running workers, so they always execute the latest code.

#
Does the platform support WebSockets for real-time endpoints?
No

No - Persistent connections are not supported on the platform. APIs that need push semantics can poll, send webhooks out to the client, or delegate that one channel to an external service dedicated to it.

#
How is API versioning handled?
By routing

By routing - Route prefixes and header negotiation are application concerns. For a hard break, run each major version as its own environment — every environment maps to its own Git branch and books its own components, so v1 stays frozen while v2 settles.

#
What does an API backend cost to run?
Per component

Per component - An environment books exactly the components it needs — PHP, MySQL, jobs — and billing is pro-rated, post-paid, on a daily cycle. A small API with a database and one worker starts small and grows one component at a time; there is no jump to a bundled tier. New apps start as a free trial: seven days, no credit card.

#

What customers say

I'd used fortrabbit years ago and liked it, but moved to a VPS, as was all the rage. I've grown tired of thinking about server admin, saw the new platform beta, and gave it a try. Frank and the team have been amazing, and taken my feedback seriously. The component-based pricing is easy to understand and competitive. The dashboard is well thought out, and the platform continues to be built for what I do: PHP, Laravel (Statamic). I'm moving my stuff back, where it always should have been.

Katja P

Katja P

Software Engineer

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

Thanks for the great service, I so prefer this to spinning up my own Linux box every time.

MB

Matt Bloomfield

2025 — Customer support

More →

Docs

Software

Solutions

Use cases

Hosting guide

Company

Legal

Contact us