The stack

The destination, not a stepping stone.

PHP, SQLite and jQuery give you a direct way to build server-rendered pages, account workflows and APIs. Run the web app on your own server and connect the services your product needs.

Database One SQLite file

Queries run in the PHP process. No separate database server is required for the default setup.

Concurrency WAL mode

Readers can run alongside a writer. SQLite still has one writer at a time; keep transactions short and test your workload.

Transactional email SMTP delivery

Use SES or your configured SMTP service. Email volume and provider options determine your bill.

See the implementation

This storefront runs on the starter.

The same PHP application handles its pages, accounts, payments and protected downloads. Explore the demos and read the setup requirements before choosing it for your own workload.

Keep

The parts that buy speed

PHP for pages, forms, APIs, and webhooks — fast to write, instant to deploy.
SQLite as the primary database. It is not a toy; it is the most-deployed database on earth.
jQuery for DOM work and AJAX, with zero build step.
A PHP-capable server with NGINX or Apache, scheduled backups and a supported PHP runtime.

Avoid

The parts that buy complexity

Premature microservices and message queues.
Frontend build pipelines and hydration for server-rendered pages.
Auth providers and password databases you have to babysit.
Abstractions that slow iteration down without paying rent.

The rule

Make the common path boring, so the product can be interesting.

Every site reuses the same login, payments, deploy shape, backups, and webhook conventions. You change the product idea, not the plumbing — whether you're vibe-coding a weekend tool or running a serious, revenue-generating SaaS.