TL;DR — PHP Station is a free, open-source local development environment for PHP and Laravel on Windows. It runs every project on its own PHP version, Composer and MariaDB server at the same time. It catches every email, dump() and error in one inbox, can undo a single bad SQL query, and protects your databases from the classic XAMPP crash. It is plain Node.js with zero npm dependencies: double-click a .bat file and it opens.

⭐ GitHub: github.com/sami-hussain-dev/PHP-Station · MIT license · Windows 10 / 11

PHP Station dashboard on Windows: five PHP and Laravel projects, each with its own PHP version, Composer and MariaDB server

Why I built it

I work on several Laravel apps at once on Windows. One is still on Laravel 8 and PHP 8.0, another is on Laravel 12 and PHP 8.3, and there are older PHP projects too. XAMPP gives you one PHP. Laragon lets you switch, but only one version at a time. And then there was the rest of the day:

  • a test OTP email went to a real user because .env still pointed to Gmail;
  • dd() broke the page layout, again;
  • a 40 MB laravel.log and one error I actually needed;
  • a DELETE without a WHERE, or migrate:fresh in the wrong terminal;
  • "MySQL shutdown unexpectedly" after Windows restarted for an update.

PHP Station is my answer to all of that, in one control panel. Here is the full tour.

Contents

  1. Install everything without admin rights
  2. Run multiple PHP versions at the same time
  3. Move from XAMPP or Laragon
  4. Open a Laravel project from GitHub
  5. Catch emails, dump() and errors
  6. Undo a bad query
  7. Several MariaDB versions, phpMyAdmin, DB Move
  8. Stop "MySQL shutdown unexpectedly"
  9. Show your local site to a client
  10. Comparison, under the hood, FAQ

What is PHP Station?

PHP Station is a local PHP development environment and control panel for Windows. It runs on your own machine only (127.0.0.1) and does four jobs:

  • it manages runtimes: PHP 7.4 – 8.5, MariaDB 10.4 – 12.x, Composer and phpMyAdmin, either your existing XAMPP / Laragon installs or fresh official downloads;
  • it runs projects: each one with its own PHP, Composer, DB server and port;
  • it helps you debug: mail catcher, dump() viewer and grouped Laravel errors;
  • it protects your data: clean shutdowns, snapshots, daily dumps, one-click repair and an undo for single queries.

It works as a modern XAMPP / Laragon alternative, but it doesn't throw away what you have. It finds your existing installs and uses them.

1. How do I install PHP, MariaDB and Composer on Windows without admin rights?

PHP Station setup wizard: what is installed on this PC and what each PHP project needs

Double-click PHP-Station.bat. If Node.js is missing, it offers to download the portable LTS from nodejs.org (SHA-256 checked) into its own folder.

The Setup wizard then works in two steps:

  1. It shows what is already on your PC (XAMPP, Laragon, WAMP, anything on PATH) and works out what your projects need from their composer.json.
  2. Auto select picks the versions, and everything installs in one batch.

Choosing PHP, MariaDB, Composer and phpMyAdmin versions in the PHP Station installer

Downloads come only from the official sources: windows.php.net, mariadb.org, getcomposer.org and phpmyadmin.net. Every file is SHA-256 verified. Everything lands in PHP Station's own runtimes folder: no admin rights, and your system PATH is never changed.

2. How do I run multiple PHP versions at the same time on Windows?

Each project card has its own PHP version, Composer, DB server and port. Switch on a Laravel 8 app on PHP 8.0 and a Laravel 12 app on PHP 8.3, and they both run at the same time. Nothing is switched globally.

