Real-quantum-hardware integration
From specialist intelligence to real quantum hardware.
Bee provides a governed bridge between classical specialist intelligence and quantum computation: local simulation for development, an explicit and metered real-QPU execution path, and customer-controlled provider connections. Quantum jobs never happen invisibly; identity, entitlement, privacy, budget and evidence controls stay attached to every run.
Hardware reach
A governed route to reviewed QPU targets
rigetti:cepheus-1-108q
Superconducting
108qubits
Allow-listed candidate
iqm:emerald
Superconducting
54qubits
Allow-listed candidate
iqm:garnet
Superconducting
20qubits
Allow-listed candidate
Local statevector
Simulator
28qubits
Local simulator
Production activation is in progress. Customer availability requires product entitlement, platform-budget approval and a currently available reviewed target.
Production controls
Quantum capability without quantum theatre.
Bee separates post-quantum cryptographic controls, local circuit reasoning, and paid real-QPU execution. They are distinct capabilities with distinct evidence and costs.
Explicit only
Ordinary chat, research, documents, media, and model inference never silently route through a QPU.
Purchased and budgeted
Bee-hosted work requires an active product entitlement, tenant allowance, atomic reservation, and independent platform budget.
Quote before execution
Managed QPU accepts only finite provider quotes within the customer reservation and independently approved platform ceiling.
Privacy boundary
Customer candidate amplitudes stay in Bee's local simulator. Public Compute receives only server-generated validation circuits.
Purchased hosted products
Entitlement is necessary; budget approval is independent.
A successful purchase creates a tenant entitlement; it does not bypass the platform circuit breaker. Every hosted job reserves product units and Bee spend atomically. An ambiguous provider outcome retains that reservation until reconciliation—never a free retry.