Run your Windows dev stack from one control room.

Download the latest Windows installer from GitHub Releases, run it, then launch EnvKit from the Start menu or tray. There is no account, licence key, or payment step between download and local services.

Start the web server, PHP runtime, databases, Redis, MongoDB, Mailpit and other tools you need for the current project. The app keeps the state visible so you can see which service owns each port before you debug framework code.

nginx      running   :443
php-fpm    running   :9000
mysql      running   :3306
redis      running   :6379
mailpit    running   :8025

Register an existing project folder and EnvKit provisions the local host, web server routing, and HTTPS certificate. Laravel, PHP, React, and Next.js projects can live side by side, each with its own local host.

Project folder
E:\Sites\acme-app

Local host
https://acme-app.test

Dev server
http://localhost:5173

EnvKit creates a local certificate authority and issues certificates for your *.test hosts. Your browser gets real HTTPS locally, so secure cookies, OAuth callbacks, and WebSocket hot reload behave like they do in production.

EnvKit is designed for Laravel apps that need more than PHP-FPM. Run Reverb beside Redis, queue workers, your database, and the trusted local web server so realtime features can be tested without exposing a public tunnel.

Laravel app
https://acme-app.test

Realtime server
php artisan reverb:start
ws://127.0.0.1:8080

Companion services
php-fpm    :9000
redis      :6379
queue      worker

React, Next.js and other Node dev servers can be linked as local sites too. EnvKit keeps the project URL stable while the framework dev server handles hot reload behind it.

Next.js project
E:\Sites\acme-dashboard

EnvKit route
https://acme-dashboard.test

Dev server target
http://localhost:5173

Use Mailpit for local password resets, notifications and test sends before an email can leave your machine. MySQL or MariaDB cover common PHP apps; PostgreSQL, Redis and MongoDB are available when your stack needs them.

If your current Windows workflow lives in Laragon, start by importing existing projects instead of rebuilding every host by hand. EnvKit can detect project folders and carry over enabled PHP extension context so migration starts from your real setup.

Laragon source
C:\laragon\www

Imported into EnvKit
sites          detected
hosts          provisioned
php extensions matched

EnvKit exposes stack operations through MCP, so an AI assistant can inspect services, read logs, add sites, diagnose broken ports, and restart the one service that actually needs attention.

Ask your assistant
"restart nginx"
"show the php-fpm log"
"diagnose why mysql will not start"
"add this project as a .test site"

When something does not respond, start with the service state and port ownership. Most local stack issues are either a stopped service, a busy port, or a browser holding old certificate state.

Port check
nginx      :443   running
mysql      :3306  running
mailpit    :8025  running

If a port is busy:
1. Stop the conflicting app
2. Restart the EnvKit service
3. Re-open the .test host