Pricing details
This page expands the Pricing overview with the detailed rules behind each charge.
Quave ONE Direct
With Quave ONE Direct, you deploy your applications on Quave-managed regions. Billing is based on actual resource consumption, measured in zCloud Units.
zCloud units
Each zCloud Unit consists of 0.5 vCPU and 0.5 GB of RAM.
We charge a fixed amount per zCloud Unit. Under certain circumstances, there might be variations in the proportion of memory and CPU. In those cases, we use the ratio that results in more zCloud Units.
Regional zCloud prices
| Region | Price per zCloud Unit per month | Provider |
|---|---|---|
| US-3 | $7.50 USD | Quave |
| US-5 | $7.50 USD | Quave |
| EU-1 | $7.50 USD | Quave |
| EU-2 | $7.50 USD | Quave |
| EU-3 | $7.50 USD | Quave |
| EU-4 | $26.50 USD | AWS |
When you operate multiple containers for apps or multiple replicas for databases, the zCloud Units are cumulative.
Network
We do not charge extra fees for network traffic in our supported regions. You can transfer data in and out of your applications without incurring additional costs.
In some regions our providers charge high fees for outgoing data. In those cases, we set an upper limit on the outbound data included at no extra charge.
| Region | Included outgoing traffic per month per zCloud |
|---|---|
| US-3 | Unlimited |
| US-5 | 10 GB |
| EU-1 | Unlimited |
| EU-2 | Unlimited |
| EU-3 | 10 GB |
| EU-4 | 10 GB |
If you need more network capacity, contact support.
Persistent disk storage overage
Storage overage billing starts with the July 2026 billing month (202607). July storage overage is charged on the invoice sent in August. Months before July 2026 are not charged for this storage overage.
Storage overage applies to Quave ONE Direct environments with managed local disk: DevOps managed databases and regular apps with a local persistent volume. It does not apply to stateless app containers, Shared Storage (NFS), or backup data that you store in your own object-storage account.
For each eligible Direct environment, included disk storage is based on the allocated zClouds: each zCloud includes 5 GB of allocated disk. Disk storage above that included amount is charged from the hourly average extra allocated GB in the billing month. The billable amount uses the configured disk allocation, not filesystem usage inside the volume.
For example, a database allocated 6 zClouds includes 30 GB of disk. If it is allocated 40 GB of disk for half of the month and 30 GB for the other half, the billable average is 5 extra GB for that month.
Managed database backup overage
We retain managed database backups for up to 7 days by default. The 7-day retention window is the default automatic deletion policy. The 30 GB amount is the included backup-storage billing allowance per app environment in each region, not a shorter retention cap.
Backup storage above 30 GB is charged from the hourly average extra GB retained in Quave-managed backup storage during the billing month.
Database dump backups and managed volume backup chains both count toward the same retained backup storage total. If you configure an environment to send backups to your own object-storage account, Quave ONE does not charge this backup-storage overage for those customer-owned backup objects. Your object-storage provider bills that storage directly.
Storage overages are measured hourly and averaged over the full billing month. Each storage component is rounded up to the nearest cent for the month.
| Component | Included amount | Billable usage | Price |
|---|---|---|---|
| Managed local disk | 5 GB per allocated zCloud | Average extra allocated GB-month | $0.06 per extra GB-month |
| Managed database backups | 30 GB per app environment in each region | Average extra retained GB-month | $0.05 per extra GB-month |
Example: a database with 6 zClouds includes 30 GB of disk. If it is allocated 40 GB for the whole month, it has 10 average extra disk GB, so the disk overage is 10 × $0.06 = $0.60 for that month. If that same environment has 50 GB of retained backups for the whole month, it has 20 average extra backup GB, so the backup overage is 20 × $0.05 = $1.00 for that month.
Build overage
Build overage applies at the account level to source builds that run in Quave ONE. It is designed so normal accounts stay inside the included amount, while unusually heavy or slow build usage contributes to the build capacity it consumes.
| Rule | Value |
|---|---|
| Included build time | 600 build minutes per account per month |
| Overage price | $0.01 per extra build minute |
| Per-build billing cap | 60 minutes per individual build |
| First charged month | August 2026 billing (202608) |
| July 2026 handling | Internal preview only; not charged to customers |
Build overage counts source builds. Deploying a pre-built Docker image does not run a Quave source build. If Quave ONE can reuse an existing image, the reused image does not consume new build minutes.
Customer-caused failed or canceled source builds can count because they consume builder time. Infra-side incidents can be handled with credits or manual exclusions when appropriate.
Build overage is calculated from recorded build minutes and rounded up to the nearest cent for the monthly line.
Example: if an account uses 750 source-build minutes in a charged month, the first 600 minutes are included and 150 minutes are billable. At $0.01 per extra build minute, that build overage is 150 × $0.01 = $1.50 for the month.
Functions
Function pods are billed at 3x the standard per-container zCloud rate. The multiplier accounts for Knative infrastructure overhead and the scale-to-zero capability. When your function is scaled to zero, you are not billed for container time.
Savings Plans
Savings Plans discount zCloud compute usage on the Direct plan:
- Approx. 6.67% discount per zCloud Unit when you pay monthly upfront.
- Approx. 13.33% discount per zCloud Unit when you pay annually upfront.
Savings Plan discounts apply to zCloud compute usage. Storage overage, build overage, and licenses and services are added after the zCloud usage discount calculation, so they are not reduced by Savings Plans. Account credits, when present, are applied later to the full monthly amount.
Quave ONE Connect
With Quave ONE Connect, Quave connects its platform to your own cloud infrastructure — whether on AWS, GCP, Azure, OCI, any provider, or on-premise. You pay your cloud provider directly for the underlying infrastructure, and Quave charges a monthly platform license fee based on your resource usage.
Pricing starts from $399/month. Check the Quave ONE Connect solution page to learn more and get in touch with our team.
Tier-based pricing
The monthly Connect license is determined by the tier that matches your provisioned resources. Each tier is a capacity band:
| Tier | Up to vCPU / memory |
|---|---|
| 1 | 25 |
| 2 | 100 |
| 3 | 250 |
| 4 | 500 |
| 5 | 1,000 |
| 6 | 2,500 |
Connect Standard is offered from tier 1. Connect Full Private is offered from tier 3.
Monthly license and setup amounts per tier are not published here. They are the ones stated in your Adhesion Agreement, together with any special commercial terms annex negotiated for your account. Talk to our team for current pricing.
Connect Full Private below tier 3, and tier 7 (above 2,500), have no default price. They require a contract-specific price before automatic billing can apply; Quave ONE does not create a zero-dollar or guessed charge.
For an active automated Connect license, Quave ONE recalculates the tier every day. When the daily tier changes, Quave ONE updates the Connect Additional Service by closing the previous monthly tier period and opening the new monthly tier period. The billing calculation uses those service start and end dates, so each period spent in each tier is prorated in the monthly invoice. Customer-facing notifications for these automatic changes can be disabled during rollout, while the internal billing calculation and Billing Slack visibility continue to run.
How your tier is determined and billed
Your tier is determined once per day, and the monthly invoice is prorated across the tiers you were in during the month.
Daily tier determination
- Throughout each day, Quave ONE takes multiple snapshots of the total vCPU and memory provisioned on the platform.
- At the end of the day, the median of those snapshots is calculated.
- The tier for that day is the one whose limit is equal to or greater than that median.
Using the median ensures that temporary usage spikes — such as autoscaling events or one-off operations — do not disproportionately raise that day's tier relative to your typical usage.
Prorated monthly charge
The amount due for the month is the sum, for each tier, of that tier's monthly license multiplied by the number of days you spent in the tier and divided by the number of days in that calendar month:
month total = Σ (tier monthly license × days in tier) ÷ days in month
The divisor is always the actual day count of the month being billed — 28, 29, 30, or 31. That has three practical consequences:
- A full month in a single tier costs exactly that tier's monthly license.
- Half a month in one tier and half in another costs the average of the two.
- Days when you did not use the platform — a mid-month start, a plan change, or a cancellation — are not charged.
Example, with illustrative amounts rather than real tier prices: in a 28-day February, with 14 days in a lower tier whose monthly license is $600 and 14 days in a higher tier whose monthly license is $900, the charge is ($600 × 14 ÷ 28) + ($900 × 14 ÷ 28) = $300 + $450 = $750 — the average of the two licenses.
The monthly license fee covers one region and one provider. Additional regions or providers may incur extra fees.
Setup fee
A one-time setup fee is charged to connect Quave ONE to your cloud infrastructure. The setup fee covers one region and one provider. Additional regions or providers may incur extra fees.
Minimum contract
Quave ONE Connect requires a minimum 12-month contract.