PHPRunner review

PHPRunner is positioned as a low-code builder for production web applications around existing data. There is an important product-identity check: the vendor homepage describes ASPRunner.NET, not PHPRunner. Its architectural details should not be assumed to apply to PHPRunner until the vendor confirms they do.

For ASPRunner.NET, the described workflow is a visual application builder that generates a structured ASP.NET web application. It connects to a database, then assembles pages for viewing, adding, editing, deleting, searching, exporting and printing records. Forms, reports, charts, dashboards, authentication and permissions are included as application components. The resulting app can be previewed with a built-in web server and uploaded to a remote web server through an FTP client. That places the builder in the application-generation layer of a stack; it is not described as a hosted API or a runtime service. The vendor says applications can be deployed on the buyer’s own infrastructure.

The homepage describes visual development rather than an API-first integration workflow. For ASPRunner.NET, developers connect to databases, edit generated SQL in a graphical pane or as text, build joins with drag-and-drop, and set query criteria such as where, order by and group by. The named runtime target is ASP.NET. The page also describes code customization and AI assistance for writing event and application logic.

The integration surfaces named are database connections, generated ASP.NET pages and FTP upload. The homepage does not present a REST API, webhooks, a CLI, plugins or a language-specific SDK workflow. Confirm SDK support in the vendor’s docs if PHPRunner must integrate with other services. The homepage links to video tutorials, screenshots, a live demo, changes history and a forum. It describes support for MySQL, SQL Server, MS Access, Oracle, PostgreSQL, DB2, Informix, SQLite and ODBC-enabled databases. Verify that these details apply to PHPRunner, rather than ASPRunner.NET, before designing around them.

The listed pricing is for one-time developer licenses, not a monthly or annual subscription. Professional costs $599 for one developer license and includes a 21-day free trial. An optional upgrade renewal after year one is listed at $249. Enterprise Edition costs $999 for one developer license, also with a 21-day trial; its optional renewal after year one is $399.

MultiDev Edition is listed at $3,599 for three Enterprise Edition developer licenses and allows multiple developers to work on one project simultaneously. It also includes a 21-day trial. No free plan is listed. Since the license price is not based on requests, seats beyond the stated licenses, or compute, the pricing page does not describe usage overages. Hosting is a separate operational cost to account for when deploying on your own infrastructure. The vendor homepage’s product-name mismatch makes it especially important to confirm these prices and renewal terms apply to PHPRunner before purchase.

The homepage describes ASPRunner.NET as software that builds applications for deployment on your own infrastructure. It offers a built-in web server for preview and an FTP client for uploading pages. That is materially different from a hosted-only app service: you can operate the generated application on infrastructure you control, subject to the vendor confirming this applies to PHPRunner.

The vendor does not publish a license or source-availability statement on the homepage, so confirm whether the builder is closed-source and what rights the license grants over generated code. The homepage describes application-level data export, but that is not the same as exporting source code or migrating application logic. Ask what files and database structures you retain if you stop using the builder. The more application behavior depends on generated code and proprietary components, the more important it is to inspect those outputs before choosing it.

The vendor describes authentication, user groups, flexible permissions, CAPTCHA, password encryption and password-strength validation for ASPRunner.NET. Its Enterprise Edition adds Active Directory, Okta, LDAP, SAML and OpenID support. Confirm which of these are included in the PHPRunner edition you are considering, and how they fit your identity and security requirements.

Deployment is described as running a built application on your own infrastructure, so your team must plan hosting, monitoring, backups, upgrades and incident response. The homepage does not publish rate limits, concurrency limits, an uptime commitment or compliance certifications. Those may matter when the application becomes business-critical; ask the vendor for applicable limits and support terms. Test generated SQL and permissions against your own schema and access model before release. Most importantly, resolve the PHPRunner versus ASPRunner.NET naming discrepancy before treating any feature or deployment detail as a production commitment.