01Axiom documentation

Guides for the release you can explain.

Start with the installed Axiom Agent workflow, then use reference material for setup, readiness, security, and recovery. Documentation distinguishes recorded plans, preview work, and verified provider state.

What this documentation covers

Every product flow answers the same questions: what is happening, why is it needed, what access is required, is it safe, what does Axiom store, can access be revoked, what happens next, what if it fails, how do I fix it. Look for these answers in every guide.

Quickstart checklist

Seven steps from verified installer to a first non-production workflow.

Getting started

Download, authenticate the desktop, configure integrations, and complete a workflow.

AWS setup

IAM role, External ID, read-only validation, region selection.

Security model

What Axiom accesses, what gets stored, what is read-only, how to revoke.

Troubleshooting

Recover from installation, connection, approval, and deployment errors.

Where the platform is right now

GitHub release evidence is the first read-only provider workflow. Cloud-provider setup guides explain the intended permission model, but a provider is not treated as connected until a tenant-scoped live validation succeeds. Azure and GCP remain preview until their inventory and provider paths are implemented and verified. Terraform and CLI artifacts can be reviewed; local Terraform apply remains disabled by the desktop safety contract.

Still blocked?

Include the failed step and error. Never send a password, token, or cloud secret.

Open support request