Describe the workflow. Ship the service.
Mantle compiles YAML manifests into native SQL and typed TypeScript for SQLite/D1 and PostgreSQL. Applications own routing, identity and migrations, and compose REST, MCP, web pages and Admin around the generated operations.
| Atom | Purpose |
|---|---|
| Schema | Stored rows, scope, indexes and lifecycle. |
| View | One SQL SELECT over declared Schemas. |
| Procedure | Business logic with typed inputs and outputs, as SQL or a handler. |
| Trigger | HTTP or MCP exposure of a Procedure. Schedules and lifecycle hooks stay in app code. |
Start building
- With an agent: Build with an agent (
mantle init, thenmantle help), or design in Builder (WebMCP, or a ChatGPT Codex deeplink). - API only: Run the minimal Worker reference.
You own the project files, manifests and service entry. mantle generate produces the target SQL and typed bindings; the application composes and deploys the service.
Find the details
| Need | Read |
|---|---|
| Model a workflow | The four atoms, reads, writes and hooks |
| Control access | Authorization, MCP and agents |
| Ship on Cloudflare | The service and its entry, authentication, deploy and operate |
| Follow an example | Examples |
| Look up syntax or APIs | Manifest reference, HTTP, MCP and Admin surfaces |
The sidebar contains the full handbook.
How mantle-home is built
This site combines renderers according to the page's needs:
| Surface | Rendering |
|---|---|
| Homepage and Builder shell | Hono JSX generates HTML at build time. |
| Interactive Builder | React loads when needed. Builder projects stay in browser IndexedDB until saved to Mantle Cloud. |
| Documentation | VitePress generates static pages from the Core handbook and this site's introduction. |
Hono JSX keeps the public shell renderable without loading the editor; React handles the interactive workspace. Shared styles and header/footer components keep them consistent. Kiwa supplied some copied components, not the site's runtime framework.
These are mantle-home's choices. Mantle Core does not require Hono JSX, React or VitePress; your application owns its frontend and templates.
Versions and agent access
These docs are the handbook shipped inside @aotter/mantle 0.2.0, the Core version pinned in apps/web/core.json; the footer links to its source commit. A project should read the copy in its own node_modules/@aotter/mantle/docs/, which matches the version it installs (agent setup).
Every page has a Markdown mirror, including this page. Agents can start from the documentation index.