Smaller things that add up:

  • The right PHP, suggested. PHP Station reads composer.json, composer.lock, vendor and .env, detects the Laravel version and marks the best PHP with ★. It warns you when the chosen PHP doesn't fit.
  • A terminal per project. Inside it, php and composer are exactly that project's versions, so composer install, php artisan tinker and migrate:status just work.
  • A setup checklist. It creates .env from .env.example, writes the DB settings and APP_URL, runs composer install and key:generate. Every .env change is backed up first.
  • Missing database on Run? Copy it from another server, import a .sql file or create it empty. Nothing is ever overwritten.
  • The right DB port without editing .env. If .env names another DB_PORT than the server really uses, the correct port is passed through the environment.
  • Servers you started yourself (php artisan serve, php -S) are detected, and you can adopt or stop them.
  • Fast server. On Windows, php -S answers one request at a time, so every CSS, JS and image waits behind the page. PHP Station puts a tiny Node proxy in front: it serves static files directly and spreads PHP over 4 workers. In my test, static files went from 2.4 s to under 10 ms during a page load.

Show paths in PHP Station: the PHP binary, php.ini, Composer, DB server, data folder and project folder of one project

Show paths lists the exact php.exe, php.ini, Composer, DB server, data folder and project folder of a project, each with a copy button. No more guessing which php.ini is loaded.

3. How do I move my projects from XAMPP or Laragon?

Click Shift from XAMPP / Laragon. PHP Station finds:

  • every project in htdocs / www;
  • the Apache and nginx virtual hosts (shop.test and friends);
  • the PHP and DB server each project used before.

Tick what you want and press Shift selected. Nothing is copied or moved, and your databases stay in their old data folder. Your XAMPP / Laragon folder is not changed, so you can still open it whenever you like.

4. How do I set up a Laravel project from GitHub in one click?

Open a Laravel project from GitHub in PHP Station: paste the repository link and choose a folder

Click Open from GitHub and paste https://github.com/owner/repo, a GitLab or Bitbucket link, or just owner/repo. PHP Station then:

  1. clones it with your installed Git (private repositories use your normal Git sign-in);
  2. picks the right PHP from composer.json;
  3. installs anything missing from the official sources;
  4. runs composer install, creates .env and APP_KEY;
  5. creates the database (MariaDB, or the SQLite file new Laravel apps expect), runs the migrations and storage:link;
  6. starts the project.

For teams, commit a phpstation.json. Every teammate who opens the folder gets the same PHP, extensions, MariaDB version and setup steps:

{ "$schema": "https://sami-hussain-dev.github.io/PHP-Station/phpstation.schema.json", "name": "Shop", "php": "8.3", "extensions": ["intl", "gd"], "database": { "engine": "mariadb", "version": "11.4", "name": "shop_db" }, "setup": ["env", "composer-install", "key", "database", "migrate", "storage-link"] } 

5. How do I catch Laravel emails, dump() and errors locally?

The Inbox page shows everything your app "says" while you build it. It needs no package, no code change and no .env change.

Mail catcher: no test email reaches a real person

PHP Station mail catcher for Laravel: caught emails on the left, an HTML order confirmation with its PDF attachment on the right

Every email a project sends while it runs in PHP Station lands here: OTP codes, password resets, invoices, and queued mail when queue:work runs in a PHP Station terminal. You get:

  • the real HTML design, in desktop or mobile width;
  • the text part and the raw headers;
  • attachments and the .eml file;
  • Bcc recipients, taken from the SMTP envelope;
  • the project that sent each email.

Nothing is ever relayed.

dump() and dd() without breaking the page

Laravel dump() output shown as collapsible trees in PHP Station, with the file and line that called it

dump($order) appears as a collapsible tree, with public, protected and private properties. It also shows the file and line that called it, and a click opens that line in VS Code, Cursor, PhpStorm or Sublime. The page stays clean. Close the panel, and dump() prints into the page as it always did.

laravel.log, grouped and readable

laravel.log errors grouped in PHP Station: repeated exceptions counted, new ones flagged, stack trace with vendor frames folded

The same exception thrown 500 times is one row marked ×500. New errors get a red chip on the project card. In the stack trace, your own frames come first and the vendor frames are folded. The log file is only read, never changed.

How does this work without touching .env?

