EnvKit: a tray app that runs nginx, PHP, MySQL and the rest of a local stack on Windows and macOS
EnvKit — free local development environment for Windows & macOS: nginx/Apache, multiple PHP versions, MySQL/MariaDB, PostgreSQL, Redis, MongoDB, Mailpit, Node.js, trusted .test HTTPS, and a built-in MCP server for AI-assistant control. A Laragon/XAMPP/Herd alternative.
At a glance
- What is it?
- EnvKit is a closed-source desktop application that installs and supervises local web-development services, with an MCP server so AI assistants can drive it. It is distributed as signed installers through this repository, which holds releases and documentation only.
- Who is it for?
- Adopt EnvKit if you develop on Windows 10/11 or Apple Silicon macOS and want one tray app to install and supervise nginx or Apache, several PHP versions, MySQL/MariaDB, PostgreSQL, Redis, MongoDB, Mailpit and Node.js, with trusted .test HTTPS and an MCP server for AI assistants.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 3 days ago.
- What is it written in?
- Mainly Shell, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What EnvKit is for, and the repository you actually get
EnvKit targets developers who want a working local stack without assembling it by hand. The README describes it as a desktop app that runs nginx or Apache, multiple PHP versions, MySQL/MariaDB, PostgreSQL, Redis, MongoDB, Mailpit, Node.js, Python, phpMyAdmin, trusted .test HTTPS and PATH sync from one tray app, positioned against Laragon, XAMPP and Herd. The stated use cases are Laravel, WordPress, PHP and Node projects including React, Next.js and Angular. It is free, and it runs on Windows 10/11 and on macOS 12 Monterey or later, Apple Silicon only.
The first thing to understand is what this repository is. It is the public home for releases and documentation; the README states that the application source is maintained privately. There is no licence file in the supplied material, so the terms under which you may use the binaries are not established here. Everything below therefore describes documented behaviour of a distributed binary, not code anyone outside the project can read. For a tool that edits your hosts file, installs root certificates and adds antivirus exclusions, that distinction is the main thing to weigh before installing.
The MCP server is the part that is not Laragon
Most of EnvKit's feature list is a superset of what Laragon and XAMPP already do. The differentiator is the built-in MCP server. The README says the app can be driven by Claude Code and Claude Desktop, Cursor, Windsurf, VS Code, Zed, OpenCode, Gemini CLI, and JetBrains IDEs including PhpStorm, and that a Set up detected clients action configures Junie automatically for JetBrains. Per the release notes for 0.33.0, assistants can create sites, run Git actions, manage databases and cron jobs, install services and change settings.
That is a wider surface than most MCP integrations expose. Site creation and service installation are not read-only operations: an assistant that can install a service or change settings can change what runs on your machine. The README does not describe a permission model, an approval step or an audit log for MCP actions in the material provided. Treat the MCP server as the feature to evaluate most carefully, and decide which clients you actually connect before enabling it.
How the stack is assembled and kept running
The mechanism visible in the material is a supervisor plus a versioned services directory. Each service version lives in its own directory, which is what allows MySQL 8 to sit side by side with MariaDB, and what makes custom versions possible: the README says you can type any version of MySQL/MariaDB, nginx, Node.js, MongoDB, Redis, PostgreSQL or Python and EnvKit installs it. A services manifest describes what is available; the release notes state that a corrupt manifest repairs itself, and that service archives are mirrored on GitHub so installs do not break when an upstream download moves.
Installation is non-blocking, with a Stop button on every install. Sites get a 127.0.0.1 hosts entry each, and a local CA signs HTTPS certificates for .test hostnames. PATH sync exposes the bundled php, composer and node binaries. The release notes also record a specific piece of restraint: EnvKit will not stop a PostgreSQL or MySQL instance you installed yourself, and removed sites stay removed. Those two lines say more about the supervision model than the feature list does, because they describe the boundary between EnvKit's services and the rest of the machine.
Installing on Windows and macOS, and what the installer changes
On Windows you download EnvKit-Setup-x.y.z.exe from the releases page and run it. The README warns that SmartScreen may flag the first run and that EnvKit is self-signed, with More info then Run anyway as the documented path. On Apple Silicon macOS there is a one-line install:
curl -fsSL https://raw.githubusercontent.com/Env-Kit/envkit-releases/main/install.sh | bash
The script downloads the latest macOS build, strips the Gatekeeper quarantine and opens it; running the same command updates, and appending -s -- --uninstall removes it. Because Windows and macOS are released independently, the newest tag is sometimes Windows-only, and both the script and the in-app updater skip past it to the latest Mac build. You can also download EnvKit-x.y.z-arm64.dmg and drag it to Applications, then right-click Open on first launch or run xattr -dr com.apple.quarantine /Applications/EnvKit.app. The app is Developer-ID signed but not notarized, and the README says notarization is pending on Apple's side.
The README also lists what EnvKit touches, and this is the section to read before installing. The Windows installer adds a Defender exclusion for the install folder (the README says real-time scanning otherwise locks the freshly installed exe and the first launch fails), and the app excludes its own services and tools folders plus bundled executables such as php, nginx and mysqld. Two certificates go into the Trusted Root store: EnvKit's code-signing certificate, so auto-updates verify, and the local CA for .test HTTPS. The code-signing certificate is removed on uninstall, as is the installer's Defender exclusion. Only Microsoft Defender is affected, and the exclusions are scoped to EnvKit's own folders.
Beta tags, independent platform releases and update cost
The three most recent releases are v0.33.0-beta.9, beta.8 and beta.7, pushed within three days of each other in early September 2026. That cadence is the maintenance picture: frequent beta builds, auto-update on both platforms, and an in-app Settings then Updates path for manual checks. Upgrades migrate your data directory, certificates and settings automatically on first launch, according to the README, so the per-upgrade cost for the user is mostly the download and a restart.
The cost that is harder to see is that this is a beta stream with a private codebase. When a release breaks a service, you cannot read the fix, patch it, or pin to a commit. You can decline the auto-update, but the README does not describe a supported way to run an older build long term. The bundling also ages: the notes list Git 2.55, GitHub CLI 2.95 and Python 3.12.10 as bundled tools, which means tool versions move on EnvKit's release schedule rather than yours unless you override PATH. On licensing, this repository contains no licence file, so nothing in the supplied material states the terms for the binaries; check envkit.net before deploying it in a company, and treat that as a question for whoever handles your software approvals rather than a legal conclusion from a review.
Where EnvKit is the wrong tool, and what to use instead
Three cases argue against it. Intel Macs are unsupported: the README states EnvKit no longer supports them. Environments that forbid antivirus exclusions or additions to the Trusted Root store are a second problem, because both are part of the documented install path rather than optional extras. Third, anyone who needs to read, patch or vendor the supervisor should look elsewhere, since the source is private.
Docker Compose is the real alternative, and the difference is architectural rather than a matter of taste. Compose expresses your stack as a YAML file in your repository: image tags, ports, volumes, environment variables. It runs the same on Linux, macOS and Windows, it is versioned with your project, and a colleague gets your exact services with docker compose up. EnvKit instead installs native service binaries on the host, manages them from a tray app, and writes one hosts entry per site. The trade-off is concrete in both directions. EnvKit gives you trusted .test HTTPS, PATH sync and one-click service control without writing a Compose file, and it runs the services natively, which is closer to typical shared hosting than a container is. Compose gives you reproducibility, Linux parity and a configuration you can review and commit. If your project already has a compose.yaml, EnvKit does not replace it; it replaces the part where you install PHP and MySQL on the host to run things outside containers.
Who should install it, and what to check first
The fit is a Windows or Apple Silicon macOS developer running Laravel, WordPress or a PHP and Node project who wants the stack installed and supervised without hand-editing configs, and who is comfortable with a beta release stream and a closed-source binary. The Laragon import path is aimed at exactly that person: the onboarding wizard offers Load from Laragon, described as a guided detect, import and database migration flow, or Start fresh. The per-project Git panel, with staging, commit, branch switching and fetch, pull and push with ahead/behind counts, is a convenience for people who would otherwise keep a terminal open next to the tray icon.
The wrong fit is anyone on an Intel Mac, anyone whose security policy rules out Defender exclusions or new Trusted Root certificates, and anyone who needs to audit or fork the code that manages their local services. Before installing, read the full What EnvKit changes on your system section in the README, confirm the licence terms on envkit.net since this repository has no licence file, and decide whether you will connect MCP clients and which ones. The release history is the other thing to look at: v0.33.0-beta.9 landed on 2 September 2026, one day after beta.8 and two days after beta.7. That is the pace you are adopting.
Editorial conclusion
Adopt EnvKit if you develop on Windows 10/11 or Apple Silicon macOS and want one tray app to install and supervise nginx or Apache, several PHP versions, MySQL/MariaDB, PostgreSQL, Redis, MongoDB, Mailpit and Node.js, with trusted .test HTTPS and an MCP server for AI assistants. Do not adopt it if you are on an Intel Mac, if you need to audit or patch the application source, or if you cannot accept a beta release stream: the newest tags are v0.33.0-beta.7 through beta.9, and the repository states the application source is maintained privately. Verify before committing: read the full What EnvKit changes on your system section, confirm the Defender exclusions and the two Trusted Root certificates it installs, and check the licence terms on envkit.net, because this repository carries no licence file.
Community notes