Is PowerBuilder Dead in 2026? An Honest Answer

No, PowerBuilder is not dead. It is actively developed and supported by Appeon, an independent company that has owned the product since 2016. The current release, PowerBuilder 2025, shipped on 7 May 2025 — on a regular cadence after 2021 and 2022. There is a public roadmap, a formal support-lifecycle policy, and an active developer community. Whatever you have heard, the platform is not abandoned.

That is the short answer, and for most readers it is the one that matters. But the question usually hides a bigger one — should I be worried about the next five years? — and that deserves an honest answer, including the one genuine risk that is real.

Where the “PowerBuilder is dead” myth comes from

The perception is a decade out of date. In the late Sybase years, and then under SAP's ownership, PowerBuilder stagnated. Releases slowed, the roadmap went quiet, and a lot of the industry quietly wrote it off. That was a reasonable read — in 2014.

Then, on 5 July 2016, SAP handed development, sales and support to Appeon, an independent company whose entire business is PowerBuilder. The product has been on a steady release cadence ever since. But reputations lag reality by years, and two other things kept the myth alive:

• The community aged rather than grew.The developers who learned PowerBuilder in its 1990s heyday are senior now, and few juniors pick it up. That means less of the online noise — blog posts, Stack Overflow churn, conference buzz — that we unconsciously read as “alive.” Quiet is not the same as dead, but it looks similar from the outside.
• It is a specialist tool, not a mass-market one. PowerBuilder was built for data-intensive business applications, and that is exactly where it still excels. It was never going to trend on social media. Niche and dead are different things.

The evidence that it is alive

Set perception aside and look at what is actually true in 2026:

1. A regular release cadence. PowerBuilder 2019, 2021, 2022 (with R2 and R3 revisions) and 2025 have all shipped under Appeon, the latest on 7 May 2025. This is not a product in maintenance-only mode.
2. A published support lifecycle. Appeon commits, in writing, to defined support windows and advance end-of-life notice. Dead products do not publish forward-looking support policies. (The details are in our version and support-lifecycle reference.)
3. Active modernization investment. Recent releases added cloud and web deployment paths (PowerServer, PowerClient), REST API tooling and UI modernization features — investment aimed squarely at keeping existing applications viable, not at winding the product down.
4. A live support community. The Appeon Community forums see daily questions and answers about current releases, migrations and real production issues. There are people to ask.

The one risk that is actually real

Here is the honest caveat. The threat to a business running PowerBuilder is not that Appeon stops developing it. It is the talent pool. Every year, the number of engineers who can confidently maintain a large PowerBuilder application gets smaller, because retirements outpace new entrants. That is a genuine, slow-moving risk — and it is a very different problem from the one the myth describes.

The distinction matters because the two risks call for opposite responses. “The vendor is abandoning us” would push you toward a panic migration. “Our ability to hire for this is shrinking” pushes you toward something calmer and cheaper: securing senior coverage, documenting the system, and planning succession on your own timeline. One is a fire drill; the other is good asset management.

What to actually do

If your PowerBuilder application is doing its job, the rational plan has three parts, none of which involve panic:

1. Get onto a supported version. Being on a current or recent Appeon release removes the only vendor-side risk that exists. If you are on Sybase-era PowerBuilder, that is the one upgrade worth scheduling.
2. Secure the knowledge, not just the code.Documented run books and a named senior fallback matter more than the platform's roadmap. The application's value is in its business logic; protect access to the people who understand it.
3. Decide modernization on merit, later. If and when you modernize or rewrite, do it because of a concrete driver — hiring, integration, deployment — not because of a myth. Our modernize-versus-rewrite framework walks through that decision.

The bottom line. PowerBuilder is not dead — it is actively developed by Appeon, with a current release and a published support policy. It is niche, and the developer pool is thinning, which is a real risk to manage. But that is a staffing and continuity problem with calm, affordable answers, not a reason to abandon a system that is quietly running your business.