Quapp Editor: Resources and Pricing
The Quapp Editor opens Quapp Lab or Quapp Code in your browser, on resources you choose before it starts. This page explains how those resources are priced, with a focus on GPU.
Choosing resources
Before the Editor opens, you choose its resources in the configuration steps:
- Select Editor – Quapp Lab or Quapp Code.
- Select CPU or GPU – the number of vCPUs, or one of the GPU options (No GPU, 1 GPU, 2 GPUs).
- Select Memory – the memory available to the Editor.
- Review & Open – check your configuration, then open the Editor.
The options you see depend on your environment and subscription. The resource pages show no prices. The price appears on the Review & Open step, once you have chosen all of your resources: the hourly rate for CPU and memory, the hourly rate for GPU, and the total hourly rate that applies to your session.
GPU pricing
A GPU is always charged, from the first minute of the session. Your subscription's free quota does not cover it, even when the CPU and memory of the same session are free.
| GPU configuration | Price per hour |
|---|---|
| 1 GPU | $3.90 |
| 2 GPUs | $7.80 |
The GPU charge and the CPU and memory charge are worked out separately, and the total hourly rate is their sum. CPU and memory are priced by the combination of vCPUs and memory you choose, and can be free for small configurations, within a free quota that your subscription shares across all its users and projects.
How the cost is worked out
- Charging starts when the Editor is ready to use. You are not charged while it is being provisioned or checked.
- The cost is counted by the second, with no minimum charge and no rounding up to a full minute.
- The rate shown at Review & Open is fixed for your session. If prices change while the Editor is running, your session keeps the rate it started with.
- If the Editor fails to start, the cost is $0.
For example, a session on 1 GPU that runs for 30 minutes costs 0.5 × $3.90 = $1.95 for the GPU, plus any CPU and memory charge.
Prices per month are not shown for actual charges. What you pay is always the hourly rate multiplied by the time the Editor was running.
When charging stops
| What you do | When charging stops |
|---|---|
| Select Stop | When Quapp accepts your request. The time Quapp then takes to clean up is not charged. |
| Close the Editor with X | Not immediately. The session keeps running, and keeps being charged, for 10 minutes. Open the Editor again within that time and you return to the same session. After 10 minutes Quapp stops the session, and charging ends then. |
| Reach the budget limit | Quapp stops a paid Editor automatically, and the Editor shows the reason. |
After a session stops, the next time you open the Editor you configure it again from the start.
⚠️ Closing the Editor with X does not stop the charge for 10 minutes. To stop a GPU session right away, use Stop.
While the Editor is running
In Quapp Lab and Quapp Code you can see, without leaving the Editor:
- The session time.
- The estimated cost, split into the CPU and memory charge and the GPU charge.
- The free quota left on your subscription, when it applies.
The estimate updates every second. The actual cost is confirmed only after the session ends.
Who pays and how it is counted
- The cost belongs to the project, and is charged to the billing account the project uses. The person who selects Open does not pay because of that; their name is kept only to trace the session.
- A paid Editor session counts toward the project budget, and toward the user budget of the owner of the billing account.
- Paid cost is available when the project's billing account is active or on a bank-transfer contract. Otherwise you can choose only configurations that are free for your subscription.
- Quapp checks the budget about once a minute, so the amount spent can go a little over a limit before the Editor is stopped.
- If the project's billing account changes while the Editor runs, the cost before the change goes to the old billing account and the cost after it to the new one.
After a paid session ends, its cost appears in Cost Analysis with the cost source Editor. You can group it by project, Editor type or resource configuration. Free usage is not shown there.