Migration Guides
Coming from another cloud?
▸AWS·Stacks
Stacks
- 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.
▸Hetzner·Server
This Quake AI feature maps to Hetzner’s Server.
▸Linode·s (Compute Instances)
Linodes (Compute Instances)
- Provisioned via the Linode API v4 (/v4/linode/instances) instead of OpenStack Nova /v2.1/servers; auth is a Personal Access Token rather than a Keystone token.
- Plan selection is fixed (Shared, Dedicated, High Memory, Premium, GPU, Accelerated) with predefined vCPU/RAM/storage; OpenStack flavors can be cloud-defined.
- Billing is hourly with a monthly cap per plan; powered-off Linodes continue to bill until deleted, unlike pause/suspend semantics common in OpenStack stop-billing setups.
- Distribution images and StackScripts are first-class; OpenStack uses Glance images and arbitrary userdata.
▸Vultr·Cloud Compute / Bare Metal Instances
Cloud Compute / Bare Metal Instances
- Provisioned via the Vultr API v2 (/v2/instances and /v2/bare-metals) instead of OpenStack Nova /v2.1/servers; auth is a Personal Access Token rather than a Keystone token.
- Plan selection is fixed (Regular Performance, High Performance, High Frequency, CPU Optimized, Memory Optimized, Bare Metal) with predefined vCPU/RAM/storage; OpenStack flavors can be cloud-defined.
- Billing is hourly with a monthly cap per plan; powered-off Vultr instances continue to bill until destroyed, unlike pause/suspend semantics common in OpenStack stop-billing setups.
- Marketplace one-click apps and ISO library are first-class; OpenStack uses Glance images and arbitrary userdata.
Migration guides
Step-by-step guides for moving your infrastructure to Quake AI from other providers and tools. Each guide maps source resources to their Quake AI equivalents and walks through a full migration workflow using OpenTofu.
Guides#
Migrate from Hetzner Cloud
Swap the hcloud provider for OpenStack, remap server types to Quake AI flavors, and translate firewalls to security groups.
Migrate from AWS CloudFormation
Convert CloudFormation stacks to OpenTofu configurations targeting the Quake AI OpenStack provider.
Migrate from Docker Compose
Move single-host Docker Compose setups to cloud-native infrastructure managed by OpenTofu on Quake AI.
Migrate from Linode (Akamai)
Swap the linode/linode provider for openstack, remap Linode plans to Quake AI flavors, translate Cloud Firewalls to security groups, and replace NodeBalancers with a self-managed edge proxy.
Migrate from Vultr
Swap the vultr/vultr provider for openstack, remap Vultr plans to Quake AI flavors, translate Firewall Groups to security groups, and replace Vultr Load Balancers with a self-managed edge proxy.
General migration workflow#
All IaC migrations follow the same pattern:
- Audit existing resources. Document servers, networks, storage, and firewall rules in your current environment.
- Map to Quake AI equivalents. Use the conceptual mapping tables in each guide to find corresponding OpenStack resources.
- Rewrite infrastructure code. Replace provider-specific resources with
openstack_*equivalents using the OpenStack Terraform provider. - Migrate data. Use
rsync,scp, orrclone(for S3-compatible storage) to transfer data between environments. - Validate and deploy. Run
tofu planto verify, thentofu applyto provision on Quake AI.
See also#
- Migration Explorer: interactive service comparison across cloud providers
- IaC on Quake AI
- Introduction to Terraform on Quake AI
- Infrastructure Templates
- Automation service overview
Usage Guidelines
The sample code, software libraries, command line tools, proofs of concept, templates, and other related technology on this page (including any of the foregoing that is provided by Quake AI personnel) is provided to you as Quake AI Content under the Quake AI Customer Agreement, or the relevant written agreement between you and Quake AI (whichever applies). Do not use this Quake AI Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the Quake AI Content (such as sample code) as appropriate for production grade use based on your specific quality control practices and standards. Deploying Quake AI Content may incur Quake AI charges for creating or using Quake AI chargeable resources, such as running Compute instances or storing data in Object Storage. Your use is also subject to the Acceptable Use Policy.
Comparisons to third-party providers in this material reflect publicly documented behavior as of the validation date below. Pricing, quotas, service limits, and feature availability change frequently on every cloud. Verify provider-specific claims against the provider's own current documentation before relying on them for a procurement, architecture, or migration decision.
For the full policy, see Usage Guidelines.
Last validated: 19.06.2026