Category: Zero-knowledge proving infrastructure / zkVM / production proving API
Summary: Axiom is OpenVM plus a hosted proving API. Useful because it turns zk proving into an operational stack — builds, artifacts, version support, proof jobs, and verifier packaging — instead of pretending the hard part ends at we have a zkVM.
What it does:
Provides OpenVM as a modular zkVM stack for writing Rust programs and verifying them onchain efficiently, with support for custom VM extensions and security claims around formally verified correctness
Offers the Axiom Proving API as hosted cloud infrastructure for OpenVM deployments, reproducible program builds, artifact management, proof generation, and proof verification
Exposes REST API, SDK, and CLI workflows for registering programs, checking build status, generating proofs, downloading proof artifacts and logs, and verifying proofs
Manages version support for production OpenVM releases with explicit supported / deprecated / retired lifecycle states
Maintains a public GitHub footprint spanning proving-system libraries, API CLI tooling, OpenVM-related repos, and browser / verification tooling
Key claims:
The official site frames Axiom as “the tools and infrastructure to integrate ZK into any application” and pairs OpenVM with the Axiom Proving API as its core product surface
The site claims developers can write programs in Rust, verify proofs onchain efficiently, add custom VM extensions, and rely on “100-bit provable security” plus formally verified zkVM correctness in Lean
Official docs describe the Axiom Proving API as reliable cloud infrastructure that reduces cost and latency for OpenVM proof generation while preserving a familiar developer experience via REST API, SDK, and CLI
The API index shows that Axiom ships concrete control-plane features beyond raw proving, including reproducible builds, configuration downloads, verifier generation, artifact retrieval, proof-job lifecycle endpoints, and verification endpoints
The version-support docs show an actively managed production lifecycle for OpenVM releases, which is a useful signal that Axiom is operating an ongoing proving service rather than publishing only research code
Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Axiom’s official site, proving-API docs, version-support docs, CLI docs, and public GitHub organization; see ../whitepapers/axiom-primary-sources-2026-04-25.md.