For 20 years, Avada Software has followed a path that is increasingly rare in enterprise technology: steady, customer-driven growth built on deep engineering rather than hype.

Since its founding in 2006, Avada has focused on solving real operational problems for enterprise IT teams responsible for middleware and integration infrastructure. Over two decades, that focus has shaped not only the company’s flagship product, Infrared360, but also the way the company itself has grown: deliberately, independently, and with a close connection to the needs of the people who run complex environments every day.

This anniversary is more than a milestone. It is a chance to look back at how Avada was built, what made it different from the beginning, and why that approach still matters today.

Avada Software was founded by Rob Sordillo and Peter D’Agosta, who first worked together in 1999 at a startup web services company in Portsmouth, New Hampshire. Their early experience gave them firsthand exposure to the complexity of enterprise technology environments and the operational challenges customers faced in managing them.

After moving on to other roles and reconnecting later, they began discussing the idea of building a middleware management platform of their own. They believed there was room in the market for something better: a solution designed around the practical realities of enterprise operations rather than the limitations of existing tools.

They also made a defining decision early: Avada would be built without angel investors or venture capital. The company was entirely bootstrapped. Rob began developing the product while working as a contractor, and during that early period the founders did whatever was necessary to keep moving forward and get the company off the ground.

That decision to build independently shaped more than the company’s finances. It shaped its culture. From the start, Avada had to earn every customer by solving real problems well enough that organizations would trust a new company with critical infrastructure operations.

Avada Software, LLC was officially created on March 1, 2006. The company’s product, Infrared360, launched with support for WebSphere MQ v5.3 & 6.0, but what made it stand out was not just the technology it supported. It was the architecture behind it.

From the beginning, Infrared360 was designed as a web-based, fully agentless platform. At a time when many enterprise management solutions depended on distributed agents, custom scripts, and ongoing deployment overhead, Infrared360 took a different approach. It ran on a single server, without requiring software to be deployed across managed endpoints.

That design choice addressed a real operational pain point by giving enterprise teams deep environment visibility without the burden of maintaining yet another layer of infrastructure.

The product also launched with a delegated security model at a time when many enterprise tools still treated access as an all-or-nothing proposition. Instead of forcing organizations into broad administrative privileges, Infrared360 allowed more granular access for different user groups, including developers, QA teams, and operations staff. That was an important early differentiator and reflected a larger pattern that would define the product for years: practical innovation aimed at how enterprise teams actually work.

The market responded quickly.

By March 2006, Avada had hired its first sales representative. By May, the company had landed its first three customers in banking, airline, and pharmaceutical environments. These early wins provided a critical layer of validation beyond immediate revenue. They proved that enterprise customers were willing to invest in a platform built from scratch when it directly addressed their operational needs.

Later that same year, Avada signed its first international customer and began exhibiting at IBM Impact conferences, increasing its visibility in the broader middleware market.

Those early milestones helped establish an important theme in Avada’s history: the company was never built around abstract market positioning alone. It grew because customers saw immediate value in the product’s approach.

As the customer base expanded, so did the scope of the platform.

What began with a core focus on MQ monitoring broadened as customers asked for visibility across adjacent technologies. In 2008, Avada added support for WebSphere Message Broker, now IBM App Connect Enterprise, as well as JMS. This was a logical step. Many MQ customers were already operating broker environments and wanted a unified way to monitor and manage both.

At the same time, Avada was steadily deepening its enterprise footprint. A major U.S. bank became one of the company’s largest early customers in 2007. Over the next several years, the customer base expanded across the United States and Europe, including financial institutions in Italy and Switzerland. In 2009, the company secured its first Fortune 10 customer.

These consecutive enterprise wins demonstrated that Avada’s architecture could confidently scale into large, demanding enterprise environments where reliability, control, and operational visibility mattered most.

To support this expanding enterprise footprint, Avada systematically scaled its internal operations.

In 2010, Avada signed its first major reseller partner and added its first additional engineer to support product development. By 2012, the company had grown to its largest internal staff size to date, with roles spanning engineering, QA, sales, and support.

Even with this growth, the company remained notably lean. For years, Pete handled a wide range of responsibilities across support, QA, technical sales, and operational business functions. This hands-on management style, common in bootstrapped companies, reinforced Avada’s attentiveness to customer needs. Product decisions were shaped by direct, unfiltered exposure to the technical and operational realities customers faced daily.

In 2018, Avada hired its first dedicated full-time support engineer, allowing leadership to focus more broadly on growth while continuing to invest in customer experience. It marked another step in the company’s deliberate evolution, adding structural capacity where it mattered while staying grounded in its original operational strengths.

One of the clearest themes in Avada’s 20-year story is that the company’s roadmap was driven by customer needs rather than technology trends alone.

Throughout the 2010s, Avada steadily expanded Infrared360’s support for additional enterprise technologies. WebSphere Application Server support was added in 2011. TIBCO EMS support followed in 2013 and expanded further in 2014.

In 2016, Avada added support for IBM DataPower, a technically demanding integration because of its XML-driven interfaces. Supporting DataPower required the platform to make URL calls, retrieve XML responses, and parse them programmatically. This substantial engineering effort was undertaken specifically to give customers deeper operational visibility into a highly complex layer of their infrastructure.

The same pattern continued in 2018, when Avada introduced several major capabilities, including IBM FTE monitoring, SSH support, Application Flow Diagrams, and Certificate Inspector. The Certificate Inspector feature is a particularly strong example of Avada’s customer-centered approach. It was built directly from customer feedback to address the tedious and error-prone process of tracking certificates manually, automating a labor-intensive task to reduce operational risk.

That year also marked an important usability milestone with the addition of dashboards and portlets. These enhancements helped users move beyond raw data and toward clearer operational insight, giving teams more intuitive visibility into what was happening across their environments.

As enterprise architectures changed, Avada continued evolving Infrared360 to meet new demands while preserving the principles that established its early value.

In 2019, the platform added REST enablement and microservice interfaces. In 2021, the user interface was redesigned using Bootstrap, modernizing the experience across the application. Support for Kafka was introduced in 2022, followed by ActiveMQ in 2023.

In 2024, Infrared360 added cluster deployment options and became fully REST-enabled. The clustering capability was especially significant because it was built from scratch and operated without a central cluster manager. That represented a meaningful engineering accomplishment and reflected Avada’s continued investment in designing for real-world enterprise requirements rather than taking the simplest path.

Then, in 2025, the platform underwent a major architectural upgrade, including transitions to Spring 6, Struts 7, and JDK 21. This was not just a technology refresh. It was part of a longer-term evolution toward modern frameworks and a stronger foundation for the future, while maintaining continuity with the platform’s existing architecture and customer base.

That balance, modernizing without abandoning what customers rely on, remains one of the strongest themes in Avada’s story.

Looking back over two decades, Avada Software’s story is not simply about staying in business for 20 years. It is about building a durable company in a demanding technical niche by staying close to customers, making thoughtful engineering decisions, and evolving with the market without chasing every trend.

From its earliest days as a bootstrapped startup to its continued investment in modernization and broader technology support, Avada has remained focused on helping enterprise teams manage increasingly complex middleware environments with greater visibility, control, and confidence.

This anniversary serves as a powerful reflection of what can happen when a company spends twenty years solving practical problems for actual users, one deliberate step at a time.

And, as enterprise environments continue to evolve, that same mindset is likely to matter even more in the years ahead.