Axiom Cloud
Accounts, projects, immutable contracts, release evidence, managed sandboxes, and observability.
Axiom Cloud is the connected control plane for artifacts and their operational evidence. It complements local Acore and CLI workflows; it is not required to parse Acore, run local checks, or build an unsigned development artifact.
developer / CI
-> immutable contract upload
-> hash + Cloud signature
-> durable validation, semantic diff, sandbox, tests, policy
-> activation-eligible release
-> versioned latest channel
-> pull by authorized clientsCurrent product boundary
| Capability | Status | Current scope |
|---|---|---|
| Accounts, workspaces, and projects | Alpha | Browser sessions, CLI device login, memberships, invitations, project roles, settings, and keys. |
| Contracts and releases | Alpha | Immutable versions, manifests, verification, semantic diff, durable pipeline evidence, explicit latest channel, activation, and rollback. |
| Managed sandbox and mock | Alpha | Project-scoped synthetic environment lifecycle where the deployment enables managed environments. |
| Contract tests and delivery policy | Alpha | Declared tests against the matching sandbox with persisted results and release-policy outcomes. |
| Runtime observability | Alpha | Scoped OTLP sources, traces, traffic, logs, retention, alerts, and security posture. |
| Contract pull requests | Alpha | Proposals, semantic changes, review comments, and review-state workflow. |
| Hosted CI/CD for every repository | Coming soon | Current release pipelines process Axiom artifacts; they are not a general replacement for arbitrary repository CI. |
| Axiom Studio, Acode, and Marketplace | Coming soon | Planned products, not additional tabs that can be inferred from the Cloud implementation. |
Choose local or connected work
Use local commands for authoring, evaluation, security/domain validation, semantic diff, mocks, and contract tests. Use Cloud when a team needs shared identity, immutable distribution, signing provenance, review records, release channels, managed environments, or retained runtime evidence.
Cloud records are not substitutes for backend authorization or repository review. A signed contract states provenance; a passing contract test states the bounded declared checks passed against the selected environment.
Start
axiom login
axiom project list
axiom project link
axiom build --release --version 1.2.0The CLI resolves the linked project from the current directory. In automation, pass an explicit project and immutable version and retain the resulting release identifier in deployment evidence.