Qubo
Quantum compute. At your command.
Turn a task into a compute workflow. Run quantum experiments, compare classical results, and track every job within your budget.
“We turn a task into a compute workflow: a validated circuit, an explicit backend, explicit limits, and a job you can follow from queue to result.
Try a circuit right here
Tap gates and watch the exact probabilities move. Computed in your browser, no account needed.
- H q0
- CX 0→1
Outcome probabilities
Bitstrings in Qiskit order: the rightmost character is q0.
These are exact probabilities from a statevector computed in your browser. In the workspace the same circuit runs on Qiskit Aer with real shots, or on IBM Quantum hardware.
Three capabilities
An agent-operated workspace for quantum and classical computation.
Proposed plan
Agent Planning
Describe an experiment in plain language. The agent turns it into a validated plan with backend, parameters and expected resources. You review and run it; it never executes anything on its own.
Compute Execution
A structured circuit schema, a Qiskit Aer statevector simulator for exact probabilities and seeded sampling, and an IBM Quantum adapter for real hardware. Every job is bounded by server limits.
Traceable Records
Each completed job gets a canonical result manifest and a SHA-256 commitment. Optionally anchor it on Robinhood Chain and verify a downloaded result against the recorded commitment.
Driven by the actual configuration
Every status on this section is read live from the compute API, not written by hand.
Local simulator
Qiskit Aer statevector: exact Born probabilities and seeded finite-shot sampling. Free, isolated in a child process with a wall-clock timeout.
Qiskit Aer · up to 8 qubits
IBM Quantum hardware
Real devices through the configured IBM Quantum credentials. Every hardware job needs an explicit approval; results are noisy counts with no seed.
Checking backends…
Qubo Agent
A language model that plans and explains. It is not a quantum computer, and every feature also works without it through the manual editor.
Quota from the API
Receipts on Robinhood Chain
Record a job's commitments on-chain from your wallet. A commitment to the result, not a proof of correctness.
Registry 0xc85A…ca18
Verify a resultPlans experiments. You run them.
A language model that plans and explains. It is not a quantum computer and it never executes anything on its own.
Plain-language planning
Describe an experiment; the agent proposes the backend, parameters and expected resources.
Validated like a manual submission
Each proposal goes through the same schemas and limits as the manual editor. You load it into the workspace and press Run.
Explains your actual results
Attach a job and the agent reads its stored spec and result, so explanations use real data.
Bounded by design
It cannot execute generated code, sign transactions, transfer funds, change limits or submit hardware jobs.
From task to result
Define, bound, execute, inspect. A job you can follow from queue to result.
Define
Pick a template or build a circuit gate by gate. Validation runs on the server before anything is queued.
Execute
A dedicated worker runs the simulation in an isolated process, or submits to the provider and polls its status honestly.
- queued14:02:11
- running14:02:12
- completed14:02:13
Bound
Choose shots, seed and backend. Qubit, gate, shot, memory and time limits are enforced by the API and again by the worker.
Inspect
Compare exact probabilities with sampled counts, read the classical baseline, download JSON, CSV, QASM and the manifest.
Runnable templates
Each one goes through the same validated job pipeline as a custom circuit: queued, executed by the worker, stored with a result manifest.
Bell State
Prepare a maximally entangled two-qubit pair and sample it.
2
qubits, H then CX
1/2
probability on 00 and on 11
Ideal00 and 11, each with probability 1/2. 01 and 10 never occur on an ideal simulator.
Open in workspaceReported as measured
No quantum advantage claims. What the workspace shows is what the backend returned.
Only live data is called live. Unavailable things say Not configured, Unavailable or No jobs yet. Toy experiments are reported as measured, including classical wins.
Workspace preview
example · GHZ-3H on q0, CX chain, measure all. Ideal output: 000 and 111 with probability 1/2 each. Run it on the simulator or edit every gate.
Exact probabilities and finite-shot counts are shown as distinct quantities, side by side.
Exact vs sampled
Two numbers, never merged
Seeded reproducibility is claimed for the simulator only. Hardware results carry device noise and no seed applies.
Seeds, simulator only
Hardware is not reproducible
No invented partnerships, benchmarks, customer numbers, capacity, queue times or prices.
Nothing invented
Reported as measured
0
Qubits per circuit
0
Shots per simulator job
0 s
Wall clock per job
Default limits; live values load from the API.
Clear costs, before anything runs
Local simulation needs no account, no key and no wallet.
Local simulator
Free/no account
Exact probabilities and seeded sampling for every template and custom circuit.
Run on simulator- Up to 8 qubits and 256 gates
- Up to 8,192 shots per job
- 30 s wall clock, isolated process
- Seeded, reproducible runs
- JSON, CSV, QASM and manifest exports
IBM Quantum hardware
Real devicesProvider/billed
Real devices through the configured IBM Quantum credentials. The provider bills the credential owner; no cost estimate is available.
Open Workspace- Backends listed live from the API
- Up to 4,096 shots per job
- 5 hardware jobs per day
- Explicit approval for every job
- Noisy counts, no seed, no hard monetary cap
Qubo Agent
Included/60 req / hour
Plans and explains in plain language; you stay in control of every run.
Try the agent- Model shown live in the workspace
- Validated against server limits
- Reads attached job results
- Never runs anything on its own
- Manual editor works without it
What it is, what it isn't
A compute workspace with explicit limits, not a claim of quantum advantage.
Qubo
- Validated circuits before anything is queued
- Explicit backend and limits on every job
- Exact probabilities next to sampled counts
- An exact classical baseline for optimization
- Seeded, reproducible simulator runs
- SHA-256 result commitments, optional receipts
It never
- Claims a quantum advantage
- Labels a simulator job as hardware
- Invents progress percentages
- Lets the agent run jobs on its own
- Treats a receipt as proof of correctness
- Parses or executes uploaded code
$QUBO
The community token of Qubo on Robinhood Chain. It plays no part in the compute pipeline: simulations, hardware jobs and receipts never depend on it.
- Ticker
- $QUBO
- Network
- Robinhood Chain · chain id 4663
- Contract address
- Soon
Announcements come from @getqubo only. The contract address will be published here at launch. Until then, any $QUBO address you see elsewhere is not ours.
Questions? Answers!
Quick answers, straight from the documentation.
No. Local simulation runs in a guest session stored in this browser. A wallet is optional: it lets you sign in again from another browser and record execution receipts.