Use cases
Created
Reviewedbyfl
Hosting is bought for a project, not for a platform. These are the project shapes fortrabbit runs, and what each one needs.
📰
Content site
Host a classic server-rendered CMS — WordPress, Kirby, TYPO3.
🚧
Weekend hack
Get the Saturday idea onto a real URL before the weekend ends.
🤖
Agentic engineering
A codebase where an agent does the typing and a developer stays responsible.
🏘️
SaaS app
One codebase, every customer, one place to operate it.
🔌
API backend
Run a JSON API with queue workers and cron jobs behind it.
🛒
E-commerce store
A store where downtime is measured in lost orders.
🧩
Headless CMS
The CMS runs here and serves the API. The front end deploys anywhere.
🖼️
Portfolio
The site that shows the work and wins the next job.
🗄️
Internal tool
20 users, and the business stops when it stops.
🔁
Integration middleware
A PHP service with no users, moving data between machines.
📅
Campaign site
A site with an end date should have a hosting bill with one too.