Projects started by PHP Station get a tiny auto_prepend_file. While the panel runs, it sets the mail and dumper variables for each request:

putenv('MAIL_MAILER=smtp'); $_ENV['MAIL_MAILER'] = 'smtp'; putenv('MAIL_HOST=127.0.0.1'); // ...and MAIL_PORT=1025 $_SERVER['VAR_DUMPER_FORMAT'] = 'server'; $_SERVER['VAR_DUMPER_SERVER'] = '127.0.0.1:9912'; 

Laravel's dotenv never overwrites a variable that already exists, so these values win over .env. VAR_DUMPER_FORMAT=server is Symfony VarDumper's own dump-server switch.

Dumps are decoded with the project's own symfony/var-dumper classes only, and unserialize() may create only VarDumper's Data and Stub classes.

The prepend checks a heartbeat file the panel rewrites every 30 seconds. Close the panel and it does nothing, so your app sends real mail again, exactly as configured.

6. How do I undo a DELETE or a migrate:fresh in MariaDB?

DB Time Machine in PHP Station: every INSERT, UPDATE and DELETE with its SQL and old and new values, and an Undo button

The DB Time Machine lists every INSERT, UPDATE and DELETE in a project's database, whether it came from your app, phpMyAdmin or a SQL console. Each one shows its time, its SQL and the old and new values with column names.

Undo this reverses only that one action. A deleted row comes back, and everything after it stays as it is. The undo is recorded too, so it can be undone. If the same rows changed again later, you are warned first.

It's built on MariaDB's own row-based binary log (10.2+), switched on through command-line flags only, with no my.ini edit. The reverse comes from mariadb-binlog --flashback.

A busy day in the DB Time Machine: actions grouped by hour, repeated inserts folded into one line, counts as filters

Thousands of actions a day stay readable:

  • they are grouped by hour;
  • orders · INSERT × 250 is one line;
  • the counts double as filters;
  • id=21 shows the whole history of one row.

Database restore points in PHP Station: full copies of a database, one click back

For big mistakes there are restore points. A full copy is saved automatically before php artisan migrate* or db:*, and you can make one by hand. Going back first saves the current state. Every restore is test-imported into a scratch database before the real one is touched.

7. Can I run several MariaDB versions side by side?

Two MariaDB servers, 12.3 and 10.4, running side by side on their own ports in PHP Station

Yes. Start and stop any MariaDB / MySQL install, including the ones inside XAMPP and Laragon, and create new isolated server instances on their own port. If the same data folder is already being served (even by an elevated Laragon), PHP Station uses that server instead of starting a second one on the same data.

  • phpMyAdmin built in. Every DB server is listed on its own port, and it opens straight into a project's database.
  • DB Move. It moves a database from an old server to a new one: dump, import, then row counts compared table by table.

phpMyAdmin opened by PHP Station directly on a project database

8. How do I stop "MySQL shutdown unexpectedly" in XAMPP?

That error usually means the DB server was killed while Windows shut down, or two servers used the same data folder. PHP Station attacks it from every side:

  • Shutdown guard. A tiny helper makes Windows wait on shutdown, restart or sign-out until every DB server has stopped cleanly.
  • Snapshots. The data folder is copied before PHP Station starts a server (daily or always, last N kept).
  • Daily dumps. Every database of each running server gets a .sql dump once a day.
  • One-click repair. It reads the error log and names the problem: crashed Aria / MyISAM tables, broken privilege tables, "log sequence number is in the future", port and lock issues. It takes a snapshot first, then fixes the problem.
  • Rescue data. For InnoDB damage it works on a copy, trying innodb_force_recovery 1 → 6, dumps everything and can import it into a fresh server.

One-click MariaDB repair in PHP Station: reads the error log, takes a snapshot, then repairs

The rule behind all of this: old data is never deleted or overwritten. Restores always go into a new folder or a new database.

Database backups in PHP Station: data-folder snapshots and daily SQL dumps

9. How do I show my local Laravel site to a client?

