|
| 1 | +--- |
| 2 | +title: Quantum computing - Billing and lifecycle |
| 3 | +excerpt: Learn how we bill Quantum Notebooks |
| 4 | +updated: 2025-06-17 |
| 5 | +--- |
| 6 | + |
| 7 | +> [!warning] |
| 8 | +> |
| 9 | +> Some links on this documentation refer to the AI and Machine Learning solution. Quantum computing shares the same infrastructure as a service so you might be redirected to another section of this documentation. |
| 10 | +
|
| 11 | +## Objective |
| 12 | + |
| 13 | +**OVHcloud Quantum Notebooks** are managed Jupyter and VSCode notebooks with assigned CPU or GPU resources, eliminating the need for installation and maintenance. This documentation will detail the notebook **lifecycle and billing**. |
| 14 | + |
| 15 | +## Introduction |
| 16 | + |
| 17 | +Quantum Notebooks are linked to a Public Cloud project. The whole project is billed at the end of the month, with **pay-as-you-go**. It means you will only pay for what you consume, based on the compute resources you use (CPUs and GPUs), their running time and data. |
| 18 | + |
| 19 | +## Quantum Notebooks lifecycle |
| 20 | + |
| 21 | +During its lifetime, the notebook will go through the following statuses: |
| 22 | + |
| 23 | +- `STARTING`: the notebook is being started and, if any, the remote data is synchronized from the Object Storage. To learn more about data synchronization, please check out the [Data - Concept and best practices](/pages/public_cloud/ai_machine_learning/gi_02_concepts_data) documentation. Then the system allocates the necessary compute resources (CPUs/GPUs) for your notebook. Finally, the base framework you have chosen is pulled for use in the notebook. |
| 24 | +- `RUNNING`: the notebook is running, you can connect to it using its endpoint and benefit from your compute resources and your attached data. |
| 25 | +- `STOPPING`: the notebook is stopping, your compute resources are freed, your work and status is saved and, if any, the data is synchronized back to the Object Storage. |
| 26 | +- `STOPPED`: the notebook ended normally. You can restart it whenever you want or delete it. It will keep the same endpoint. |
| 27 | +- `FAILED`: the notebook ended in error, e.g. the process in the notebook finished with a non 0 exit code. For more information, refer to the "CLI: My notebook is in failed status |
| 28 | +" section of our [Troubleshooting documentation](/pages/public_cloud/quantum_computing/troubleshooting). |
| 29 | +- `ERROR`: the notebook ended due to a backend error. You may reach our [support](https://help.ovhcloud.com/csm?id=csm_get_help). |
| 30 | +- `DELETING`: the notebook is being removed. When it is deleted, you will no longer see it, it will no longer exist. |
| 31 | + |
| 32 | +{.thumbnail} |
| 33 | + |
| 34 | +## Billing principles |
| 35 | + |
| 36 | +Quantum Notebooks is a **pay-per-use solution**. You only pay for the **resources** consumption. |
| 37 | + |
| 38 | +**Included** in Quantum Notebooks resources: |
| 39 | + |
| 40 | +- Dedicated CPU/GPU compute resources (based on the selected amount during notebook creation) |
| 41 | +- Ephemeral local notebook storage (the size depends on the selected compute resources). The first 10GB are free. |
| 42 | +- Workspace remote storage (Optional) |
| 43 | +- Ingress/Egress network traffic (Optional) |
| 44 | + |
| 45 | +Here is a detailed graph that illustrates every step that is billed or not during the AI Notebook workflow: |
| 46 | + |
| 47 | +{.thumbnail} |
| 48 | + |
| 49 | +### Compute resources details |
| 50 | + |
| 51 | +During the notebook creation, you can select **compute resources**, known as CPUs or GPUs. Their official pricing is available in the [OVHcloud Control Panel](/links/manager) or on the [OVHcloud Public Cloud website](/links/public-cloud/prices). |
| 52 | + |
| 53 | +Rates for compute are mentioned per hour to facilitate reading of the prices, but the billing granularity remains **per minute**. |
| 54 | + |
| 55 | +As stated above and shown in the image above, you pay for these resources as long as you consume them. This happens when the image of your notebook is pulled, during the `STARTING` phase, but also during `RUNNING` and `STOPPING` phases, until you reach the `STOPPED` phase. |
| 56 | + |
| 57 | +### Storage details |
| 58 | + |
| 59 | +There are three types of storage within Quantum Notebooks: |
| 60 | + |
| 61 | +- Remote Object storage |
| 62 | +- Workspace storage |
| 63 | +- Ephemeral local storage |
| 64 | + |
| 65 | +The pricing of these different storages is different. |
| 66 | + |
| 67 | +#### Remote Object storage |
| 68 | + |
| 69 | +Remote data is the one that comes from the OVHcloud Object Storage solution. During notebook creation, you are able to mount some Object Storage containers into your notebook. |
| 70 | + |
| 71 | +In situations where you are utilizing notebooks with attached remote data, you will be charged separately for the storage of this data. The cost of Object Storage is independent from the pricing of notebooks. |
| 72 | + |
| 73 | +#### Workspace storage |
| 74 | + |
| 75 | +By default, your notebook will be mounted in a remote Object Storage container on the `/workspace` location. This will be your default folder when you access your notebook. |
| 76 | + |
| 77 | +You can store your data there. |
| 78 | + |
| 79 | +The first 10GB are free for 30 consecutive days once your notebook is stopped, then you pay at the price of OVHcloud Object Storage. |
| 80 | + |
| 81 | +#### Ephemeral local storage |
| 82 | + |
| 83 | +Each compute resource (CPU or GPU) comes with local storage, that we can consider ephemeral since this storage space is not saved when you stop or delete your notebook. |
| 84 | + |
| 85 | +The sizing depends on the selected amount of compute resources. Check the details on the [OVHcloud Public Cloud website](/links/public-cloud/prices). |
| 86 | + |
| 87 | +This concerns locations outside your `/workspace`, as well as outside any other remote Object Storage containers you may have mounted on your notebook. |
| 88 | + |
| 89 | +This storage is not billed as it is directly linked to the compute resource(s) you have chosen. |
| 90 | + |
| 91 | +### Pricing examples |
| 92 | + |
| 93 | +#### Example 1: one GPU notebook for 10 hours then deleted |
| 94 | + |
| 95 | +We start one AI Notebook, with two GPUs and we keep it running for 10 hours then we **delete it**. |
| 96 | + |
| 97 | +- compute resources: 2 x GPU NVIDIA V100s (1,93€ / hour) |
| 98 | +- remote storage: nothing |
| 99 | +- duration: 10 hours then deleted |
| 100 | + |
| 101 | +Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93€ (price / GPU) = **38,6 euros**, billed at the end of the month. |
| 102 | + |
| 103 | +#### Example 2: one GPU notebook for 10 hours but stopped, not deleted |
| 104 | + |
| 105 | +We start one AI Notebook, with two GPUs and we keep it running for 10 hours then we stop it and finally we **delete it after 10 days**. |
| 106 | + |
| 107 | +- compute resources: 2 x GPU NVIDIA V100s (1,93 / hour) |
| 108 | +- remote storage: nothing |
| 109 | +- workspace storage: 100GB used. The first 10GB are free. |
| 110 | +- duration: 10 hours then stopped for 10 days |
| 111 | + |
| 112 | +Price calculation for compute : 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month. |
| 113 | +Price calculation for workspace : 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month. |
| 114 | + |
| 115 | +#### Example 3: one GPU notebook for 10 hours with 1TB remote storage |
| 116 | + |
| 117 | +We start one AI Notebook, with two GPUs and 1TB remote storage. We keep it running for 10 hours then we delete it. |
| 118 | + |
| 119 | +- compute resources: 2 x GPU NVIDIA V100s (1,93 / hour) |
| 120 | +- remote storage: 1TB in OVHcloud Object Storage |
| 121 | +- workspace storage: 100GB used. The first 10GB are free. |
| 122 | +- duration: 10 hours then we delete it. |
| 123 | + |
| 124 | +Price calculation for compute: 10 (hours) x 2 (GPU) x 1,93 (price / GPU) = **38,6 euros**, billed at the end of the month. |
| 125 | +Price calculation for workspace: 90 (GB) x 0,01€ (price for object storage / GB) = **0,9 euros**, billed at the end of the month. |
| 126 | + |
| 127 | +Also, price calculation for remote Object Storage : 1000 (GB) x 0,01€ (price for object storage / GB) = **10 euros**, billed at the end of the month. |
| 128 | + |
| 129 | +#### Example 4: 15 CPU notebooks for 5 hours then deleted |
| 130 | + |
| 131 | +We start 15 Quantum Notebooks, each of them with one vCPU |
| 132 | + |
| 133 | +- compute resources: 1 x vCPU (0,03€ /hour /cpu) |
| 134 | +- remote storage: nothing |
| 135 | +- duration: 5 hours then we delete it. |
| 136 | + |
| 137 | +Price calculation for compute: 15 (notebooks) x 5 (hours) x 1 (CPU) x 0,03€ (price / CPU) = **2,25 euros**, billed at the end of the month. |
| 138 | + |
| 139 | +## Going further |
| 140 | + |
| 141 | +For training or technical assistance, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis. |
| 142 | + |
| 143 | +## Feedback |
| 144 | + |
| 145 | +We would love to help answer questions and appreciate any feedback you may have. |
| 146 | + |
| 147 | +Please send us your questions, feedback, and suggestions regarding Quantum Notebooks: |
| 148 | + |
| 149 | +* In the #quantum-computing channel of the OVHcloud [Discord server](https://discord.gg/ovhcloud). |
0 commit comments