Low-code tools have a reputation: fast for the first screen, frustrating at the first real requirement. Developers worry about three things — can I get to the code, does it integrate, and is it secure enough to put in front of customers. This guide answers all three for PPPHP RAD Studio by walking the modern web development stack layer by layer.
Key takeaways
- Every app can expose a REST API with bearer, HMAC-signed or OAuth2 authentication, plus GraphQL and OpenAPI documentation.
- Real-time updates stream over Server-Sent Events — no WebSocket server or Node.js process to run.
- Security is layered: prepared statements, CSRF tokens, security headers, passkeys, 2FA, row-level security, field encryption and an audit trail.
- Payments, cloud storage, e-mail/SMS and AI are built in; the output is plain PHP 8 you deploy anywhere.
The escape hatch: real code where you need it
PPPHP generates readable PHP — prepared statements, no obfuscation — and gives you defined places to add your own:
The event editor has IntelliSense and live syntax checking, and a pre-deploy scan flags broken code before it ships. Queries can use SQL variables such as :user.id or :session.region, always quoted safely, so per-user logic needs no string concatenation. See the events reference and the SQL variables guide.
API-first: REST, OAuth2, GraphQL and OpenAPI
Expose any table as an API from the REST API settings, choosing per table whether clients may read, create, update or delete. Then issue keys:
- Authentication — bearer tokens, HMAC-signed requests, or an OAuth2 token endpoint.
- Identity — a service key with explicit scopes, or a key that acts as a user and inherits that user's permissions and row-level security.
- Protection — rate limits, CORS rules and HTTPS-only enforcement.
- Safe retries — an
Idempotency-Keyheader on POST means a retried request never creates a duplicate record. - Discovery — generated OpenAPI documentation and a GraphQL endpoint for clients that prefer it.
That makes a PPPHP app a natural backend for a mobile app, a single-page front end or a partner integration — a headless database API with an admin UI attached.
Webhooks in and out
Outgoing webhooks notify other systems when a record is created, updated or deleted — signed with an HMAC signature header and retried on failure, so the receiver can verify the sender and never miss an event. Incoming webhooks land on a public endpoint in every built app; your "On Webhook Receive" event gets the payload, headers and raw body, maps it to your tables, and verifies the sender's signature (returning false rejects the call). Payment providers, form services and warehouse systems all integrate this way.
Real-time without a WebSocket server
Live dashboards, activity feeds and "someone else is viewing this record" presence usually require a WebSocket service. PPPHP streams updates over Server-Sent Events with an automatic polling fallback, so it runs on ordinary PHP hosting. A one-line broadcast from any event pushes data to every open tab — or to a single user — and the page updates without a refresh.
Security that passes a review
Security is where shortcuts hurt most, so PPPHP makes the safe path the default path.
Secure by construction
- SQL injection: every generated query uses prepared statements with bound values; sort columns are checked against real columns.
- XSS: printed values are HTML-escaped; HTML content passes an allow-list sanitizer.
- CSRF: forms and AJAX calls carry a per-session token checked on every write.
- Headers:
X-Frame-Options,X-Content-Type-Options,Referrer-Policy, a Content-Security-Policy for framing and plugins, and HSTS over HTTPS. - Sessions: HttpOnly, SameSite cookies, idle and absolute timeouts, concurrent-login limits and remote sign-out; login lockout and a password policy.
Identity and access
Passkeys (WebAuthn — Face ID, Touch ID, Windows Hello, hardware keys) in pure PHP, two-factor authentication with authenticator apps or e-mailed codes, role-based permissions per table, and row-level security so each user sees only their rows. For a multi-tenant SaaS, one rule — tenant_id = :user.tenant_id — keeps every company in its own data across lists, exports, dashboards and the API.
Data protection and accountability
Field encryption stores sensitive columns with AES-256-GCM, the audit trail records who changed what with before and after values, and record locking stops two people overwriting each other. The security documentation covers configuration.
Payments, files, messaging and AI
| Need | What ships |
|---|---|
| Online payments | Stripe, PayPal, Razorpay, Khalti, eSewa and Fonepay, plus manual bank transfer and a test simulator. Amounts are fixed on the server and verified with the gateway; subscriptions on Stripe, PayPal and Razorpay. |
| File storage | Amazon S3, Cloudflare R2 and MinIO through a pure-PHP S3 client (no SDK or Composer needed), plus Google Drive and OneDrive. Files stay private by default. |
| E-mail & SMS | Any SMTP or e-mail service with failover, and 21 SMS gateways — see the e-mail and SMS guides. |
| Documents | Numbered, gap-free PDF invoices and certificates with letterheads, line items, watermarks and bulk e-mailing — see Document Studio. |
| AI | Claude, OpenAI, Gemini, Llama, Mistral or OpenRouter — or a self-hosted, OpenAI-compatible model such as Ollama. Keys stay on the server, never in the browser. |
Databases and portability
Design against MySQL, MariaDB, TiDB, PostgreSQL, CockroachDB, SQLite, SQL Server or Oracle, or start on the built-in Virtual Database. Generated apps include a runtime dialect layer, so the same app can be installed onto MySQL, PostgreSQL, SQL Server or SQLite; the built-in database follows MySQL's rules (collation, exact decimals, 64-bit integers, grouping), so moving between them doesn't change results. JSON columns, window functions, WITH ROLLUP totals and MySQL's JSON functions behave the same on each.
Shipping: builds, versions and deployment
- Version everything. Every build saves a restorable version of the project; checkpoints and a local Git repository (initialise, commit) keep a history you can push with your own Git tools.
- Build for the environment. Development and Production presets switch compression, asset versioning, error reporting and debug mode in one click.
- Deploy. Use the built-in FTP, FTPS or SFTP client, or ship the folder through your own CI/CD pipeline. An installer can let the destination choose its database, with no credentials baked in.
- Run anywhere. PHP 8 on shared hosting, cPanel, a VPS or Docker host you manage — no runtime fees, no phone-home.
When PPPHP is the right tool
PPPHP shines for data-centric applications — admin panels, internal tools, portals, multi-tenant SaaS back offices, document workflows — where most screens are lists, forms and dashboards over a relational database, and where owning the code matters. If your product is a highly bespoke consumer interface, PPPHP can still be the API and admin behind it. Start with the complete guide, see how mobile works, or ask in the community.
Frequently asked questions
Does a PPPHP app have a REST API?
Yes. Any table can be exposed with read, create, update and delete permissions, authenticated by bearer token, HMAC signature or OAuth2, with scopes, rate limits, CORS, OpenAPI documentation and a GraphQL endpoint.
Do real-time features need WebSockets or Node.js?
No. Updates stream over Server-Sent Events with a polling fallback, so they run on ordinary PHP hosting.
How does PPPHP prevent SQL injection and XSS?
Generated queries use prepared statements with bound values, printed values are HTML-escaped, forms carry CSRF tokens, and the app sends security headers. SQL you write yourself should bind values or use SQL variables, which are quoted safely.
Can I build a multi-tenant SaaS with PPPHP?
Yes. A row-level security rule such as tenant_id = :user.tenant_id limits every user to their own company’s rows across pages, exports, dashboards and the API.
Which payment gateways are supported?
Stripe, PayPal, Razorpay, Khalti, eSewa and Fonepay, plus manual bank transfer and a test simulator.
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.