Describe the workflow. Ship the service.
Mantle turns a YAML Manifest into a typed service. Core compiles your data model and operations into a RuntimePlan; your chosen adapter connects it to storage and exposes supported APIs.
| Atom | Purpose |
|---|---|
| Schema | Stored data, indexes and lifecycle. |
| View | A named read over a Schema. |
| Procedure | Business logic with typed inputs and outputs. |
| Trigger | An entry point to a Procedure: HTTP, MCP or a lifecycle hook. |
Choose your runtime
Mantle runs on Cloudflare, Bun, Vercel Functions and in the browser. Their integrations differ; choosing an adapter does not enable every Mantle feature.
| Host / adapter | Storage | What you get |
|---|---|---|
| Cloudflare Workers | D1 | REST and HTTP Triggers, plus integrations for Admin, Auth, MCP, public web and cache. Optional R2 and Queues. |
| Bun | Your bun:sqlite database | Runtime, REST and HTTP Triggers. Your app owns the server, auth and other integrations. |
| Vercel Functions | An injected storage adapter; optional libSQL / Turso driver | Runtime, REST and HTTP Triggers, with platform waitUntil. Your app owns auth and route composition. |
| Browser / IndexedDB | An application-owned browser database | Direct runtime calls for local apps and previews. No mounted HTTP, Admin, Auth or MCP endpoints; SQL Views are unsupported. Sync is application-owned. |
Core shares the Manifest model and execution pipeline across these adapters. Check the capability matrix and setup examples before choosing a host. The Worker quickstart below follows the Cloudflare path.
Start building
- With code: Run a minimal Worker, then follow the project layout and CLI loop.
- With an agent: Design and preview in Builder, then download a handoff ZIP for your coding agent.
You own the project files and manifests/. mantle generate compiles existing manifests; it does not scaffold a project or fetch a Starter.
Find the details
| Need | Read |
|---|---|
| Model a workflow | The four atoms, reads, writes and hooks |
| Control access | Authorization, MCP and agents |
| Ship on Cloudflare | Worker composition, authentication, deploy and operate |
| Build public pages | Templates, SEO and cache |
| Follow an example | Intake, publication, reservation, commerce |
| Look up syntax or APIs | Manifest reference, HTTP, MCP, CLI and packages |
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. |
| Blog | mantle-web composes content and SEO; the site's templates render HTML on request using the shared Hono JSX shell. |
| Interactive Builder and Admin preview | React loads when needed. Builder projects and preview data stay in browser IndexedDB. |
| 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 cover an unreleased development snapshot. The site's SDK is source-packed from Core 3ed5b7f, retaining the 0.1.0-alpha.17 label; it is not the npm alpha.17 release artifact. The footer links to the pinned handbook revision. Use version-matched guidance for npm installs.
Every page has a Markdown mirror, including this page. Agents can start from the documentation index.