Skip to content

How billing works

Explanation · Updated Sep 2026

Coming from another cloud?

▸AWS·Billing and Cost Management

AWS Billing and Cost Managementhigh

  • AWS has native consolidated billing via Organizations (single bill for all accounts); OpenStack has no standard billing service—usage metered via Ceilometer but billing is external/provider-implemented.
  • Cost allocation: AWS uses cost categories/tags, Cost Explorer; OS relies on custom integrations.
  • Architecture: AWS payer account charges; OS per-project quotas but billing not core.
  • No API equivalence; AWS Billing APIs for reports/budgets, OS no core billing API.
AWS docs ↗
▸Azure·Billing

Azure Billinghigh

  • Consumption-based metered billing via Microsoft Commerce pipeline with rated usage, monthly invoices, discounts/reservations; OpenStack has no built-in billing, relies on add-ons like CloudKitty for rating/chargeback.
  • Scopes include subscriptions/RGs for cost analysis, anomaly detection, budgets; OpenStack usage collected via Ceilometer, rated externally.
  • Enterprise Agreements/MCA with complex scopes (billing profiles); OpenStack operator-defined.
  • Cost Management + Billing portal for payments/invoices; OpenStack requires custom integration.
Azure docs ↗
▸DigitalOcean·Billing API

Billing APIhigh

  • REST endpoints for balance, history, invoices (PDF/CSV), insights via team URN (do:team:uuid).
  • Usage-based with monthly invoices on 1st; prepaid credits model.
  • Invoice items include project_name; no OpenStack Ceilometer-style real-time metering API.
  • Pagination and rate-limited.
DigitalOcean docs ↗
▸Google Cloud·GKE Pricing

GKE Pricinghigh

  • Per-hour cluster platform fee with a free tier allowance; Autopilot offers pod-based billing as an alternative model. On Quake AI, whether you use Magnum or self-managed Kubernetes, you pay only for the underlying Nova instances and associated resources, with no Kubernetes platform fee.
  • Separate Cloud Billing Account linked to multiple projects, with self-serve/invoiced, postpay/prepay cycles; OpenStack typically uses external billing systems integrated via usage notifications, no built-in account.
  • Payments via Google Payments Profile (cards/ACH/wire); OpenStack has no native payment processing.
  • Billing-specific IAM roles (e.g., Billing Account Creator) inherited from Org; OpenStack quotas/usage per project via Keystone/Nova, no billing IAM.
Google Cloud docs ↗
▸Hetzner·Project Billing

Project Billinghigh

  • Hourly pro-rated with monthly cap, invoiced monthly post-usage to project Owner vs real-time OpenStack usage data via Ceilometer/gnocchi.
  • No billing API endpoints; view invoices in console vs queryable meters/resources via APIs.
  • Owner always billed for all project resources irrespective of member actions vs flexible billing/project assignment in OpenStack.
  • Traffic overage in 100MB blocks with notifications to owner.
Hetzner docs ↗

How billing works

Quake AI uses resource-based monthly billing: you pay a fixed monthly amount for the subscription package and add-ons you choose.

Invoicing and subscription records live in the Quake AI account portal.

Billing cycle#

Quake AI issues invoices monthly at the start of each billing period.

What your bill includes#

Your bill includes your subscription plan (compute and included resources for that tier) plus add-ons you enable, such as extra object storage or additional public IPs.

Each plan includes unlimited data transfer; Quake AI does not charge separate egress fees for normal use.

Guarantees#

Named monthly plans include a 30-day money-back guarantee.

Next steps#

Was this page helpful?