PowerBuilder 2019 R3 released with automated application deployment and long-term support!

Learn More
Need help with your products' trial? Schedule a call with an Appeon tech expert to discuss your trial needs and features you want to explore. Schedule Now

PowerServer automatically deploys PowerBuilder desktop apps to the Cloud and .NET framework. Existing PowerBuilder skills and source code can be leveraged. There is no faster, scalable approach to Cloud-enable mission-critical systems built with PowerBuilder.

Why Choose PowerServer?

Lowest Cost and Risk

PowerServer automatically converts most existing PowerBuilder source code, including complex DataWindows and frameworks. Subsequent maintenance is performed in the PowerBuilder IDE, keeping the existing development team highly productive and minimizing disruptions. A typical project can be completed in just months or even weeks rather than years!

Lowest Cost and Risk
Powerful Remote Access

Powerful Remote Access

Allow remote users to work securely over a standard Internet connection. End Users access your PowerBuilder apps via leading Web browsers for Windows OS or as Installable Web Apps (IWAs). IWAs stay resident on the desktop and run without a Web browser, minimizing configuration issues. Application deployment is centralized and updates are delivered automatically.

Desktop User Experience

Experience powerful UI and features typical of sophisticated desktop apps. Now you no longer need to choose between accessibility and functionality. In fact, you can even seamlessly integrate with other Windows apps and OLEs/OCXs/DLLs, access Windows APIs, and utilize peripheral devices. The rich UI is not only more intuitive, but also eliminates the need for end user retraining.

Desktop User Experience
Native .NET Technologies

Native .NET Technologies

The middle tier of PowerServer is powered by Web standards and the .NET framework. As such, your PowerBuilder application deploys to the Microsoft IIS server and is compatible with leading cloud providers. Your PowerBuilder projects can interop with other .NET or Java applications through REST APIs.

PowerServer Conversion Capability

What Developers Say

“PowerServer enabled us to offer our customers a web-based workforce optimization product deployed to the Microsoft Azure Cloud.”


Tony Orsini, Senior Director

PowerServer Web App Architecture

PowerServer deploys your PowerBuilder apps to a standard n-tier Web architecture and a .NET server. The presentation tier and data tier are physically separated. The Web and application servers can be separated onto multiple servers and clustered. You can take advantage of numerous security mechanisms, including HTTPS protocol, firewall and Web server security. No matter how small or large your organization is, you will realize the benefits of greater availability, scalability, security, and reliability.

PowerServer Web App Architecture


Sorry, PowerServer does not support Macintosh.

You may use Chrome, FireFox, and Edge on Windows OS.

Sorry, PowerServer does not support Web browsers on iOS or Android. PowerServer strives to faithfully replicate Windows desktop app functionality, and as such must be deployed to the Windows OS.

However, if you wish to deploy DataWindow reports and/or simple data entry functionality to mobile devices, you can try run your app on iOS and Android using the Appeon Workspace. Appeon Workspace is for internal deployment only, and is not permitted on the Apple or Google app stores.

Yes and no, depending on if you access your app via a Web browser or as an Installable Web App (IWA). A Web browser plug-in is required if accessing your app via Web browsers. Installable Web Apps do not utilize a Web browser and as such do not require any Web browser plugins.

The deployment of your PowerServer app should be more straightforward and reliable as you eliminate a key environment dependency – proper configuration of the Web browser. Also IWAs are easier to launch since they are resident on the user’s machine and have shortcuts. In terms of performance, response times are similar but IWAs will consume less client-side memory.

While PowerServer executes data access logic on the middle tier using C# and ADO.NET, it is not a code conversion solution. If you want to migrate your code to C#, we recommend you try the PowerScript Migrator.

The development and maintenance is performed in the PowerBuilder IDE, leveraging existing PowerBuilder skills.

PowerServer is truly utilizing an n-tier architecture, Web standards, the .NET framework, stateless server objects and database connection pooling, and so on. As such, you can expect for higher scalability, greater interoperability, and free yourself from the typical limitations and headaches of terminal service technologies.

Yes, and much faster than rewriting your existing apps from the ground up. PowerServer has been certified with Amazon AWS, Microsoft Azure, VMWare, and RackSpace.

Yes, the Web servers hosting your PowerServer apps can be clustered and load-balanced if you use Microsoft IIS or Apache Web server; however, this feature will require you purchase the Enterprise Edition of PowerServer.

Please refer to the appropriate PowerServer Installation Guide for detailed software environment requirements of the desktop, middleware, and database.

It is very difficult to generalize this as a number of variables can affect the Web deployment effort. Generally, the web deployment project consists of remediating unsupported PowerBuilder features, optimizing data access logic for Internet connectivity, and thoroughly testing your project. Many customers have completed their projects in several months and some even in as little as several weeks.

Most PowerBuilder features are supported, including complex DataWindows and frameworks (such as PFC). Please refer to the Support Features Guide for a complete list of all supported and unsupported PowerBuilder features.