PowerBuilder 2025 R3: What We Know So Far
Appeon has not dated PowerBuilder 2025 R3, but it has published a lot about it: a roadmap, a notice of what gets removed, and in October 2026 conference slides outlining how AI coding agents will connect to the IDE. Here is what is public so far, with the sources, and what it means for your upgrade plan.
Published 26 October 20265 min read
When it ships
Appeon has not published a date, and the slides from its October talk contain none. Its roadmap promises releases in “agile 10–12 month release cycles” and calls the feature list a “minimum plan that is subject to change without notice”. That is Appeon's stated cycle: 2025 R2, released on 3 June 2026, came about 13 months after 2025.
The only estimate we found comes from the PowerBuilder Japan Portal, run by Nippon Computer Systems. On 29 September 2026 it put the English 2025 R3 around mid-2027, about a year after R2, and wrote that R3 is planned as the last revision of the 2025 series, which would make it a long-term support version with at least five years of support. The portal calls this its own assumption, and Appeon has not confirmed it.
AI: agents connected to the IDE
The roadmap lists for 2025 R3: “Integrate Claude AI capabilities into the IDE, with an initial focus on code completion, DataWindow development, and an AI Assistant.” On 19 October 2026, at the German PowerBuilder User Group in Berlin, Appeon CEO Armeen Mazda gave a talk that the PBUGG agenda describes as covering the AI features of the upcoming 2025 R3. His slides name no version or date.
What the slides describe:
- Agents through ACP. A PowerBuilder AI Assistant connects the IDE to coding agents through the Agent Client Protocol. “Initial support is planned for Claude Code and Kilo Code.”
- A PowerBuilder MCP server that lets agents work with projects, modify code, compile and run applications, and use supported debugging operations. PowerBuilder-specific context and agent skills are listed as “evolving capabilities”.
- Two ways to work: a full agentic workflow, where the developer hands over a task and reviews, and a developer-guided one in the code editor: code generation, completion, optimization and security checks, and help with bugs.
- Separate from the IDE: the AI capability is a separate installation with its own updates, so it can evolve without waiting for major PowerBuilder releases.
The slides do not say which PowerBuilder versions the AI Assistant will support or how it will be licensed; the agents themselves come from their own vendors.
You don't have to wait to use an agent, though: on 2025 R2 in the Solution format an agent can already edit the source files, while building and running stay in the IDE. Our Claude Code guide covers that workflow.
The rest of the R3 roadmap
| Area | Planned for 2025 R3 |
|---|---|
| Compatibility | Runtime support for ARM processors with Windows, including Apple hardware through Windows virtual machines; PDF output aligned with ISO 14289 (PDF/UA); Terminal Server–aware builds from the IDE and PBAutoBuild; current Windows and database versions. |
| Security | ASLR, DEP/NX, SafeSEH (x86), CFG and DEH extended from executables to the runtime DLLs; key-based SSH for self-hosted Git servers; Windows authentication for HTTPClient. |
| IDE | Rename across the whole object, tabs that open in separate windows, and refinements to the Solution format for DevOps. |
| Application features | Per-column padding and vertical alignment; more string functions; banker's rounding in Round(); reset for JsonGenerator and JsonParser; right-to-left RibbonBar and menus; built-in SVG images and SVG in NativePDF; “%20” as an option in UrlEncode. |
From Appeon's roadmap page, October 2026. Appeon may still change the list.
What R3 removes: docking windows
Appeon's notice says docking windows are completely removed in 2025 R3: “Customers who use docking windows in their application please migrate to normal floating windows.” Appeon's alternative is to stay on 2025, 2025 R2 or 2022 R3 LTS; of those, only 2022 R3 has a published mainstream maintenance date beyond mid-2027 (no sooner than 8 January 2029). Docking windows are the dockable MDI frames, window types MDIDock and MDIDockHelp, which Appeon already marked obsolete in 2019 R2. If your application uses them, plan that rework before the upgrade.
What to do now
- On 2025: move to 2025 R2. Maintenance builds now ship for R2, and R2 runs on .NET 10, while the .NET 8 that some 2025 features need loses Microsoft support on 10 November 2026 (our .NET 8 guide). Appeon's EOL policy says a revision “does not extend the EOMM date” of its major version; for 2025 that is 3 June 2027.
- On 2022 R3: it is the current long-term support version, with mainstream maintenance until at least 8 January 2029, so R3 is not urgent.
- Using docking windows: list them now, since they will need rework before any move to R3.
- Curious about AI: start on 2025 R2 in the Solution format; the R3 integration should make the same work more convenient.
We update this page as Appeon publishes more, from Elevate 2026 on 30 November onwards.
Frequently asked
When will PowerBuilder 2025 R3 be released?
Appeon has not published a date. Its roadmap states a 10–12 month release cycle, and 2025 R2 shipped on 3 June 2026. The PowerBuilder Japan Portal estimates the English 2025 R3 around mid-2027; that is its own assumption, not an Appeon announcement.
Will PowerBuilder 2025 R3 work with Claude Code?
That is the plan. Appeon's roadmap lists Claude AI integration in the IDE for 2025 R3, and in October 2026 Appeon presented a planned PowerBuilder AI Assistant that connects the IDE to AI coding agents through the Agent Client Protocol, with initial support planned for Claude Code and Kilo Code, plus a PowerBuilder MCP server for the agents to use.
What is removed in PowerBuilder 2025 R3?
Docking windows. Appeon's notice says they are completely removed in 2025 R3 and asks customers who use them to migrate to normal floating windows before upgrading, or to stay on 2025, 2025 R2 or 2022 R3 LTS.
Should I wait for 2025 R3 or upgrade to 2025 R2 now?
There is no published R3 date to wait for. 2025 R2 is the current release and runs on .NET 10, while .NET 8, which some 2025 features need, loses Microsoft support on 10 November 2026. AI agents can already edit 2025 R2 source in the Solution format, with building and running kept in the IDE.
PowerBuilder notes, now and then
New writing on upgrades, databases and modernization — a few times a month, nothing more.