Skip to content

Knowledge catalog

Generated reference

Read-only pages rendered from the Quake AI knowledge graph.

Published pages, services, concepts, and competitor analogs in one graph. Search or pick a service to explore its neighborhood; related pages appear beside the graph. Authoring lives in the documentation; the catalog renders the graph model read-only.

No active filter.
Nodes
1,647
Edges
11,535
Pages
548
Services
13
Concepts
185
Competitor analogs
517

Start here

Product documentation organised by service area. Quickstart, platform overview, compute, network, storage, kubernetes, automation, and more.

283pages
Quickstart

Pick a starting path on Quake AI: deploy an app, provision with an AI assistant, or launch your first server. Each path ends in a working result you can keep.

  • Add persistent storage to your server04.06.2026

    In this tutorial, you create a block storage volume, attach it to a running virtual machine, format and mount it, and configure the server to remount it automatically after a reboot. By the end, you...

  • Automate your infrastructure with OpenTofu26.05.2026

    In this tutorial, you recreate the infrastructure from the Launch your first server tutorial, but entirely through code using OpenTofu. By the end, you will have a working OpenTofu project that...

  • Deploy a containerized web application04.06.2026

    In this tutorial, we deploy a containerized web application to Quake AI. By the end, you will have a running Docker container serving a web page on a cloud instance, accessible from the internet...

  • Deploy a database sandbox26.05.2026

    Set up a database on a Quake AI VM for prototyping and local development. Choose between SQLite (zero overhead, file-based) and PostgreSQL (tuned for low-RAM tiers).

  • Deploy an API service04.06.2026

    Run a lightweight API server on a Quake AI VM: either Node.js (Express) or Python (Flask). The API runs as a systemd service so it starts automatically on boot and restarts on failure.

  • Host a static website on Quake AI04.06.2026

    In this tutorial, we deploy a static website served by Nginx on a Quake AI instance. By the end, you will have a publicly accessible web page served from your own cloud server, with a public IP you...

  • Launch your first server07.07.2026

    The fundamentals path: launch a Developer-plan instance on Quake AI, open the right ports, and serve a public web page over SSH in about 30 minutes.

  • Set up automated backups to Quake AI04.06.2026

    In this walkthrough, you build a complete backup pipeline that copies your project files to Quake AI object storage on a schedule. By the end, you will have rclone configured as a Quake AI remote, an...

  • Store and retrieve files with S3-compatible object storage04.06.2026

    In this tutorial, we create S3 credentials, configure the AWS CLI to point at Quake AI's object storage endpoint, create a storage container, upload and download files, and apply a basic access...

Platform

Quake AI is a US-based public cloud built on OpenStack, offering compute, networking, storage, and Kubernetes through standard OpenStack APIs.

  • How the platform validates its content

    How the Quake AI developer platform keeps documentation, infrastructure templates, and launch manifests accurate: live-platform checks, continuous integration gates, regenerated machine-readable surfaces, and manifest validation.

  • Ways to build on Quake AI

    The common ways to build on Quake AI, from the Console to infrastructure as code, containers, Kubernetes, and AI-assisted development, with the rationale for each and who it fits.

Compute

Create and manage virtual machine instances on Quake AI: choose an image and flavor, connect to project networks, and snapshot, resize, or destroy.

  • Compute FAQNewHub08.09.2026

    Frequently asked questions about Quake AI Compute: instances, flavors, images, key pairs, snapshots, networking, and migration.

  • Concepts

    Background and rationale for the Compute service primitives. Read these to understand what each piece is, how the platform composes them into a running instance, and how to think about availability...

    • Apps23.06.2026

      Apps is a deployment feature in the Compute section of the Console (Compute > Apps). You pick an app from the catalog, and the platform provisions an instance from a pre-built image with the...

    • cloud-init and first-boot configuration19.06.2026

      cloud-init is the industry-standard first-boot agent that runs inside Linux and BSD guests. When you launch an instance, Compute (OpenStack Nova) passes user data to the guest. cloud-init reads that...

    • Flavors23.06.2026

      Flavors define the resource shape of an instance: vCPU count, memory, root disk size, and optional ephemeral or swap storage. The Compute service (OpenStack Nova) exposes flavors as named resource...

    • High Availability on Quake AI23.06.2026

      A single instance running your application is a single point of failure. When that instance goes down (planned maintenance, hardware fault, or software crash), your users see an outage. High...

    • Images23.06.2026

      Images give each new instance the same starting point: operating system, tooling, and baseline configuration. The Images service (OpenStack Glance) lets you discover, register, and retrieve virtual...

    • Instance SnapshotsHub23.06.2026

      Instance snapshots capture the full state of a running instance (root disk data, memory, and configuration) as an image you can store, clone from, or restore to. They are part of the Compute service...

    • InstancesHub23.06.2026

      Instances are virtual machines (VMs) that run on Quake AI. They give you isolated compute (CPU, memory, disk, and network), so you deploy applications and services inside projects without sharing an...

    • Key pairs23.06.2026

      Key pairs are the default way you prove you are allowed to log in to Linux instances without sending a password over the network. Quake AI stores the public half and injects it into the guest; you...

    • Self-Hosted AI on Cloud Infrastructure23.06.2026

      Self-hosted AI means running language models on infrastructure you control. Your prompts and completions stay on your network. You pay a fixed compute cost (not per token), and you can run open-weight...

    • Server Groups23.06.2026

      Server groups apply placement policies (affinity or anti-affinity) that control whether your instances land on the same physical host or are spread across different hosts. The Compute service...

    • Also known as
      • AMIs and machine images25.06.2026

        An AWS AMI (Amazon Machine Image) is a boot template for EC2. On Quake AI the same role is an image in the Images service (OpenStack Glance): a disk template with metadata (minimum disk, OS family)...

      • Droplets on Quake AI25.06.2026

        A DigitalOcean Droplet is a Linux or Windows VM with a fixed plan size and a proprietary control API. On Quake AI the same role is an instance created through Nova: you pick a flavor, an image...

      • EC2 on Quake AI25.06.2026

        Amazon EC2 is AWS compute. On Quake AI the equivalent workload runs as Nova instances in a project, sized with flavors, booted from images, and reached over networks and security groups.

      • Servers (compute instances)25.06.2026

        When documentation or the OpenStack CLI says server, it means a compute instance on Quake AI: a running virtual machine backed by Nova, not a physical rack server and not a server group placement...

      • Snapshots (instance vs volume)25.06.2026

        Snapshot means different things depending on which service creates it. On Quake AI, separate the two cases before you plan backup or migration.

      • SSH keys on Quake AI25.06.2026

        SSH keys in migration guides and provider consoles map to key pairs on Quake AI: a stored public key Nova injects at instance boot through cloud-init, paired with the private key you keep on your...

      • Virtual machines (VMs)25.06.2026

        On Quake AI, a virtual machine (VM) is an instance: an isolated guest OS running on the Compute service with its own vCPU, memory, disk, and network attachments. Console copy, billing, and most...

  • How-to

    Procedural guides for the Compute service: launching instances on public or private networks, managing images and snapshots, accessing the VM console, and running Windows Server. For background on the...

  • Apps

    Tutorials for deploying open-source applications on a Quake AI VM through the Console Apps installer. Each guide provisions an instance and walks the application's first-run setup over SSH. For the...

    • Deploy OpenClaw on Quake AI19.05.2026

      This guide walks you through deploying OpenClaw, the open-source AI agent framework with 337,000+ GitHub stars, on Quake AI using the Console Apps installer. You deploy OpenClaw by connecting to a new...

  • Migration

    You move virtual machines and compute workloads to Quake AI from another provider. Major cloud providers do not offer one-click VM migration to OpenStack, so you use rebuild and rsync: you provision a...

