Quantum jobs fail for boring reasons: wrong backend, queue too long, shots over the device limit, capabilities that drifted since last week. QubitIaC brings Terraform's discipline to quantum computing: one declarative YAML spec, a plan step that diffs your intent against live backend state, and an apply step that submits only when reality agrees.
Workload name, circuit reference, target backend, shots, and constraints. Version it, review it, diff it - like any other infrastructure.
qubitiac plan pulls the backend's real status - online or not, pending jobs, shot limits - and tells you exactly what would happen, or exactly what blocks you. Works offline against recorded snapshots too, and says so.
qubitiac apply refuses when the plan is blocked. In v0.1 apply is dry-run only - we ship honesty before we ship your jobs into a queue.
The whole language. If you can read this, you can use QubitIaC.
# examples/bell-state.yaml name: bell-state circuit: circuits/bell.qasm # OPENQASM path or inline string backend: provider: qiskit # qiskit | braket name: ibm_brisbane shots: 4096 constraints: max_queue_seconds: 3600 max_shots: 20000
Core installs with one dependency (PyYAML). Provider SDKs are optional extras, only needed for live state.
pip install git+https://github.com/gitdhillonai/qubitiac.git qubitiac validate examples/bell-state.yaml qubitiac plan examples/bell-state.yaml --snapshot examples/snapshot.json
valid: bell-state -> qiskit:ibm_brisbane, 4096 shots RUN submit 'bell-state' to qiskit:ibm_brisbane with 4096 shots NOTE planning against recorded snapshot of ibm_brisbane; live state may differ
What it does today, what it does not, and what is next. No roadmap cosplay.
| Capability | Status |
|---|---|
| Spec validation with precise error paths | Works |
| Plan vs recorded backend snapshot (offline) | Works |
| Plan vs live backend state (IBM Quantum, Amazon Braket) | Works with provider SDK + your credentials |
| Blocked-plan detection (offline backend, shot limits) | Works |
| Live job submission (apply --yes) | Not yet - dry-run only in v0.1 |
| State locking, multi-workload graphs, drift history | Not yet |
Two providers at v0.1: IBM Quantum (Qiskit Runtime) and Amazon Braket. The spec format is provider-neutral by design; more providers land after apply goes live.
QubitIaC is the umbrella for a family of open quantum tools. Each one works today, in your browser or your terminal.
What will fault-tolerant quantum actually cost? Interactive calculators for Shor, Grover, and chemistry workloads, grounded in the published literature. quantumresourceestimator.com
Paste a Quantum Resource Estimation Format program, get structural validation, a routine tree, and a resource breakdown. qref-render.com
The plain-English reference for the Quantum Resource Estimation Format: schema, examples, validator. quantumresourceestimationformat.com