The whole stack, honestly.

Status

One line on where FrontierJS stands: pre-alpha, what is solid, what may still move. Then a maturity badge per package below, read from data rather than written here.

Every package

• Litestone Data · Model

  Authorization is part of the data definition, not a layer above it.

• Junction API · Service

  Name a model and its CRUD, validation and authorization come with it.

• Auth API · Identity

  A route establishes a session. Everything after it is an ordinary service.

• Caravan API · Jobs

  Background work in the database you already have. No second service to run.

• Conduit API · Integrations

  Every third party an app talks to, declared in one place.

• Notifications API · Slice

  One call fans out to a record, a live event and an email.

• MCP API · Agent

  An MCP endpoint over the app you are already running, with the gate as the permission model.

• Orion API · Automations

  Automations that run inside your app, against your schema, refused by your gates.

• Sierra UI · Resource

  Your file tree is the route table. A Resource is a service, made reactive.

• Mesa UI · Component

  One file renders to a page, an email, a fragment or a module. Zero dependencies.

• The component kit UI · Kit

  Sixty-odd components over the design system. A form that already knows what it is editing.

• The design system UI · Style

  Thirty-five semantic terms. Plain CSS, no build step. This site is styled by it.

• Email kit UI · Email

  An email is a component. The same language, compiled for a worse renderer.

• Print kit UI · Print

  A document to a PDF, an element to a PNG, in one headless Chrome.

• Jetty UI · Extension

  A browser extension as a surface of the app, not a second app.

• Toolbelt Substrate

  The facts that have many possible answers and must have exactly one.

• Testing Testing · Suite

  A real app, a real database, a real port when you want one. Stub nothing but the clock.

• fli Tooling

  Every command is a markdown file. Help text and implementation cannot disagree.

• create-frontier Tooling

  The front door, and nothing else — it resolves the CLI and runs it.

• The tooling opinion Tooling

  tsconfig, biome and editorconfig as a dependency — never as a copy.

• Basecamp Control plane

  The app for managing your apps — and itself a FrontierJS app.

• Editor support Tooling

  The seed is as pleasant to write as the code it produces.

• Outpost Ops · Fleet

  The process on the machine. A control plane’s hands, with a signature on every one of them.

How they fit

The dependency direction, Litestone to Junction to Sierra, drawn once.

From: The map · The stack