Web app hosting

Ship the app, not the server. Shipping a product is hard enough without becoming a sysadmin on the side. fortrabbit runs the platform so the work stays on the application — the one part that is actually the business.

# No DevOps hire required

A small team cannot spare a person to patch servers, wire up a deploy pipeline, and chase certificates. None of that exists to do here: connect a Git repository, push, and the app is live over HTTPS. The operating system, the web server, scaling, and TLS are handled. What remains is the code and the database.

# The chores that are not requests run in workers

Trial expiry, usage metering, invoice runs, imports, dunning mail — the machinery behind a web app happens on a schedule, and none of it belongs inside a web request. The jobs component runs real cron jobs and long-running queue workers next to the web processes, on the same code and the same environment. Laravel Cashier and Symfony Messenger drop straight in, and a billing run that takes 20 minutes takes 20 minutes in a worker, with nothing timing out.

# Pay as it grows, not per seat

Cost follows load and data, not the number of accounts — the first customers run for cents a day. Components are booked individually and billed pro-rated by the day, so PHP can scale ahead of the database, or the reverse, without jumping to the next bundled tier. Customer 500 usually needs more PHP processes and nothing else: scale that one component and keep going, same app, same host.

# Why fortrabbit?

Because we run one. fortrabbit is a bootstrapped subscription business that has been running on AWS since 2012 with no VC money behind it — roughly the position most founders reading this are in. Spend the runway on the product: start on a free trial, deploy with a push, and let the platform be the DevOps team the company hasn't hired yet.