Understanding the True Cost of Mainframe Maintenance

When CFOs ask "how much does our mainframe cost?" the answer they get is almost always wrong. Not because anyone is lying — but because the true cost of mainframe maintenance is distributed across so many line items, departments, and hidden opportunity costs that no single person in the organization sees the full picture.

The number most executives hear is the annual IBM licensing fee. That's like saying the cost of owning a car is the monthly payment. It ignores insurance, gas, maintenance, parking, depreciation, and the hours you spend sitting in traffic instead of taking the train.

We've analyzed the total cost of ownership for mainframe environments across dozens of organizations. The reality is sobering: the true annual cost of mainframe maintenance is typically 3–5x what leadership thinks it is. And it's growing faster than almost any other line item in the IT budget.

Here's where the money actually goes.

The IBM Licensing Black Hole

IBM's mainframe pricing model is built around MIPS (Million Instructions Per Second) — a measurement of processing capacity that determines your software licensing costs. And it's where the pain starts.

How MIPS Pricing Works

Every z-series mainframe has a rated capacity measured in MIPS or MSUs (Million Service Units). IBM and third-party software vendors charge based on your peak processing capacity — not what you actually use, but what you could use. Think of it as paying for a 10-lane highway when you typically only need 3 lanes, but once a month at quarter-end processing, you briefly need 8.

As of 2025, typical IBM software licensing costs range from $2,500 to $3,500 per MIPS per year for the full z/OS software stack. For a mid-size enterprise running at 10,000 MIPS, that translates to:

• IBM z/OS licensing: $3,000 × 10,000 = $30 million/year
• DB2 licensing: Additional $5–8 million/year
• CICS transaction processing: $3–5 million/year
• IMS, MQ, and middleware: $2–4 million/year

That's $40–47 million annually just for the software sitting on the mainframe — before a single line of business logic runs. And these costs increase every year. IBM has raised z/OS licensing fees by an average of 5–8% annually over the past decade, well above inflation.

The MIPS Trap

Here's the insidious part: as your business grows and transaction volumes increase, your MIPS consumption grows too. More MIPS means higher licensing costs. You're essentially being taxed on your own growth.

One regional insurance carrier we spoke with saw their MIPS consumption grow 15% over three years — not because they added new functionality, but because their customer base grew. Their IBM licensing costs jumped from $12 million to $16.5 million annually, a $4.5 million increase for doing exactly the same thing with more customers.

In the cloud, processing more transactions costs pennies more per unit. On the mainframe, it costs millions.

The Talent Crisis Tax

If IBM licensing is the biggest line item, COBOL talent is the fastest-growing one. The economics of mainframe staffing have shifted dramatically — and not in your favor.

The Numbers

The average COBOL developer in the United States is 58 years old (Micro Focus, 2024). Over 75% plan to retire within the next decade. Basic supply and demand is doing exactly what you'd expect:

• Average COBOL developer salary: $95,000–$130,000/year (up 35% since 2019)
• Specialized COBOL contractor rate: $100–$175/hour
• Emergency mainframe support: $200–$350/hour (weekend/after-hours)
• COBOL developer recruiter fees: $25,000–$40,000 per placement

A typical mid-size mainframe shop needs 8–15 COBOL developers for ongoing maintenance. At current market rates, that's $1.2–2.0 million annually in fully-loaded compensation. And it's getting worse every year as the talent pool shrinks.

But salary is only part of the story. The real cost is what happens when key developers leave.

Knowledge Concentration Risk

In most mainframe environments, 60–80% of critical system knowledge lives in the heads of 2–3 senior developers. When one of those developers retires or leaves, the organization faces a choice:

1. Hire a replacement (if you can find one — average time-to-fill for a senior COBOL role is now 6–9 months)
2. Pay a contractor ($150+/hour, often with a 6-month minimum commitment)
3. Distribute the work across remaining team members, increasing their workload and burnout risk

None of these options are good. All of them are expensive. And the trend line is clear: COBOL talent costs will only accelerate as the supply continues to shrink. As we detailed in our post on the COBOL programmer retirement crisis, this isn't a future problem — it's happening right now.

Infrastructure and Operations

Beyond software and people, the physical infrastructure of running a mainframe is a significant and often underestimated cost center.

Hardware

Modern IBM z16 mainframes start at approximately $250,000 for entry-level configurations, but enterprise configurations commonly run $2–5 million. With a typical refresh cycle of 4–5 years, that's $400,000–$1 million annually in amortized hardware costs.

But the mainframe doesn't exist in a vacuum. Supporting infrastructure includes:

