Pick an archetype.
Directory, CRUD, Marketplace, or Ecommerce (a preset noun/verb set) — or write your own typed Definition.
apps.axthe multi-tenant App interpreter
A directory, a CRUD admin, a marketplace, a store — an App deserves to be DATA when it can be, and secure CODE when it must be. Zero per-face authoring, multi-tenant with zero per-tenant code.
$ curl https://apps.ax/ # apps.ax — write one Definition, get every face **apps.ax is the multi-tenant App interpreter.** ## Mount an App, in three steps 1. Pick an archetype 2. Mount it 3. Ship ## Machine surfaces - docs: https://apps.ax/docs - llms.txt: https://apps.ax/llms.txt
The problem
A page for humans. A markdown face for agents. A REST API. An admin. Standing up an App today means hand-building and wiring all four — separately, each free to drift from the state it describes. Multi-tenant means doing it again per tenant. That is groundhog-day building: the same plumbing re-authored every time, nothing compounds, and every face is a place the truth can diverge.
The answer
So we built the interpreter we wanted: ONE typed Definition — the nouns and verbs of your App — folds into a single read model, and every face is a projection of that SAME model. Never authored twice. One machine already mounts four distinct Apps as data, by hostname (apis.directory, apis.ax, api.lawyer, api.insure) with per-instance themes and zero per-tenant code — live, today.
Two tiers
{Definition, seed, theme} → every face via one render pass. Zero per-face authoring, zero marginal cost — the free optimization, not the limit.
Custom verbs, custom logic, or custom components (npm, React), running securely in their own isolated Worker — first-class, never an escape hatch.
Three steps
Directory, CRUD, Marketplace, or Ecommerce (a preset noun/verb set) — or write your own typed Definition.
The interpreter renders every face by hostname from {Definition, seed, theme}, no build; swap the theme (pure data) to rebrand.
The page face, the agent face, the API face, and the admin face all fall out of one Definition. Climb the customization ladder — defaults → theme → override → custom — only if you need to.
In production
One interpreter Worker mounts four distinct Apps as data, by hostname, zero per-tenant code:
The stakes
Machine access
The machine contract lives at this same URL — curl https://apps.ax/ returns it as markdown. Also published: docs and llms.txt.