Network

Connect Quake AI workloads with isolated project networks, subnets, routers, floating IPs, and security group firewall rules.

  • Network FAQNewHub08.09.2026

    Frequently asked questions about Quake AI Network: networks, subnets, routers, floating IPs, security groups, TLS, and cloud migration.

  • Concepts

    Background and rationale for the building blocks that make up the Network service. Read these to understand what each primitive is, how it relates to the others, and why the platform models networking...

    • Floating IPsHub23.06.2026

      The Network service (OpenStack Neutron) implements floating IPs as public addresses you attach to an instance on a private network when you need reachability from the internet or another external...

    • IP address management23.06.2026

      Instances on Quake AI receive at least one private IP address from the subnet they connect to. How that address is allocated, how it reaches the guest OS, and what happens when you need multiple...

    • NetworksHub23.06.2026

      Networks are isolated Layer 2 segments that give your instances connectivity. Instances attach to at least one network; most production deployments use private networks with routers and floating IPs...

    • Ports23.06.2026

      The Network service (OpenStack Neutron) implements ports as the logical attachment between a network and a device, most often a VM’s virtual NIC, but also router interfaces and other integrations...

    • Routers23.06.2026

      The Network service (OpenStack Neutron) implements routers as virtual layer-3 gateways inside your project. They connect private subnets to each other and, when you set an external gateway, to...

    • Security Groups23.06.2026

      The Network service (OpenStack Neutron) implements security groups as stateful packet filters attached to instance ports. Each rule describes allowed traffic by direction (ingress or egress), IP...

    • Also known as
      • Cloud firewalls on Quake AI25.06.2026

        Provider firewalls, security lists, and cloud firewalls filter traffic to VMs. On Quake AI port-level rules are security groups in the Network service (OpenStack Neutron).

      • Elastic IPs and static public addresses25.06.2026

        Elastic IP (AWS), reserved IP (DigitalOcean), static external IP (GCP), and public IP (Azure) names all describe a stable public address you attach to a workload. On Quake AI that role is a floating...

      • VPC on Quake AI25.06.2026

        Quake AI does not expose a single object named VPC or virtual private cloud. The same job is done with networks (including subnets as IP ranges inside a network), routers (routing and NAT between...

  • How-to

    Procedural guides for the Network service: provisioning networks and subnets, attaching routers, allocating floating IPs, defining security groups, configuring DNS, and protecting public endpoints...

  • Migration

    Move your networking configuration to Quake AI from another provider. Quake AI's network layer runs OpenStack Neutron with OVN as the SDN backend, providing software-defined networking with five core...

    • Migrate from AWS VPC to Quake AI22.06.2026

      AWS VPC exposes more networking primitives than the other major cloud providers, so it has the largest gap to bridge when migrating to Quake AI. The core shift: AWS layers subnets, an Internet...

    • Migrate from Azure VNet to Quake AI22.06.2026

      Azure's networking model introduces these constructs with no direct Neutron equivalent: the dual NSG layer (subnet-level and NIC-level), User Defined Routes for traffic inspection, Application Gateway...

    • Migrate from DigitalOcean VPC to Quake AI22.06.2026

      DigitalOcean's networking model is among the simplest of the major cloud providers and maps most cleanly to Quake AI's OpenStack Neutron. Cloud Firewalls are stateful and allow-only (matching Neutron...

    • Migrate from GCP VPC to Quake AI22.06.2026

      GCP's global VPC model is architecturally unique among cloud providers and requires the most significant conceptual restructuring for migration. A single GCP VPC spans all regions within a project...

    • Migrate from Hetzner Cloud Networks to Quake AI22.06.2026

      Hetzner Cloud's private networking, firewall, and floating IP models map closely to Quake AI's OpenStack Neutron. The primary structural addition on Quake AI is the explicit router object: Hetzner...

    • Migrate from Linode VPC and Cloud Firewall to Quake AI

      Linode (now branded Akamai Cloud Computing) exposes a compact networking surface: a VPC that bundles a network and a single subnet, a free intra-region L2 VLAN for private traffic, a stateful Cloud...

    • Migrate from Vultr VPC 2.0 and Firewall Groups to Quake AI

      Vultr exposes a compact networking surface: VPC 2.0, account-level Firewall Groups, Reserved IPs, and Vultr Load Balancers. Quake AI's OpenStack Neutron provides explicit networks, subnets, routers...

Block Storage (Volumes)

Create persistent NVMe-backed block volumes on Quake AI, attach them to instances, and snapshot, extend, clone, or transfer them between projects.

  • Block Storage (Volumes) FAQNewHub08.09.2026

    Frequently asked questions about Quake AI Block Storage (Volumes): creating and attaching volumes, snapshots, clones, resizing, ownership transfers, migration from other providers, and troubleshooting.

  • Concepts

    Background on Quake AI block storage: what a volume is, how it attaches to an instance, how snapshots and clones differ, and what survives instance deletion. For step-by-step procedures, see the...

    • VolumesHub23.06.2026

      Applications need storage that survives reboots, instance deletions, and infrastructure changes. Volumes provide that: persistent block storage devices that attach to instances, behave like physical...

    • Also known as
      • Disks and persistent storage25.06.2026

        When guides say disk, persistent disk, or block storage, they usually mean a detachable volume that survives instance reboots. On Quake AI that object is a volume in the Block Storage service...

  • How-to

    Procedural guides for block storage volumes: creating, resizing, cloning, snapshotting, and transferring volumes between projects. For background on volume lifecycle and how snapshots and clones...

Databases

Run PostgreSQL and MySQL/MariaDB on Quake AI: compute instances with a dedicated Block Storage data volume, private network access, and scheduled logical backups.

  • Concepts

    Background on how relational databases compose Compute, Block Storage, and Network on Quake AI, how clients reach them, and how backups and recovery work.

    • Database backup and recovery

      The recovery layers available to a self-managed database on Quake AI: scheduled logical dumps, volume snapshots, off-instance copies in Object Storage, and restore drills.

    • Database networking and access

      How applications and administrators reach a database on a Quake AI private subnet: private addressing, security group scope, database ports, and bastion paths.

    • Self-managed relational databases

      How a PostgreSQL or MySQL/MariaDB deployment on Quake AI composes a compute instance, a Block Storage data volume, a private network, and a security group.

  • How-to

    Procedures for deploying, connecting to, backing up, restoring, and branching PostgreSQL and MySQL/MariaDB databases on Quake AI.

  • Migration

    Move an existing PostgreSQL, MySQL, or MariaDB database onto Quake AI with a dump, transfer, restore, and verification pass.

    • How to migrate MySQL or MariaDB to Quake AI

      Move an existing MySQL or MariaDB database onto a Quake AI instance: check engine compatibility, dump the source, transfer through a bastion, restore, verify, and cut over.

    • How to migrate PostgreSQL to Quake AI

      Move an existing PostgreSQL database onto a Quake AI instance: check versions, dump the source, transfer the dump through a bastion, restore, verify, and cut the application over.

Object Storage (S3-compatible)

Store and retrieve unstructured data on Quake AI's S3-compatible object storage using standard S3 SDKs and tools, backed by OpenStack Swift.

Kubernetes

Provision Kubernetes clusters on Quake AI from reusable templates: the platform creates master nodes, worker nodes, and networking with Magnum.

  • Kubernetes FAQNewHub08.09.2026

    Frequently asked questions about Quake AI Kubernetes: cluster provisioning via Magnum, cluster templates, lifecycle, high availability, migration from EKS/AKS/GKE/DOKS/Hetzner, and troubleshooting.

  • Concepts

    Background on Kubernetes on Quake AI: how the platform provisions clusters, what your team operates versus what the platform handles, and how cloud-native patterns map to Quake AI's primitives. For...

    • Cloud-Native Computing on Quake AI23.06.2026

      Traditional application deployment is straightforward: install software on a server, configure it, run it. That model works until you need to scale to multiple instances, deploy updates without...

    • Kubernetes on Quake AIHub23.06.2026

      The Quake AI Kubernetes service (OpenStack Magnum) automates cluster provisioning on top of existing Compute, Network, and Storage infrastructure. You define the cluster shape through a reusable...

    • Also known as
      • Kubernetes clusters25.06.2026

        A Kubernetes cluster is a control plane plus worker nodes that run your container workloads. On Quake AI you provision clusters through the Kubernetes service (OpenStack Magnum) or by running...

  • How-to

    Procedural guides for the Kubernetes service: defining a cluster template, creating a cluster, and managing it day to day. For background on how Quake AI provisions Kubernetes (OpenStack Magnum), see...

  • Migration

    Move your Kubernetes workloads to Quake AI from a managed Kubernetes provider or from a self-managed setup on another cloud. The core shift in most migrations is from a provider-operated control plane...

Automation

Define Quake AI infrastructure as code with OpenTofu or Terraform for provisioning, and Ansible for configuration management and deployment.

Access & Credentials

Access Quake AI programmatically with the REST APIs and command-line tools, and manage the credentials and tokens that authenticate your requests.

  • Add an SSH key pair to your account04.06.2026

    One of the first things to do in Quake AI is to set up an SSH key pair.

  • API Access Console Reference22.06.2026

    The API section in the Quake AI console ({CONSOLE_REGION_URL}/papi/*) provides tools for managing programmatic access to your cloud project. It contains three pages (S3 Credentials, App Credentials...

  • API changelog19.05.2026

    > Changes to the Quake AI API surface. For product and feature updates, see the product changelog. For documentation edits, see the docs changelog.

  • API Endpoints23.05.2026

    Select API > API Endpoints to display the APIs dashboard.

  • API rate limits18.05.2026

    Quake AI distinguishes between two types of limits that affect API usage: resource quotas (how many resources you can create) and API rate limits (how many requests you can send per time window)...

  • API Versions and Microversions19.05.2026

    Quake AI runs OpenStack 2023.1 (Antelope). The SLURP upgrade path is Antelope → Caracal (skip-level).

  • Application Credentials19.06.2026

    Select API > App Credentials ({CONSOLE_REGION_URL}/papi/application-credentials) to manage application credentials for your current project.

  • Credentials and tools

    How the OpenStack CLI, application credentials, API tokens, S3 credentials, and SSH keys relate: what each authentication surface is, what it reaches, how scoping works, and which tool consumes it.

  • How to create application credentials22.06.2026

    Create application credentials to authenticate against the OpenStack API without using your account password. Application credentials are the recommended authentication method for CI/CD pipelines...

  • How to debug CLI errors25.05.2026

    The openstack CLI communicates with Quake AI APIs over HTTP. When a command fails, the error may originate from your local configuration, network connectivity, authentication, or the remote API. This...

  • How to get an API token19.06.2026

    Generate a project-scoped API token from the Quake AI console to authenticate direct HTTP requests against OpenStack service endpoints. Tokens are issued by the Identity service (Keystone), scoped to...

  • Install OpenStack Client03.06.2026

    OpenStack client is a tool you can install on your local computer. Using the client, you'll be able to run commands on services in your Quake AI projects.

  • OpenStack Client04.06.2026

    Looking for the full command reference? See the CLI Reference for curated per-service commands, S3-compatible storage tools, and Quake AI-specific context.

  • S3 Credentials22.06.2026

    Select API > S3 Credentials ({CONSOLE_REGION_URL}/papi/s3-credentials) to manage your S3-compatible object storage credentials.

  • Service Endpoints25.05.2026

    Quake AI exposes supported OpenStack services at dedicated hostnames following the pattern {service}.{region}.rumble.cloud. This page lists the public service endpoint base URLs and explains how to...

  • Set Up a Linux CLI Environment on Windows04.06.2026

    The CLI examples throughout this documentation use bash, the default shell on Linux and macOS. If your local machine runs Windows, you need a Linux-compatible shell environment before following CLI...

Operate

Monitor, troubleshoot, and maintain workloads running on Quake AI, with operational runbooks for keeping your infrastructure healthy in production.

Security

Understand the Quake AI shared responsibility model: the platform secures the infrastructure while you protect your workloads, data, and access.

  • Quake AI: Compliance & CertificationsHub25.06.2026

    This page lists the compliance attestations Quake AI currently holds, and the regulatory frameworks it does not currently hold.

  • Secrets management23.06.2026

    Managing credentials securely is a core part of operating workloads on any cloud platform. Quake AI uses distinct credential types, each with different scopes, lifetimes, and rotation requirements...

  • Security hardening checklist18.06.2026

    Use this checklist to audit and harden your Quake AI project. Each item links to the relevant documentation for implementation details. Work through the sections in order: project-level controls...

  • Shared responsibility modelHub23.06.2026

    Security on Quake AI is a partnership between the platform and you. Quake AI secures the infrastructure that runs all services: physical hardware, hypervisors, network backbone, and the control plane...

  • How-to
Account & Billing

Manage your Quake AI account, projects, subscriptions, and billing across the Cloud Console and the portal at portal.rumble.cloud.

  • Account & Billing FAQNewHub16.09.2026

    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.

  • Account modelNew16.09.2026

    How Rumble.com identity, organizations, projects, resource tiers, team roles, and application credentials fit together, and how the portal and console divide responsibilities.

  • Console Dashboard04.06.2026

    The console dashboard is the landing page after you log in to the Quake AI console. It summarizes your project's resource usage, with quota progress bars for compute, storage, network, and Kubernetes.

  • How to sign out21.05.2026

    From the cloud console, select Account > Sign Out.

  • Manage cloud projectsNew16.09.2026

    New to Quake AI? The Get started sequence in the Quickstart walks creating your first project and picking a tier. This page is the reference for project management in the portal.

  • Manage cloud subscriptionsNew16.09.2026

    You'll manage your cloud subscription from the Quake AI portal.

  • Manage your accountNew16.09.2026

    Quake AI authenticates you with a Rumble.com identity. After you register, the portal at portal.rumble.cloud creates your organization, first project, and billing records.

  • Portal ConsoleNew16.09.2026

    The Quake AI portal at portal.rumble.cloud is the management interface for your account, organizations, projects, teams, billing, and help desk. The portal is separate from the cloud console (for...

  • Resource TiersNew16.09.2026

    Resource tiers are billing packs that set how much compute, memory, and block storage a project subscription includes.

  • Service Level Agreement

    Where to find Quake AI's Service Level Agreement, what it covers, and how to file a credit claim.

  • Also Known As
    • IAM and identity on Quake AI25.06.2026

      IAM on AWS, Cloud IAM on Google Cloud, and Microsoft Entra ID on Azure centralize users, roles, and API access for an entire cloud estate. On Quake AI identity flows through Rumble.com sign-in...

  • Billing

    The Quake AI account portal handles billing and subscriptions: manage subscriptions, invoices, and payments there. You do not manage billing from the docs site.

Utilities
  • Glossary08.05.2026

    Affinity specifies that instances within a server group are co-located on the same host or hosts. Anti-affinity specifies that instances within the server group are distributed across different hosts...

  • Changelog25.06.2026

    Platform and infrastructure updates for Quake AI. For OpenStack API changes, see the API changelog.

  • Docs changelog30.06.2026

    All notable documentation changes in reverse chronological order, following Keep a Changelog.

  • Usage guidelines

    This page sets the terms under which Quake AI publishes sample code, command line transcripts, infrastructure-as-code templates, proofs of concept, configuration snippets, and other technical content...

  • Get help23.06.2026

    Where to start when something on Quake AI fails: status, troubleshooting, support tickets, and what evidence to bring.

Real workloads you stand up from a validated template, grouped by topic.

71pages
Deployments
Getting Started
Edge & Gateways
AI & Machine Learning
  • Run a Local LLM with Ollama26.05.2026

    Stand up Ollama on a Quake AI instance for local LLM inference. You run the model runtime yourself; this is a self-hosted inference endpoint you operate, not a managed model API.

  • Add a Browser Interface to Ollama with Open Webui26.05.2026

    Stand up Open WebUI on the same Quake AI instance as Ollama. Open WebUI provides a browser chat UI with conversation history, model switching, and file uploads, backed by models on your instance.

  • Deploy a Vector Database with Qdrant26.05.2026

    Stand up Qdrant on a Quake AI instance for vector search, embedding storage, and retrieval-augmented generation. You run the database yourself; this is a self-hosted vector store you operate, not a...

  • Build a RAG Pipeline with Ollama and Qdrant26.05.2026

    Stand up a retrieval-augmented generation pipeline on Quake AI by composing Ollama inference with Qdrant vector search. You ingest documents, embed chunks with Ollama, store vectors in Qdrant, and...

  • Deploy an AI Agent26.05.2026

    Stand up an AI agent framework on a Quake AI instance using Docker Compose. An agent connects a language model to tools, memory, and external services. You control the model provider, data, and...

  • Deploy an Inference Gateway with OpenTofu

    Stand up a LiteLLM model router on one CPU VM with a single OpenAI-compatible HTTPS endpoint using the inference-gateway OpenTofu template.

  • Deploy a Bursty-gpu Control Plane with a Queue and Workers

    Run the durable control plane on Quake AI CPU compute: a Redis or Valkey queue and a worker process accept jobs, submit each one to a third-party GPU or model API, poll for completion, retry on failure, and land results in Object Storage. The queue and workers stay always-on and cheap; the GPU work runs on a provider you choose.

  • Deploy Mlflow with the Mlflow Template

    Stand up MLflow, an open-source experiment-tracking and model-registry platform, on a single Quake AI instance using the validated OpenTofu template mlflow. You apply the template, wire it to an...

Data & Analytics
  • Deploy Metabase with the Metabase Template

    Stand up Metabase, an open-source BI tool, on a single Quake AI instance using the validated OpenTofu template metabase. You apply the template, complete the setup wizard, connect a warehouse, and...

  • Deploy Superset with the Superset Template

    Stand up Apache Superset on a single Quake AI instance using the validated OpenTofu template superset. You run it yourself; this is a self-hosted tool you operate, not a managed service.

  • Deploy Airflow with the Airflow Template

    Stand up Apache Airflow, an open-source workflow orchestration platform, on a single Quake AI instance using the validated OpenTofu template airflow. You apply the template, read the generated admin...

  • Deploy Streamlit with the Streamlit Template

    Stand up Streamlit, a Python framework for data apps and interactive demos, on a single Quake AI instance using the validated OpenTofu template streamlit. You apply the template, open the sample app...

  • Deploy Airbyte with the Airbyte Template

    Stand up Airbyte, an open-source extract-and-load platform, on a single Quake AI instance using the validated OpenTofu template airbyte. You apply the template, reach the web UI over the floating IP...

  • Deploy Clickhouse with the Clickhouse Template

    Stand up ClickHouse, a fast analytical column store, on a single Quake AI instance using the validated OpenTofu template clickhouse. You apply the template, read the bootstrap credentials, connect...

  • Deploy Trino with the Trino Template

    Stand up Trino, an open-source federated SQL query engine, on a single Quake AI instance using the validated OpenTofu template trino. You apply the template, run a smoke-test query against the...

  • Deploy Feast with the Feast Template

    Stand up Feast, an open-source feature store, on a single Quake AI instance using the validated OpenTofu template feast. You apply the template, confirm the bundled Postgres and Redis containers...

  • Run Dbt Transforms as a Scheduled Job01.07.2026

    Compose the Airflow and self-managed PostgreSQL templates to run dbt Core in a container on a schedule against your warehouse.

  • Deploy Redpanda with the Redpanda Template

    Stand up Redpanda, an open-source Kafka-API streaming broker, on a single Quake AI instance using the validated OpenTofu template redpanda. You apply the template, create a topic, produce and consume...

Web Apps & Services
Storage & Datastores
Creator & Media
Infrastructure as Code

Concept translation and phased migration guides per source provider.

22pages
Migration25.06.2026

Evaluate Quake AI against your current provider and move workloads, with service mappings from AWS, Azure, GCP, DigitalOcean, and Hetzner.

By Workload
AWS
  • Coming from AWSHub22.06.2026

    If you have been using AWS, here is how Quake AI maps to what you already know. Quake AI runs on OpenStack: the services below expose standard OpenStack APIs with upstream documentation. When a CLI...

  • Migrating from AWS to Quake AI22.06.2026

    This guide walks you through moving workloads from AWS to Quake AI, service by service. If you have not reviewed the concept differences between the two platforms, start with Coming from AWS for the...

  • OpenStack for AWS DevelopersHub23.06.2026

    OpenStack is an open-source cloud computing platform used by thousands of organizations, from CERN to Walmart to government agencies. Quake AI runs on OpenStack, so Quake AI APIs follow standard...

Azure
  • Coming from AzureHub22.06.2026

    If you have been using Microsoft Azure, here is how Quake AI maps to what you run today. Quake AI maps compute, storage, networking, and identity to OpenStack-backed services with fixed monthly...

  • Migrating from Azure to Quake AI22.06.2026

    This guide walks you through moving workloads from Microsoft Azure to Quake AI, service by service. Object storage has a dedicated how-to guide. Practical notes below cover compute, networking, and...

DigitalOcean
  • Coming from DigitalOceanHub22.06.2026

    If you have been using DigitalOcean, here is how Quake AI maps to what you run today. Quake AI maps compute, storage, networking, and Kubernetes to OpenStack-backed services with fixed monthly pricing...

  • Migrating from DigitalOcean to Quake AI22.06.2026

    This guide walks you through moving workloads from DigitalOcean to Quake AI, service by service. If you have not reviewed the concept differences, start with Coming from DigitalOcean for the full...

GCP
  • Coming from GCPHub22.06.2026

    If you have been using Google Cloud Platform, here is how Quake AI maps to what you run today. Quake AI maps compute, storage, networking, and identity to OpenStack-backed services with fixed monthly...

  • Migrating from GCP to Quake AI22.06.2026

    This guide walks you through moving workloads from Google Cloud Platform to Quake AI, service by service. Object storage has a dedicated migration how-to guide. Practical notes below cover compute...

Hetzner
  • Coming from Hetzner CloudHub22.06.2026

    If you have been using Hetzner Cloud, here is how Quake AI maps to what you run today. Quake AI maps compute, storage, networking, and Kubernetes to OpenStack-backed services with fixed monthly...

  • Migrating from Hetzner Cloud to Quake AI22.06.2026

    This guide walks you through moving workloads from Hetzner Cloud to Quake AI, service by service. Hetzner has a well-developed cross-service migration path: both the IaC and object storage guides...

Linode
Vultr
  • Coming from Vultr

    If you have been running on Vultr, you already know the primitives: Cloud Compute and Bare Metal instances, Block Storage, Object Storage (S3-compatible), VPC 2.0, Firewall Groups, Load Balancers, and...

  • Migrating from Vultr to Quake AI

    This guide walks you through moving workloads from Vultr to Quake AI, service by service. The two platforms share a self-managed ethos, so most migrations are a translation of API calls and a remap of...

Background
  • How Quake AI Uses OpenStack22.06.2026

    Quake AI runs on OpenStack {OPENSTACK_RELEASE}. Each public Quake AI service (compute, networking, storage, automation, and Kubernetes) maps to an OpenStack project. The standard OpenStack CLI, APIs...

Reference architectures by industry vertical and functional pattern.

35pages
Solutions
Start here
  • Self-hosted vibecode stackHub

    The modern vibecode stack is assembled from a sprawl of separately metered SaaS: hosting, Postgres, Redis, vector search, inference, auth, object storage, queues, and observability. This page maps each category to a validated OpenTofu template and its deployment walkthrough on Quake AI, so you can run the whole stack on Compute you operate with flat egress.

  • AI-native development

    Engineering teams that build with AI coding assistants can point those tools at Quake AI Developer's plain-markdown docs, llms.txt corpora, Meilisearch search, knowledge graph, and hosted MCP server so retrieval stays current and IaC output maps to validated templates.

Apps and sites
  • Web applications and APIsHub

    Run a web application or HTTP API on Quake AI compute, networking, and storage. Migrate from a VPS, Heroku, or hyperscaler VM by composing provider and primitive migration guides into a workload-shaped cutover path.

  • SaaS and B2B applicationsHub

    Run a multi-tenant B2B SaaS application on Quake AI compute, networking, and storage. Publish through a self-managed edge proxy, keep tenant data in self-managed Postgres, and serve uploads from Object Storage.

  • Ecommerce storefrontsHub

    Run an online storefront that serves catalog pages, takes orders, and stores product media on Quake AI compute, networking, and storage. Card data stays with an external PCI-DSS payment processor such as Stripe or Adyen; Quake AI holds SOC 2 attestations but not PCI-DSS.

  • Internal tools and admin panels

    Build internal tools, admin panels, and database-backed UIs on a self-hosted Appsmith instance on Quake AI Compute, a self-hosted alternative to Retool.

AI, data, and storage
  • AI inference and RAG pipelinesHub

    Run inference and retrieval-augmented generation on Quake AI compute and storage. Migrate from hyperscaler VMs and object storage by composing provider and primitive migration guides into a workload-shaped cutover path.

  • AI/ML platformsHub

    Run model serving, experiment tracking, and batch pipelines on Quake AI. Migrate from SageMaker, Vertex AI, Azure ML, or self-managed Kubernetes by composing provider and primitive migration guides into a workload-shaped cutover path.

  • Scientific computing and researchHub

    Run batch simulation, analysis, and research pipelines on Quake AI compute and storage. Migrate from hyperscaler VMs, object stores, and Kubernetes batch queues by composing provider and primitive migration guides into a workload-shaped cutover path.

  • Data pipelines and analyticsHub

    Run ETL and ELT pipelines and an analytics warehouse on Quake AI by composing validated templates for Airflow orchestration, Object Storage, self-managed Postgres or ClickHouse, and Metabase or Superset, with predictable cost and no per-query warehouse pricing.

  • Self-service BI stack

    Compose Metabase or Apache Superset with a self-managed Postgres warehouse and S3-compatible Object Storage on Quake AI for analyst dashboards without per-query warehouse billing.

  • Open lakehouse

    Compose MinIO, Apache Iceberg, Trino, and Metabase or Superset on Quake AI compute and storage. You operate the catalog, query engine, and dashboards; Quake AI provides Object Storage, Block Storage, and predictable plan pricing.

  • Notebook workbenchHub

    Compose JupyterHub, self-managed Postgres, Object Storage, MLflow, and a Feast feature store for classic ML and feature work on Quake AI, then publish Streamlit or Gradio data apps. GPU training runs on an external backend you choose.

  • Backup, archive, and object storageHub

    Store snapshots, archives, and backups on Quake AI S3-compatible Object Storage. Migrate from hyperscaler buckets and S3-compatible providers by composing provider and primitive migration guides into a workload-shaped cutover path.

Delivery and DevOps
  • Kubernetes platformsHub

    Run self-managed Kubernetes on Quake AI with Magnum. Migrate from EKS, GKE, AKS, or DigitalOcean Kubernetes by composing provider and primitive migration guides into a workload-shaped cutover path.

  • CI/CD pipelinesHub

    Thread an end-to-end CI/CD pipeline on Quake AI: push to a self-hosted Forgejo forge, build on its Actions runner, store images in a Harbor registry, and deploy to a VM over SSH or Coolify or to a Kubernetes cluster with GitOps. Every component is self-managed on Compute you operate, composed from validated OpenTofu templates and their companion tutorials.

  • DevOps automation and CI/CDHub

    Run CI/CD pipelines, OpenTofu or Heat stacks, and build automation on Quake AI. Migrate an existing IaC and CI estate from AWS, Azure, GCP, or another provider by composing provider and primitive migration guides into a workload-shaped cutover path.

Web3
  • Web3 and stablecoin infrastructure

    Web3 teams run smart-contract CI, self-hosted blockchain nodes, wallet back ends, The Graph indexers, IPFS pinning, and dapp frontends on Quake AI Compute, storage, network, and self-managed Postgres. This page sequences the stack, maps each layer to the primitives and templates behind it, and links out to the RPC and wallet leaves.

  • RPC and blockchain nodesHub

    Run your own full, archive, or validator nodes and RPC endpoints on Quake AI compute, NVMe Block Storage, and networking instead of paying per-request managed RPC. Ethereum is the strongest fit; Solana, Bitcoin, and other chains vary by per-chain hardware and bandwidth requirements.

  • Wallet and payments back end

    Run the supporting infrastructure for self-custodial wallet clients and stablecoin payment, settlement, DeFi, and analytics workers on Quake AI compute, storage, and networking. Custody stays with the wallet user or your own signing service; Quake AI runs no managed wallet, custody, or payments product.

Media, creators, and games
  • Media archive and VOD originHub

    Store video masters and packaged derivatives in Quake AI Object Storage and serve VOD origin behind a third-party CDN. Attach DAM tools over the S3 API, derive HLS and DASH with CPU transcode workers, and serve playback with flat egress.

  • Creator businessesHub

    Run the archive, batch workers, and audience surface for a creator business on Quake AI. Migrate from hyperscaler VMs and object storage by composing provider and primitive migration guides into a workload-shaped cutover path.

  • Indie multiplayer game serversHub

    Run community multiplayer game servers on Quake AI compute and networking for titles that ship a dedicated server binary. Persist saves on Block Storage, back up to Object Storage, and give players a stable Floating IP.

Developer tooling
  • Self-hosted secrets management

    Centralize secrets for a team on a self-hosted Infisical instance on Quake AI Compute, with versioning, environments, and access control.

  • Feature flags and experiments

    Roll out feature flags, gradual releases, and A/B experiments on a self-hosted Unleash instance on Quake AI Compute, a self-hosted alternative to LaunchDarkly or Flagsmith.

  • Testing and QA infrastructure

    Run WebDriver-based UI test suites from CI against a self-hosted Selenium Grid 4 on Quake AI Compute, without a per-minute device-farm bill.

Team and collaboration
  • Team chat

    Run channel-based team chat and integrations on a self-hosted Mattermost Team Edition instance on Quake AI Compute, a self-hosted alternative to Slack.

  • Scheduling and booking

    Run availability, event types, calendar sync, and booking pages on a self-hosted Cal.com instance on Quake AI Compute, a self-hosted alternative to Calendly.

  • Files and collaboration

    Store, sync, and share files for a team on a self-hosted Nextcloud instance on Quake AI Compute, a self-hosted alternative to Dropbox or the file layer of Google Workspace.

  • Whiteboarding and diagramming

    Sketch diagrams together in real time on a self-hosted Excalidraw instance on Quake AI Compute, a self-hosted alternative to Figma or Miro for lightweight diagramming.

  • Project and work management

    Track issues, cycles, and projects on a self-hosted Plane instance on Quake AI Compute, a self-hosted alternative to Linear or Jira.

Content and publishing
  • WordPress and CMS hosting

    Run self-hosted WordPress and other PHP-based CMS platforms on Quake AI compute, networking, and storage. Publish through a self-managed reverse proxy, keep content in self-managed MySQL, and serve media uploads from Object Storage.

  • Podcast and audio publishingHub

    Host, master, transcribe, and publish podcast and audio on Quake AI compute and Object Storage. Migrate from hyperscaler VMs and object storage or a SaaS host by composing provider and primitive migration guides into a workload-shaped cutover path.

  • Live streaming and restreamHub

    Self-host RTMP and SRT ingest, multi-platform restream, and live-to-VOD capture on Quake AI Compute. You run NGINX-RTMP, SRS, or similar ingest software on VMs you own; Quake AI provides the compute...

API, CLI, and console reference material organised by OpenStack service.

92pages
Getting started
Compute (Nova)
  • API endpoints
  • API reference04.06.2026

    The Compute API reference documents every Nova endpoint with interactive request and response examples.

  • CLI referenceNew01.09.2026

    This page indexes the OpenStack CLI surface for Quake AI Compute. For curated commands with Quake AI-specific context, use the Compute CLI reference. For the full command set on a single resource, use...

  • CLI commands
  • API errorsNew08.09.2026

    HTTP status codes, instance fault messages, and resolution steps for Compute API (Nova) errors on Quake AI.

  • Instances APINew08.09.2026

    Compute (Nova v2.1) instance endpoints on Quake AI: create boot-from-volume servers, run lifecycle actions, attach volumes, snapshot, and read response codes and error envelopes.

  • Instances CLINew08.09.2026

    See https://docs.openstack.org/nova/2023.1/cli/index.html.

  • Flavors APINew08.09.2026

    See https://docs.openstack.org/api-ref/compute/.

  • Flavors CLINew08.09.2026

    See the OpenStack CLI flavor reference for the full list of openstack flavor subcommands.

  • Images APINew08.09.2026

    These endpoints operate on images: listing, creating, updating, deleting, uploading and downloading image data, and sharing images with other projects. They are the OpenStack Glance v2 API. For the...

  • Images CLINew08.09.2026

    See the OpenStack CLI image reference for the full list of openstack image subcommands.

  • Key pairs APINew08.09.2026

    See the upstream Nova API reference for the full specification.

  • Key pairs CLINew08.09.2026

    See the OpenStackClient keypair command reference for subcommands, arguments, and examples.

  • Server groups APINew08.09.2026

    In these methods, \{server_group_id\} is a placeholder for the ID of the server group; replace it with the actual ID. The API lists existing server groups, shows details of a specific server group...

  • Server groups CLINew08.09.2026

    See the OpenStackClient server group command reference for subcommands, arguments, and examples.

  • Snapshots APINew08.09.2026

    See the upstream Compute (Nova) API reference and Image (Glance) API reference.

  • Snapshots CLINew08.09.2026

    See the OpenStack CLI reference for the full command set.

  • Model resource requirementsNew08.09.2026

    Reference for selecting a Quake AI instance flavor based on the language model you intend to run. All figures assume Ollama with 4-bit quantization (the default), CPU-only inference, and no other...

  • Console

    The Compute section of the Quake AI console (web interface) lets you create, monitor, and manage virtual machines and their supporting resources. Select Services > Compute to access the Compute...

    • InstancesNew08.09.2026

      Instances are the building blocks for running applications and services in the cloud. They provide a flexible and scalable way to deploy workloads, with the ability to manage and scale resources as...

    • AppsNew08.09.2026

      Select Compute > Apps (/compute/apps) to view the Apps console. The Apps page lists pre-configured application templates you can deploy as fully provisioned instances.

    • SnapshotsNew08.09.2026

      Instance snapshots can be used for backup purposes, to create new instances with identical configurations, or to roll back to a previous state in case of errors or issues.

    • FlavorsNew08.09.2026

      Flavors define the vCPU, memory, and disk resources allocated to an instance. Quake AI organizes flavors into four categories: General Purpose, Compute Optimized, Memory Optimized, and Shared...

    • ImagesNew08.09.2026

      Images are pre-configured files that contain a virtual machine's (VM) operating system and associated data. Images serve as templates for creating instances (VMs) within the Compute service. The Image...

    • Key pairsNew08.09.2026

      The Key Pair service enhances the security of virtual machine instances by providing a mechanism for secure, passwordless authentication using SSH keys. It is an essential feature for users who need...

    • Server groupsNew08.09.2026

      Server groups provide a mechanism for controlling the placement of instances and can be an essential tool for optimizing performance, availability, and fault tolerance in a cloud environment.

Network (Neutron)
  • API endpoints
  • API referenceNew08.09.2026

    The Network API reference documents every Neutron endpoint with curl examples and request bodies.

  • CLI referenceNew08.09.2026

    The Network CLI reference lists curated commands with Quake AI-specific context. This page covers core resource commands; router static routes and security-group commands are documented on that...

  • CLI commands
  • API errorsNew08.09.2026

    HTTP status codes, port/router/security group errors, and resolution steps for Network API (Neutron) errors on Quake AI.

  • Floating IP APINew08.09.2026

    On Quake AI, the floating IP API is served by Neutron at https://network.us-east-1.rumble.cloud/v2.0/floatingips. The legacy Nova os-floating-ips proxy endpoints remain available on the default...

  • Floating IP CLINew08.09.2026

    See the OpenStack CLI floating IP reference for the full list of openstack floating ip subcommands.

  • Ports APINew08.09.2026

    See https://docs.openstack.org/api-ref/network/.

  • Ports CLINew01.09.2026

    See the OpenStack CLI port reference for the full list of openstack port subcommands.

  • Routers APINew08.09.2026

    See https://docs.openstack.org/api-ref/network/.

  • Routers CLINew01.09.2026

    See the OpenStack CLI router reference for the full list of openstack router subcommands.

  • Security groups CLINew01.09.2026

    See the OpenStackClient Network v2 references for security group commands and security group rule commands.

  • Console

    The Network section of the Quake AI console (web interface) lets you create and manage virtual networks, routers, floating IPs, ports, and firewall rules. Select Services > Network to access the...

    • NetworksNew08.09.2026

      The Networks console lists all networks in your project. Quake AI provides two shared networks: PublicEphemeral (dynamic public IP, released on instance delete) and PublicStatic (persistent public IP...

    • RoutersNew08.09.2026

      Use routers to connect different networks within a cloud environment and to provide external connectivity to instances (virtual machines).

    • PortsNew08.09.2026

      Ports are a fundamental component of networking in the Network service, providing the necessary connectivity and configuration for instances and other network resources to communicate within the cloud...

    • Floating IPsNew08.09.2026

      Floating IPs (FIP) are a critical feature for enabling external access to instances in your cloud projects. They provide the flexibility to expose services to the outside world while maintaining the...

    • Security groupsNew08.09.2026

      Security groups provide a flexible mechanism for securing virtual machine instances by controlling the flow of network traffic. They are an essential component of network security in a cloud...

    • TopologyNew08.09.2026

      The topology console in the Network service provides a visual representation of the network resources and their relationships within your cloud environment. Use topology to view and understand the...

Block Storage (Cinder)
  • API endpoints
  • API referenceNew08.09.2026

    The Block Storage API reference documents every Cinder endpoint with curl examples and request bodies.

  • CLI referenceNew01.09.2026

    The Block Storage CLI reference lists curated commands with Quake AI-specific context.

  • CLI commands
  • API errorsNew08.09.2026

    HTTP status codes, volume state machine errors, and resolution steps for Block Storage API (Cinder) errors on Quake AI.

  • Console

    Reference pages for the block storage views in the Quake AI console. Each entry maps console UI elements to the actions and resources they manage. For procedural walkthroughs, see the how-to guides.

    • VolumesNew08.09.2026

      Select Storage Service > Volumes to show the volumes console.

    • Volume snapshotsNew08.09.2026

      Select Storage > Volume Snapshots to view the volume snapshots console. The console displays a list of volume snapshots available in your project.

Object Storage (Swift)
  • API endpoints
  • S3-Compatible API
  • S3 storage tools
  • API referenceNew08.09.2026

    Endpoint documentation lives on the Object Storage API reference (Swift) and the S3-compatible API reference.

  • CLI referenceNew01.09.2026

    The Swift command reference covers the swift client. The S3-compatible storage tools reference covers AWS CLI, s3cmd, and rclone.

  • CLI commands
  • API errorsNew08.09.2026

    S3-compatible error codes, authentication failures, and resolution steps for Object Storage API errors on Quake AI.

  • Bucket policiesNew08.09.2026

    AWS-style S3 bucket policy JSON examples for Quake AI object storage: public read, prefix-scoped read, IP restrictions, and read-only principals.

  • Console

    Reference pages for the Object Storage views in the Quake AI console. Each entry maps console UI elements to the actions and resources they manage. For procedural walkthroughs, see the how-to guides.

    • Object storageNew08.09.2026

      Use the object storage console to manage buckets (called containers in OpenStack Swift CLI/API) and upload files to your cloud project.

Kubernetes (Magnum)
  • API endpoints
  • API referenceNew08.09.2026

    The Kubernetes API reference documents every Magnum endpoint with curl examples.

  • CLI referenceNew01.09.2026

    The Kubernetes CLI reference lists commands with Quake AI-specific context.

  • CLI commands
  • Console

    The Kubernetes section of the Quake AI console (web interface) lets you create and manage Kubernetes clusters and the templates that define them. Select Services > Kubernetes to access the Kubernetes...

    • ClustersNew08.09.2026

      The Clusters page lets you deploy, inspect, scale, and delete Kubernetes clusters. Select Services > Kubernetes > Clusters (/container-infra/clusters) to access this page.

    • Cluster templatesNew01.09.2026

      The Cluster Templates page lets you create, inspect, and delete the reusable blueprints that define Kubernetes cluster configuration. Select Services > Kubernetes > Cluster Templates...

Automation (Heat)
  • API endpoints
  • API referenceNewHub08.09.2026

    The Automation API reference documents every Heat endpoint with curl examples.

  • CLI referenceNew08.09.2026

    The Automation CLI reference lists curated commands with Quake AI-specific context.

  • CLI commands
  • API errorsNew08.09.2026

    This page documents common error responses from the Automation API (OpenStack Heat), explains what they mean operationally, and provides next-step actions. Use this reference when a stack operation...

  • Ansible modulesNew01.09.2026

    This page lists the openstack.cloud Ansible collection modules that are usable on Quake AI, grouped by service. Each entry names the module, the operation it performs, and Quake AI-specific...

  • ConsoleNew08.09.2026

    The Automation section of the Quake AI console lets you view and manage Heat stacks (collections of cloud resources deployed from orchestration templates). Select Automation > Heat Stacks...

Storage
  • ConsoleNew08.09.2026

    The Storage sections of the Quake AI console (web interface) let you manage block storage volumes and object storage buckets. Block storage and object storage appear as separate items in the console...

Showing the catalog entry view.

Use the graph in your tools

Export last generated 16.09.2026.

knowledge-graph.json is the full export of pages, services, concepts, competitor analogs, templates, and the edges between them. Fetch it for RAG pipelines, offline analysis, or tooling that needs relationships, not only a flat page list.

Open knowledge-graph.jsonConnect AI toolsSchema reference