Axiom Cloud

What the Axiom Cloud dashboard and API do today, what is Coming soon, and how workspaces, projects, releases, environments, secrets and resources fit together.

Axiom Cloud is the hosted control plane for your contracts and their operational evidence. It has two surfaces: the Cloud Dashboard in the browser, and the API that the Axiom CLI calls for axiom login, axiom project, axiom release, axiom pull and axiom deploy.

Cloud is optional. You do not need it to write Acore, run local checks or build an unsigned development artifact.

How Cloud is organized

How Axiom Cloud organizes workspaces, projects and their records

A workspace groups members and projects. A project owns everything else: immutable contract releases, the latest channel that consumers pull from, contract pull requests, a managed sandbox for tests, and observability data. A project environment (such as development, staging or production) is a separate configuration scope. Secrets, a managed database and its application authentication issuer attach to one environment.

What Cloud does today

Axiom Cloud signup is invite-only. Managed database and authentication features marked Alpha below are available to invited accounts, and new managed databases are limited to admitted projects. See the support matrix for each engine.

Capability	Status	Scope
Accounts, workspaces and projects	Alpha	Browser sessions, CLI device login, memberships, invitations, project roles, settings and signing keys.
Contracts and releases	Alpha	Immutable versions, manifests, verification, semantic diff, durable pipeline evidence, an explicit `latest` channel, activation and rollback.
Contract pull requests	Alpha	Proposals, semantic changes, review comments and review states.
Managed sandbox and mock	Alpha	A project-scoped synthetic environment, where the deployment enables managed environments.
Contract tests and release policy	Alpha	Declared tests against the matching sandbox, with saved results and release-policy outcomes.
Runtime observability	Alpha	Scoped OTLP sources, traces, traffic, logs, retention, alerts and security posture.
Project secrets	Alpha management; Experimental protected consumption	Write-only values, versions, bindings, grants and activity. Application use has separate runtime limits.
Managed databases	Alpha	Database preferences, provisioning in available locations, suspend, resume, access rotation and deletion.
Hosted migrations	Alpha	Signed schema migrations for a managed SQLite or PostgreSQL database. Needs CLI 0.151.0 or later. See Hosted migrations.
Hosted database connections	Alpha	Cloud Run servers with a registered Google identity and a database grant read and write managed SQLite and PostgreSQL. Needs CLI 0.151.0 or later. See Connect a server on Google Cloud.
Managed application authentication	Alpha	Signup, password sign-in, sessions, token exchange with a trusted issuer, and roles and permissions in tokens, on managed SQLite and PostgreSQL. See Managed and external authentication.
Token verification in Axiom servers (`axiomAuth`)	Coming soon	Needs a runtime release; the CLI scaffold needs CLI 0.151.0 or later. Other backends can verify tokens with a JWT library. See Verify access tokens.
Authentication administration in the dashboard	Alpha	The Authentication page enables authentication and manages users, roles, trusted issuers and keys.
Dashboard table and SQL editor	Alpha	Browse and edit a managed database's tables, run SQL and export CSV, with role-based access.
Backups, restore and archive	Coming soon for all projects	Turned on for selected projects only. No hosted recovery SLA is announced. See Limits.
OAuth applications, MFA, passkeys, webhooks, claim hooks and policy releases	Alpha	Invited accounts; an Owner turns each on per environment. Needs CLI 0.151.0 or later. See Advanced authentication and database placement.
Preview branches, SQLite to PostgreSQL conversion and database moves	Alpha for selected projects	Available to selected projects during the Alpha. Needs CLI 0.151.0 or later.
Phone verification, Microsoft sign-in, issuer presets, Sign in with Apple and your own Turso database	Coming soon	Built, but switched off for customers.
Public paid checkout	Coming soon	Pro can be selected as a preference. Only controlled test checkout runs today.
Hosted CI/CD for every repository	Coming soon	Release pipelines process Axiom artifacts. They do not replace general repository CI.
Axiom Studio, Acode and Axiom Marketplace	Coming soon	Planned products. They are not hidden parts of the Cloud Dashboard.

Find your way around the dashboard

Dashboard area	Pages	Guide
Workspace	Projects, Recent Activity, workspace settings	Workspaces and projects
Project	Overview, Contracts, Pull Requests	Releases and environments, Contract pull requests
Development	Sandbox, Tests	Cloud mocks
Observability	Traffic, Logs, Traces, Speed Insights, Alerts	Observability
Settings	CI/CD Actions, Resources, Secrets, Project settings, Security Audit, Usage & Limits	Managed resources, Secrets

Choose local or connected work

Use local commands for authoring, evaluation, security and 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 do not replace backend authorization or code review. A signed contract states where an artifact came from. A passing contract test states that the declared checks passed against the selected environment.

Start

Cloud access is invite-only during the Alpha. The first Cloud command asks for a referral code. Without one, join the waitlist with axiom join <EMAIL>.

Terminal

axiom login
axiom project list
axiom project link
axiom build --release --version 1.2.0 --out backend.axiom

The CLI resolves the linked project from the current directory. In automation, pass an explicit --project and immutable --version, and keep the released project and version with your deployment evidence.