PHPRunner: an Airtable alternative for custom business applications

In Airtable, a collaborator is someone given access to a workspace, base or interface. On self-serve Team plans, owners, creators, editors and commenters are billable. On self-serve Business plans, owners, creators and editors are billable. Read-only access, shared views and standalone public forms are not charged in the same way, but they do not replace an authenticated application in which users need to work with their own records.

PHPRunner is licensed to the developer who builds the application. Employees, customers and suppliers who log in to the finished web application do not each need a PHPRunner developer license.

That difference produces clear savings as usage grows. Ten Airtable Team collaborators cost $2,400 each year with annual billing, or $4,800 over two years at the current price. PHPRunner Professional costs $599 for one developer in the first year, and the current maintenance renewal for the following year is $249. That is about $850 over two years, nearly $4,000 less than Airtable in this software-licensing example. Enterprise Edition costs $999 initially and $399 to renew maintenance for the following year, totaling about $1,400 over two years and saving about $3,400. Each PHPRunner renewal includes another year of upgrades and email support. Hosting, database administration and application maintenance are separate costs, but adding another application user does not add another PHPRunner license.

Choose PHPRunner for: employee applications, customer portals, supplier portals and operational systems in which many authenticated users must add or update information.

Airtable is designed around bases, tables, views and interfaces. That is useful when a team understands the workspace and needs a flexible way to collaborate. A business application has a different goal: each person should see only the screens, records and actions required for a specific job.

With PHPRunner, an equipment checkout system can give employees a reservation form, supervisors an approval queue and administrators inventory and audit pages. A customer portal can show each customer only their own orders, invoices or support requests. An inventory application can give warehouse employees a simple receiving screen without exposing the rest of the database.

PHPRunner provides group permissions for tables, pages and actions, plus record-level security for cases where users may work only with their own records. Dynamic permissions can be managed from an administration area in the finished application. Enterprise Edition adds Active Directory, Azure AD, Okta, OpenID and SAML authentication options.

Choose PHPRunner when: users should feel that they are using your application, not editing a shared data workspace.

An Airtable solution continues to run on Airtable's cloud platform. PHPRunner generates a web application that can be deployed to a company server, a private cloud environment or a hosting provider selected by the customer.

The application can work directly with MySQL, MariaDB, SQL Server, PostgreSQL, Oracle, Microsoft Access and other supported databases. If the business already has customer, inventory or order data in one of those systems, PHPRunner can build the application around the existing database instead of creating another operational copy. Enterprise Edition can also use multiple database connections in one project.

This is particularly important when confidential data must remain inside a corporate network, when the database is shared with other company systems, or when the organization requires its own deployment, monitoring and backup procedures.

Choose PHPRunner when: the company must decide where the application runs and where its operational data is stored.

Formulas and automations are valuable, but an operational system often needs rules that run at precise points in a workflow. PHPRunner events can validate a change before it is saved, update related records as one process, call another service, send a notification or prevent an action that would leave the data inconsistent.

An equipment checkout application can verify availability again when a reservation is saved. An inventory system can reject a transfer that would make stock negative. A customer application can calculate status from orders, payments and account rules stored in different tables.

Developers can combine visual page design with SQL, PHP, JavaScript, REST APIs and custom files. The generated application files are available in the output directory and can be deployed on the customer's server. Persistent changes should be kept in the PHPRunner project, events, templates or Custom Files so they remain intact when the application is rebuilt.

Choose PHPRunner when: the system must enforce the company's process rather than asking users to remember it.

You do not have to replace Airtable on the first day. PHPRunner can connect to an Airtable base through Airtable's Web API using a Personal Access Token. A REST View can retrieve Airtable records and provide List, View, Add, Edit and Delete pages in the PHPRunner application.

This gives you a direct transition path. Build a focused interface and security model in PHPRunner while Airtable continues to store the records. Later, when data location, scale or subscription cost justifies replacing Airtable completely, export the tables and move them to a relational database.

The direct connection still depends on Airtable. Its access permissions, API rate limit, monthly API allowances and subscription remain relevant. This approach improves the application interface first; it does not yet provide the deployment and data-control advantages of moving the database.

Choose this approach when: you want to prove the new application workflow before committing to a full data migration.

See the PHPRunner tutorial for connecting directly to Airtable's REST API.

Airtable is difficult to beat for a small team that wants to organize information quickly, collaborate in a flexible spreadsheet-like workspace and leave hosting and platform maintenance to a vendor. Read-only sharing and public forms can also cover simple workflows without adding paid seats.

PHPRunner becomes the stronger choice when the system needs many authenticated users, a dedicated interface, existing relational data, custom rules or control over deployment. Those benefits come with responsibility for building, hosting, securing and maintaining the application.

A full migration is not a one-click conversion. Airtable exports data one table at a time, while the application behavior must be mapped deliberately. Start with one representative workflow and verify record counts, relationships, attachments and permissions before the final cutover.

Can PHPRunner connect directly to an Airtable base?

Yes. PHPRunner can use Airtable's Web API as a REST data source. The connection uses an Airtable Personal Access Token with access to the required base and record scopes. PHPRunner can retrieve records and, when configured with the appropriate methods and permissions, add, update and delete them.

Is PHPRunner less expensive than Airtable?

Yes, when several employees, customers or suppliers need authenticated write access. At current prices, ten Airtable Team collaborators cost $4,800 over two years with annual billing. One PHPRunner Professional license plus the following year's maintenance renewal is about $850; Enterprise Edition plus its renewal is about $1,400. PHPRunner is licensed per developer rather than per application user, so adding users does not add PHPRunner license fees. Hosting, database administration and application maintenance remain separate.

Do I have to stop using Airtable immediately?

No. A PHPRunner application can use Airtable through its Web API while you build and test the new interface. You can keep that architecture or move the data later when you need full control over hosting, data location or database design.

Do users of the finished application need PHPRunner licenses?

No. The PHPRunner license applies to the developer using PHPRunner to build the application. The employees, customers or suppliers who use the deployed web application do not each need a PHPRunner developer license.

Which PHPRunner edition should I evaluate?

Professional Edition is suitable for many single-database applications. Enterprise Edition adds multiple database and REST API connections, data encryption, an online report and chart builder, and enterprise authentication options. Test the workflow you actually need during the free trial.

Do not rebuild the easiest table. Choose the workflow that exposes the reason you are considering an alternative: too many paid users, an awkward customer interface, a rule that is difficult to enforce, data that must stay on your server or records already stored in another database.

Build that workflow in the PHPRunner trial, create two user roles and deploy it to a test server. The result will show the difference between extending a shared workspace and owning a dedicated business application.

Try PHPRunner free   Compare PHPRunner editions