Today we are releasing omega-functions as open source under Apache-2.0. The runtime is live at github.com/Anzaetek/omega-functions-public.
What it is
A Rust quantum-circuit runtime. Eleven crates, 262+ tests passing, CPU-only, no Python anywhere in the workspace, no GPU dependency. Four simulation backends behind one Backend trait:
- Statevector — dense
Complex64, full gate set, adjoint differentiation, composable noise channels. - MPS — matrix-product-state with truncated SVD for low-entanglement circuits that exceed 30 qubits.
- Pauli — Aaronson–Gottesman stabilizer tableau for Clifford-only circuits, with linear-time sampling.
- Photonic — Fock-space SLOS plus Reck/Clements mesh and 6×6 permanent evaluation for discrete optical circuits.
Mid-circuit measurement, conditional gates, and reset work across all four backends. The dispatcher picks a backend from the circuit shape, or you can pin one explicitly.
What you can do with it today
A single CLI (omega-run) covers the production paths. The README has the full list, but a short tour:
omega-run circuit.qasm --statevector --shots 1024 --seed 42
omega-run --qubo maxcut.json --qaoa-depth 2 --optimizer cma-es
omega-run --shor --N 15
omega-run --greeks --spot 100 --strike 100 --vol 0.2 --time 1.0
omega-run circuit.qasm --gradient Z0Z1 --method adjoint --params 0.3,0.7
omega-run circuit.qasm --noise '{"depolarizing":0.001,"amplitude_damping":0.0005}'
Beyond the CLI there is omega-server (Axum HTTP plus a PQC WebSocket), a C FFI (libomega_ffi) for non-Rust hosts, and a wasmtime-backed WASM runtime that lets you ship variational optimizer guests as fuel-limited sandboxed binaries.
Why Apache-2.0 and not MIT
Shor, Grover, QAOA, and VQE intersect active patent portfolios. Apache-2.0 ships an explicit patent grant in Section 3 and a formal attribution mechanism (Section 4(d) + NOTICE) that MIT does not. For a runtime that exists to execute those algorithms, the legal surface matters.
Post-quantum serving
The server ships PQC on day one: ML-DSA-65 (FIPS 204) signed tokens with TTL and a rights bitfield, ML-KEM-768 (FIPS 203) key-encapsulated WebSocket sessions, HKDF-SHA256 session keys, and AES-256-GCM framing with counter-nonces. Certificates are CBOR-native OmegaCert — self-signed by default, chain-ready. Both the pure-Rust (ml-dsa, ml-kem) and the C-backed (pqcrypto-dilithium) crypto backends are wired and cross-checked.
The practical result is that you can register circuits as named lambda functions behind PQC-authenticated invocations without stitching together separate auth and transport layers.
Formal verification
Every optimizer rewrite that we ship as a pass carries a Lean 4 proof of denotational equivalence. Self-inverse gates (H·H = I, X·X, CNOT·CNOT, CZ·CZ), rotation merging (Rz(α)·Rz(β) = Rz(α+β), Ry-merge, zero-rotation collapse), and commutation identities for the Clifford-CX/CZ pairs all type-check in verification/ via lake build. The proofs are small and not meant to be a research contribution — they exist so that when a user runs omega-run --optimize, the correctness of the rewrite is not trust-me-bro.
What's in the open-source build vs. internal
The open-source build is the runtime. It contains everything in the crate table above, the CLI, the server, the FFI, the WASM host, the four backends, the PQC stack, and the verified optimizer.
Anzaetek-specific backends, the Quantum toolkit that sits on top (Aria DSL, 13 optimizer passes including the F₂ Gaussian-elimination kernel search, spec extraction to Lean 4 and Rocq, Shor-DLP / Shor-ECDLP circuits, ECC with MWPM decoder), the managed Sqetch integration, and the release-side compile-time licence checks remain closed source.
Both sides track the same core. The split is that the runtime is broadly useful for anyone building quantum-hybrid infrastructure in Rust, whereas the closed-source layer is where our applied research and customer-specific integrations live.
Install
git clone https://github.com/Anzaetek/omega-functions-public
cd omega-functions-public
cargo build --workspace --release
cargo test --workspace # 262+ tests, 0 failures
./target/release/omega-run examples/circuits/bell.qasm --statevector
rustup target add wasm32-wasip1 if you want to build the sample VQE and QAOA WASM guests. lake is optional and only needed if you want to re-check the Lean proofs locally. macOS and Linux (x86_64, aarch64) are the supported primary platforms; Windows is untested.
What's next
On our side, the short-term roadmap is the phase-plan in PLAN.md: CLI JSON output, richer noise channels, a Qiskit QPY bridge, GPU backends (Metal first, then CUDA, then OpenCL/wgpu) when we can do it without pulling in a vendor SDK sprawl. None of those blockers the runtime being useful today.
Issues and pull requests welcome at github.com/Anzaetek/omega-functions-public. For commercial integrations that need the closed-source layers, contact@anzaetek.com.