# Account & Billing FAQ Source: https://docs.quake.ai/docs/account/faq Markdown: https://docs.quake.ai/docs/account/faq.md > Frequently asked questions about Quake AI Account and Billing: projects, organizations, resource tiers, subscriptions, billing cadence, invoices, payment methods, application credentials, and the portal and console. --- {/* --- FAQ: Account & Billing service --- Confidence tiers: T1 High-confidence: direct restatement of canonical content. T2 Medium-confidence: synthesized across multiple pages. T3 Validation-needed: billing/pricing/policy specifics, quotas, SLA, support. Every answer carries a "Source:" line. This service is especially T3-heavy because billing, pricing, and policy questions dominate and must not be invented. Many answers are skeletons with an explicit Action: line noting what needs finance/legal/PM signoff before publication. */} # Account & billing FAQ Frequently asked questions about Quake AI accounts, projects, subscriptions, and billing. For step-by-step setup instructions, see the [Account & Billing overview](/docs/account). For resource tier details and pricing, see the [resource tiers reference](/docs/account/resource-tiers) and the [pricing reference](/docs/account/billing/pricing). For billing concepts and invoicing, see [How billing works](/docs/account/billing/how-billing-works). For interactive pricing, see [quake.ai/pricing](https://www.quake.ai/pricing/). --- ## Getting started ### Q: How do I create a Quake AI account? [T1] Quake AI uses your **Rumble.com identity** for authentication. Register with email and password at [rumble.com/register.php](https://rumble.com/register.php), or use Single Sign-On (Apple, Google, or Facebook) on the Rumble **Sign In** page (SSO also creates a new identity). After registration, the **Quake AI portal** at `portal.rumble.cloud` runs the welcome wizard: organization name, first project, datacenter, and resource tiles. Payment methods live under **Billing**. --- ### Q: What are the two separate websites I need to know about? [T1] Quake AI uses two distinct surfaces: | Surface | URL pattern | Purpose | |---|---|---| | **Portal** | `portal.rumble.cloud` | Manage organizations, projects, teams, billing, invoices, subscriptions, and help desk | | **Console** | `sky.us-east-1.rumble.cloud` (region-specific) | Provision and operate cloud resources (instances, networks, storage, Kubernetes) | You sign into both using your Rumble.com account. Billing, team membership, and plan changes happen in the portal; day-to-day infrastructure work happens in the console. --- ### Q: How do I enable two-factor authentication (2FA)? [T1] 2FA is managed at the Rumble.com level and applies across all Rumble platforms, including Quake AI. To enable it, go to [rumble.com/account/security/](http://rumble.com/account/security/) and select **Setup Two-Factor Authentication**. Email is the initial 2FA method; after enabling. You can optionally switch to SMS or an authenticator app. --- ## Core concepts ### Q: What is a project, and how does it compare to an AWS account? [T1] A **project** is Quake AI's billing and resource isolation unit, the boundary that owns resources, quotas, and billing records. It is the closest analog to an **AWS account** inside an AWS Organization. Key differences from AWS: - Quake AI projects live inside an **organization** (the billing entity), whereas AWS accounts are the billing entity directly. - Authorization inside a project uses **Keystone application credentials** with three roles (`admin`, `member`, `reader`), not IAM policies with JSON documents. No IAM-style policy language exists. - Projects are billed as a fixed monthly subscription tied to a **resource tier**, not per resource-hour. - You isolate environments (production, staging, tooling) into separate projects, not through IAM policies. --- ### Q: What is an organization? [T1] An **organization** groups related projects and team members under a single billing entity. You create an organization when you first set up your Quake AI account. One organization can hold multiple projects, each in a different datacenter region if needed. You manage the organization, its name, linked projects, and team roster, from the portal at `portal.rumble.cloud`. --- ### Q: What roles can team members hold, and at what level? [T1] Quake AI has roles at two levels: **Organization-level roles** (managed under **Organization** > **Team** in the portal): | Role | Manage org | Manage projects | Manage users | Billing access | |------|-----------|----------------|-------------|----------------| | **Owner** | Full | Full | Full | View + pay | | **Manager** | Full | Full | All except owners | View + pay | | **Member** | View | View (assigned only) | View | None | | **Billing Admin** | None | View | View | Full | **Project-level roles** (assigned when adding a member to a specific project): | Role | Access | |---|---| | **Project Reader** | Read-only access to compute resources (VMs, networks, routers, and volumes) | | **VM Admin** | Full read-write access to compute resources | | **Object Storage Admin** | Full read-write access to object storage resources | | **Project Admin** | Full read-write access to both compute and object storage | A team member must be added at the organization level before they can be assigned to a project. --- ### Q: What are application credentials, and how do they differ from AWS IAM? [T1] **Application credentials** are project-scoped secrets you generate to authenticate non-interactive workloads: CLI tools, CI/CD pipelines, Terraform, scripts, against the OpenStack API. They are backed by [OpenStack Keystone](https://docs.openstack.org/keystone/latest/). The key differences from AWS IAM: - **No policy language.** Authorization uses three coarse roles (`admin`, `member`, `reader`), not JSON policy documents with resource-level grants. - **Project-scoped, not account-wide.** A credential is valid only within the project it was created for. You separate blast radius with separate projects, not with policy conditions. - Treat each Quake AI project as its own trust boundary; production, staging, and tooling get separate projects when you need isolation that AWS would express with IAM policies. Generate application credentials from the console at **Generate application credentials** or via the CLI. --- ## Resource tiers and subscriptions ### Q: What is a resource tier, and what tiers are available? [T1] A **resource tier** is a billing category that defines the amount and type of resources bundled into your monthly project subscription. Three standard tiers are documented: | Tier | vCPUs | RAM | Block Storage | Object Storage | |---|---|---|---|---| | **Developer** | 1 shared | 1 GiB | 20 GiB NVMe | Add-on | | **OpenClaw Starter** | 4 shared | 4 GiB | 25 GiB NVMe | Add-on | | **Basic** | 4 dedicated | 16 GiB | 50 GiB NVMe | Add-on | All tiers include AMD EPYC processors, NVMe block storage, subnets, routers, security groups, outbound data transfer, and one public IP. Outbound network speed is up to 0.5 Gbps per 2 vCPUs. Tiers are billed monthly and can be upgraded, downgraded, or paused. See the [pricing reference](/docs/account/billing/pricing) for pack prices. The [Quake AI pricing page](https://www.quake.ai/pricing/) hosts the custom-package slider. --- ### Q: What is the difference between dedicated and shared vCPUs? [T1] - **Dedicated vCPUs** give you exclusive access to those vCPUs, with stable, guaranteed performance. Dedicated VM sizes step in multiples of two. Each dedicated vCPU can be used as 1 dedicated vCPU or as 4 shared vCPUs across VMs. - **Shared vCPUs** cost less and suit development and smaller projects. Performance is dynamic because shared vCPUs draw from dedicated capacity. Developer and OpenClaw Starter start on shared vCPUs. Basic starts on dedicated vCPUs. --- ### Q: How do I map a resource tier to the instance flavors I can launch? [T1] Your resource tier determines the total **quota** of vCPUs, RAM, block storage, and object storage available in the project. Within that quota you launch individual instances using **flavors** (named vCPU/RAM/disk combinations). For example, a Basic tier with 4 dedicated vCPUs and 16 GiB RAM can run dedicated flavors up to that quota, or shared-vCPU instances up to the shared conversion the pack allows. The console dashboard shows quota progress bars for compute, storage, network, and Kubernetes so you can see how much of your tier you have consumed. --- ### Q: Can I customize my resource tier beyond the standard tiers? [T1] Yes. You can add and remove individual vCPUs, memory, block storage, object storage, and additional public IPv4 addresses from the **Projects** > **``** view in the portal. The online checkout process shows your total cost as you customize. Use the [pricing calculator](https://www.quake.ai/pricing/) to assemble and price a custom package before committing. --- ### Q: How do I upgrade, downgrade, or pause a subscription? [T1] All subscription changes are made in the **Quake AI portal** under **Projects** > **``**: - **Upgrade / downgrade:** Select the new resource tier or adjust individual add-ons, then proceed to checkout and confirm. - **Pause:** Reduce all vCPUs, memory, block storage, and object storage to zero so your charge drops to $0.00. You must delete any provisioned VMs, networks, routers, storage, and other cloud components before pausing. You can resume by adding resources back through the same checkout flow. - **Cancel / full account deletion:** Contact **support.cloud@rumble.com**. --- ## Billing operations ### Q: How does billing work? [T1] Quake AI uses **resource-based monthly billing**: you pay a fixed monthly amount for the subscription plan and any add-ons you choose, not per virtual machine or per hour within that plan. Invoices are issued on a **monthly** cycle at the start of each billing period. No separate egress charges apply: **unlimited data transfer** is included in every plan. Add-ons (additional object storage, extra public IPs) appear as line items on your invoice alongside the base plan. --- ### Q: What payment methods are accepted? [T2] The portal accepts credit card payments. You manage payment methods under **Billing**, then **Payment Methods**: add a new card, delete an existing one, or replace the card on file. For accepted card networks, or for non-card payment options (bank transfer, wire, purchase order) in an enterprise procurement context, contact [support.cloud@rumble.com](mailto:support.cloud@rumble.com) before you sign. --- ### Q: How do I view and download my invoices? [T1] 1. Sign into the portal at `portal.rumble.cloud`. 2. Open **Billing**, then **Invoices** (or **All Invoices**). 3. You will see a list of invoices with invoice date, due date, status, and amount due. 4. Select an invoice to view details. Use **Download** for a PDF or **Print** to print from your browser. You can also view **sales orders** (subscription records) under **Billing**, then **Subscriptions**. --- ### Q: Is there a money-back guarantee? [T1] Named monthly plans include a **30-day money-back guarantee**. The full terms, including any exclusions for add-ons, partial months, or mid-period plan changes, are governed by Quake AI's commercial terms at [rumble.cloud/legal](https://rumble.cloud/legal). For a written copy of the current terms before you sign, contact [support.cloud@rumble.com](mailto:support.cloud@rumble.com). --- ## Dashboard and portal operations ### Q: What does the console dashboard show? [T1] The console dashboard is the landing page after you log into the Quake AI console (`sky..rumble.cloud`). It displays your project's resource usage as **quota progress bars** across five categories: - **Compute:** instances, vCPUs, memory, key pairs, server groups - **Block Storage:** volumes, volume capacity, volume snapshots - **Network:** routers, networks, subnets, floating IPs, ports, security groups, security group rules - **Object Storage:** containers (buckets), objects - **Kubernetes:** clusters Quick-access tabs let you jump directly to instances, volumes, networks, and routers. --- ### Q: How do I switch between multiple projects? [T1] Each project has a dedicated console URL (e.g., `sky.us-east-1.rumble.cloud`). To open a project, go to the portal, navigate to **Projects** > **``**, and select **Open Cloud Project**: a new browser window opens pre-authenticated to that project's console. You can work across multiple projects by keeping separate browser windows open, each pointing to a different project's console URL. --- ## Migration from AWS ### Q: What is the equivalent of an AWS account on Quake AI? [T1] The **project** is the closest equivalent to an AWS account: it is the billing and resource isolation unit, holds all resources, and is where quotas apply. AWS nests accounts under Organizations with centralized IAM; on Quake AI, projects live inside an **organization**, and identity is managed by Keystone, not IAM. For a full service-by-service mapping, see [Coming from AWS](/resources/migration/coming-from-aws). --- ## Pricing, quotas, availability, and support ### Q: What regions and availability zones is the account/billing service available in? [T2] The portal and billing services are global, accessible from any browser at `portal.rumble.cloud` regardless of which region your resources live in. Resources themselves are region-scoped: when you create a project you pick the region (`us-east-1`, `us-east-2`, or `us-west-1`) it lives in, and the per-project console URL becomes region-specific (`sky..rumble.cloud`). Quake AI uses regions, not availability zones. See [Regions](/docs/platform#regions) for the current region table and console URLs. --- ### Q: What is the SLA for account and billing services? [T2] The contractual availability targets and credit schedule for the platform are published as part of Quake AI's commercial terms at [rumble.cloud/legal](https://rumble.cloud/legal). The [Service Level Agreement page](/docs/account/sla) explains how to read those terms and how to file a credit claim. Credits are not automatic; they require a claim filed within the window the SLA specifies, with the project ID, region, time window, and resource identifiers. --- ### Q: How do I get help if something is broken or I have a billing dispute? [T2] For technical issues, start at [Get help](/docs/get-help), then open a ticket from **Help Desk** in the portal or [open a support ticket](https://rumble.cloud/support) if the self-service path does not resolve the issue. For billing questions you can also leave messages in **Billing** under **Subscriptions** or **Invoices** via **Communication history**. For account deletion or other account-lifecycle requests, contact [support.cloud@rumble.com](mailto:support.cloud@rumble.com). --- ## See also - [Account & Billing overview](/docs/account): starting point for all account, project, and billing tasks - [Manage your account](/docs/account/guide): account setup, 2FA, organization management, team roles - [Manage cloud projects](/docs/account/projects): project creation, team assignment, upgrade/downgrade/pause - [Resource Tiers](/docs/account/resource-tiers): tier specs, Developer Plan details, dedicated vs. shared vCPUs - [Manage cloud subscriptions](/docs/account/subscriptions): view subscription details, invoices, sales orders - [How billing works](/docs/account/billing/how-billing-works): monthly model, what appears on your invoice, money-back guarantee - [Pricing Reference](/docs/account/billing/pricing): plan and add-on prices, always-included list, cost estimator - [Manage your subscription](/docs/account/billing/manage-subscription): update payment method, change plan, cancel - [Console Dashboard](/docs/account/dashboard): quota progress bars for all resource categories - [Portal Console](/docs/account/portal): portal navigation reference - [How to sign out](/docs/account/sign-out): closing your console session - [Pricing transparency](/docs/platform#pricing): fixed vs. per-second pricing, worked examples against AWS - [Coming from AWS](/resources/migration/coming-from-aws): AWS account → project, IAM → application credentials - [Quake AI pricing page](https://www.quake.ai/pricing/): authoritative current pricing and interactive calculator