PowerBuilder has powered mission-critical business applications for more than three decades. Many of those applications still run core operations today, and the organizations that depend on them face a familiar problem. The talent pool for PowerBuilder is shrinking, the platform is increasingly difficult to integrate with modern systems, and a full manual rewrite carries significant cost and risk.
Today we are introducing VELO for PowerBuilder, a new capability in the GAPVelocity AI platform designed to solve this problem directly.
Legacy modernization has historically forced a choice between two imperfect options.
The first is a manual rewrite, where engineers rebuild the application from the ground up in a modern framework. This approach can produce a clean result, but it is slow, expensive, and prone to losing business logic that was never fully documented. Years of accumulated decisions live inside these applications, and much of that knowledge exists only in the code itself. When a rewrite misses it, the new application behaves differently from the one it replaced, and the cost of finding and fixing those gaps grows quickly.
The second option is automated code migration with GenAI, where tools translate old code into new code. This is faster, but it often cannot handle the complex dependencies that come with most business applications. The result is code that compiles but does not meet the expectations of the teams who have to maintain it. Engineers inherit an application that looks unfamiliar and carries forward the patterns of a platform they were trying to leave behind.
| Approach | Pros | Cons |
|---|---|---|
| Manual rewrite | Clean, purpose-built result | Slow and expensive |
| Full control over architecture | Loses undocumented business logic | |
| Behavior gaps are costly to find and fix | ||
| GenAI code migration | Fast | Cannot handle complex dependencies |
| Low upfront effort | Compiles but falls short of team standards | |
| Carries forward old platform patterns |
VELO takes a different path.
VELO applies agentic AI to the modernization process. Rather than performing a single mechanical translation, VELO uses AI agents that reason about the application, separate business logic from presentation, and generate modern code that reflects current framework conventions. The agents work through the application in a structured and bounded way, which keeps the output verifiable rather than unpredictable.
This distinction matters. An agent that operates without boundaries can produce results that are difficult to review and impossible to trust at scale. VELO constrains the process so that each step can be checked and understood. Modernization is not only about producing new code. It is about producing new code that an engineering team can trust, review, and own. An application that no one is confident maintaining is not truly modernized, regardless of the framework it now runs on.
The outcome is a fully modernized application. For PowerBuilder, that means moving to a modern framework such as Blazor with a clean architecture, rather than a direct copy of the original structure carried forward into a new language. The business logic is preserved and made explicit, the presentation layer is rebuilt to modern standards, and the result is an application that fits naturally into a current development environment.
VELO runs its agentic models on Microsoft Foundry. This gives the platform a foundation built for enterprise scale, security, and governance, and it aligns VELO with the Microsoft ecosystem that many of our customers and partners already operate within. For organizations already invested in Microsoft technologies, this alignment reduces friction and keeps modernization efforts within a familiar and well governed environment.
It also means that the AI at the core of VELO benefits from the reliability and oversight that enterprise workloads require. Modernization often touches an organization's most sensitive systems, and running on Foundry allows that work to happen with the controls and accountability those systems demand.
The advantage of VELO becomes clear when compared to other traditional approaches. A manual rewrite delivers quality at the expense of time and cost. Generic Generative AI migration delivers speed at the expense of quality. VELO is designed to deliver both. The agentic approach produces modern, maintainable code while dramatically compressing the timeline and cost of the project.
The results reflect this. Applications modernized with VELO reach a fully modernized state up to twenty times faster than a manual rewrite and at sixty percent less cost. These outcomes come from the structure of the approach itself, not from cutting corners on quality. The speed is a product of automation applied intelligently, and the cost savings follow from doing the work correctly the first time.
Check out some of our resources for PowerBuilder:
VELO for PowerBuilder is available now as part of the GAPVelocity AI platform. If your organization is weighing the future of a PowerBuilder application, or if you are evaluating modernization approaches more broadly, we would welcome a conversation about what VELO can do for your codebase.