Most business software is the same shape: tables of records, forms to add and edit them, lists that search and filter, dashboards that summarise, and rules about who may see what. PPPHP RAD Studio is a rapid application development (RAD) studio that builds all of that from your database — and then hands you plain PHP you own.
This guide walks the whole journey, zero to one hundred: what PPPHP is, how a project starts, how pages and dashboards are designed, how security works, and how the finished web application is built and deployed. Whether you are a full-stack developer tired of writing the hundredth CRUD screen, an agency shipping internal tools, or a founder who needs an admin panel by Friday, this is the map.
Key takeaways
- PPPHP is a web-based low-code studio that generates a complete, responsive PHP web application from any SQL database.
- It works with eight SQL engines — MySQL, MariaDB, TiDB, PostgreSQL, CockroachDB, SQLite, SQL Server and Oracle — or a built-in zero-setup database.
- You design visually (a drag-and-drop designer with 130+ components), extend with PHP and JavaScript events when a rule needs code, and own the output.
- The generated app runs on any PHP 8 host — shared hosting, cPanel, a VPS — with no runtime fees and no lock-in.
What PPPHP RAD Studio is (and is not)
PPPHP sits between two worlds. No-code builders are fast but keep your app on their platform and charge per seat; hand-written frameworks give total control but every list, form and permission is yours to code and maintain. PPPHP takes the low-code middle path: the studio generates the predictable 90% of a database application, and you write code only for the 10% that is genuinely unique to your business.
Three things make it different from a typical PHP CRUD generator:
- It runs in the browser. There is nothing to install on your laptop; you design from macOS, Windows or Linux.
- The output is ordinary PHP. Readable code using prepared statements, which any PHP developer can review and extend — not an obfuscated runtime.
- The modern stack is already inside. A REST API, real-time updates, passkeys, cloud storage, translations, payments and an AI client ship with every app rather than as paid add-ons.
Step 1 — Start a project and connect a database
A project is one application. When you create it, you choose where its data lives:
- The built-in Virtual Database. A real SQL database (SQLite) created instantly inside the project — no server, no host, no credentials. It is the recommended default for most apps, and the built app carries its own copy.
- An existing database. Connect MySQL, MariaDB, TiDB, PostgreSQL, CockroachDB, SQL Server, Oracle or SQLite. Tables, primary keys and relations are detected, so an existing schema becomes an application in minutes. This is the fastest way to turn a legacy MySQL database into a modern web application.
The two are not a one-way door. Build on the Virtual Database and deploy to MySQL later — PPPHP's built-in database follows MySQL's rules (case- and accent-insensitive text matching, exact decimals, big integers kept exact, MySQL's grouping rules), so the app behaves the same after the move.
Step 2 — Model your data: tables and relationships
The Tables workspace is a visual schema designer. Create tables and columns with real SQL types, add indexes and unique rules, and draw relationships by linking a master key to a detail column. You can import a CSV file into a table in a few clicks, and owners have a SQL editor for anything you would rather type.
Relationships matter because they drive the generated user experience: a foreign key becomes a lookup that shows a customer's name instead of an ID, and a master–detail link puts a customer's orders right on the customer page — with "add order" prefilled. Dropdowns can even cascade: choose a country, and the state list shows only that country's states.
Step 3 — Get a complete app instantly: lists, forms and views
Pick the page types each table needs — list, add, edit, view, print, export, import — and PPPHP generates them. Out of the box, every list is sortable, searchable, filterable and paged on the server, so it stays fast with hundreds of thousands of rows. Users get inline editing, a spreadsheet mode, Excel-style filter dropdowns, bulk actions and exports to CSV, Excel, Word, JSON and XML.
Forms get the right control for each field automatically, plus validation on both the browser and the server. Dates, choices, lookups, file and image uploads, and specialised controls such as a Bikram Sambat (Nepali) date picker are all a dropdown away — see the add & edit pages guide and the list page guide.
Step 4 — Design visually: the drag-and-drop designer
When the defaults are not enough, open the Designer. It is a drag-and-drop page builder with 130+ components: fields and field groups, detail grids, cards, KPI tiles, charts, gauges, funnels, heatmaps, pivot tables, kanban boards, calendars, menus, hero sections and layout blocks. Every component has properties you set in an inspector panel — labels, hints, visibility per device, styling per part.
Dashboards bind straight to your data. Drop a chart, choose a table or write a SQL query, and it is live. Add a page filter and every widget re-queries when the value changes; a date-range filter drives period reporting. The dashboard guide shows the patterns.
Look and feel come from design tokens. Sixteen ready-made themes, each with light and dark mode, restyle buttons, cards, tables and charts together; duplicate one to apply your brand colours, and choose a navigation layout — classic, horizontal, sidebar, rail, boxed or hero. Per-page custom CSS and JavaScript are there for the last pixel.
Step 5 — Add business logic with events (when you need code)
Settings cover most rules, but some logic is genuinely yours: compute a total, call an external API, send a notification when an order ships. PPPHP's events are lifecycle hooks — before a record is saved, after it is added, when a page loads, on login, on a schedule — where you drop PHP (server) or JavaScript (browser) code. The editor offers IntelliSense, checks your syntax as you type, and has a pre-deploy "check all" so a typo never reaches production.
Scheduled tasks run nightly reports or clean-ups through a standard cron runner, and SQL variables such as :user.id let any query depend on the signed-in user, safely quoted. The events reference lists every hook.
Step 6 — Secure it: authentication, roles and row-level security
Turn on login and PPPHP adds sign-in, registration, password reset, login lockout and a password policy. Security is layered so you switch on only what you need:
Underneath, every generated query uses prepared statements, every printed value is escaped against XSS, forms carry CSRF tokens, and the app sends modern security headers. The security guide covers each layer.
Step 7 — Make it mobile: responsive by default, an app when you want
Every generated page is responsive — it adapts from a wide desktop to a phone. Switch on the Mobile layer and phones get a native-style experience: a large-title app bar, card-style rows, a floating add button and a bottom tab bar, while the desktop layout stays untouched. The app also becomes an installable progressive web app (PWA) that works offline and can receive push notifications. Our guide to responsive, mobile-first apps goes deep on this.
Step 8 — Connect it to everything else
Modern apps never live alone. Each PPPHP app can expose a secure REST API (with bearer, HMAC or OAuth2 authentication, scopes, rate limits and OpenAPI documentation), send webhooks when records change, receive webhooks from other services, push real-time updates to open browsers, send e-mail and SMS through many providers, take online payments, store files on S3, Cloudflare R2, Google Drive or OneDrive, and call an AI model of your choice with keys kept on the server. The modern web development stack guide explains each.
Step 9 — Build and deploy
- Pick a preset. Development keeps files readable and errors visible; Production compresses JavaScript and CSS, versions assets for cache-busting, and logs errors instead of showing them.
- Build. One click generates the complete application. A version of your project is saved at every build, so you can always go back.
- Deploy. Upload with the built-in FTP, FTPS or SFTP client, or copy the folder yourself. An optional installer lets the app's owner choose the database — MySQL, PostgreSQL, SQL Server or SQLite — on first run, with no credentials baked into the package.
- Check. The health check confirms the server has what the app needs.
The result runs anywhere PHP 8 runs: shared hosting, cPanel, a VPS or your own data centre.
Who uses PPPHP — and for what
Where to go next
Watch the live capability demos, browse the documentation, or ask anything in the community forum. If you are comparing tools, see how PPPHP compares with PHPRunner, Retool, Budibase and others.
Frequently asked questions
Is PPPHP a no-code or a low-code tool?
Low-code. You can build complete applications without writing code, and add PHP or JavaScript in lifecycle events when a rule needs it. The generated application is plain PHP you own.
Which databases does PPPHP support?
MySQL, MariaDB, TiDB, PostgreSQL, CockroachDB, SQLite, SQL Server and Oracle, plus a built-in zero-setup Virtual Database. A generated app can also be installed onto MySQL, PostgreSQL, SQL Server or SQLite.
Do I need to know how to code?
No for the standard application — tables, pages, dashboards, security and deployment are all visual. Developers can extend anything with PHP and JavaScript events.
Where can I host the generated application?
Anywhere PHP 8 runs: shared hosting, cPanel, a VPS or your own server. There are no runtime fees.
Is PPPHP a PHPRunner alternative?
Yes. Like PHPRunner it generates PHP CRUD applications you own; PPPHP runs in the browser and includes a built-in database and a modern feature set such as a REST API, real-time updates, passkeys and cloud storage.
Build your first app today
Point PPPHP RAD Studio at a database — or start on the built-in one — and have a secure, responsive web app running before lunch.