◆AXIOM

axiom.farm · the managed platform

One open foundation, run as a service.

AXIOM is an open, content-addressed computing stack — OS, toolchain, models, mesh. This host is its commercial surface: hosted inference, the customer console, mesh join, and the public chain tools. It exists to fund the commons, not to own it. Everything it sells also runs on your own machine, for free, with no account.

start here

Sign in
console.axiom.farm

Keys, usage, plan and billing. Sign-in is a passkey, not a password — nothing to phish, nothing to reuse.

Inference API
api.axiom.farm/v1

OpenAI-wire /v1/chat/completions and the typed AXIOM Inference Protocol at /v1/infer: chat, decide, classify, embed, guard, score, predict, rerank. Auth-gated and metered; the machine-readable contract is /openapi.json on the same host.

Documentation
wiki.axiom.farm

The living knowledge base: doctrine, specs, architecture, crate docs — generated from the chain, so it cannot drift from the code.

The project
axiomfarm.org

The manifesto, the stack, the ratchet, the funding model — what AXIOM claims, and the constraints it will not break to get there.

run it locally — no account, no root

Join the mesh
curl -sL axiom.farm/join | bash

A node of your own: ax-netd + avs, a locally generated identity, a verified mesh hop. Prebuilt binaries are signed; the installer refuses anything that does not verify against the pinned key.

Install an OS
axiomfarm.org → downloads

User OS (desktop), Server OS (headless relays), Lab OS (inference + mesh). Source archive and signed release manifests — no package manager, no registry, no account.

Relay directory
axiom.farm/relays.json

The public relay capacity, discoverable by any node. Free at the point of use; every pipe is AX-E2E-v1, so a relay carries ciphertext only.

Health
axiom.farm/health

Machine-readable status of this host. The only endpoint a monitor needs, and deliberately the least informative one.

verify, don't trust

Ratchet
ratchet.axiom.farm

The canonical chain. Every snapshot, every object, every byte — content-addressed under blake3 and verifiable by anyone who loads it.

Kaizen
kaizen.axiom.farm

The upward spiral: forge queue, human-in-the-loop approvals, progress board, mesh health.

Forge
forge.axiom.farm

Multi-model reasoning arena. Several models answer the same question; the best reasoning wins, in the open.

Contribute
contribute.axiom.farm

Submit evidence, not opinions. Proposals are evaluated against current best knowledge. Authority is proof.

A node is not this page.

AXIOM also runs on your own machine, and there the local gateway serves its own front page — the passkey sign-in, the operator UIs, the local setup. That page is deliberately not reachable here: this host is one server of the platform, and it says nothing about yours. Node identity, hostname and local origin are local facts, never published at the root of the internet.

On your own machine the gateway logs its own origin at startup — one ◆ node … → … line carrying a .localhost name that resolves to loopback on that machine, never a public hostname. Open that; it is the only correct address for a node's own front page.

Public, unauthenticated surfaces on this host — and nothing else: /health · /relays.json · /.well-known/security.txt. Everything else under /api/* answers 401 until you present a key.

Found a vulnerability?

The reporting channel isn't printed on this page on purpose. Read it from /.well-known/security.txt (RFC 9116), which is served as served, or fetch it:

curl -s axiom.farm/.well-known/security.txt

A project that asks strangers to run its code has to say where to report a hole in it. Please give us a chance to fix it before you publish.