IBM i Cloud & Hosting
Cloud and Hosting Options for IBM i Workloads
Compare IBM Power Virtual Server, managed IBM i hosting, private cloud, colocation, disaster recovery, and hardware refresh options for IBM i environments.
Independent analysis — not tied to a single cloud provider, hardware vendor, or systems integrator.
What are the main hosting options for an IBM i workload?
There's no universal answer — the right path depends on your workload profile, licensing terms, application support requirements, data center geography, target architecture, and the provider's contract terms. IBM Power Virtual Server, managed IBM i hosting, private cloud, colocation, disaster recovery as a service, and a straight hardware refresh each trade off control, cost predictability, and migration effort differently.
Workload Discovery
What to inventory before you choose a path
A clear picture of the current environment prevents surprises later in licensing, application support, and cutover timing.
OS and technology refresh level
Current IBM i release and Technology Refresh (TR) level, plus how close the environment is to IBM's end-of-support dates.
LPAR inventory
Every logical partition (LPAR), its processor and memory entitlement, and how workloads are split across partitions.
DB2 for i
Database size, journaling configuration, and any replication or high-availability dependencies tied to DB2 for i, the integrated relational database built into IBM i.
BRMS and backup strategy
How Backup, Recovery and Media Services (BRMS) policies, retention schedules, and save windows are configured today.
Network dependencies
Subsystem connections, VPN tunnels, and latency-sensitive integrations that a new hosting location must preserve.
Third-party application support
Whether independent software vendor (ISV) applications are certified to run on the target OS release, cloud, or hosting platform.
Options at a Glance
How IBM i hosting and cloud options compare
Each path trades off control, cost structure, and migration effort differently. Suitability depends on your workload, licensing, application support, geography, architecture, and provider terms.
| Option | Best fit when… | Key considerations |
|---|---|---|
| IBM Power Virtual Server | You want IBM infrastructure without owning hardware, with fast provisioning of new LPARs. | Consumption pricing, region availability, and connectivity back to on-premises systems. |
| Managed IBM i hosting | You want a provider to operate the OS, BRMS, and patching so your team focuses on applications. | The provider's IBM i version support, service-level agreement (SLA) terms, and how much administrative access your team retains. |
| Private cloud | You need dedicated infrastructure with more control than a shared managed service. | Higher setup effort and ongoing capacity planning versus a fully managed option. |
| Colocation | You want to keep owned hardware but exit an aging or costly data center. | You still own the hardware refresh cycle and the OS/BRMS administration burden. |
| Disaster recovery as a service | Production stays in place but needs a modern, tested recovery posture. | Recovery time objective (RTO) and recovery point objective (RPO), replication method, and test frequency. |
| Hardware refresh | Application or contractual constraints make relocation impractical right now. | Capital cost, lead time, and whether the refresh simply delays a future migration decision. |
Decision Aids
Key decision points for IBM i moves
Best fit
When IBM Power Virtual Server or managed hosting fit best
If the goal is to exit a hardware refresh cycle while preserving IBM i application compatibility, these two paths typically require the least application change.
Use caution
Where IBM i moves run into trouble
Licensing entitlement transfer, ISV certification gaps, and underestimating BRMS and backup redesign are common sources of delay. Plan for all three during discovery, not cutover week.
Key decision
Modernize now or relocate first?
Relocating the current environment preserves timeline and budget predictability. Modernizing addresses technical debt but extends the project. Many organizations phase the two rather than choosing one outright.
Migration Approach
A phased path for moving or refreshing an IBM i environment
Downtime and validation are usually the top concerns for IBM i teams — a phased approach keeps both controlled.
- 1
Discovery and assessment
Inventory LPARs, DB2 for i databases, BRMS policies, network dependencies, and third-party application certifications.
- 2
Target environment design and sizing
Right-size processor, memory, and storage entitlements for the destination platform based on current utilization.
- 3
Migration planning and test cutover
Build a runbook, define maintenance windows, and validate the move in a non-production test cutover before committing to a date.
- 4
Production cutover and validation
Execute the cutover against the runbook, then validate application function, performance, and data integrity before releasing users.
- 5
Post-migration operations
Confirm backup, high availability (HA), and disaster recovery (DR) are operating as designed, and decide what ongoing administration shifts to managed services versus your team.
What drives IBM i cloud and hosting costs
LPAR sizing and processor entitlement
Interactive and batch capacity requirements directly affect processor and memory sizing, and pricing scales with both. Treat any example figures as directional only.
Storage capacity and performance
DB2 for i database size and required I/O performance influence storage tier and cost.
Network bandwidth and connectivity
Dedicated, low-latency connectivity back to on-premises systems or other clouds adds recurring cost.
Software licensing
IBM i, DB2 for i, and third-party ISV license terms may or may not transfer to a new environment — confirm before budgeting.
Backup and DR redundancy
Retention periods, replication frequency, and the number of recovery sites all scale cost with the level of protection chosen.
Managed services scope
The more OS, BRMS, and security administration a provider takes on, the higher the recurring service fee and the lower the internal staffing burden.
Migration and professional services
One-time costs for assessment, cutover planning, and testing vary with environment complexity and compressed timelines.
For IBM i Administrators
Questions your technical team will ask
IBM i administrators tend to focus on the mechanics of the move itself.
IBM i version and TR compatibility
Does the target platform support your current IBM i release, or does the move force an OS upgrade first?
LPAR migration mechanics
How are logical partitions moved, resized, or consolidated, and what's the fallback if a partition doesn't behave as expected?
BRMS and backup continuity
Do existing BRMS policies carry over, or does backup and recovery need to be redesigned for the new environment?
Licensing entitlement transfer
Which licenses move with the workload, and which need to be repurchased or renegotiated?
Performance and interactive capacity
Will interactive job and batch performance match or improve on the new platform under real workload conditions?
Downtime and application compatibility
How long is the cutover window, and have third-party applications been validated against the target environment?
For CIOs and Directors
Questions leadership will ask
Chief Information Officers (CIOs) and IT directors weigh cost, continuity, and strategy more than migration mechanics.
Cost predictability
Does the option convert unpredictable capital refresh cycles into a forecastable operating expense, or introduce new variability?
Business continuity posture
Does the move improve or risk current recovery time and recovery point objectives during the transition and afterward?
Modernization roadmap alignment
Does relocating the workload now support or delay a longer-term application modernization strategy?
Provider and exit risk
How portable is the environment afterward, and what does it take to change providers again if terms or service quality change?
Frequently asked questions about IBM i cloud and hosting
What is the best cloud option for IBM i?
There isn't a single best option — it depends on your IBM i release level, DB2 for i database size, licensing terms, application support requirements, and how much administrative control your team wants to keep. IBM Power Virtual Server and managed IBM i hosting are common starting points for teams that want to reduce hardware ownership without re-platforming applications.
Should we modernize or just relocate the IBM i workload?
Many organizations relocate first to exit a hardware refresh cycle or improve continuity, then modernize specific applications over time. Whether to combine or sequence the two depends on budget, timeline pressure, and how much technical debt the current applications carry.
How much downtime should we expect during an IBM i migration?
Downtime depends on database size, replication method, and how much testing precedes the cutover. A non-production test cutover before the production event is the most reliable way to get a realistic estimate for your environment.
Does our IBM i and DB2 for i licensing transfer to a new provider?
It depends on the license terms and the target platform. Some licenses are tied to specific hardware serial numbers or processor groups, so confirm transferability with IBM and any third-party software vendors before committing to a timeline.
Will our third-party applications keep working after a move?
Only if they're certified on the target IBM i release and platform. Confirming independent software vendor (ISV) certification should be one of the first steps in discovery, not something left until cutover weekend.
What's the difference between IBM Power Virtual Server and managed IBM i hosting?
IBM Power Virtual Server is IBM's own cloud infrastructure offering. Managed IBM i hosting typically layers a third-party provider's operational support — patching, BRMS administration, monitoring — on top of infrastructure that may or may not be Power Virtual Server itself. The two are not mutually exclusive.
Sources
- IBM Power Virtual Server — product overview
- IBM i documentation
- IBM Power Systems overview
- IBM Backup, Recovery and Media Services (BRMS) and high-availability documentation for IBM i
Assess Your IBM i Environment
Get a clear, vendor-neutral view of which hosting option fits your IBM i workload, licensing, and continuity requirements before you commit to a provider.