Picture this: You walk into a massive insurance company’s headquarters. The lobby’s got those fancy curved glass walls, employees tapping away on MacBook Pros, and someone’s literally talking about “AI-powered customer engagement” in the elevator.
Then you get to the IT department.
And there it is—Insure 90, running on IBM AS400 hardware from an era when floppy disks were still a thing. The system that’s older than most of the company’s employees is quietly processing millions of insurance policies, handling claims worth billions, and somehow… it just keeps working.
Welcome to one of tech’s weirdest paradoxes.
What Is Insure 90?
nsure 90 is a legacy insurance management system built on IBM AS400 (IBM i) infrastructure. It is used by insurance companies to manage policy administration, claims processing, payments, and regulatory workflows, and is still widely deployed in billion-dollar insurance operations due to its reliability and stability.
Why Replacing Insure 90 Can Cost Insurance Companies Millions
Here’s what keeps insurance CIOs up at night: Should they replace a decades-old system that actually works with something shiny and new that might work?
Because here’s the ugly truth—according to research from consulting firms tracking legacy system replacements, modernization results have been mixed, with many carriers not fully realizing expected returns. One European insurance group literally wrote off $500 million after abandoning an eight-year platforming project. Another finished their claims modernization but went 500% over budget.
Five. Hundred. Percent.
So when your boss asks, “Why are we still using Insure 90 when there are all these modern cloud platforms?” maybe the real question is: “Why would we risk half a billion dollars trying to fix something that isn’t broken?”
What Even IS Insure 90? (The Version Your CTO Won’t Tell You)
Let’s cut through the corporate speak.
Insure 90 is basically the plumbing of insurance companies. You don’t see it, you don’t think about it, but when it breaks, everything goes to hell.
It’s an insurance management platform that handles:
- Every policy detail from creation to cancellation
- Claims from “I bumped my car” to “Hurricane destroyed my house”
- Payments going in and out
- Risk calculations that determine if someone pays $50/month or $500/month
- Workflow routing so claims don’t just disappear into a black hole
The system runs on IBM AS400 (now called IBM i, because IBM likes renaming things). This platform was designed in the 1980s with one obsessive goal: Never. Ever. Go. Down.
And guess what? It doesn’t.
The Origin Story Nobody Talks About
Insure 90 wasn’t built by some Silicon Valley startup with ping pong tables and free kombucha. It was created during a time when insurance companies needed something that could handle thousands of transactions per second without choking.
The developers used CREATE90 technology specifically for insurance ERP (that’s Enterprise Resource Planning, aka “the software that runs everything”). They picked IBM AS400 because it was known for two things:
- Reliability that borders on obsessive
- The ability to handle massive databases without melting down
Companies like CGU, Ansvar, Mitsui, and Admiral signed up. Beacon Insurance in Trinidad deployed it across their Caribbean operations. And here’s the kicker—they’re still using it in 2026.
Not because they can’t afford to upgrade. Not because they’re technologically backwards.
Because it works.
The Real Reason Insurance Companies Keep “Old” Tech Alive
Let me tell you about what happened at Beacon Insurance.
They sat down, did the math, and looked at replacing Insure 90. The costs? Astronomical. The timeline? Years. The risk? Career-ending if something went wrong.
So instead of ripping everything out like they were renovating a house, they did something smarter—they renovated around it. Using LANSA’s modernization framework, they added modern workflow capabilities without touching the core system.
It’s like keeping the engine of a reliable old truck but upgrading the interior, adding a backup camera, and installing Bluetooth. The thing still drives like a beast, but now it doesn’t feel like you’re time-traveling to 1995.
One insurance provider who went this route reported cutting their processing time by 30%. Not by replacing Insure 90—by making it work smarter.
Four Reasons “Outdated” Doesn’t Mean “Useless”
1. When “Always On” Actually Means Always On
According to industry data, legacy maintenance consumes up to 80% of the IT budget for many insurers. But you know what costs even more? System downtime.
When someone’s house burns down at 2 AM and they need to file a claim, they don’t care about your “scheduled maintenance window.” The AS400 platform running Insure 90 is known for supporting financial organizations and insurers as critical infrastructure that just… doesn’t fail.
Your modern cloud platform with its fancy microservices architecture? It might have four nine’s uptime (99.99%). Impressive, right?
AS400 systems regularly hit five or even six nine’s. That’s the difference between 52 minutes of downtime per year versus 5 minutes. When you’re dealing with insurance, those 47 extra minutes could mean millions in losses.
2. The Integration Party Trick That Shocks Everyone
“But surely,” you’re thinking, “a system from the 80s can’t talk to modern apps, right?”
Wrong.
Admiral Insurance connected Insure 90 to IBM’s Enterprise Content Management system. They created a unified desktop where staff could pull up policy documents and process data simultaneously. No more tabbing between twelve different windows like some kind of digital circus act.
Modern Insure 90 implementations integrate with:
- Web APIs (yes, really)
- Mobile apps
- Cloud storage
- Contemporary payment gateways
- Document management systems
- Even AI analytics tools
The secret? IBM never stopped updating the IBM i platform. While the core architecture stayed rock-solid, they kept adding modern connectivity. It’s like how your grandpa can still text you even though he’s using a flip phone—different tech, same result.
3. The Budget Conversation CFOs Actually Like
Here’s a conversation that happens in insurance companies more often than you’d think:
IT Director: “We need to modernize our core system. It’ll only cost $5-8 million and take 18 months.”
CFO: laughs in spreadsheet “No.”
Replacing an insurance core system isn’t like upgrading your iPhone. Insurers will spend about $6.5 billion and $10.5 billion in EMEA and North America respectively on core IT modernization from 2024 to 2026. That’s billion with a B.
Meanwhile, Insure 90 just keeps chugging along with its manageable maintenance fees. Users report that even after years of operation, the costs remain reasonable—especially compared to modern cloud platforms where your bill can suddenly triple because you hit some usage threshold.
4. Backward Compatibility Is a Superpower
Applications written for Insure 90 decades ago still run on today’s IBM Power Systems. Without rewrites. Without “minor adjustments.” Without consulting firms charging $400/hour to fix things.
For insurance companies with highly customized products—and they all have customized products—this is absolute gold. You can add new features without breaking the 10,000 other things that depend on how your system works.
How Insure 90 Actually Powers Real Insurance Operations
The 90/10 Insurance Thing (Where the Name Makes Sense)
Ever heard of the “90/10 coinsurance rule” in property insurance? It’s where your coverage needs to meet at least 90% of your property’s replacement value, or you get penalized during a claim.
Insure 90 handles these calculations automatically. For residential and commercial property insurers, this means:
- Accurate property valuations
- Proper coverage percentage tracking
- Automated claim adjustments based on coinsurance penalties
- Documentation that survives audits
Try explaining that business logic to a developer building a modern cloud platform. Now imagine documenting every edge case, every state regulation variation, every exception. You’ve just added six months to your project timeline.
The 90-Day Coverage Game
Short-term health insurance plans often run for—surprise—90 days. These plans serve people between jobs, waiting for employer coverage, or just needing temporary protection.
Insure 90 manages:
- Rapid enrollment (because nobody wants to wait 2 weeks for temporary coverage)
- Essential service tracking
- Quick claims for doctor visits and emergencies
- Premium calculations for short-term policies
The system was literally designed with these timeframes in mind. Modern platforms? They’re usually optimized for annual policies and get weird with short-term coverage.
Travel Insurance and Supplemental Chaos
Travel insurance is legitimately complicated. You’ve got trip cancellations, medical emergencies in foreign countries, lost luggage, adventure sports riders, pre-existing condition exclusions…
Insure 90’s flexibility lets companies configure all these moving parts without hiring a team of developers every time they want to offer coverage for scuba diving in Thailand.
Supplemental insurance—accident coverage, critical illness, hospital indemnity—adds another layer. These plans provide cash benefits directly to policyholders for out-of-pocket expenses. Insure 90 handles these without breaking a sweat because it was designed when insurance was already complicated.
The Technical Stuff (For the Nerds in the Room)
Database Architecture: Insure 90 runs on DB2 databases inside the IBM i environment. For non-database geeks, this means it’s using proven relational database tech that can handle complex insurance products with multiple coverage tiers, a million exclusions, and pricing that varies based on 47 different factors.
Programming Languages: Mostly RPG (Report Program Generator) and COBOL. Yes, I can hear you groaning. But here’s the thing—these languages are stable, well-documented, and integrate fine with modern languages like Java, Python, and PHP through IBM i’s environment.
Workflow Management: Modern implementations added sophisticated workflow frameworks that track every step from policy creation to claim settlement. These tools identify delays, ensure regulatory compliance, and generally keep everything moving.
Security: Running on IBM i gives you enterprise-grade security with built-in encryption, role-based access controls, and comprehensive audit trails. For handling sensitive customer data and meeting regulatory requirements, this matters a lot more than having a trendy tech stack.
The Modernization Middle Path (AKA Having Your Cake and Eating It Too)
Smart insurance companies aren’t doing the “rip and replace” thing anymore. They’re taking a hybrid approach:
Keep the reliable core → Insure 90 continues handling the mission-critical stuff
Add modern interfaces → Build web portals and mobile apps that talk to Insure 90 via APIs
Integrate selectively → Connect document management, e-signatures, payment processing
Automate intelligently → Add AI for fraud detection, chatbots for customer service, analytics for risk assessment
Migrate gradually → Move non-critical systems first, test thoroughly, minimize disruption
Beacon Insurance’s approach became a case study in smart modernization. They used workflow frameworks that integrated seamlessly with Insure 90 without requiring complex data conversion. The result? Better efficiency, happier customers, no catastrophic failures.
Who Should Actually Care About Insure 90 in 2026?
You’re a Regional Insurer
You value reliability over flashy features. You need systems you can customize extensively without hiring expensive consultants. You’re competing on service and pricing, not on having the newest tech.
Verdict: Insure 90 might be perfect.
You’ve Got Decades of Legacy Data
You have policy histories going back 30+ years. Customer relationships spanning generations. Claims data that’s invaluable for risk assessment. Migrating all that without losing something critical? Nightmare fuel.
Verdict: Keeping Insure 90 and modernizing around it makes sense.
You Operate in Heavily Regulated Markets
System reliability and audit trails matter more than innovation speed. Your regulators want comprehensive documentation. Downtime could trigger compliance issues.
Verdict: Proven stability beats cutting-edge features.
You Have AS400/IBM i Expertise
Your team understands the platform. They can optimize it, troubleshoot it, and leverage its capabilities. Retraining everyone on a completely new platform would cost a fortune.
Verdict: Use what you know well.
The Honest Downsides (Because Nothing’s Perfect)
The Talent Problem Is Real
Finding RPG and COBOL developers who understand insurance systems? Good luck. Job sites show thousands of open AS400 positions, which means there’s demand but also scarcity.
Young developers coming out of college learned Python, JavaScript, and React. They didn’t learn RPG400. You’ll be hiring from a shrinking pool and probably paying premium rates.
The Interface Looks Like Windows 95 Had a Baby with a Calculator
The original green-screen terminal interface is… not pretty. New employees expect sleek UIs, not text-based systems that look like something from WarGames.
You can modernize the front-end, but that requires investment. It’s doable, just not free.
The Learning Curve Hurts
Employees accustomed to intuitive modern software will struggle initially. Training takes time and money. Expect complaints during the transition period.
The Perception Battle Never Ends
Try convincing your board, investors, or potential tech talent that a system running on “1980s technology” is actually the smart choice. Even when you’re technically correct, you’re fighting an uphill battle against the “old = bad” assumption.
Where Does Insure 90 Go From Here?
Honestly? It’s not going anywhere fast.
The insurance industry doesn’t move like tech startups. Systems that work reliably stick around for decades. As long as IBM keeps supporting the Power Systems platform and IBM i operating system—and they show no signs of stopping—Insure 90 will keep processing policies.
The likely future looks like:
Continued front-end modernization → Better UIs while keeping the robust backend
API-first architecture → Everything talks to everything else via web services
Hybrid cloud strategies → Some workloads move to cloud, core stays on-premises
Selective AI integration → Machine learning for fraud detection, risk assessment, customer service
Incremental replacements → Maybe some modules get replaced over 10-20 years, but not all at once
Maintained compliance → Regulatory requirements keep evolving, Insure 90 adapts
Some companies will eventually migrate completely. But based on current trends, many will still be running Insure 90—or at least parts of it—in 2035, 2040, maybe longer.
And you know what? That’s perfectly fine.
The Bigger Lesson Here
Insure 90’s continued success teaches us something important about enterprise technology that the tech industry doesn’t like to admit:
New doesn’t automatically mean better.
Boring and stable often beats exciting and risky.
Total cost of ownership includes hidden costs like migration risk, training, downtime, and failed projects.
Sometimes the best investment is maintaining what works rather than chasing what’s new.
When McKinsey research shows that organizations that update their IT are more productive than their peers stuck on legacy technologies, achieving an over 40% higher number of policies per full-time equivalent, they’re talking about smart modernization. Not just replacing everything because it’s old.
The insurance companies still running Insure 90 aren’t technology laggards. Many of them are making deliberate, calculated decisions that their CFOs, CIOs, and boards support.
They’re choosing to handle billions of dollars in policies on a proven system rather than gambling on unproven platforms that might offer marginal improvements at massive cost and risk.
The Bottom Line (In Plain English)
If you’re trying to understand why Insure 90 still matters in 2026, here it is:
It’s a specialized insurance management platform running on IBM AS400/IBM i hardware. It handles policy administration, claims processing, payments, and workflow management for insurance companies that prioritize reliability over novelty.
Companies like CGU, Ansvar, Mitsui, Admiral, and Beacon Insurance still use it. Not because they’re behind the times, but because it delivers what they need: stability, extensive functionality, manageable costs, and proven performance handling billions in insurance operations.
The system integrates surprisingly well with modern technology. Through APIs, web services, and middleware, it connects to customer portals, mobile apps, document management systems, and analytics tools.
It’s not perfect. The talent pool is shrinking, the interface needs work, and convincing people that “old” can be “smart” requires effort.
But for many insurance operations, especially regional insurers, companies with complex legacy data, and organizations in heavily regulated markets, Insure 90 represents a viable path forward.
It’s a reminder that in enterprise IT, sometimes the boring choice is the brave choice. Sometimes keeping the lights on matters more than chasing the next big thing. And sometimes, the best technology decision is the one that lets you focus on your actual business instead of managing IT disasters.
Insure 90 isn’t sexy. It isn’t going to win any innovation awards. It won’t get your company featured in tech blogs.
But it works. Day after day, year after year, decade after decade.
And in insurance, that’s worth more than all the buzzwords in Silicon Valley.
Your Burning Questions About Insure 90 (Answered Honestly)
Can regular people buy Insure 90 insurance?
No. Insure 90 isn’t a consumer product you can purchase. It’s the management system that insurance companies use internally. However, if you buy insurance from companies like CGU, Ansvar, or Mitsui, your policy might be managed by Insure 90 behind the scenes—you just wouldn’t know it.
Is anyone actually supporting Insure 90 in 2026?
Yes, through specialized IT consultancies and IBM i service providers. Companies like Ravenswood Consulting, LANSA, and various IBM partners provide implementation and ongoing support. It’s not a single vendor situation, but support is definitely available if you know where to look.
What’s this actually cost to run?
That’s the “it depends” answer nobody likes. Costs vary wildly based on company size, customization needs, and existing infrastructure. However, maintenance fees stay relatively manageable compared to modern cloud platforms where costs can spiral unpredictably. If you’re already running IBM i environments, the additional cost is even more reasonable.
What happens when AS400 expertise completely dies out?
Fair concern. IBM continues actively developing Power Systems and IBM i, so complete abandonment isn’t happening anytime soon. Companies have contingency plans ranging from gradual migration to maintaining legacy environments with archived data. Some are training new developers in RPG and COBOL specifically to maintain these systems. It’s a real issue, but not an immediate crisis.
Can Insure 90 actually work with modern cloud stuff and AI?
Absolutely. Through web services, APIs, and middleware solutions, Insure 90 connects to contemporary systems without issue. Many successful modernization projects keep Insure 90 as the core while adding modern interfaces, cloud storage, AI analytics, and mobile apps. The IBM i platform supports this kind of integration surprisingly well.
Why don’t insurance companies just start fresh?
Because starting fresh is terrifying and expensive. A central European group gave up on a large cross-country platforming project after eight years, with a write-off of more than $500 million; a carrier in southern Europe completed its claims-platforming program but did so 500% over budget. When the risk of failure is that high and the costs are that unpredictable, keeping a working system and modernizing selectively makes a lot more business sense.
Is Insure 90 secure enough for today’s threats?
Running on IBM i provides enterprise-grade security including built-in encryption, role-based access controls, and comprehensive audit trails. IBM actively updates security features on the platform. Is it as trendy as zero-trust cloud-native security? No. Is it effective? Yes. Many financial institutions and insurance companies trust IBM i with their most sensitive data.
This deep-dive analysis was researched and written for Viravio.com to help insurance technology professionals, IT decision-makers, and industry observers understand the practical realities of legacy systems in modern insurance operations. For more honest, practical insights into enterprise software, legacy modernization strategies, and insurance technology, explore our complete resource library.
