AIX cloud hosting options
AIX runs natively on Power in the cloud, so a lift-and-shift keeps your applications and runbooks intact. Here's where AIX can run, and when leaving Power is actually worth it.
AIX is IBM's enterprise UNIX, and like IBM i it is proprietary to Power. Hosting AIX in the cloud means running it on cloud Power hardware, the operating system and applications move largely as-is, with no re-architecture. The realistic destinations differ mainly in where the Power capacity physically lives and what cloud services sit next to it.
Where AIX can run in the cloud
| Destination | Type | Best for |
|---|---|---|
| IBM PowerVS | Cloud (IBM) | Straight lift-and-shift |
| Skytap on Azure | Cloud (Azure) | Power next to Azure services |
| Managed Power cloud | Managed | Hands-off operations |
All three keep AIX on Power, so the move is low-risk. Choose on proximity to your other systems (Azure-adjacent via Skytap), how much you want to operate yourself (PowerVS), or whether you'd rather hand off administration entirely (managed Power).
When to consider an AIX-to-Linux replatform instead
Re-architecting AIX onto Linux is the only path that fully exits the Power platform (see Linux on Power cloud options), and the longest, riskiest one. It means recompiling, testing, and sometimes rewriting the application. It's worth it only when there's a strategic mandate to leave proprietary UNIX behind, not simply to reach the cloud.
- Removes Power licensing and hardware from the long-term picture
- Opens the full x86 and cloud-native ecosystem
- High effort and risk; application recompile, test, and possible rewrite
- Plan it as a 9–18 month program, not a lift-and-shift
Frequently asked questions
Can I move AIX to the cloud without changing my applications?
Yes. A lift-and-shift to cloud Power, PowerVS, Skytap on Azure, or managed Power, keeps AIX and your applications intact, with no re-architecture and no recompile.
What's the difference between PowerVS and Skytap on Azure for AIX?
Both run AIX on Power in the cloud. Skytap places that Power capacity inside Azure data centers, so AIX sits next to Azure-native services with low latency, useful when the rest of your estate is on Azure.
Do I have to move AIX to Linux to get to the cloud?
No. Replatforming AIX to Linux is a separate, much larger project, and only worth it when leaving the Power platform entirely is a strategic goal. To simply reach the cloud, a lift-and-shift keeps AIX on Power.
How is AIX licensed in the cloud?
AIX and ISV licensing should be checked for portability before migrating. Cloud Power providers handle licensing differently, so confirm how each license transfers during planning.
What an AIX move looks like in practice
For most AIX estates the cloud answer is a lift-and-shift that keeps everything intact. Two representative examples.
Situation. A mission-critical ERP on AIX and Power8, with the rest of the estate already on Azure.
Approach. Lift-and-shift AIX to Power via Skytap on Azure, placing it next to the existing Azure services.
Outcome. AIX unchanged and low-latency to Azure-native systems, off end-of-life hardware in a single quarter.
Situation. An AIX database tier with a lean team and no interest in running Power hardware.
Approach. Move to a managed Power cloud so administration, patching, and DR sit with the provider.
Outcome. A like-for-like AIX environment with operations offloaded, and a replatform deliberately deferred as a separate decision.
Representative scenarios reflect common IBM Power migration patterns and typical ranges, not specific named client engagements.
An AIX cloud-hosting checklist
A lift-and-shift is usually the low-risk answer for AIX. These questions tell you which destination fits, and whether a replatform is ever worth raising.
Move AIX to the cloud, the low-risk way
We'll size a lift-and-shift to cloud Power, and tell you honestly if a replatform is worth it.
No pitch, no obligation. A Foretel advisor responds within one business day.