Developer docs
An agent-first framework for full-stack apps.
A project is a folder of plain files: paths become routes, SQL becomes schema, one TOML file declares the rest. The same contract is legible to you, to the deploy validator, and to any AI agent you connect. Hand-write a repo and import it, or build through an agent. The framework reads both the same.
Project structure
What a project is: the file tree, routing, and a complete app in four files. Start here.
Rules & restrictions
The sandbox contract, hard caps, and everything the deploy validator rejects, with the supported alternative for each.
hatchable.toml
Auth, cron, secrets, external APIs, buyer-editable config, MCP tools. Every block, every field, every validation rule.
SDK reference
One namespace for database, identity, AI, storage, email, scheduling, browser, and knowledge bases.
Secrets & BYOK
Declared keys stay server-side by design. Tenancies, the provider catalog, and the security model.
Import, deploy & export
Bring any repo as a zip or GitHub URL, understand drafts and promotion, leave with your source and data.
MCP
Connect Claude, ChatGPT, Cursor and others to the 32-tool surface, and expose your own app's tools to its users' agents.