Start the project and press Live link. You get a public https://….trycloudflare.com address that opens on any phone. It uses a Cloudflare quick tunnel: no account, no hosting, no router settings. Laravel sees HTTPS correctly. The link ends when you stop it, stop the project or close the panel.

Also: three languages and two themes

The interface speaks English, Roman Urdu and Urdu (right-to-left), with a dark and a light theme.

PHP Station in Urdu, right to left

PHP Station vs XAMPP vs Laragon

PHP Station XAMPP Laragon
Different PHP version per project, at the same time ✅ ❌ ⚠️ one global version
Several MariaDB / MySQL servers side by side ✅ ❌ ⚠️ manual
dump() / dd() viewer outside the page ✅ ❌ ❌
Grouped laravel.log errors with editor links ✅ ❌ ❌
Undo one INSERT / UPDATE / DELETE ✅ ❌ ❌
Restore points before migrate:fresh ✅ ❌ ❌
GitHub link → running project ✅ ❌ ❌
Clean DB stop on Windows shutdown ✅ ❌ ❌
Snapshots, daily dumps, one-click repair ✅ ❌ ❌
Public HTTPS link, no account ✅ ❌ ⚠️ ngrok, manual
Official downloads with SHA-256 check ✅ – –
Size of the tool ~1 MB, zero deps ~150 MB+ ~100 MB+

Based on the default behaviour of XAMPP and Laragon at the time of writing. If something is out of date, tell me in the comments.

Under the hood

  • Node.js 18+, zero npm dependencies, no build step. server.js handles HTTP and the CLI, there is one lib/*.js module per feature, and the UI is plain vanilla JS.
  • Local only. It listens on 127.0.0.1, checks Host and Origin, needs a per-start token for every API call, and sends a strict Content-Security-Policy.
  • It only stops processes it has verified itself. Other programs are never touched.
  • DB passwords are never stored or logged.
  • Tested. A node --test suite with 229 tests, including real PHP servers, the SMTP server and the dump server on loopback.

Quick start

git clone https://github.com/sami-hussain-dev/PHP-Station.git 
  1. Double-click PHP-Station.bat. The panel opens at http://127.0.0.1:7070/.
  2. Let the Setup wizard install what your projects need.
  3. Click Shift from XAMPP / Laragon, Open from GitHub or + New project, then switch a project on.

FAQ

Is PHP Station free?
Yes. It's open source under the MIT license, with no paid tier and no account.

Does PHP Station replace XAMPP or Laragon?
It can. It installs PHP, MariaDB, Composer and phpMyAdmin on its own, but it also works on top of an existing XAMPP or Laragon and uses their PHP versions and DB servers.

How do I run two Laravel projects with different PHP versions on Windows?
Add both projects, choose a PHP version on each card, and switch both on. Each runs with its own php.exe on its own port, at the same time.

Will my Laravel app send real emails while I test?
Not while it runs in PHP Station with the mail catcher on (the default). Every email lands in Inbox → Mail. If you used php artisan config:cache, run config:clear first.

Can I recover a row I deleted by mistake in MariaDB?
Yes. Open Time Machine → Every action, find the DELETE and press Undo this. Only that row comes back.

Does it need admin rights or change my PATH?
No. Everything goes into PHP Station's own folders.

Does it work on macOS or Linux?
Not yet. It's Windows 10 / 11 only for now; macOS and Linux are on the roadmap.

Which versions are supported?
PHP 7.4 – 8.5 and MariaDB 10.4 – 12.x can be installed. Any PHP / MariaDB / MySQL already on the PC can be used too.

What's next

*.test domains with local HTTPS, queue workers and a scheduler per project, Redis, a "new Laravel project" template, and macOS / Linux.

I'd really like feedback, especially from people with complicated Windows setups (old XAMPP, Laragon, several MariaDB versions). Which feature would you use first, and what is missing?

If PHP Station saves you an afternoon, a ⭐ on GitHub helps other PHP developers find it. 🙏