• Dedicated data center space: Mainframes require specialized cooling, power, and physical security. A single mainframe footprint costs $150,000–$300,000/year in facility costs.
• Storage (DASD): Enterprise mainframe storage runs $500,000–$2 million/year depending on capacity.
• Network connectivity: Dedicated SNA/IP connectivity, channel extenders, and network hardware add $100,000–$250,000/year.
• Disaster recovery: A DR mainframe environment (required for any regulated industry) effectively doubles your hardware and facility costs. Budget $1–3 million/year.

Operations Staff

Mainframes require specialized operations staff beyond developers:

• Systems programmers (z/OS, CICS, DB2 administration): 2–4 FTEs at $120,000–$160,000 each
• Storage administrators: 1–2 FTEs at $100,000–$130,000 each
• Job scheduling/batch operations: 1–3 FTEs at $80,000–$110,000 each
• Security administrators (RACF/ACF2/Top Secret): 1–2 FTEs at $110,000–$140,000 each

Total operations staffing: $800,000–$1.5 million annually — and these roles are becoming just as hard to fill as developer positions.

The Hidden Costs Nobody Talks About

The line items above are at least visible in budgets, even if they're spread across departments. But the most damaging costs are the ones that never show up in any spreadsheet.

Integration Tax

Every time your organization wants to connect a modern system to the mainframe, it costs time and money. Building an API wrapper around a COBOL program typically takes 4–8 weeks and costs $50,000–$150,000 per integration point. A typical enterprise has 20–50 integration points, creating an ongoing integration maintenance burden of $500,000–$2 million annually.

Compare this to cloud-native systems where API integration is measured in hours or days, not weeks or months.

Opportunity Cost

This is the biggest hidden cost of all — and the hardest to quantify. Every week your engineering team spends maintaining COBOL code is a week they're not spending on:

• Building new customer-facing digital products
• Implementing real-time analytics and AI capabilities
• Launching mobile experiences
• Responding to competitive threats

We've seen organizations where 40–60% of IT budget goes to "keeping the lights on" with legacy systems, leaving only a fraction for innovation. As we explored in why COBOL costs more every year, this ratio gets worse over time, not better.

McKinsey research shows that companies spending more than 50% of their IT budget on maintenance grow revenue 2.5x slower than companies that have modernized their core systems.

Compliance and Audit Costs

Regulated industries face additional mainframe-specific costs:

• Audit preparation: Mainframe environments require specialized audit procedures. Budget $200,000–$500,000/year for SOX, PCI-DSS, or regulatory compliance activities related to legacy systems.
• Remediation: When auditors flag issues with legacy systems (and they increasingly do), fixing them in COBOL takes 3–5x longer than in modern systems.
• Cyber insurance: Insurers are starting to charge higher premiums for organizations running unsupported or legacy technology. Some are refusing coverage altogether.

Adding It All Up: The Real TCO

Let's build a complete picture for a mid-size enterprise (10,000 MIPS, 500 COBOL programs, 15-person mainframe team):

For many organizations, the true TCO is 50–70% higher than what leadership believes. And unlike cloud costs, which decrease as you optimize, mainframe costs compound upward year after year.

The ROI Case for Modernization

Understanding costs creates urgency. But the real question is: what does the math look like if you modernize?

A Realistic Comparison

Take our mid-size enterprise spending $55 million annually on mainframe operations. After a successful migration to cloud:

• Cloud infrastructure (AWS/Azure/GCP): $3–6 million/year
• Modern developer team (Java/Python, easier to hire): $1.5–2.5 million/year
• DevOps and operations: $0.5–1.0 million/year
• Licensing (open-source stack): $0.2–0.5 million/year
• Total post-migration: $5.2–10 million/year

That's a potential annual savings of $45–50 million. Even accounting for the cost of migration itself (typically $5–15 million with an AI-powered approach), the ROI payback period is often under 6 months.

The Five-Year View

The numbers speak for themselves. And this doesn't even account for the revenue growth enabled by faster innovation on a modern platform.

What To Do With This Information

If you've read this far, you probably have a suspicion that your organization's mainframe costs are higher than leadership realizes. Here's how to move forward:

1. Build the complete cost picture using the framework above. Pull data from IBM invoices, HR records, facility costs, and project budgets.
2. Quantify the opportunity cost by calculating what percentage of your IT budget goes to maintenance vs. innovation.
3. Model the post-migration state with realistic cloud and staffing costs.
4. Present the five-year comparison to leadership — the cumulative savings are impossible to ignore.

Want to see how these numbers apply to your specific environment? Our free COBOL Risk Assessment analyzes your mainframe footprint and generates a customized TCO comparison in minutes. It's the fastest way to get a clear-eyed view of what your mainframe is really costing you — and what you could save.

The first step to solving any problem is seeing it clearly. When it comes to mainframe costs, most organizations are flying blind. It's time to turn the lights on.