Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteThere is no single price for an Amazon Braket job: the bill depends on whether you submit an on-demand QPU task, run a managed simulator, reserve QPU time, or use a Hybrid Job—and on which supporting AWS resources stay active. To estimate before submission, identify that execution path, count tasks and shots or estimate runtime, apply the current price for the selected device and Region, then add compute, notebook, storage, and other AWS charges.
Start by identifying what you are running
Amazon Braket’s pricing unit changes with the execution method. A QPU task is priced by task and shots; a managed on-demand simulator is priced by simulation runtime; a reservation is priced by reserved time. Hybrid Jobs can combine quantum charges with classical instance charges. A local simulator runs in your own environment, although the machine or notebook hosting it may still cost money.
As an Amazon Associate I earn from qualifying purchases.
| Execution path | Main billing unit | What to count before running |
|---|---|---|
| On-demand QPU | Task plus shots | Submitted tasks and total shots, using the selected QPU’s rates |
| QPU reservation | Reserved time | Booked duration and current reservation rate |
| Managed on-demand simulator | Simulation runtime | Runtime per simulation, simulator type, and Region |
| Hybrid Job | Classical instance time plus applicable quantum charges | Instance type and runtime, QPU tasks/shots or managed simulator runtime, and any extra storage |
| Local simulator | No managed Braket simulator task charge; local compute may cost separately | Where it runs, how long that machine or notebook is used, and any related storage |
AWS’s pricing page says there are no upfront charges and customers pay for the AWS resources they use. That does not mean a quantum task is the only charge: supporting services are billed separately.
Recommended Free Tools
Estimate an on-demand QPU task
For an on-demand QPU, estimate the QPU portion as:
QPU task cost = (number of tasks × per-task price) + (total shots × selected QPU’s per-shot price)
#1 Best Overall
A shot is one execution of the algorithm. A task groups repeated shots of a circuit or Hamiltonian. If your program submits multiple circuits or resubmits work, count each submitted task and add the shots across them. For the listed gate-based QPUs, AWS says the per-shot price does not depend on the number or type of gates, so do not multiply the shot count by gate count.
Rates listed on AWS’s pricing page
The following were listed by AWS when the page was accessed on October 4, 2026. These are time-sensitive rates, not guaranteed future prices; check the live page and confirm device availability in your target Region before relying on them.
| On-demand QPU | Per task | Per shot |
|---|---|---|
| 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 |
Amazon Braket pricing is the source for these listed rates. Use the price for the actual QPU you select; a cheaper per-shot rate does not by itself establish that a device is the right or available choice for your workload.
Worked example: 10,000 Rigetti Cepheus shots
Using the rates listed by AWS on October 4, 2026, one Rigetti Cepheus task with 10,000 shots is estimated as follows:
Rank #2
- Task: 1 × $0.30 = $0.30
- Shots: 10,000 × $0.000425 = $4.25
- QPU subtotal: $4.55
This is only the QPU portion. Add any Hybrid Job instance time, managed notebook runtime, storage, or other AWS resources that the workflow uses.
Account for minimum shots when applicable
AWS states that IonQ error mitigation requires at least 2,500 shots per task. At the $0.08000 per-shot and $0.30 per-task rates listed on October 4, 2026, that minimum is $200.30 for one task. The required shots can therefore matter more than a small task count when estimating an error-mitigated run.
Compare a QPU reservation with on-demand pricing
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 the time booked, then compare that amount with the task-and-shot estimate for the same expected workload. AWS lists reservations in one-hour increments; its pricing page says free cancellation is available up to 48 hours in advance. Confirm the current terms in the console, since expert advice and experimental capabilities may be billed separately.
Rates listed by AWS when accessed on 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 from the AWS pricing page, not a prediction that reserving time will save money. The comparison only helps if the reservation duration, expected workload, and current terms match your use case.
Estimate managed simulator runtime separately
Managed on-demand simulators use runtime billing rather than a QPU’s per-shot price. AWS bills in millisecond increments, with a three-second minimum per simulation. The listed services are SV1, DM1, and TN1; availability varies by Region. AWS describes SV1 as a general-purpose state-vector simulator, DM1 as supporting noisy circuit simulation, and TN1 as specializing in certain larger-scale circuits. Check current rates and regional availability on the pricing page.
As an illustration, AWS lists SV1 at $0.075 per minute in a pricing example. A four-minute simulation after the example’s free-tier coverage costs $0.30. Treat that as an example tied to its stated conditions, not as a promise of the rate or of free-tier eligibility for your account.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The Braket SDK’s local simulator is a different execution model: it runs in your environment, and the local state-vector simulator supports prototyping on small circuits. Practical limits depend on available hardware. A local run avoids a managed simulator task charge, but it does not make a separately billed notebook or compute machine free. See AWS’s simulator documentation.
Add Hybrid Job and supporting AWS charges
A Hybrid Job can incur classical instance charges in addition to quantum execution charges. When it calls an on-demand QPU or managed simulator, those quantum tasks retain their respective task-and-shot or runtime pricing. An embedded simulator is part of the Hybrid Job instance cost rather than a separate managed simulator task. Include the selected instance type, job duration, and any extra job storage in the estimate.
AWS’s pricing example for an SV1 Hybrid Job uses 1,500 seconds of simulation at $0.075 per minute plus an ml.m5.xlarge instance listed at $0.23 per hour. It shows $1.875 in simulator charges and $0.096 in instance charges, or $1.97 total after the example’s stated free-tier condition. The arithmetic illustrates why the classical job container belongs in the estimate; current rates and eligibility may differ.
A separate AWS example describes a QPU Hybrid Job with 50 iterations, two tasks per iteration, 100 shots per task, and 26 minutes on an ml.p3.8xlarge. Its calculation is $30 in task charges, $4.25 in shot charges, and $6.36 in instance use, for $40.61 total. The example uses the listed Rigetti Cepheus rate of $0.000425 per shot. Iteration count can add task charges quickly even when each task has relatively few shots.
Free tools Windows power users keep installed
One-click scans. No signup required.
Other AWS services are outside the Braket quantum charge. For example, S3 result storage is billed separately, and managed Braket notebooks are hosted and billed through SageMaker according to instance type and use duration. Include only resources your workflow actually uses, but include any that it does. The AWS pricing page describes these separate charges.
Best Value
Build a pre-run estimate you can audit
Use one row per resource in a spreadsheet or checklist. Record both the assumptions and the rates’ source/date so you can revise the estimate if the workload or pricing changes.
- Selected device or simulator and the planned Region
- Execution path: on-demand QPU, reservation, managed simulator, Hybrid Job, or local simulator
- Number of submitted tasks and shots per task, or estimated managed simulator runtime
- Applicable per-task and per-shot rates, or reservation duration and rate
- Hybrid Job instance type and expected runtime; note whether simulation is embedded
- Managed notebook instance and expected runtime, if used
- S3 storage and any other AWS services the workflow will use
- Whether the estimate includes applicable free-tier usage, credits, discounts, or taxes
Do not assume an example’s free-tier treatment applies to your account. AWS says Braket Tracker’s maximum cost estimates do not include credits or discounts and may differ from actual charges.
Use estimates and spending controls as guardrails, not guarantees
Validate usage with the Braket SDK Tracker
The 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, and Tracker does not include every possible service cost, such as EC2 charges. In AWS’s documented Bell State example, a run on SV1 with 1,000 shots produces a sample estimated cost of $0.00375; that is an example output, not a general simulator per-shot rate. See the Braket cost-tracking guide.
Know what a Braket QPU spending limit covers
Optional Braket spending limits apply per device. AWS checks a task’s estimated cost against the remaining limit and rejects task creation if it would exceed the remaining amount, which accounts for current and queued spend. The documented control excludes simulators, managed notebooks, Hybrid Job EC2 instance costs, and Braket Direct reservations. A QPU limit therefore does not cap the total cost of a workflow that includes those resources. The AWS tracking documentation explains the control.
Use AWS Budgets for broader monitoring
AWS Budgets can monitor account costs and usage, but it is not an immediate kill switch. AWS says budget data updates up to three times per day, typically 8–12 hours after the previous update, so alerts can arrive after charges accrue. Treat it as account-level monitoring rather than a precise pre-run cap; see AWS Budgets documentation.
Debug with simulators and audit every Region
AWS advises verifying circuits with simulators before running them on a QPU, which can help catch coding or configuration issues without QPU usage charges. Simulator results can differ from hardware results, so this is a debugging step rather than a guarantee of QPU behavior. Also, the Braket console shows quantum tasks only for the current Region; check other Regions when auditing submissions and charges.
Quick Recap
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.
