Quake AI offers Heat (legacy OpenStack orchestration) and recommends OpenTofu for new IaC work; EKS uses declarative console/CLI.
EKS Auto Mode automates data plane; Quake AI uses OpenTofu modules for infrastructure provisioning.
CloudFormation stacks are managed via AWS-specific REST API (e.g., cloudformation.us-east-1.amazonaws.com) requiring AWS SigV4 auth, while Heat (legacy) uses OpenStack Identity API v3 (keystoneauth) and OpenTofu uses the OpenStack provider with application credentials. Migrators notice different endpoint discovery and auth flows.
Stacks support StackSets for cross-region/account deployment; Heat has no equivalent. OpenTofu workspaces offer a different multi-environment pattern.
Authoring format differs: ARM templates are JSON documents for Azure Resource Manager deployments, whereas Quake AI offers Heat (legacy, HOT/YAML format) and recommends OpenTofu (HCL) for new infrastructure automation.
Deployment target/scope differs: ARM templates can deploy at multiple scopes (resource group, subscription, management group, tenant) via Azure Resource Manager's management layer, while Heat orchestrates within a single OpenStack project/tenant. OpenTofu can target multiple projects via provider configuration.
Change-preview behavior differs: ARM supports a built-in “what-if” style preview of changes via Resource Manager deployments, while OpenTofu provides `tofu plan` for change previews. Heat relies on stack update events (legacy workflow).
Resource coverage lifecycle differs: ARM templates support Azure resource types exposed by Azure resource providers; OpenTofu covers OpenStack resource types via the OpenStack provider, and Heat (legacy) supports a narrower set via built-in resource plugins.
Uses YAML configurations with optional Jinja2/Python templates expanded server-side; Quake AI offers Heat (legacy, HOT/YAML) and recommends OpenTofu (HCL) for new work.
Resource types named as service.v1.resource (e.g., compute.v1.instance) tied to GCP APIs, vs OpenStack prefixed types like OS::Nova::Server.
Single integrated GCP service (no separate API/engine processes); Heat has a multi-service architecture (heat-api, heat-engine) but is legacy. OpenTofu runs client-side with no server component.
No additional service fee; bills only for deployed GCP resources, same as OpenStack resources billing via provider.
OpenTofu templates for common Quake AI deployment patterns: compositions of Compute, Network, Block Storage, Object Storage, and Kubernetes primitives wired together for repeatable workloads.
Templates include security groups, private networking, and resource sizing by default. Each template specifies the Quake AI services it provisions, the concepts it exercises, and an expected deployment time.
Every template passes tofu validate in continuous integration before it ships, so each one is well-formed against Quake AI's OpenStack provider schema. For what that guarantee does and does not cover, see how the platform validates infrastructure templates.
When you author or extend templates, follow Authoring IaC templates for Quake AI for catalog literals, security group conventions, and platform-specific OpenStack quirks.
This pattern composes Compute, Network, and Block Storage into a self-hosted reverse proxy with automatic TLS on infrastructure you control.Custom package · ~$14/mo · 20 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted L7 web application firewall on infrastructure you control.Custom package · ~$15/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted API gateway on infrastructure you control.Custom package · ~$31/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted tunnel endpoint on infrastructure you control.Custom package · ~$15/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a regional HTTP cache on infrastructure you control.Custom package · ~$14/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a regional function gateway on infrastructure you control.Custom package · ~$15/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted business-intelligence host you run on infrastructure you control.Custom package · ~$16/mo · 25 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted business-intelligence host you run on infrastructure you control.Custom package · ~$67/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted workflow orchestration host you run on infrastructure you control.Custom package · ~$34/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted data-app host you run on infrastructure you control.Custom package · ~$16/mo · 20 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted extract-and-load host you run on infrastructure you control.Custom package · ~$68/mo · 30 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted analytical column store you run on infrastructure you control.Custom package · ~$68/mo · 25 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted open lakehouse catalog you run on infrastructure you control.Custom package · ~$67/mo · 25 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted federated SQL query engine you run on infrastructure you control.Custom package · ~$137/mo · 30 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted Kafka-API streaming broker you run on infrastructure you control.Custom package · ~$18/mo · 25 minutes
This pattern composes Compute, Network, Block Storage, and Object Storage into a self-hosted experiment-tracking and model-registry server you run on infrastructure you control.Custom package · ~$16/mo · 25 minutes
This validated OpenTofu template composes Compute, Network, and Block Storage into a self-hosted ML feature store you run on infrastructure you control.Custom package · ~$16/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted identity provider you run on infrastructure you control.Custom package · ~$32/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted deploy platform you run on infrastructure you control.Custom package · ~$34/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted git forge with a built-in CI runner on infrastructure you control.Custom package · ~$34/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted container registry on infrastructure you control.Custom package · ~$72/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted model router on infrastructure you control.Custom package · ~$32/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted workflow-automation host you run on infrastructure you control.Custom package · ~$16/mo · 20 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted multi-user notebook server you run on infrastructure you control.Custom package · ~$33/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted team wiki you run on infrastructure you control.Custom package · ~$32/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into the full self-hosted Supabase backend you run on infrastructure you control.Custom package · ~$133/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted secrets-management platform you run on infrastructure you control.Custom package · ~$32/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted project and work-management platform you run on infrastructure you control.Custom package · ~$67/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted feature-flags and experimentation platform you run on infrastructure you control.Custom package · ~$32/mo · 20 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted low-code platform for internal tools and admin panels, on infrastructure you control.Custom package · ~$32/mo · 20 minutes
This pattern composes Compute and Network into a self-hosted browser-testing grid for WebDriver-based UI test suites, on infrastructure you control.Custom package · ~$63/mo · 15 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted team-chat platform for a team, on infrastructure you control.Custom package · ~$32/mo · 25 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted scheduling and booking platform, on infrastructure you control.Custom package · ~$66/mo · 30 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted file-sync and collaboration platform for a team, on infrastructure you control.Custom package · ~$34/mo · 25 minutes
This pattern composes Compute and Network into a self-hosted collaborative whiteboard for a team, on infrastructure you control.Custom package · ~$13/mo · 20 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted uptime-monitoring and status-page host you run on infrastructure you control.Custom package · ~$15/mo · 15 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted web and product analytics host you run on infrastructure you control.Custom package · ~$32/mo · 20 minutes
This pattern composes Compute, Network, and Block Storage into a self-hosted error-tracking service you run on infrastructure you control.Custom package · ~$32/mo · 30 minutes
Pricing data last validated: . For current rates, check quake.ai/pricing.
Most templates are authored in OpenTofu (HCL). OpenTofu is the open-source, MPL-2.0-licensed fork of Terraform maintained by the Linux Foundation, compatible with Terraform providers and modules. The OpenTofu templates work with terraform as well; replace tofu with terraform in commands.