IBM Power Virtual Server Pricing: How the Bill Is Built

IBM Power Virtual Server in IBM data centers bills a small set of meters: virtual server instances (processor cores and memory in GB), storage volumes and snapshots (GB), dedicated hosts (host units), and the licensed operating systems that ride along with each instance. Each resource carries a monthly rate that is metered every hour, and IBM's worked example uses a 730 hour month. Resize a machine mid-month and the change is prorated by the hour, which is what makes scheduled downsizing worth the automation effort.

Two framing facts matter before any line item. First, IBM labels every price in its documentation illustrative and points to its cost estimator for the numbers that actually bill; rates also vary by region, and the examples below are IBM's Americas figures. Second, stopping an instance does not stop the meter. IBM's pricing doc says it plainly: if you stop the LPAR, the billing process is not stopped, and you are charged even if the instance is in a suspended state. Billing ends only when you delete the instance.

Memory is priced per GB against a ratio of 64 GB per core. Stay at or under the ratio and you pay the standard rate; go over and the excess bills at a premium high-use RAM price, with separate invoice part numbers for standard and high-use gigabyte-hours across Power9, Power10, and Power11 systems. IBM's own example draws the line: more than 16 GB on 0.25 cores triggers the premium, while 128 GB on 2 cores does not. Memory-heavy, CPU-light workloads, common in consolidated IBM i estates, are exactly the shape that trips this rule.

There is a documented escape hatch: virtual servers configured within a Shared Processor Pool do not incur the additional per-instance core cost or the high-use memory parts, per IBM's pricing doc. For estates with many small LPARs, an SPP can restructure the same workload into a noticeably cheaper bill.

For IBM i shops, the operating system is usually the line that decides the bill. IBM's pricing doc states that PowerVS pricing for AIX and IBM i includes the license and IBM software maintenance, metered per core per hour. The included IBM i stack is 5770-SS1 with unlimited users plus dozens of bundled licensed programs; three products cost extra through PowerVS (Cloud Storage Solutions 5773-ICC, PowerHA 5770-HAS, and Rational Development Studio 5770-WDS), and IBM states you cannot use existing licenses for those three. A custom image does not dodge the charge either: IBM prices the OS license the same whether you deploy a stock or custom image. The exception is IBM's Moveable Operating License, which moves existing on-premises IBM i entitlements to PowerVS and bills on reduced mobile, SWMA paid meters; IBM directs customers to its support team for the details. Our guide to IBM i licensing in the cloud goes deeper on entitlement portability.

On Power10 and later systems, IBM i billing runs through software tiers that set the per-core rate and cap instance size at the same time. For a sense of magnitude, when PowerVS launched in 2019 IT Jungle reported the IBM i P10 license at roughly $1,000 per core per month and P30 near $2,200. Those figures are dated and current amounts must come from IBM's estimator, but they explain why the license, not the hardware, dwarfs everything else for small IBM i shops.

Release age is its own meter. IBM's release notes state that service extension pricing has been automatically added to the IBM i charge for 7.3 usage since October 1, 2023, and per-tier service extension core-hour billing parts exist for P05 through P30; the surcharge amount is not published in the docs. IBM i 7.4 reaches end of standard support on September 30, 2026 per IBM's announcement letter as reported by IBM i trade press, so budget for the same surcharge on 7.4 after that date and verify with IBM, since the PowerVS release notes had not confirmed it as of this writing. AIX bills through scale-out and scale-up license core-hour meters; AIX 7.1 was announced for service extension, but IBM's April 2024 release note says it continues at standard usage rates until further notice, so check its current status before budgeting. Linux is either a full subscription through IBM (Red Hat Enterprise Linux and SUSE meters) or bring your own subscription purchased directly from the vendor.

There is no public reserved-instance price list for PowerVS in IBM data centers. Discounts are account-level: IBM's Enterprise Savings Plan grants platform-wide discounts in exchange for a committed spend, and IBM's FAQ states that overage on the account continues to receive the discount even after the commitment term ends. IBM marketing has cited committed-use savings of up to about 17 percent; we could not verify that figure on a fetchable IBM page as of this writing, so treat it as directional and negotiate from your own numbers.

For large steady estates there is PowerVS Private Cloud, IBM-managed pods in your own location that bill the same meter families against a minimum committed spend: you pay the commitment or the metered consumption, whichever is greater. You can add nodes but cannot reduce the node count, and the docs state no commitment term length, so get both in writing before signing. Committed spend belongs in the same spreadsheet as your one-time migration costs; our IBM Power migration cost guide covers that side of the ledger.

Because every published number is illustrative, a PowerVS budget stands on the estimator, not the docs. Build the configuration in IBM's estimator for your actual region, then interrogate the result: which IBM i software tier is assumed and what happens when you outgrow its cap; whether memory exceeds 64 GB per core anywhere; which tier the boot images landed on; whether any LPAR runs a release in service extension; what Transit Gateway data transfer costs at your real replication volume; and which Enterprise Savings Plan or promotional discount applies, in writing. Our Power cloud cost estimator produces an independent directional figure to check against, and an independent assessment pressure-tests the whole business case before you commit.