Capability boundaries

Use this page when the exact limit of a feature affects your application. The support matrix is the short entry point; this page keeps the detailed qualifications behind each Available, Alpha, Experimental, and Coming soon label.

Review dates

These are historical qualifications. They do not mean that every feature ships in the newest public binary.

Language, contracts, and packages

Managed language foundations

Experimental.

• Requires: a compatible compiler and the matching native server runtime.
• Covers: bounded shared validation and codecs, selected typed failures, finite managed branches and await, private typed configuration and purpose-bound secrets, owned cleanup, and explicitly prepared PostgreSQL transactions.
• Web and guests: web owners and verified Rust/Wasm guests use selected checked helpers.
• Separate gates: the worker, generated mobile readers, editor versions, and distribution.

Owned concurrency, operation policies and timing

Experimental.

• Requires: a compatible compiler and native host.
• Covers: finite named read groups, typed collected outcomes, cancellation and drain, root budgets, provider-attested retry policies, and typed durable enqueue through an explicit reviewed controller.
• Separate native fixture evidence: Redis recovery, and composed job and provider attempt bounds.
• Web and mobile: web and generated mobile owners support bounded foreground polling and debounce. Mobile activation requires the explicit foreground-events host capability. Compiled lifecycle queues and generated owner tests do not certify a mounted mobile application.
• Rust/Wasm: query groups require a group-capable trusted broker adapter. Other SDK and host profiles reject unsupported groups.
• Separate gates: the installed editor and public binary publication keep exact-toolchain gates.

Advanced application candidate

Experimental.

• Requires: the matching source compiler and native host.
• Covers: bounded authority-partitioned read caching, typed read batches, managed finite snapshot streams, qualified receipt-backed archive batches, inherited form rules and selected failures, runtime-owned submission identity, and generated selected Rust, TypeScript, and Python codecs with finite named reentry.
• Complete task source: combines signed pure guest computation, managed PostgreSQL receipt and outbox writes, cache invalidation, and bounded snapshot reduction.
• Reports: bind the actual execution level, artifact hashes, assertions, and cleanup.
• Not equivalent: actual durable-provider and mounted web fixtures remain distinct from scripted or generated mobile adapters.
• Separate gates: exact installed editor delivery, wider target qualification, and public artifact promotion.

Observability, scenarios and delivery

Experimental.

• Covers: exact source-linked private observations; opt-in typed public, private, and secret telemetry fields with redaction; strict artifact-bound native scenarios with logical retry and batch-window barriers, cancellation, and cleanup; explicit synthetic credential and provider expiry environments that cannot activate in production.
• Frontend scenarios: reference frontend scenarios virtualize polling and stream windows. Native OS containment and actual provider recovery keep distinct real-time gates.
• Playground: the task and inventory examples include editable database contracts and manifests with live checked table previews.
• Requires: matching CLI and LSP, VS Code and Zed adapters, compiler, and host readers.

Backend and schema inputs

See Database contracts for the current authoring, explicit inspection, and adoption workflows, and later impact boundaries.

Acore database contracts

Experimental. Offline PostgreSQL authoring, typed server-only schema packages, semantic comparison, editor services, and WebAssembly preview. Legacy v1 remains data-only. Separately qualified private persistence mappings use the named PostgreSQL application profile.

Schema-derived PostgreSQL persistence

Experimental.

• Covers: private typed native operations, pools, primary readiness, tenant transactions, codecs, bounded retry and cancel, atomic outbox and idempotency, and compiler-linked API and UI impact.
• Qualified on: the exact PostgreSQL 17.11, Darwin 25.2 arm64, loopback TLS, and file profile.
• Not covered: other runtimes, replicas, and a general ORM remain gated.

PostgreSQL inspection and adoption preparation

Experimental.

• Covers: explicit private bindings, verified native Rust TLS, read-only scoped catalogs, static SQL and HCL imports, physical comparison, and sanitized dependency graphs.
• Qualified on: native fixture validation with PostgreSQL 17.5 on macOS arm64.
• Not covered: baseline registration and a backend query provider.

PostgreSQL isolated planning and private history

Experimental.

• Covers: Rust typed transitions, disposable pinned development replay, source-linked risks and impacts, typed fixture tests, and checksummed offline candidate history.
• Qualified on: native acceptance with PostgreSQL 17.5 on macOS arm64.
• Not covered: target history remains unregistered. There is no production data-safety claim.

PostgreSQL controlled local/staging application

Experimental.

• Covers: Rust signed private prefixes; explicit target, role, and incarnation bindings; an owned revision ledger; locks; fresh drift and ownership checks; empty or no-change baseline registration; explicit Atlas adoption provenance; atomic group outcomes; and bounded status, verify, and reconcile.
• Qualified on: native fault acceptance with PostgreSQL 17.5 on macOS arm64.
• Not covered: production data and online-workload certification.

PostgreSQL data evolution

Experimental.

