Local
An intended local context under the owner’s systems and data boundary. No local deployment is supplied here.
Haivian Quantum Qonduit Quantum decision boundary
The intent to quantum computation pipeline.
Start with the objective rather than a circuit. Qonduit makes relevance, evidence, cost, authority, allowed routing, reconciliation and return of results explicit before quantum work can become an execution decision.
Public Preview. Product availability and final commercial terms are unconfirmed.
The problem
Everything between the idea and the machine is missing.
Quantum SDKs begin after a team has already decided what to run. They do not own the earlier decision: whether the objective suits quantum, what evidence qualifies that conclusion, what it may cost, who has authority, which route is allowed or whether a submission actually occurred.
Qonduit owns that surrounding decision pipeline and returns the result to the objective that asked. A supported stop decision is a valid result of operating the pipeline correctly; filtering alone is not the product.
How it works
Seven responsibilities between intent and evidence.
Intent in
State the objective and decision context rather than submitting a circuit.
Relevance decided
Record whether quantum suits the objective and why.
Evidence qualified
Establish formulation, classical baseline, decoder and target-specific resource evidence.
Estimated and authorized
Estimate cost and require explicit owner approval before execution.
Routed
Constrain any later route to an allowed provider or simulator.
Submission reconciled
Establish whether execution occurred before retry when submission status is uncertain.
Evidence returned
Attach result, provenance and limitations to the originating objective.
These are product responsibilities. This page does not connect to a simulator, provider, credential, account or execution service.
Product scope
A decision record the project can carry forward.
- Product capability
- A relevance decision, accepted cost and authority boundary, allowed route, reconciliation status and evidence returned to the originating project.
- Current maturity
- Implemented internal foundation. It is not generally commissioned.
- Release qualification
- No production-ready, provider-tested, hardware-run or generally available release identity is claimed.
- Project screening and advice
- Research and technical teams can examine whether quantum belongs before committing data, budget or execution authority.
- Actual execution
- No execution is initiated, promised or evidenced by this page.
Deployment and privacy
Each route requires its own authority and agreement.
Simulator only
An intended simulator-oriented qualification context. No simulator is connected or included by this page.
Allowed provider
A later route constrained to a provider list controlled by the owner. Credentials and authority remain separate.
Haivian Factory
A separately governed Factory context under one authority and evidence model. Integration availability is unconfirmed.
Verifiable and protected
Inspect the decision without exposing the mechanism.
What remains inspectable
The relevance decision, authority, allowed route, reconciliation record, result, provenance and limitations remain visible to the project.
What may remain protected
The handshake, routing, estimation and reconciliation implementation may remain protected while their behavior and evidence boundary stay inspectable.
Standalone context
HQQ can be considered as a standalone quantum decision boundary. Availability is not claimed.
Optional Factory context
HQQ can operate inside Haivian Factory so quantum work follows the same governed action and evidence model. No Factory entitlement or live integration is included.
Planning figures
Three provisional scopes for discussion.
Public Preview pricing. The USD planning figures below are owner-confirmed for this preview, not an offer or checkout. Online purchase is closed, availability is unconfirmed, and final scope, terms and provider costs require a separate written agreement.
PROVISIONAL TIER
SIMULATOR-ORIENTED
Explorer
A starting scope for deciding whether quantum is the right instrument before any provider procurement.
$390/ year
or $39 per month
- Relevance decided before any run
- Cost estimated and authorized up front
- Simulator-oriented qualification path
- Evidence returned to the objective
- No provider account expected for the intended starting path
- Authorization required before any run
- Source describes batch submission as built but not yet tested for efficient use
- Live-provider execution is outside the confirmed Explorer scope
FEATURED FOR DISCUSSION
AUTHORIZED ROUTING
Professional
An intended owner-approved provider-routing context under the same authority and evidence model.
$2,990/ year
or $299 per month
- Everything in Explorer
- Allowed provider list controlled by the owner
- Provider routing inside that boundary
- Submission reconciled before retry
- Deeper cost governance
- Source-described batch submission built but not yet tested across providers
- Provider execution requires separate credentials and authority
- Execution charges are paid to the provider
PROVISIONAL TIER
FACTORY CONTEXT
Enterprise
An intended Haivian Factory context in which quantum work follows the same governed action and evidence model.
$4,500/ year
or $450 per month
- Everything in Professional
- Optional Haivian Factory context
- One authority model across classical and quantum work
- Results returned to the Factory evidence trail
- Organizational cost governance
- Integration requires a separate agreement
- No integration availability or included Factory entitlement is confirmed
No online purchase. No checkout, payment, account creation, order submission or reservation is present. A consultation link opens a local information page; its email action opens a draft only.