Your whole PHP stack, in one folder.
PHP 8.5, MariaDB, Caddy, phpMyAdmin and a SQLite studio — unzipped, not installed.
Start it, open localhost, build. Delete the folder and your machine is exactly as it was.
Windows 10/11 macOS 12+ Linux
Everything a PHP project needs. Nothing it doesn't.
One download per platform. No Docker, no package manager, no services registered on your machine, no administrator password.
PHP 8.5 with the full set
PDO for MySQL, SQLite, Postgres and SQL Server, plus sodium, GD, intl, zip, cURL and OPcache — already on, already tuned.
MariaDB and phpMyAdmin
A real database on the port every tutorial assumes. phpMyAdmin is already wired to it, themed to match, and opens without a single warning — the configuration storage is created for you.
SQLite Studio
Create, browse, query, dump and vacuum file databases in the browser. No server process; nothing to configure.
Caddy, already routing
Clean URLs without touching a config file. Your sites live in www/ and answer on plain localhost.
A control panel, not a config file
Memory, timezone, OPcache, ports, extensions, InnoDB tuning — every setting with an explanation, validated before it is saved.
Light or dark, everywhere
It opens light, because most people run it beside an editor in a lit room. One button in the corner turns the whole thing dark — the welcome page, the control panel, SQLite Studio and phpMyAdmin alike — and it remembers which one you chose.
Two icons, no terminal
Start PPServer carries a green tick, Stop PPServer a red cross, and they sit at the top of the folder on Windows and macOS. Double-click to start, double-click to stop. One switch in the panel starts PPServer with your computer, and you can stop it from the welcome page or the panel too.
One folder is yours
www/ is the document root and the only folder you ever edit. PPServer never writes there, so an
upgrade cannot touch your work — and a button on both the welcome page and the control panel opens it in
Finder or File Explorer.
Backups, in one file
Tick your databases and the folders you care about, press one button, and get a single compressed file. Carry it to another computer, or to a newer PPServer, and press Restore. PPServer can also do it for you every night — and it takes a safety copy before it replaces anything.
Private by default
Everything binds to 127.0.0.1, so the panel, phpMyAdmin and the SQLite studio answer only on your own machine. A new install prints its password on the lock screen — no file to open — and the Security tab changes that password and the database one in about ten seconds.
Running in about a minute
Download the archive for your platform, unpack it anywhere you can write — a Documents folder is fine — and start it. There is no installer and nothing to uninstall.
Unpack it
Put the folder wherever you like. It never writes outside itself.
C:\PPServer ~/PPServer
Start it
Double-click Start PPServer — the icon with the green tick — on Windows or macOS.
On Linux, or from a terminal anywhere:
./ppserver start # macOS · Linux .\ppserver.cmd start # Windows
Open what it prints
Usually plain localhost. Your sites go in www/.
http://localhost/ http://localhost/_ppserver/
About the address. On the first start PPServer takes the standard ports when your
machine will give them up, so the address is plain localhost and the database is on 3306.
If something already holds them — IIS or Skype on port 80, an existing MySQL on 3306 — it steps aside rather than
fighting, and remembers the choice so the address never moves afterwards.
Watch it, start to finish
Every screen in this walkthrough is the running product: download the right build, unpack it, start it with a double-click, go through every tab of the control panel and both database tools — then install PPPHP RAD Studio on top of it.
- The problem
- What PPServer is
- Download it
- Where to put it, and unpacking
- Starting it
- The control panel, tab by tab
- Kept current, closed by default — and reversible
- Your work, in one file you can carry
- phpMyAdmin and SQLite Studio
- Light or dark, your choice
- On, off, and always there
- The one rule, and www
- Install PPPHP RAD Studio
- Where to go next
- Delete the folder — that is the uninstall
- It keeps moving
Part of Getting Started with PPPHP RAD Studio — short episodes, each one a real build.
Built to stay out of your way
Components live in versioned slots, so an upgrade installs beside the working one and rolls back
cleanly. Your www/ folder is never touched by an upgrade. A crashed PHP worker is replaced
automatically, and doctor checks the things that actually break a local stack — busy ports, missing
extensions, a PHP that cannot verify HTTPS.
Patched, and built to prove it
A local server runs your code all day, so the version it ships matters. PPServer 0.7.0 carries the current release of every component, and the archive is checked before it is published — not just assembled.
8.5.12Fixes the two critical remote-code-execution flaws disclosed on 21 October 2026 (CVE-2026-109618, CVE-2026-109619 — CVSS 4.0 base 9.2, assigned by PHP). Checked 27 October 2026: no PHP vulnerability is outstanding against 8.5.12.2.11.7A year of fixes on from 0.5.0, in exactly the parts PPServer relies on: FastCGI path handling, the path matcher, and the Windows file server.11.8.9The newest release in the 11.8 long-term-support line.5.2.3Current release, shipped with its setup wizard removed — nothing in the bundle can rewrite your database connection.1.0.22Built from source rather than taken from the distribution, so modern cryptography is available on every platform, Arm included.2026-10-20Mozilla's current root list, so HTTPS from your own code is verified on Windows, macOS and Linux alike.Closed by default
It only answers to you
Every service binds to 127.0.0.1, and the web server replies only to localhost
names. A page on the internet that points itself at your machine gets a refusal, not your control panel.
Your secrets stay unserved
Dot-files are blocked outright, so a .env or a .git folder sitting in a real
project cannot be fetched — including through encoded or mixed-case paths.
No remote control surface
The web server's administration API is switched off entirely, and phpMyAdmin ships without its installer. There is nothing listening that can reconfigure the stack.
Nothing arrives unchecked
Every component is downloaded over HTTPS and matched against a recorded checksum at build time. A digest that does not match stops the build; it never becomes a release.
Checked before it ships
Each archive is unpacked and actually run before it is published — the stack is started, the control panel, phpMyAdmin and the SQLite studio are opened, a database is created and dropped, a PHP worker is killed to confirm it is replaced while requests keep succeeding, and the cryptography PPPHP depends on is exercised end to end. The macOS and Linux archives clear 71 checks each; the Windows archive clears 48. A build whose libraries would not resolve on another machine, or whose cryptography does not work, cannot be packaged at all — both are hard gates in the build itself.
PPServer is unsigned, so Windows SmartScreen and macOS Gatekeeper will warn the first time you open it; the installation steps above show what to click. Every archive is published with its SHA-256 so you can confirm what you downloaded.
Not sure whether your own server is affected? Read the two-minute check — what the October 2026 PHP flaws actually are, how to find the version your site really runs (the command line and the web server are often different builds), and what to do about it on shared hosting and on a VPS.
Your work, in one file you can carry
A local server holds the only copy of a lot of work. PPServer takes that seriously: tick what matters, press one button, and everything you made is in a single compressed file — ready to move to a new machine, a newer PPServer, or back onto this one.
It can run itself
Every day or every week, at a time you choose. PPServer uses your own computer's scheduler, for your account only — nothing installed system-wide, no administrator password, and switching it off removes it again.
A half backup never happens
If the database is not running when the scheduled moment comes, the run is skipped and says so rather than writing an archive with your files and none of your data. The panel shows you what the last run did, and when the next one is due.
Restoring is three clicks
PPServer opens the file, lists what is inside it, and marks each item new here or replaces the one here. Untick anything you would rather keep. A safety copy of whatever it is about to replace is taken first, so a restore can be undone.
A passphrase, if it is leaving your hands
Going on a USB stick, into a shared folder, or to cloud storage? Put a passphrase on it and only that passphrase opens it — modern authenticated encryption, with the key stretched by Argon2id. PPServer keeps no copy of it.
Keep them where you like
The folder beside your sites, an external disk, or a folder your cloud storage syncs — your choice. Keep the last few automatic ones and PPServer prunes the rest; the ones you made by hand are never touched.
Nothing to trust blindly
Every item is checked against the fingerprint recorded when it was made, before anything is written — so a damaged or half-copied file stops the restore instead of importing half a database. You can also verify a backup on a good day, rather than discovering it on a bad one.
What is in a backup: your MariaDB databases, your SQLite databases, and the parts of your web root you chose. What is not: PPServer itself. Ports, passwords, PHP settings and extensions are a few clicks on the new machine, so carrying them would only add weight — and would let you import another computer's configuration by accident.
Made for PPPHP, useful for anything
PPServer exists because PPPHP RAD Studio needs a dependable place to run while you build. It checks
for exactly what PPPHP requires and tells you in one line whether this machine can run it. But it is an ordinary
PHP stack: Laravel, WordPress, a single index.php — drop it in www/ and it works.
Stop configuring. Start building.
A development server should be ready before your coffee is. PPServer unpacks, starts, and gets out of the way.