Installation
Getting AXON
axon-lang is licensed commercially — it is neither open source nor open core, and there is no public package to install. Access to the compiler goes through sales:
Contact SalesOpens a WhatsApp chat with sales.
What you get is one binary, axon. The rest of this page is what it needs from
the host and what its optional features cost.
Prerequisites
| Requirement | Why |
|---|---|
| Rust 1.95+ | The rust-version in every manifest. An older toolchain fails with an MSRV error, not a compile error. |
| A working C compiler (MSVC / clang / gcc) | ring — reached through rustls, which is how this compiler speaks HTTPS to every model provider — compiles C unconditionally in its build script. On Windows the MSVC Build Tools suffice; on Debian or Ubuntu, build-essential. |
These are checked at build time, not install time. If cargo install stops
with a cc or linker error rather than a Rust error, the C toolchain is what is
missing.
Features
The default install is the compiler and the governance CLI — check, compile,
run, dossier, sbom, audit, pcc prove, pcc verify — and it adds no
dependencies beyond that. Everything heavier is opt-in:
| Feature | What it turns on | What it costs |
|---|---|---|
cli (default) | the compiler + governance surface | — |
server | the HTTP / SSE / NDJSON / WebSocket server, and the axon-server binary | the axum service stack |
postgres | the axonstore data plane against real PostgreSQL | ~36 crates — the single largest lever on install time |
documents | the OOXML surface and axon evidence-package | pure-Rust compression |
csys-native | the C23 kernels: exact BPE token counts, the crypto boundary | needs a C toolchain |
Leaving csys-native off is bounded and labelled, not silent: count_tokens
returns an estimate instead of an exact BPE count, and mandate drops its
Tier 1 logit-bias bans — while Tier 2, the refinement loop that is the
guarantee, is untouched.
Verify the install
axon --version
axon check app.axon
Both axon --version and axon version print the same string.