• Covers: exact Acore intent, stable physical renames, bounded resumable transforms, fenced catch-up and enforcement, scoped insert, upsert and synchronize, explicit scalar and finite-enum conversion, simple concurrent btree indexes with signed OID repair, data-retaining checkpoints, and new fresh-target roots.
• Qualified on: PostgreSQL 17.5 on macOS arm64, local and staging.
• Not proved: application dual writes, general cursors and SQL, and production workload compatibility.

PostgreSQL advanced objects and security

Experimental.

• Covers objects: selected domains, composites, ranges, and sequences; views and materialized refresh; SQL and PL/pgSQL routines; triggers and event hooks; aggregates and casts; libc collations; and pgcrypto and postgres_fdw.
• Covers security: exact scoped roles, memberships, ACLs, default privileges, and RLS; private runtime credentials; and security impact.
• Qualified on: native PostgreSQL 17.5 on macOS arm64.
• Not covered: opaque or dynamic effects stay unknown, and unmodeled properties block coverage.

PostgreSQL partitions, storage and foreign objects

Experimental.

• Covers: finite range, list, hash, and default bounds; retained detach; separately checkpointed attach and recovery; selected ordinary heap storage, tablespace, owner, and options; and secret-safe postgres_fdw server, table, and mapping.
• Qualified on: native writer, placement, and foreign tests on PostgreSQL 17.5, macOS arm64.
• Not proved: repartitioning, parent storage, inherited CHECK and foreign keys, and remote compatibility and availability.

Frozen database fleet delivery

Experimental.

• Covers: enrolled PostgreSQL and SQLite targets, bounded frozen inventories, source, security, and operations review with an independent policy digest, serial canary groups, native checkpoint reruns, immutable offline promotion, masked monitoring, and a typed column and impact dashboard.
• Protocol: CI, Axiom operator, and Terraform CLI.
• Not covered: production execution requires exact qualified PostgreSQL profile admission.

Named PostgreSQL production management

Available, for the qualified PostgreSQL profile only.

• Profile: PostgreSQL 17.11, Darwin 25.2 arm64, Rust 1.93 native release digest, verified TLS, and private file providers.
• Admission: reviewed exact-build admission requires an actual populated physical backup and PITR, native data and history comparison, fenced failover and rotation, and retained feature drills.
• Workloads: bounded measured workloads only.
• Separate gates: other engines, platforms, and providers; full property coverage; unsupported mixed transitions; and the backend runtime.

SQLite contracts and local lifecycle

Experimental.

• Covers: separate SQLite authoring, private views and triggers, populated rebuild validation, signed prefixes, owned empty enrollment, and atomic schema and revision recovery.
• CLI: CLI 0.149.0 resolves SQLite automatically and provides versioned migrate, rollback, status, history, and run, plus bounded typed application persistence.
• Qualified on: selected macOS arm64 and Linux arm64 acceptance.
• Separate gates: attached databases, unsupported conversions, and production data safety.
• Deferred: MySQL, MariaDB, and other adapters.

Frontend and application targets

Cloud and applications

For managed project databases, you select SQLite or PostgreSQL; allocation depends on location, capacity, and entitlement. Hosted migrations for managed SQLite and PostgreSQL are Alpha, checked on October 20, 2026 with a source build of the CLI; a released CLI with those commands is Coming soon. On managed SQLite, a change to an existing table's columns or constraints is refused (ADB1132). Hosted runtime connections from Cloud Run servers to managed SQLite and PostgreSQL are Alpha, checked on October 24 and 25, 2026 with source builds of the CLI and runtime; a released CLI with those commands is Coming soon. Managed PostgreSQL schemas support no row-level security policy yet; tenant isolation comes from the runtime's tenant filter. Managed application authentication (signup, password sign-in, sessions, token exchange, roles and permissions) is Alpha, checked on October 25, 2026 on managed SQLite and PostgreSQL. Verifying its tokens in a deployed Axiom server (axiomAuth) needs a CLI and runtime release; a released CLI with these commands is Coming soon. Dashboard pages for administering authentication are Coming soon. Axiom Cloud signup is invite-only, so these Alpha capabilities are available to invited accounts. Advanced authentication, preview branches, SQLite to PostgreSQL conversion, database moves and your own Turso database are Coming soon; see the support matrix. Public paid checkout is Coming soon. The new resource-management CLI commands are source-only.

Project secrets

• Management (Alpha): deployed write-only environment, version, binding, grant, and audit views.
• Protected consumption (Experimental): the matching source preview qualifies macOS arm64 native ActionHost and server WASM. The source web frontend delegates to backend operations.
• Not qualified: published CLI 0.149.0 and 0.149.1, host 0.6.12, mounted mobile, containers, and Workers.

See Secrets at runtime, Cloud secrets, and the Secrets commands (source preview).

Database developer workflow

CLI 0.149.0 adds:

• explicit Acore contract identity and version;
• native PostgreSQL and SQLite connections;
• atomic versioned migration and compensation;
• status, history, and comparison;
• non-interactive preparation and frozen promotion;
• a native SQL console; and
• source-owned private mappings.

Default Axiom-generated artifacts, locks, and reports are hidden. The playground compiles matching metadata and simulates versioned transitions with retained valid rows and clean downloads.