Documentation
Azoth OS documentation
Azoth sits between your applications and the model providers. Every call answers three questions: who answers for it (the mandate), what it may do and under which law (the rule), and how a third party can check it (the proof).
Mandate · Rule · Proof
Mandate
Who answers for each AI use: systems with a named accountable person, a purpose and an end; agents with versioned mandates; the uses no mandate covers yet.
Rule
What a call may do, checked at the gateway before the model: policy rules, budgets, the applicable law, human approvals, the emergency stop.
Proof
What was decided, sealed in a hash-chained journal, signed in a receipt on every answer that is not streamed, exported as dossiers anyone can verify offline.
Build and run
Quick start
Send your first governed call, keep its receipt, find its sealed decision.
SDK & CLI
The SDK, the CLI with azoth proxy and the commit hook, MCP and the v1 REST API.
Enrichments
Costs and savings, model routing, the semantic cache, prompts, energy, the model catalog, the AI footprint in code.
Integrations
Governance webhooks, Slack, Microsoft Teams, PagerDuty and the GitHub App.
Self-hosted and air-gapped
One image for every deployment, a Helm chart, a signed offline bundle.
Changelog
What changed, release by release.
Need help?
Email hello@azothos.ai. Signed in to Azoth? Help, in your dashboard, answers first and writes to support with your context.