Core Features

You do not need to learn the framework architecture to start building.

Pick the feature you need right now. Each page shows working code you can paste, explains what you get for free, and links to deeper docs when you are ready.

Data and Entities Define a model, get a full CRUD API with validation, OpenAPI docs, and swappable storage.

Events and the Event Bus User signs up → welcome email + search index + admin notification. One event, zero coupling.

Realtime Push live updates to browsers with SSE, or build chat and collaboration with WebSockets.

Auth Registration, login, JWT sessions, OAuth, MFA, and passkeys. Test with curl in 2 minutes.

Permissions Users edit their own posts. Admins delete anything. One model across routes, entities, and realtime.

Jobs and Orchestration Send emails, process imports, retry API calls, run scheduled tasks — all off the request path.

Build anything

These features compose. A SaaS app uses entities + auth + permissions + events. A chat platform uses WebSockets + events + entities. A content pipeline uses entities + jobs + search. Pick the pieces you need.

You are building…	Start with
A CRUD API	Data and Entities
A SaaS with user accounts	Auth + Data and Entities
A multi-tenant platform	Auth + Permissions + Multi-Tenancy
A chat or collaboration app	Realtime + Auth
A dashboard with live updates	Realtime + Events
A platform with background processing	Jobs + Events
A content or publishing platform	Data and Entities + Events

Or jump straight to a complete example: Examples.

What is stable vs preview

The core framework is the stable foundation:

• defineApp() (with createServer()/createApp() as the imperative APIs) — app assembly
• definePackage(...), domain(...), route.*(...) — package-first authoring
• defineEntity(...), defineOperations(...) — entity system
• Events, WebSockets, SSE — built-in realtime

Feature packages now sit in the non-stable buckets: Experimental, Prod path, and Deferred. Auth stays in the experimental bucket, while permissions and orchestration are on the production-hardening path. They all still sit below the stable core, so check the maturity guide before committing a product surface to one of them.

Read Maturity and Package Status before betting a product surface on one of the non-stable package buckets.

When you want to understand the framework

Once you have a feature working and want to understand how the pieces fit together:

1. Authoring Model — the canonical app → package → entity progression
2. App Roots and Runtime — defineApp, config, context, middleware
3. Package-First Authoring — organizing code into composable packages
4. Entity System — the full entity authoring and customization story