Managed Hosting
Managed IBM Power Hosting: Overview and Fit
How third-party managed hosting for IBM i and AIX on Power differs from self-service Power Virtual Server or running infrastructure on-premises, and what to check before signing a contract.
Independent overview — confirm capabilities and service levels directly with any provider.
What is managed IBM Power hosting?
Managed IBM Power hosting is Power infrastructure — running IBM i or AIX — that's hosted and operated by a third-party provider rather than run through IBM's own Power Virtual Server service or on hardware you own. It typically bundles day-to-day operating system (OS) and sometimes application management into the contract, so your team isn't handling patching, monitoring, and backup directly. Specific capabilities, service-level agreements (SLAs), and pricing vary significantly by provider and must be verified independently.
Who It Fits
Who Managed Hosting Tends to Fit
Signals that managed hosting may be worth evaluating for your environment.
Limited in-house Power skills
Your team doesn't have, or doesn't want to maintain, deep IBM i or AIX administration expertise.
Wanting one accountable partner
You want a single vendor accountable for infrastructure, OS patching, and support rather than coordinating several.
Needing predictable support coverage
You need guaranteed response times or after-hours coverage that an in-house team can't reliably provide.
Preferring a bundled contract
You'd rather pay one predictable fee that covers infrastructure and operations than staff and manage it yourself.
Why Now
What Usually Triggers This Decision
Most organizations start evaluating managed hosting in response to a specific event rather than a routine review.
Losing in-house expertise
Retirements or turnover have left a gap in IBM i or AIX operational knowledge that's hard to backfill.
Hardware end-of-life
Aging hardware needs to be retired, but there's no appetite to manage cloud infrastructure directly either.
New service-level requirements
Contractual or regulatory requirements call for guaranteed service levels the current team can't commit to.
Consolidating vendors
Multiple point solutions for backup, monitoring, and patching are being consolidated into a single contract.
How It Works
How Managed Hosting Engagements Generally Work
The specifics vary by provider and contract — confirm each step directly with any provider you're evaluating.
- 1
Assess the current environment
The provider reviews your existing IBM i or AIX workloads, dependencies, and support requirements.
- 2
Define the scope of management
The contract specifies whether the provider covers infrastructure only, infrastructure plus OS, or infrastructure plus OS plus applications.
- 3
Migrate and onboard
Workloads move to the provider's environment, and monitoring, patching, and backup processes are established.
- 4
Operate under the SLA
The provider takes on day-to-day operations against the service levels defined in the contract.
Comparison
Self-Managed vs. Co-Managed vs. Fully Managed
A starting point for comparing management models. Treat every cell as directional — actual terms are set by each provider's contract.
| Option | Management responsibility | Cost model | Control | Typical SLA | Best for |
|---|---|---|---|---|---|
| Self-managed (customer-operated) | Customer handles OS, patching, monitoring, and backup | Infrastructure cost only; internal labor cost is separate | Highest customer control | No vendor SLA beyond infrastructure uptime (varies by provider) | Teams with strong in-house IBM i or AIX skills wanting full control |
| Co-managed | Split between customer and provider (e.g., provider handles patching and monitoring, customer handles applications) | Infrastructure cost plus a partial management fee | Shared control with negotiated boundaries | Partial SLA covering the provider's scope (varies by provider) | Teams wanting to retain some control while offloading routine operations |
| Fully managed | Provider handles OS, patching, monitoring, backup, and often application support | Bundled monthly fee covering infrastructure and management | Lowest day-to-day customer control; governed by contract | Broadest SLA, often including response-time and uptime commitments (verify with provider) | Teams without in-house Power skills wanting a single accountable partner |
Fit Check
Is Managed Hosting a Good Fit?
Best fit
Good fit signals
You don't have, or don't want to maintain, in-house IBM i or AIX operational skills, and you value having one accountable partner for infrastructure and OS support.
Use caution
Proceed with caution if
You see vague SLA language, unclear boundaries between what's managed and what's your responsibility, or contract terms that lock you in longer than your business plan can commit to.
Key decision
Decision point
If keeping more control over the OS layer yourself while still avoiding physical hardware sounds preferable, compare this page against IBM Power Virtual Server's self-service model before deciding.
What Drives Managed Hosting Cost
Scope of management
Self-managed vs. co-managed vs. fully managed changes the bundled fee substantially.
Compute and storage sizing
The same infrastructure sizing drivers apply here as with any Power hosting option.
Support tier and response times
24/7 coverage and faster response-time commitments typically cost more.
Compliance and audit support
Providers supporting regulated workloads may charge more for audit assistance and compliance reporting.
Contract length and minimum commitment
Longer commitments may lower the unit price but reduce flexibility to exit or renegotiate.
Migration
Migration Considerations
Moving into a managed hosting arrangement starts with a detailed assessment of the current environment, not just a data migration. Expect the provider to inventory logical partitions (LPARs), storage, network dependencies, and any third-party software before proposing a transition plan. Build in a defined onboarding period where responsibilities are clearly split between your team and the provider, test cutover windows before the production event, and confirm who owns rollback decisions if something doesn't go as planned.
Security & Compliance
Security and Compliance Considerations
Responsibility for security and compliance should be defined explicitly in the contract, since the split between what the provider manages and what you retain varies by provider and by service tier — unlike IBM's own documented model for Power Virtual Server. Ask for current audit reports or attestations, such as SOC 2 or ISO 27001, rather than relying on marketing copy, and confirm data residency and any industry-specific requirements, such as HIPAA (Health Insurance Portability and Accountability Act) or PCI DSS (Payment Card Industry Data Security Standard), directly with the provider before signing.
Managed IBM Power Hosting FAQ
How is managed hosting different from Power Virtual Server?
Power Virtual Server is IBM's own self-service infrastructure — you typically manage the OS and applications yourself. Managed hosting adds a third-party provider that takes on some or all of that day-to-day operational work, and may or may not run on Power Virtual Server underneath.
Do I still need in-house IBM i or AIX skills with managed hosting?
Less than with a fully self-managed environment, but you'll still want enough internal knowledge to evaluate the provider's work, manage the relationship, and handle anything explicitly excluded from the contract.
What's typically included in a fully managed contract?
Common inclusions are infrastructure, OS patching, monitoring, and backup. Application-level support, security administration, and compliance reporting are sometimes included and sometimes billed separately — get the exact scope in writing.
How long are managed hosting contracts usually?
Terms vary widely by provider, but multi-year commitments are common. Confirm renewal terms, price escalation clauses, and exit or data-portability provisions before signing.
Can managed hosting providers support compliance requirements like HIPAA or PCI DSS?
Some do, but capability and current attestation status vary by provider. Ask for recent audit evidence specific to the environment your workload would run in, not just general company-level certifications.
Sources
- IBM Power Systems overview
- IBM Power Virtual Server — product overview (for comparison against self-service infrastructure)
- Individual provider contracts, SLAs, and audit reports — verify directly with each provider
Not Sure Managed Hosting Is the Right Fit?
Get an independent read on how it stacks up against Power Virtual Server or staying on-premises before you sign a contract.