Software built around contracts
Build, connect, test, and evolve software through typed, auditable contracts.
AxiomCore is a contract platform for describing and connecting software across backend services, user interfaces, runtimes, tests, security policy, packages, and delivery workflows. Its authoring language is Acore.
You can adopt the platform incrementally. A Python or Go service can remain imperative. A Flutter, web, or Swift application can remain in its native framework. AxiomCore provides the versioned contract boundary between those parts—and Acore can also describe more of the application when that is useful.
Choose your path
Understand AxiomCore
See how contracts connect source, artifacts, runtimes, packages, and cloud workflows.
Learn Acore
Learn what the language describes, how composition works, and where its boundary ends.
Build your first contract
Install the CLI and follow the current local development path.
Adopt in an existing system
Follow end-to-end guides for incremental adoption, CI, and release readiness.
Browse platform capabilities
Separate what is available now from alpha, experimental, and coming-soon work.
One contract path, multiple adoption models
existing source or Acore modules
│
▼
extract + evaluate
│
▼
versioned .axiom packages ───► diff, test, mock, audit
│
├───────────────► native framework clients
│
└───────────────► Acore UI + .axiomappThe platform does not require a single language or framework on both sides of the contract. Start at the boundary that reduces the most integration risk for your team.
What exists today
| Capability | Status | Current scope |
|---|---|---|
| Acore language and tooling | Alpha | Independent parser, evaluator, standard library, language server, and contract-oriented authoring. |
| Contract and package lifecycle | Alpha | Canonical .axiom packages, locks, semantic diffing, local tests, mocks, and runtime consumption. |
| Backend integration | Available | FastAPI is the primary path; Go is alpha. OpenAPI and SQL currently provide bounded domain bootstrap workflows. |
| Frontend and UI | Alpha | Vanilla web, React, Flutter, Swift distribution, and Acore-authored UI have different maturity boundaries. |
| Cloud control plane | Alpha | Implemented account, project, and release workflows. Broader collaboration and automation remain in development. |
| Studio, Acode, and Marketplace | Coming soon | Planned product experiences; they are not installable or supported workflows today. |