Manage your subscription
Coming from another cloud?
▸AWS·Billing and Cost Management
AWS Billing and Cost Management
- 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.
▸Azure·Billing
Azure Billing
- 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.
▸DigitalOcean·Billing API
Billing API
- 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.
▸Google Cloud·GKE Pricing
GKE Pricing
- 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.
▸Hetzner·Project Billing
Project Billing
- 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.
Manage your subscription
Complete these tasks in the Quake AI account portal on the Billing page.
1. View invoices#
- Sign in to the Quake AI account portal.
- Select Billing.
- Under Invoices, select All Invoices.
- Open an invoice to view details or download a PDF, if offered.
2. Update payment method#
- Sign in to the account portal.
- Select Billing.
- Under Payment Methods, select Manage.
- Add, edit, or replace the card, then save.
3. Manage billing addresses#
- Sign in to the account portal.
- Select Billing.
- Under Billing Addresses, select Manage.
- Add or edit an address, then save.
4. Upgrade or change plan#
- Sign in to the account portal.
- Select Billing, then All Subscriptions, or open the project and change its resource tier.
- Select the subscription and choose a new pack or adjust a custom package.
- Confirm the change and review any proration or next invoice summary shown.
5. Cancel or downgrade#
Use the account portal to change or end a subscription where that option exists, or contact Quake AI support for help with cancellation or downgrades.
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
For the full policy, see Usage Guidelines.
Last validated: 16.09.2026