You can deploy on ARM64 servers today across AWS, Google Cloud, Azure, and Hetzner: Graviton, Ampere Axion, Ampere Cobalt, CAX. Pick the chip, pick the cloud, and deploy the stack you already run. There's no feature flag and no waitlist. It's on for every account.
Why ARM
AWS says Graviton instances cost up to 20% less than comparable x86 instances and use up to 60% less energy for the same performance. Google makes a similar case for Axion: up to 65% better price-performance than comparable x86 machines. Microsoft and Hetzner publish comparable numbers for Cobalt and CAX. ARM server chips are not a niche option anymore; for a lot of workloads they are simply the cheaper, more efficient default, and every major cloud's instance catalog now reflects that.
What's supported
ARM64 servers are now available via AWS (Graviton), Google Cloud (Ampere Axion, plus the older Ampere and N-series machine families), Azure (Ampere Cobalt), and Hetzner (CAX).
You can also bring your own ARM hardware. We support 64-bit machines on both AMD/Intel and ARM64 as registered servers — run the registration script on the ARM machine exactly as you would on any other server.
If your stack already runs on Cloud 66, there's nothing new to configure. The deployment pipeline, health checks, and rollback behavior stay the same. The only thing that changes is which CPU architecture the server runs on.
How to switch
Pick an ARM size the same way you already pick a server size: in the size dropdown when you create a new stack, when you scale up an existing server, or through the public API and CLI for scripted deploys. ARM sizes now show up everywhere sizes are listed, including CSv3 onboarding and cluster creation.
If you're moving an existing service, the fastest way in is a scale-up. Add an ARM64 server alongside your current fleet, confirm the workload behaves the way you expect, then retire the old size once you're comfortable.
What we handled so you don't have to
Underneath the stack, the runtime installers, database engines, and message queue your deployment depends on each needed to become architecture-aware on their own, because not every upstream vendor ships ARM builds the same way, or in some cases at all. None of that shows up in your dashboard. It just means the ARM server behaves like the amd64 one you're used to.
Try it
If you're already running on Cloud 66, spin up an ARM64 server on any supported stack and see what it does to your bill.
If you're evaluating us, spin one up during your trial and compare it against what you're running today!