Armeen Mazda Took the Long Way to Modern Software

There is a particular kind of suspense in old enterprise software. The interface may be gray. The database may remember the first Clinton administration. The developer who understands the oddest module may be nearing retirement. Yet every morning, somebody opens the application and the company begins moving money, inventory, permits, claims, or people through the world. The system is old in the way a bridge is old: its age matters less than the traffic depending on it.

Armeen Mazda has built his career around that traffic. As co-founder and CEO of Appeon, he operates in a corner of technology where progress cannot be measured by how cleanly the past is deleted. Appeon's central constituency is the PowerBuilder developer, often responsible for applications with years of business rules folded into them. Mazda's proposition has been consistent: keep the useful knowledge, change the constraints, and give the people maintaining the software a credible route to the next platform.

This is less cinematic than the standard Silicon Valley rewrite. It is also closer to how most technology changes. The spreadsheet remains while a dashboard arrives. The mainframe gains an API. The client/server application learns to speak cloud. A company rarely wakes up in a new world. It commutes there.

“We leverage existing investments, skills, and people, then bridge the gap between today and tomorrow.”Armeen Mazda, 2009

The browser before the buzzword

Mazda's route into this problem began before “modernization” became a budget category. He graduated from UC Berkeley's Haas School of Business after studying there from 1997 to 1999. Before Appeon, he co-founded NetUpSide, a Silicon Valley incubator for technology startups. Appeon was founded in 1999; by 2000, Mazda was working with PowerBuilder technologies inside the company he had helped establish.

The early patent record is a useful time capsule. In 2001 and 2002, Mazda and three co-inventors filed applications for techniques that let browsers behave more like responsive software: calling remote functions through JavaScript without plug-ins, updating parts of a page without rebuilding the whole thing, transmitting data over HTTP without cluttering browser history, synchronizing HTML interface controls, and translating Windows interface logic to the web. Five U.S. patents followed in 2005 and 2006.

The claims are technical, but the instinct behind them is easy to recognize: preserve context. Do not make the user reload everything to change one thing. Do not demand a heavy installation to create an interactive experience. Reduce the cost of crossing from one computing model to another. Years later, the same instinct would surface in Appeon's pitch for taking PowerBuilder applications to browsers, mobile devices, APIs, and cloud infrastructure.

An apprenticeship in the whole company

Mazda did not arrive at the CEO role by staying in a single lane. At Appeon he worked across product management, business development, and operations. That sequence matters. A modernization product lives or dies in the seams between those functions. Engineering decides what can be converted. Product decides what should be converted. Business development learns which promise gets a meeting. Operations discovers which promise survives contact with a customer's actual stack.

By 2009, Mazda was president and CEO, explaining Appeon for PowerBuilder 6.2 in language that sounds remarkably current. The company was serving nearly 1,000 customers at the time. Mazda described its developers as a large pool defining the roadmap and argued against the expensive “scrap and rewrite.” The surface vocabulary was Vista-style interfaces, Java, and .NET. The deeper sale was continuity.

“Appeon is about knocking down barriers,” he said. The line is short enough to fit on a slide, but it also describes the commercial logic. A barrier can be a programming language a team has not learned, a browser plug-in users cannot install, a deployment process that cannot reach remote workers, or a migration budget that loses to three more urgent projects. Remove enough barriers and an old application does not need to become young. It only needs to become useful in the next environment.

The platform changes hands

In July 2016, the relationship between Appeon and PowerBuilder changed scale. Appeon signed an agreement with SAP to develop a new generation of the platform and became responsible for developing, selling, and supporting its own PowerBuilder-powered offering. A company that had spent years extending the platform now carried responsibility for its direction.

Mazda's announcement focused on PowerBuilder's loyal following and the unusual combination of developer productivity with rich business interfaces. Appeon's plans ranged from mobile and cloud deployment to test-driven development and continuous integration. The first Appeon PowerBuilder release followed in 2017. What looked like a product handoff was also a transfer of trust: teams with production applications needed to believe there would be releases, support, compatibility, and a path through the next operating-system or database change.

PowerBuilder's persistence makes more sense when viewed through switching costs that are not merely financial. The code embodies exceptions that never made it into a requirements document. The users have muscle memory. The developers know which table cannot be touched during month-end close. A rewrite must rediscover all of that while producing something visibly new. An incremental path starts with the knowledge already present.

The roadmap is a conversation

Mazda's public work now has a recurring rhythm. He opens Appeon's Elevate conference with the wide-angle view, then product specialists go deep. He visits local groups and release events. In July 2024, he presented in Osaka and Tokyo on PowerBuilder's features, the rebuilt PowerServer, and the roadmap. At Elevate that December, he hosted a roadmap discussion after the keynote. In April 2025, the circuit included PowerBuilder user groups in London and Berlin.

The rooms are part of the product process. At Elevate 2025, Mazda set out four long-term priorities and added an important qualification: Appeon is customer-driven, so the order can change when customer priorities change. This is conviction without pretending the backlog arrived on stone tablets.

The customer survey reviewed at Elevate 2024 shows the practical forces beneath that framework. Updating operating systems and databases was the most common reason respondents gave for upgrading. Developer productivity and end-user experience followed. Security mattered, but so did bug fixes and deployment improvements. Mature software does not move for one grand reason. It moves because enough ordinary pressures accumulate.

That cadence continued in 2026. Appeon released PowerBuilder 2025 R2 with more IDE refinement, application-security work, and broader environment compatibility. By August, Mazda was on the agenda for October roadmap sessions in Florence and London, where the announced topics included the R2 features and coming AI developer capabilities. The labels change with the cycle; the operating loop does not: release, explain, listen, adjust.

The quiet economics of respect

There is a useful management idea inside Mazda's long tenure: respect can be an economic strategy. Respect the code enough to understand why it survived. Respect the developer enough not to make expertise feel obsolete by decree. Respect the user enough to preserve the workflows that are genuinely fast. Then be unsentimental about the parts that block security, integration, deployment, or support.

The approach also turns an installed base into a form of research infrastructure. Each upgrade question reveals where the platform around an application has shifted. Each migration exposes another dependency. Each user-group complaint is a small report from production. For a specialized developer-tool company, those reports can be more valuable than a broad trend forecast because they arrive attached to working systems and real budgets.

That balance is harder than either extreme. Preservation can become avoidance. Reinvention can become waste. The operator's job is to locate the boundary repeatedly, because the answer changes with every browser, processor, authentication standard, database, and customer constraint. Mazda's four priorities are less a destination than a method for redrawing that line.

His career is public mostly through product roadmaps, patents, and conference rooms, not personal branding. The pattern is workmanlike: return to the same community, explain what changed, invite questions, ship the next version. In a field addicted to clean breaks, Appeon's story is about managed continuity. The old application crosses another technology cycle. The developer keeps hard-won context. The bridge gets rebuilt while traffic is still moving.

That may be the least dramatic version of transformation. It is also the version most companies can actually use.