Backends
Kinich orchestrates quantum workloads across multiple hardware providers through a unified adapter registry. Azure Quantum serves as the primary production backend with automatic failover to IBM Quantum, while SpinQ desktop computers enable community-operated quantum nodes across Belize. Hardware execution requires provider credentials; jobs run on local simulators otherwise.
Supported Backends
Azure Quantum (Primary)
Production backend with IonQ (11 qubits, trapped-ion), Quantinuum (20 qubits, 0.995 fidelity, full connectivity), and Rigetti (40 qubits, 2D grid). Automatic transpilation and cost tracking.
IBM Quantum (Fallback)
127-qubit Eagle processors with heavy-hex connectivity. Serves as primary fallback when Azure is unavailable. Full Qiskit integration with runtime optimization level 2.
Google Cirq
Simulator backend for development and testing. Used for rapid circuit prototyping and validation before job submission to hardware providers.
SpinQ (Community)
Affordable desktop quantum computers for community nodes — Gemini (2 qubits) and Triangulum (3 qubits). Ideal for educational institutions and local research in Belize.
Adapter Registry
AdapterRegistry manages all backends with unified execute_on_best_adapter API. Automatic backend selection based on qubit requirements, cost limits, and availability.
Cost Calculator
Real pricing models for Azure Quantum and IBM Quantum. recommend_backend() optimizes for cost, speed, or quality. Budget denominated in DALLA with USD conversion.