Flavors
Named virtual hardware templates specify vCPU count, RAM, root disk class, and optional extras like huge pages. Curated flavors keep capacity planning predictable for finance and scheduling teams. Resizing may require shutdown when disk footprints shrink.
28 documentation pages cover this concept. Editorial glossary
Concepts
How-tos
Reference
Overview
faq
migration
- →
Compute migration guides
migration
- →
Migrate from Azure Virtual Machines to Quake AI Compute
migration
- →
Migrate from DigitalOcean Droplets to Quake AI Compute
migration
- →
Migrate from AWS EC2 to Quake AI compute
migration
- →
Migrate from GCP Compute Engine to Quake AI compute
migration
- →
Migrate from Hetzner Cloud Servers to Quake AI Compute
migration
- →
Migrate from Linode compute instances to Quake AI compute
migration
- →
Migrate from Vultr to Quake AI compute
migration
runbook
Related
Covers concept (incoming)
- Apps→
- Cluster templates console→
- Compute→
- Compute concepts→
- Compute Console→
- Compute FAQ→
- Compute migration guides→
- Compute Service CLI Reference→
- Flavors→
- Flavors API Reference→
- Flavors CLI Reference→
- Flavors Console→
- How to Create a Cluster Template→
- How to customize a template's image and flavor→
- How to maintain a Quake AI VM over its lifetime→
- How to provision a production-ready VM→
- How to resize a Quake AI VM to a dedicated-CPU plan→
- Instance lifecycle troubleshooting→
- Instances→
- Migrate from AWS EC2 to Quake AI compute→
- Migrate from Azure Virtual Machines to Quake AI Compute→
- Migrate from DigitalOcean Droplets to Quake AI Compute→
- Migrate from GCP Compute Engine to Quake AI compute→
- Migrate from Hetzner Cloud Servers to Quake AI Compute→
- Migrate from Linode compute instances to Quake AI compute→
- Migrate from Vultr to Quake AI compute→
- Model Resource Requirements→
- Resource Tiers→
documented at
- Apps→
- Cluster templates console→
- Compute→
- Compute concepts→
- Compute Console→
- Compute FAQ→
- Compute migration guides→
- Compute Service CLI Reference→
- Flavors→
- Flavors API Reference→
- Flavors CLI Reference→
- Flavors Console→
- How to Create a Cluster Template→
- How to customize a template's image and flavor→
- How to maintain a Quake AI VM over its lifetime→
- How to provision a production-ready VM→
- How to resize a Quake AI VM to a dedicated-CPU plan→
- Instance lifecycle troubleshooting→
- Instances→
- Migrate from AWS EC2 to Quake AI compute→
- Migrate from Azure Virtual Machines to Quake AI Compute→
- Migrate from DigitalOcean Droplets to Quake AI Compute→
- Migrate from GCP Compute Engine to Quake AI compute→
- Migrate from Hetzner Cloud Servers to Quake AI Compute→
- Migrate from Linode compute instances to Quake AI compute→
- Migrate from Vultr to Quake AI compute→
- Model Resource Requirements→
- Resource Tiers→
Maps to (incoming)
Citations
- Amazon Web Services
- Microsoft Azure
- Google Cloud Platform
- Hetzner Cloud
- DigitalOcean
- Linode (Akamai)
- Vultr
These citations record configured source URLs in the knowledge graph. They are not a live platform walk verification date.