Skip to content

Results are limited to the current section : Third-party Cloud Providers

Third-Party Cloud Providers

Pasqal QPUs and emulators are accessible through multiple cloud platforms. Depending on how your organisation works, you may access Pasqal through Google Cloud Marketplace, Azure Quantum, OVHCloud, or Scaleway — each with their own authentication, billing, and available backends.

The table below summarises access scope, available backends, pricing model, and features per provider.

Google CloudAzure QuantumOVHCloudScaleway
Access scope
Full portal + SDKSDK-based accessSDK-based accessSDK-based access
Pricing
Pay-as-you-goPay-as-you-goPay-as-you-goPay-as-you-go
Billing
Billing via GoogleBilling via AzureBilling via OVHCloudBilling via Scaleway
Features

Not all backends are available in all environments, this is not always obvious from the SDK alone. Use connection.fetch_available_devices() to confirm what’s available on your specific connection.

Google CloudAzure QuantumOVHCloudScaleway
FRESNEL
AvailableAvailableAvailableAvailable
FRESNEL_CAN1
AvailableAvailableAvailableAvailable
FRESNEL_KSA
UnavailableUnavailableUnavailableUnavailable
EMU_FREE
AvailableAvailableAvailableAvailable
EMU_MPS
AvailableAvailableAvailableAvailable
EMU_SV
AvailableAvailableUnavailableAvailable
EMU_TN
UnavailableUnavailableAvailableAvailable

A connection is the authenticated session that links your Python code to whichever platform processes your job. Think of it as the cloud provider entry point — it determines which backends you can access, how billing works, and where you monitor results.

Creating a connection is independent of your choice of library (QoolQit, Pulser, QUBO, etc.) and backend (EMU_FREE, FRESNEL, etc.). The same Pulser sequence can be submitted through any of the four providers below, only the connection object changes.

Last updated: