Support and availability

This matrix separates an implemented path from the broader AxiomCore product direction. It was last reviewed against the local repositories on September 16, 2026.

Status definitions

Status	Meaning
Available	Implemented, documented, and usable on the stated path. It does not imply a stable major release or universal production certification.
Alpha	Implemented and testable, but APIs or workflows can change.
Experimental	A bounded implementation exists; parity, compatibility, or distribution is incomplete.
Coming soon	Planned or in development, with no supported user workflow today.

Language, contracts, and packages

Capability availability
Capability	Status	Current scope
Acore language toolchain	Alpha	Parser, evaluator, standard library, diagnostics, and language-server foundations.
.axiom service contracts	Alpha	Build, inspect, semantic diff, local test/mock, release, pull, and runtime workflows.
Typed package envelope	Alpha	Service, theme, component-library, database-schema, extension, and application-policy kinds with canonical encoding and validation.
Theme and component packages	Alpha	Typed exports, targets, roles/props/slots/composition constraints, lock resolution, and semantic change classification.
Executable extensions	Experimental	Packages carry reviewed metadata and a module digest; executable bytes are deliberately outside the declarative package envelope.

Backend and schema inputs

Capability availability
Capability	Status	Current scope
Python / FastAPI	Available	Primary extraction and local contract-build path. The service dependencies must be installed in the build environment.
Go	Alpha	Route and type extraction exists; review the extracted surface before release.
OpenAPI input	Experimental	Bounded composition/domain bootstrap path. It is not full parity with every Acore behavior.
SQL schema input	Experimental	Bounded domain bootstrap path, not a complete database runtime or management UI.
Other backend languages	Coming soon	No supported first-party extractor is documented today. Custom integration work is required.

Frontend and application targets

Capability availability
Capability	Status	Current scope
Vanilla web / ATMX	Available	Generated client and web runtime path. Validate target browsers and application CORS policy.
React / ATMX	Alpha	Bindings exist; validate bundler integration and application boot order.
Flutter / Dart	Alpha	Bindings and runtime path exist; validate platform storage and consumer release builds.
Swift / Apple platforms	Experimental	Runtime distribution exists; full binding and lifecycle parity is not claimed.
Acore UI hosts	Alpha	Browser, Android Emulator, and iOS Simulator development paths, including assets, interaction, diagnostics, and hot reload.
.axiomapp	Alpha	Target-specific and multi-target builds plus inspect/install/package/run workflows. App-store signing and publishing are outside this boundary.
Physical-device certification	Coming soon	Current documentation does not claim a certified physical-device or store-distribution matrix.

Cloud and applications

Capability availability
Capability	Status	Current scope
Cloud accounts, projects, releases, and pull	Alpha	Connected workflows require a live account and configured control plane.
Axiom Cloud Dashboard	Alpha	Implemented control-plane views; the broader collaborative vision is not all shipped.
Axiom Studio	Coming soon	Planned visual and collaborative software workspace; not installable today.
Acode	Coming soon	Planned contract-aware IDE; existing language-server/editor foundations are not the product.
Axiom Marketplace	Coming soon	The package format exists, but catalog browsing and supported installation do not.

Before adopting an alpha or experimental path, add an end-to-end example for your application, run the owning repositories' checks in CI, and inspect the semantic diff for every contract or package upgrade.