What Does PowerBuilder Cost in 2026?
Sooner or later someone on the finance side asks the blunt question: what does this PowerBuilder thing actually cost us to keep? Here are the real 2026 numbers — the licence tiers, what production deployment costs, and how the total stacks up against the rewrite people keep proposing.
Aug 2026
Sooner or later someone on the finance side asks the blunt question: what does this PowerBuilder thing actually cost us to keep? The honest 2026 answer is smaller than most people expect — a working application is licensed per developer seat, not per user, and classic deployment is royalty-free. Here are the real numbers, and the one comparison that actually matters.
What a developer seat costs
PowerBuilder is licensed per developer, as an annual subscription that bundles product updates and standard support. Three tiers matter:
- CloudPro ($1,595/dev/yr) — the full toolkit: client/server, PowerClient, a 5-session PowerServer development licence, .NET DataStore and the UI-modernization features. This is what most teams actively developing an app run on.
- Professional ($895/dev/yr) — client/server and Web API development without the PowerServer deployment toolkit.
- InfoMaker ($295/dev/yr) — reporting and DataWindow authoring only, for report writers rather than application developers.
A 10% volume discount applies automatically at 10+ subscriptions of the same product. So a typical shop with, say, three developers on CloudPro is looking at roughly $4,785 a year in licences — the cost of a few days of contractor time, for the whole team.
What production deployment costs
This is where the biggest misconception lives. Classic client/server deployment is royalty-free — you ship the compiled executable and the matching runtime to as many users as you like at no per-user cost. You only pay a deployment fee if you use PowerServer to deliver the app as an installable cloud app, and that is licensed by concurrent user sessions:
| PowerServer sessions | Annual list price | ≈ per session |
|---|---|---|
| 150 | $3,500 | ~$23 |
| 300 | $5,500 | ~$18 |
| 600 | $8,500 | ~$14 |
| 1,200 | $10,500 | ~$9 |
| Unlimited | $25,000 | — |
Perpetual PowerServer licences exist but are quote-based. The practical point: if you are not deploying through PowerServer, your only licence cost is the developer seats above — production is free.
Subscription vs perpetual
Appeon moved to an annual-subscription model, which is the source of a lot of the “they made it a subscription” frustration. What Appeon actually documents: the developer bundles are non-perpetual, and if you let a subscription lapse you re-purchase at the then-current price — so renewing before it expires is what keeps the cost predictable, rather than any promise that list prices never change. Perpetual licensing is offered for PowerServer (the deployment runtime) on request; the PowerBuilder IDE bundles are subscription-only. For most teams the subscription is a small, fixed cost; the money question is a different one entirely.
The number that actually matters: keep vs rewrite
The licence bill is rounding error next to the decision it is usually attached to — should we keep this or rewrite it? Put the two against each other honestly:
Keeping a PowerBuilder application supported costs low thousands to a few tens of thousands a year. A rewrite is a $300K–$2.5M, 12–24 month undertaking by commonly-cited estimates — and large rewrites frequently overrun their budget and timeline. That does not mean never modernize; it means the licence cost is almost never the reason to. We lay out when a rewrite is actually the right call in modernize or rewrite — a decision framework.
Bottom line. Budget roughly $1,595 per developer per year for CloudPro, nothing for classic client/server deployment, and PowerServer sessions only if you deploy that way. It is a small, predictable line item — and a fraction of the rewrite it is often mistaken as a reason for.
Appeon list prices as published in August 2026; prices change — confirm current figures before you budget. Rewrite costs are industry estimates, not a quote.
Frequently asked
How much does PowerBuilder cost per year?
As of 2026, Appeon's list prices are: PowerBuilder CloudPro $1,595 per developer per year, PowerBuilder Professional $895, and InfoMaker $295. These are annual subscriptions that include product updates and standard support during the term. There is no charge for classic client/server deployment — you pay per developer seat, not per end user.
Do I pay a runtime fee to deploy a PowerBuilder application?
Not for classic client/server deployment — that is royalty-free; you only license the developer seats. A runtime cost applies only if you use PowerServer to deploy installable cloud apps, which is licensed by concurrent user sessions: roughly $3,500/year for 150 sessions up to $25,000 for unlimited. Perpetual PowerServer licences are available from Appeon on request.
Is PowerBuilder subscription or perpetual now?
The PowerBuilder developer bundles (CloudPro, Professional, InfoMaker) are annual subscriptions — Appeon describes them as non-perpetual. If you let a subscription lapse, Appeon has you re-purchase at the then-current price, so renewing on time is what keeps the cost predictable. Perpetual licensing is offered for PowerServer (the deployment runtime) on request; the PowerBuilder IDE bundles themselves are subscription-only.
Is it cheaper to rewrite in .NET than to keep paying for PowerBuilder?
Rarely, in the near term. Licences plus support are low single-digit thousands per developer per year; commonly-cited estimates put a PowerBuilder-to-.NET rewrite in the low hundreds of thousands to a couple of million dollars over roughly 12–24 months, and large rewrites frequently overrun their budget and timeline. A rewrite pays off mainly when your annual maintenance genuinely exceeds the amortized cost of the new system — not before.
PowerBuilder notes, now and then
New writing on upgrades, databases and modernization — a few times a month, nothing more.