Quake AI uses your Rumble.com identity for authentication. Register with email and password at 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.

Quake AI uses two distinct surfaces:

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.

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/ and select Setup Two-Factor Authentication. Email is the initial 2FA method; after enabling. You can optionally switch to SMS or an authenticator app.

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.

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.

Quake AI has roles at two levels:

Organization-level roles (managed under Organization > Team in the portal):

Project-level roles (assigned when adding a member to a specific project):

A team member must be added at the organization level before they can be assigned to a project.

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.

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.

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:

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 for pack prices. The Quake AI pricing page hosts the custom-package slider.

• 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.

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.

Yes. You can add and remove individual vCPUs, memory, block storage, object storage, and additional public IPv4 addresses from the Projects > <your-project> view in the portal. The online checkout process shows your total cost as you customize. Use the pricing calculator to assemble and price a custom package before committing.

All subscription changes are made in the Quake AI portal under Projects > <your-project>:

• 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 [email protected].

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.

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 [email protected] before you sign.

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.

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. For a written copy of the current terms before you sign, contact [email protected].

The console dashboard is the landing page after you log into the Quake AI console (sky.<region>.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.

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 > <your-project>, 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.

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.

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.<region>.rumble.cloud). Quake AI uses regions, not availability zones. See Regions for the current region table and console URLs.

The contractual availability targets and credit schedule for the platform are published as part of Quake AI's commercial terms at rumble.cloud/legal. The Service Level Agreement page 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.

For technical issues, start at Get help, then open a ticket from Help Desk in the portal or open a support ticket 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 [email protected].