Open protocol & runtime · Apache-2.0

AI writes the app. ObjectStack is what it writes.

The open target format and runtime for AI-written business apps. Your coding agent writes models, UI, workflows, and permissions as compact typed metadata — a complete CRM is under 2,000 lines, so the whole app fits in the agent's context — and strict TypeScript, Zod schemas, and a validation gate catch its mistakes at authoring time. The runtime derives the database, REST API, UI, and MCP server, and enforces permissions and audit on every call.

Get startedDocumentationGitHub
Fits in an agent's contextTyped, validated, governedSelf-host anywhere

you → claude code

“Build an expense approval app for a 50-person team.”

expense.object.ts

+export const Expense = ObjectSchema.create({
+ name: 'expense_request',
+ fields: {
+ amount: Field.currency({ required: true }),
+ status: Field.select({ options: [...] }),
+ approver: Field.lookup('sys_user'),
+ },
+});
os validatetypes · permissions · flowsos devConsole preview
one definition → tables · REST API · Console UI · MCP tools
01 · The loop

From requirement to running app

01

Create a project

npx create-objectstack my-app

A typed project skeleton — spec, seed data, and the Console already wired.

02

Describe the requirement

claude · os validate ✓

Tell Claude Code what the business needs. It writes compact typed metadata, and the validation gate rejects anything that would fail silently.

03

Preview in the browser

os dev

The Console renders it live — records, boards, dashboards. Requirement changed? Same loop: describe, validate, preview.

02 · The gates

Four gates between the agent and production

01

Typed

Strict TypeScript + Zod — shape errors die in the editor, seconds after the agent writes them.

02

Validated

os validate rejects metadata that would fail silently at runtime — before it ships.

03

Reviewed

You approve a small readable diff in the Console — not fifty thousand lines of glue.

04

Governed

Permissions and audit are enforced by the runtime on every call. Even a wrong app stays inside the fence.

03 · The vocabulary

What can it actually build?

Point an agent at an empty repo and you get a one-off codebase — every screen hand-invented, every mistake yours to find at runtime. ObjectStack gives the agent a vocabulary instead: typed, validated primitives for everything enterprise software needs. The agent composes the definition; the runtime already knows how to run it.

object
Objects & fields — Typed schemas with relations, validation, formulas, and files.
permission
Permissions — RBAC plus row- and field-level security, enforced by the runtime.
flow
Automation — DAG flows, record triggers, scheduled jobs, and webhooks.
approval
Approvals — Multi-step approval chains with queues and a full audit trail.
view
Views — Lists, kanban boards, calendars, gantt, galleries — declared, not coded.
dashboard
Dashboards & reports — Charts, aggregations, and KPIs bound to live data.
action
Actions — Permission-checked buttons and server operations.
api
APIs & SDK — Generated REST and realtime endpoints with a typed client SDK.
mcp
AI tools — Every object and action doubles as a governed MCP tool.
i18n
Translations — Labels and UI text as metadata, per locale.
seed
Seed data — Fixtures and demo datasets that ship with the app.
driver
Datasources — Postgres, MySQL, SQLite, MongoDB, or in-memory.
1,600+ typed schemas5 database drivers7 framework adaptersMCP built-in
Browse the full vocabulary in the docs

Your objects, permissions, and flows are your business ontology — the definition layer of the AI era should be an open protocol you own. Read why

Want it governed and hosted, with Build & Ask AI built in? Try ObjectOS