From Products to Engines - The Story Behind Sitemule

Every platform has an origin story. Sitemule's begins not in a boardroom or a strategy document, but in the server rooms of the mid-1990s, on a platform the rest of the industry had already begun to overlook: the IBM i.

Filling the Gaps in the Operating System

The IBM i (then the AS/400) was - and remains - one of the most reliable business platforms ever built. But reliable did not mean complete. In the mid-1990s, our customers were running their entire businesses on the platform, and they kept encountering the same missing pieces: How do we keep an eye on the health of our systems around the clock? How do we get documents and messages out of the machine and into the hands of customers and partners?

The operating system had no good answer. So we built one.

BlueNote was born to watch over the systems themselves - monitoring jobs, message queues, and system events, and alerting operators before small problems became outages. For companies whose business stopped when the IBM i stopped, this was not a luxury. It was survival.

BlueSeries answered the second question: communication. Fax, email, FTP, XML invoicing, SMS messaging - BlueSeries turned the IBM i into a communication hub, letting business applications send an invoice, a confirmation, or an alert through whatever channel the receiver needed. Long before "integration" became a buzzword, BlueSeries was quietly moving millions of business documents between companies, directly from the platform where the business logic lived.

These two products covered the general business needs of the era. They spread across the IBM i community, installation by installation, country by country - and they earned something that cannot be bought: trust.

The Modernization Wake-Up Call

Then the world changed. At the beginning of the 2000s, our customers began asking a new kind of question. Their systems worked - decades of business logic, refined and battle-tested - but the world around those systems had moved. New employees expected a browser, not a green screen. Business partners expected web services, not file transfers. IT departments expected open standards, modern languages, and system integration.

The prevailing advice at the time was brutal: rip it out and replace it. We disagreed. The legacy systems were not the problem - they were the asset. What was missing was a bridge.

IceBreak became that bridge. A web application server running natively on the IBM i, IceBreak made it possible to build modern web applications and services directly on top of existing programs and databases. RPG and COBOL logic that had run reliably for twenty years could suddenly speak HTTP, serve web pages, and expose services - with only smaller adjustments, and without middleware, without external servers, and without throwing anything away.

IceCap completed the picture at the user interface. It transformed the classic 5250 screens into modern, browser-based interfaces - giving the next generation of end users the experience they expected, while the proven applications underneath kept doing exactly what they had always done.

Together, the four products now covered the full stack of a modernization journey: the database, the applications, the integration, and the user interface. They became an essential core part of the daily operation for hundreds of companies around the world - and they are still running at customers on the IBM i platform today.

The Turning Point - From Four Products to Four Engines

By the time two decades had passed, something had become clear to us. IceBreak, IceCap, BlueSeries, and BlueNote were no longer just four products. They were four proven, high-performance foundations - each refined through twenty years of real-world production use, each solving a fundamental problem that every modernization effort eventually faces:

Web serving and microservice-driven architecture - the legacy of IceBreak
Screen and interface transformation - the legacy of IceCap
Messaging and communication - the legacy of BlueSeries
System monitoring - the legacy of BlueNote

But as standalone products, they could only ever solve their own corner of the problem. Customers didn't want four tools; they wanted one path - a realistic, scalable way to modernize without betting the company on a risky replacement project.

So we made a decision that defined the next chapter: the products would become engines.

Instead of retiring them or rewriting them, we did what we had always advised our customers to do with their own legacy systems - we reused the proven core and modernized around it. The four products were transformed into fully integrated runtime engines, delivering their functionality as runtime services to a new generation of purpose-built modules, all presented through a single, unified, browser-based workspace: the Sitemule Platform.

It was, in a sense, the ultimate proof of our own philosophy. We modernized ourselves the same way we modernize our customers.

Sitemule: The Full Potential Realized

Inside Sitemule, the four engines finally outlive their full potential. What was once four separate value propositions is now one coherent ecosystem - eight purpose-built modules powered by four battle-hardened engines, running natively on IBM i with no middleware and no external infrastructure.

The engines handle everything beneath the surface: web serving, service-based architecture, screen transformation, messaging, and monitoring. The modules build on top of them, covering everything from visual and functional modernization to domain-driven applications, AI context-specific guidance, and documentation for both technical staff and end users.

And true to the story's beginning, the engines still serve the community that made them possible. Essential functions have been released as open source, engaging developers across the IBM i community. Partners use the engines as replacements for outdated technologies and as enhancements to their own solutions.

Thirty Years, One Thread

Looking back, the thread is unbroken. In the 90s, we filled the gaps in the operating system. In the 2000s, we built the bridge between legacy and modern. Today, with Sitemule, the four products that carried hundreds of companies through those decades have become the engines carrying them into the next one.

IceBreak, IceCap, BlueSeries, and BlueNote didn't retire. They were promoted.