There is no single Amazon Braket price: estimate each part of your planned workload using the billing unit for its execution path. On-demand QPU work is charged per task and shot; managed simulator tasks by runtime; reservations by reserved time; and Hybrid Jobs can add classical instance costs. Then add any notebook, storage, or other AWS services the workflow uses.
1. Identify how the workload will run
Start with the execution path, because it determines what to count. A Braket workflow may use an on-demand QPU, an on-demand managed simulator, a QPU reservation, or a Hybrid Job. A local simulator runs on your own environment rather than as a managed Braket simulation task, though the computer or notebook hosting it may still cost money.
- On-demand QPU: count submitted tasks and shots, using the selected QPU’s rates.
- QPU reservation: estimate reserved hours rather than treating it as ordinary per-task access.
- Managed on-demand simulator: estimate simulation runtime.
- Hybrid Job: add the job’s classical instance time to any separately billed QPU or managed-simulator work. An embedded simulator is part of the Hybrid Jobs instance cost.
- Local simulator: no managed Braket simulation-task charge, but include the cost of the machine or notebook running it.
Confirm the device and Region you intend to use. Device availability, simulator availability, and prices can vary, so check the Amazon Braket pricing page and the current service options before submitting.
2. Estimate on-demand QPU task and shot charges
For an on-demand QPU, estimate the quantum portion with:
#1 Best Overall
QPU cost = (number of tasks × per-task price) + (total shots × selected QPU’s per-shot price)
A task groups repeated shots of a circuit or Hamiltonian. If you submit multiple circuits or resubmit work, count each submitted task and add its shots to the total. For the listed gate-based QPUs, AWS says the per-shot price does not depend on the number or type of gates; do not multiply shots by gate count.
Amazon Web Services’ pricing page, accessed October 4, 2026, listed a $0.30 charge per task for the on-demand QPUs below. Its listed shot prices were:
| QPU | Per-task price | Per-shot price |
|---|---|---|
| AQT IBEX-Q1 | $0.30 | $0.02350 |
| IonQ Forte | $0.30 | $0.08000 |
| IQM Emerald | $0.30 | $0.00160 |
| IQM Garnet | $0.30 | $0.00145 |
| QuEra Aquila | $0.30 | $0.01000 |
| Rigetti Cepheus | $0.30 | $0.000425 |
These are time-sensitive listed rates, not a promise of current price or availability. Verify the selected QPU’s live rate and Region before using them for a budget.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
Worked example: one Rigetti Cepheus task
Using the rates in that AWS pricing-page example, one task with 10,000 shots comes to:
- Task charge: 1 × $0.30 = $0.30
- Shot charge: 10,000 × $0.000425 = $4.25
- QPU subtotal: $4.55
This is only the QPU portion. Add any Hybrid Job instance, managed notebook runtime, storage, or other AWS resources used by the workflow.
Account for minimums and repeated work
Some execution choices impose a practical minimum. AWS says IonQ error mitigation requires at least 2,500 shots per task. Its listed example for one task at that minimum is $0.30 plus 2,500 × $0.08, or $200.30. Iterative algorithms also accumulate task fees: count the tasks across every iteration, not just the number of iterations or circuits in one iteration.
3. Compare a QPU reservation with on-demand execution
A reservation is billed by reserved time, not by the number of tasks or shots. Estimate it as the reservation’s hourly rate multiplied by booked duration, then compare that amount with the on-demand task-and-shot estimate for the same expected workload.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →AWS listed these reservation rates per hour on its pricing page accessed October 4, 2026:
| QPU | Listed reservation rate per hour |
|---|---|
| AQT IBEX-Q1 | $4,800 |
| IonQ Forte | $7,000 |
| IQM Emerald | $4,000 |
| IQM Garnet | $3,000 |
| QuEra Aquila | $2,500 |
| Rigetti Cepheus | $4,100 |
These are volatile list prices; confirm current rates and console terms. AWS says free cancellation is available up to 48 hours in advance. Expert advice and experimental capabilities may be billed separately, so do not assume the reservation rate includes them.
4. Estimate managed simulator runtime
Managed on-demand simulators are billed by simulation-task runtime, at per-minute rates in millisecond increments, with a three-second minimum per simulation. They do not use a QPU per-shot tariff. AWS lists SV1 for general-purpose state-vector simulation, DM1 for noisy circuit simulation, and TN1 for certain larger-scale circuits; rates and regional availability differ, so verify the current pricing page for your chosen simulator and Region.
As an illustration, AWS’s accessed pricing example lists SV1 at $0.075 per minute: a four-minute simulation after free-tier coverage costs $0.30. Treat that as an example tied to the stated rate and free-tier condition, not a universal simulator price.
The Braket SDK’s local simulator is a different execution model. AWS describes its local state-vector simulator as useful for prototyping small circuits, with practical limits depending on available hardware. If it runs on a billed cloud machine or managed notebook, include that machine’s charges even though the simulation is local to that environment.
5. Add Hybrid Job and supporting-service costs
A Hybrid Job can combine quantum execution charges with classical compute charges. If it calls an on-demand QPU or managed simulator, those tasks retain their applicable task, shot, or simulation-runtime charges, while the job’s classical instance is billed for its runtime. If it uses an embedded simulator, include the instance cost rather than adding a separate managed-simulator task charge. Include extra job storage if configured.
Use the right runtime and iteration counts
Estimate the job’s instance type and duration, and count every quantum task the algorithm creates. AWS’s Hybrid Job QPU example uses 50 iterations, two tasks per iteration, and 100 shots per task, plus 26 minutes on an ml.p3.8xlarge. AWS calculates $30 in task charges, $4.25 in shot charges, and $6.36 in instance use, for $40.61 total. The task count is 100, so the example illustrates how task fees can add up even when each task has a modest shot count.
AWS also shows an SV1 Hybrid Job example with 1,500 seconds of simulator use at $0.075 per minute and an ml.m5.xlarge listed at $0.23 per hour: $1.875 in simulator charges plus $0.096 in instance charges, or $1.97 total after the example’s stated free-tier condition. Both examples depend on the prices and conditions stated in AWS’s pricing material; check live rates before estimating your own run.
Recommended Free Tools
Best Value
Include notebooks, storage, and other AWS resources
Braket does not bundle every supporting AWS service into one quantum charge. AWS says associated services such as S3 storage for results are billed separately. Managed Braket notebooks are hosted and billed through SageMaker according to the selected instance type and how long it runs. Add only resources your workflow will actually use, but include them even if their costs are separate from Braket task charges.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Build a pre-run estimate you can audit
A simple worksheet helps expose what is included and what is not. Make one row for each resource or billing component:
- Selected device or simulator and Region
- Execution type: on-demand QPU, reservation, managed simulator, local simulator, or Hybrid Job
- Task count and shots per task, where applicable
- Current per-task and per-shot rates, or simulator runtime rate
- Reservation duration, if applicable
- Hybrid Job instance type and runtime, including iterations that generate tasks
- Notebook instance type and runtime
- S3 storage and any other AWS services used
- Whether Free Tier usage, credits, discounts, and taxes are included
Keep the date and Region beside the rates so you can revisit assumptions if the device, tariff, or account terms change. Do not treat credits or discounts as guaranteed reductions in a cost estimate: AWS says Braket Tracker’s maximum-cost estimates exclude them.
7. Use cost tools as checks, not guarantees
Braket SDK Tracker
The Braket SDK Tracker can report shots, completed tasks, execution duration, billed duration, and a maximum cost estimate for QPU and on-demand simulator usage. AWS cautions that estimated charges may differ from actual charges; estimates also exclude credits and discounts, and other services such as EC2 can add costs. Use Tracker to validate and monitor Braket usage, not as a guaranteed final bill. AWS’s documented Bell State example reports an estimated $0.00375 for 1,000 shots on SV1; that is an example output for that run, not a general simulator rate.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePer-device QPU spending limits
Amazon Braket’s optional QPU spending limits can reject creation of a task if its estimated cost would exceed the remaining limit for that device. The remaining amount accounts for current and queued spend. The documented control does not cover simulators, managed notebooks, Hybrid Job EC2 instance costs, or Braket Direct reservations, so it is not an all-in workflow cap.
AWS Budgets
AWS Budgets can monitor account costs and usage, but it is an alerting and monitoring tool rather than an immediate stop control. AWS documentation says cost data can update up to three times per day, typically 8–12 hours after the previous update, and an alert can arrive after charges accrue.
Reduce avoidable QPU charges and audit the right Region
AWS recommends verifying circuits with simulators before running them on a QPU, so you can catch coding or configuration problems without QPU usage charges. A simulator is a debugging step, not a guarantee that its output will match hardware behavior. When auditing quantum-task activity in the console, check each Region: the console displays tasks for the current Region only.
Quick Recap
Before you submit
- Choose the actual execution path and confirm the device or simulator is available in your intended Region.
- For on-demand QPU work, count every task and sum shots across tasks; multiply by the live task and shot rates.
- For reservations, multiply the current hourly reservation rate by booked duration and compare it with the on-demand estimate.
- For managed simulators, estimate billable runtime and account for the three-second minimum per simulation.
- For Hybrid Jobs, add instance runtime to any separately billed QPU or managed-simulator tasks; treat embedded simulation as instance use.
- Add notebook, storage, and other AWS services, then state whether credits, discounts, Free Tier, and taxes are included.
- Use Tracker, spending limits, and Budgets only within their documented coverage; recheck current prices and terms before launch.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
