.svg){kind=small}
The power of quantum at your fingertips.
Basic
Free
Features:
.svg)
Unlimited access to the PlanQK Community
Access to the PlanQK Marketplace
Unlimited job and service executions
Access quantum backends using your own access tokens
Trial budget for classical resources (up to 1 CPU and 4GB RAM)
Manage your organization with up to 3 members
Up to 1 on-premise service
Share up to 3 services in your account/organization
PlanQK CLI and PlanQK SDK
Community support
Pro
0 €
All from "Basic", plus:
Use PlanQK beyond trial budget
Pay-per-use with no extra charges
Up to 4 CPUs and 8GB RAM
Use T4 and V100 GPUs
20+ quantum backends and simulators
Monetize services in the PlanQK Marketplace
Business
10 €
All from "Basic", plus:
Tailored best-in-world CPU and RAM configurations
Use HPC A100 and L4 GPUs (soon)
Unlimited members in your organization
Unlimited services shared in your account/organization
Unlimited on-premise service
Workflows (soon)
Premium support
Enterprise
Let's talk
All from "Business", plus:
Payment mechanisms on demand
Input on the PlanQK feature roadmap
PlanQK premium partner badge
Dedicated support contact from our Quantum Service Integration team
Compare plans & features
Pay for what you use,
on classical & quantum resources.
CPU & Memory
As an example, running a PlanQK Service with a one gigabyte memory configuration for 1 second consumes 1024 megabyte-seconds. Similarly, running a PlanQK Service with a 256 megabyte memory configuration for 4 seconds consumes 1024 megabyte-seconds as well.
Definitions
- vCPU per milliCPU-second: The virtual CPU resources reserved for your PlanQK Service. A milliCPU-second is defined as the usage of a one thousandth of one virtual CPU for one second.
- Memory per megabyte-second: The memory resources reserved for your PlanQK Service. A megabyte-second is defined as the usage of 1 MB of memory for one second.
GPU
As an example, running a PlanQK Service with one (1) NVIDIA® T4 GPU for 5 minutes would cost € 0.05835.
Definitions
- GPU core-second: The GPU resources reserved for your PlanQK Service. A GPU core-second is defined as the usage of one GPU core for one second.
Azure Quantum
IonQ resources are charged based on the number of gates in your program, the complexity of the gates you use, and the number of shots. These units are called gate-shots.
Every quantum program consists of N quantum logical gates of one or more qubits, and is executed for a certain number of shots. The number of gate-shots is calculated by the following formula:
QGS = N ⋅ C
where:
Nis the number of one- or two-qubit gates submittedCis the number of execution shots requested
Multi-controlled two-qubit gates are billed as 6 * (N-2) two-qubit gates, where N is the number of qubits involved in the gate. For example, a NOT gate with three controls would be billed as (6 * (4-2)) or 12 two-qubit gates.
AWS Braket
Simulators are billed for a minimum of 3 seconds per simulation.
There are two pricing components when using AWS Braket quantum hardware: a per-shot fee and a per-task fee. Per-task pricing is the same across all QPUs. The per-shot pricing depends on the type of QPU used. For gate-based QPUs, the per-shot price is not affected by the number or type of gates used in a quantum circuit.
Note that the use of error mitigation on IonQ's Aria QPU requires a minimum of 2,500 shots per task.
Pricing example: A scientist runs a quantum algorithm on the Rigetti Aspen-M-3 quantum computer. This task includes 10,000 repeated shots of the same circuit design. The cost to run this task includes a per-task charge of €0.60, plus 10,000 shots at a per-shot price of €0.0007.
The cost to run this algorithm:
- Task charges: 1 task x €0.60 / task = €0.60
- Shots charges: 10,000 shots x €0.0007 / shot = €7.00
Total charges: €0.60 + €7.00 = €7.60
