[ AxiomCore · Documentation ]

AxiomCore documentation

Learn what AxiomCore is, how its parts connect through typed contracts, and where to start.

AxiomCore connects the frontend, backend and database of an application through typed, versioned contracts. A contract describes the operations, data, validation and behavior a consumer can rely on. You can keep a supported backend and frontend, or write your API, UI and database schema in Acore, AxiomCore's declarative language.

How the pieces connect

Acore source or an existing backend becomes a contract that clients, UI, database and tools use
Acore source or an existing backend becomes a contract that clients, UI, database and tools use
Diagram source
flowchart LR
  A[Acore source] --> C[.axiom contract]
  B[Existing FastAPI or Go backend] --> C
  C --> D[Client SDKs]
  C --> E[Acore UI app]
  C --> F[Database migrations and storage]
  C --> G[Axiom Inspector]
  C --> H[Axiom Cloud releases]
  1. Source. Write .acore files, or extract the contract from a FastAPI or Go service.
  2. Contract. The Axiom CLI builds a .axiom contract you can review, diff, test and lock.
  3. Consumers. Web, React, Flutter and Swift clients call the API through generated SDKs. An Acore UI app uses the same contract. Database contracts drive SQLite or PostgreSQL migrations and typed storage.
  4. Tools. Axiom Inspector shows relationships and the impact of a change. Axiom Cloud stores shared releases.

Choose a starting point

Find your way

You want toStart here
Understand the product and its statusWhat is AxiomCore?
Build or connect an APIBuild a backend
Author a UI or use an existing clientBuild a frontend
Define data and change a schemaDatabases
Learn from working applicationsExamples
See what a change affectsAxiom Inspector
Work with an AI coding agentAI coding agents
Look up syntax, errors or limitsReference

Cloud account, project and release workflows are Alpha. Axiom Studio, Acode and Axiom Marketplace are Coming soon.