🤖
It writes. It ships.
Hosting for agentic engineers
Orchestrate the agents. Host it on fortrabbit.
Built with
Built by
Built what
Your agent writes the code and ships it through fortrabbit. You describe the intent, it edits the codebase, the tests run, and you review and deploy. What comes out is an ordinary Laravel or Symfony project. What changed is how fast the loop around it turns.
Agent interfaces
The open source agent skills install locally and turn platform operations into prompts: /fortrabbit deploy, db down and ssh run deployments, database syncs and remote commands over plain SSH and rsync. Your agent tails the PHP, Apache and job logs the same way, so it quotes the failing line instead of asking you to go look.
The MCP server hands over the platform objects themselves — apps, environments, deployments, domains, variables. You authorize it in the browser, with no token pasted into a config file.
The public API is the same surface over REST for everything that is not an agent.
The CLI wraps it in one binary for your terminal or a CI job. Run one agent or a fleet; none of these interfaces assume a human is holding them.
Accessible docs
Your agent needs to know how deployment works, or why a build failed. It reads. Documentation wrapped in a JavaScript app behind a search box is close to unusable for that. Plain Markdown at a predictable URL works. Every docs article ships as raw Markdown, plus llms.txt and llms-full.txt for retrieval — a structured index and the whole docs in one file, regenerated on every deploy. Point your pipeline at them.
