Every AMI is built for one specific CPU architecture: x86_64 (Intel or AMD) or ARM64 (aarch64, the one behind AWS Graviton and its equivalents). There is no image that “works for both”: they are different binaries. So when we put our catalogue together, we had to decide which one would be the default.
We looked at cost, performance, efficiency, ecosystem maturity and where the market is heading. The conclusion was clear: ARM64 is today the best bet for most workloads. And that is how we build our images.
Why ARM64 wins for most people
1. Better price-performance
This is the decisive argument. ARM (Graviton) instances consistently deliver more performance per euro than their x86 equivalents across a wide range of workloads: web, APIs, microservices, containers, databases and queues. In practice, moving to ARM usually translates into savings in the order of 20 % to 40 % on compute cost. In a cloud that keeps getting more expensive, that margin is too big to ignore.
2. More efficiency, less energy
ARM processors were born optimising power consumption. That means more work per watt, lower energy cost and a smaller carbon footprint per unit of compute. If sustainability is part of your goals —or your customers’— ARM plays in your favour.
3. The ecosystem is already mature
A few years ago, “will it have an ARM version?” was a legitimate question. Today the vast majority of server software —operating systems, languages, runtimes, databases, popular container images— has first-class ARM64 support. Compatibility stopped being the exception and became the norm.
4. Same security, same operating model
Changing architecture does not change how you work: configuration, hardening, cloud-init, your provisioning scripts and your pipeline are all the same. ARM64 does not ask you to give up anything in your operations or your security posture.
The comparison, in one table
| Criterion | ARM64 (Graviton) | x86_64 (Intel/AMD) |
|---|---|---|
| Price-performance | Superior on most workloads | Good, but pricier per unit |
| Energy efficiency | Very high | Lower |
| Software compatibility | Excellent and broad today | Maximum, universal |
| Legacy proprietary binaries | Sometimes no ARM build | Full support |
| Market direction | Growing and strategic | Consolidated |
| Typical cost | Lower: between 20 % and 40 % | Higher |
For modern workloads, ARM64 wins where it matters most: cost, efficiency and future.
When x86_64 still makes sense
Being honest is part of choosing well. There are cases where x86_64 is still the right call, and we do not want anyone forcing a migration that makes life harder:
- Proprietary software or binaries that only exist compiled for x86.
- Native dependencies —compiled extensions— with no ARM build available.
- Legacy tools or third-party integrations tied to x86.
- Very specific workloads hand-optimised for x86 instructions.
Our decision: ARM64 by default, x86_64 on request
For all of the above, our AMIs are built on ARM64 by default. We believe that is what brings most value to most people: you pay less for the same work, you consume less energy and you ride the architecture that is setting the cloud’s direction.
But we know not every workload fits. That is why, if you need x86_64, all you have to do is ask: we will prepare a custom image with the same configuration, the same hardening and the same quality, built for x86_64. Same product, same base, the architecture your case requires.
How to decide in 30 seconds
- Modern stack —web, API, containers, interpreted languages, common databases—: ARM64, no hesitation.
- Do you have a proprietary binary or a dependency that only runs on x86? Ask us for the x86_64 variant.
- Not sure? Start on ARM64 and try it; if something does not fit, we build the x86_64 one and that is that.
Frequently asked questions
Are your AMIs ARM64 or x86_64?
By default we build them on ARM64 (Graviton), because it offers the best price-performance for most workloads. If you need x86_64, we prepare a custom one with the same configuration and quality.
Do I have to change my application to use ARM64?
In most cases, no. Interpreted languages and modern software run on ARM unchanged. There is only friction with proprietary binaries or native dependencies with no ARM version; in those cases we offer you the x86_64 variant.
How do I request a custom x86_64 image?
Just ask. We start from the same base and the same hardening and build the image for x86_64, so you get exactly the same product on the architecture you need.
Am I really going to save with ARM64?
For suitable workloads, savings of 20 % to 40 % on compute cost are common, on top of lower energy consumption. The way to confirm it for your specific case is to run your workload and compare.
At imaxe.cloud we bet on ARM64 because we believe it is best for your bill, your performance and the planet. And if you need x86_64, all you have to do is ask: we build you a custom one.
