A quantum instance is how a workspace organizes access to compute, in the same style as IBM Quantum instances. Each instance defines three things:
  1. A pricing plan — how runs submitted through it are billed.
  2. A target allowlist — which computers/targets it may submit to (empty allowlist = any target the workspace is entitled to; up to 50 targets).
  3. An access group — who in the workspace may use it.
Submitting a job with an instance_id makes that instance’s plan decide the billing; submitting without one uses plain prepaid billing against the workspace wallet.

The three plans

Per-plan refusals you may see when running: free_plan_simulators_only (free instance pointed at real hardware), free_plan_limit_met (monthly cap reached), paygo_not_released, instance_target_not_allowed (target outside the allowlist), instance_access_denied (you are not in the access group). All are listed in Errors.

Access groups

When creating an instance you choose who can run through it:

Create an instance

Console: Compute Console → Quantum instances → Create instance. Pick the plan, name it, select allowed computers and the access group. When the plan is free, real-QPU targets are not selectable and only one free instance can exist (a second returns 409 free_instance_exists). SDK / CLI / REST:
Each instance row reports its plan, allowlist, access group, the monthly runtime used against the cap (free plan), and the amount spent through it. Deleting an instance (DELETE /api/v1/platform/quantum-instances/{id}) retires it; jobs already settled keep their history.

Requesting pay-as-you-go

Pay-as-you-go is invoiced monthly with no prepaid hold, so it is gated on a contract:
1

Request it

In the Compute Console (or POST /api/v1/platform/quantum-instances/paygo/request with a short justification). One pending request per workspace; a second returns 409.
2

SoftQuantus reviews

SoftQuantus staff approve or reject the request. An approval requires a signed contract reference — a release without one is not possible, by design.
3

Check status, then create paygo instances

GET /api/v1/platform/quantum-instances/paygo/status returns none, pending, approved or rejected. Once approved, creating paygo instances and running through them works; before that, both return 403 paygo_not_released.

Pricing catalog

GET /api/v1/platform/quantum-instances/pricing-catalog returns the pricing source of truth: provider-published hardware prices (with source URLs) merged with the platform’s own simulator and compute rates. The console’s Quantum Computers view renders the same catalog. See Backends & pricing.