Hosting for vibe coders

Code is cheap. Getting it live is the wall. A designer or a business owner describes what the application should do, an AI writes it, and it runs on a laptop — and then stalls at the gap between "works here" and "has a URL". fortrabbit is built to remove that wall entirely.

Prompt to deploy.

# An absence of ops

Closing that gap normally means a server, a web server, certificates, and a deploy pipeline — none of which the person building wanted to learn. Here it is a git push. Components are booked in a dashboard and scaled with a slider, the runtime is fully managed, and there is nothing to administer. The work stays on the application; the operations disappear.

Every environment answers on a test domain like en-34fdsa.frbit.app, TLS already installed, every request over HTTPS. That is enough to share a link and collect a first reaction the same afternoon. A custom domain, when the project earns one, has its certificate issued and renewed automatically — nothing to configure, nothing to renew by hand.

# A dashboard for the human, a headless interface for the agent

The AI does not need to click through a console, and the person does not need to leave one. fortrabbit publishes open source agent skills↗ — they install locally and let a coding agent connect a project, deploy, sync files, and pull the database straight from a prompt with commands like /fortrabbit deploy. An MCP server, a public API, and a CLI are in the making, launching soon, so every platform action becomes scriptable.

The docs are built for machines as much as people: every article is plain Markdown at a predictable URL, with llms.txt and llms-full.txt aggregated for retrieval. An agent looks up how deployment works and finds a readable answer instead of a search box. The dashboard stays for the human — to watch what shipped, not to babysit it.

# Cheap to abandon, ready to grow

Most experiments go nowhere, and the platform is built for that outcome: a trial app without a payment method deletes itself at the end of the week, and a paid app stops billing the day it is deleted. Nothing runs on in the background.

The few that catch on scale a component at a time on the same host. And when accepting what runs is no longer enough, the same app steps up to agentic engineering — the same deploy, with review and staged releases added around it. No re-platforming, ever.

# Why fortrabbit?

Because the distance between a prompt and a live URL should be a single push — and here it is. No server to meet, no certificate to chase, no bill for a month that an afternoon's experiment never used.