EnvKit: a free local web stack for Windows and Apple Silicon Macs

What EnvKit replaces on a Windows or Mac workstation

The problem is familiar to anyone who has set up Laravel or WordPress locally: nginx or Apache, a PHP version that matches the project, a database, Redis, a mail catcher, and a certificate the browser trusts. EnvKit packages that into one desktop app with a tray icon. The README describes it as a free Laragon, XAMPP and Herd alternative, and it targets Windows 10/11 and macOS 12 Monterey or later on Apple Silicon only. The audience is PHP and Laravel developers first, plus WordPress work and Node projects (React, Next.js, Angular, Express), which the app auto-detects and serves over .test HTTPS with live reload. The distinctive extra is an MCP server: assistants such as Claude Code, Cursor, Windsurf, VS Code, Zed, OpenCode, Gemini CLI and JetBrains IDEs can drive the stack, and the 0.32.0-beta.8 notes say assistants can create sites, run Git actions, manage databases and cron jobs, install services and change settings.

One tray app, per-service directories, and a local CA

The architecture visible in the repository is a bundled-runtime model rather than a container model. EnvKit installs service runtimes into its own directories, and the README notes that MySQL 8 can sit side by side with MariaDB because each version lives in its own directory. Sites get a hosts entry of the form 127.0.0.1 <site>.test, removed when the site is removed, and HTTPS for those names is signed by a local CA that the installer places in the Trusted Root store. The bundled tools (php, composer, node and others) are exposed through PATH. On Windows the installer also adds Windows Defender exclusions for the install folder, the services and tools folders, and the bundled executables, with the installer's exclusion removed on uninstall. That is a real footprint on your machine, and the README is unusually direct about listing it. The trade-off is that EnvKit is not isolated from the rest of the system the way a container per project would be: it is designed to run side by side with what you already have, and it states that it never stops a PostgreSQL or MySQL you installed yourself.

Installing EnvKit on Windows and macOS

On Windows there is no package manager step. You download the latest EnvKit-Setup-x.y.z.exe from the releases page and run it. The README warns that SmartScreen may flag the first run because the build is self-signed, and that you pass it with More info then Run anyway.

On Apple Silicon the documented path is a one-line script that fetches the latest macOS build, removes the Gatekeeper quarantine attribute and opens it:

curl -fsSL https://raw.githubusercontent.com/Env-Kit/envkit-releases/main/install.sh | bash

Running the same command again updates the app. To remove it, the README gives the uninstall form:

curl -fsSL https://raw.githubusercontent.com/Env-Kit/envkit-releases/main/install.sh | bash -s -- --uninstall

The script skips release tags that have no macOS asset, because Windows and macOS are released independently and the newest tag is sometimes Windows-only. A manual route also exists: download EnvKit-x.y.z-arm64.dmg from the releases page, drag EnvKit to Applications, and on first launch right-click the app and choose Open, or run the quarantine removal the README shows:

xattr -dr com.apple.quarantine /Applications/EnvKit.app

After that, a first-run wizard asks whether to load a Laragon setup (a guided detect and import flow that includes databases) or start fresh. EnvKit auto-updates on both platforms through GitHub, and the README states that data directory, certificates and settings migrate automatically on upgrade.

Beta releases, a private source tree, and an unstated licence

Two limitations stand out before you install anything. First, the release history is beta: the three releases listed for this repository are v0.33.0-beta.7, beta.8 and beta.9, dated 2026-08-31 through 2026-09-02. The changelog is dominated by community-reported fixes, including sites that reappeared after removal, PostgreSQL and MySQL instances being stopped by the app, and install progress reporting. That reads like software that is still settling, and the release cadence is fast. Second, this repository is explicitly the public home for releases and documentation, and the README says the application source is maintained privately. You can read what EnvKit does to your system, but you cannot read how it does it or send a patch. The licence field on the repository is not filled in, and the README does not state licence terms for the application. If you need an OSI-approved licence or the ability to fork, the README does not establish that EnvKit gives you either, and you should treat that as an open question rather than an assumption. macOS support is also narrower than the platform badge suggests: the README states that Intel Macs are no longer supported.

How EnvKit differs from Laragon, XAMPP and Herd in approach

Laragon and XAMPP are the closest comparisons and the project names both as alternatives. The practical difference is scope of control. XAMPP ships a fixed set of components for a given release; adding a second PHP version or a different database means managing that yourself. Laragon is Windows-only and built around its own bundled stack. EnvKit instead offers per-service version selection, including the ability to type an arbitrary version of MySQL/MariaDB, nginx, Node.js, MongoDB, Redis, PostgreSQL or Python and have the app install it, which is a different model from pinning to whatever the bundle ships. Herd, by contrast, is the comparison for the macOS and Windows PHP workflow, and EnvKit's answer to it is the breadth of bundled services plus the MCP server. That MCP server is the clearest divergence from all three: none of the tools named in the README are described there as exposing the local stack to an AI assistant for site creation, Git operations or database management. If you only need PHP and a database and you already have a working Laragon setup, the migration flow exists but you are also taking on a beta release cadence for capabilities you may not use.

Maintenance, upgrades and what the repository does not tell you

The last push to this repository was on 2026-09-10, and the most recent release listed is v0.33.0-beta.9 from 2026-09-02. The project is not archived. That tells you releases are moving, but it does not tell you anything about the closed source tree behind them. Upgrades are handled in place: the README states that EnvKit checks GitHub for new releases and installs them, that Settings has a manual check and download path, and that the data directory, certificates and settings are migrated automatically on first launch after an upgrade. On Windows the installer is self-signed, which is why SmartScreen warns and why the code-signing certificate is added to the Trusted Root store so auto-updates verify; the README notes there is no paid EV/OV cert yet. On macOS the app is Developer-ID signed but notarization is still pending on Apple's side, which is the reason for the right-click Open step. Both of those are supply-chain details worth reading before you roll the tool out to a team, because they determine how much of the trust decision rests on the project's own certificates.

Editorial conclusion

Adopt EnvKit if you build PHP, Laravel or WordPress projects on Windows or an Apple Silicon Mac and want one installer to manage the services and the local certificates. Do not adopt it if you need to read or patch the application source, since this repository holds releases and documentation only, or if you are on an Intel Mac, which the README states is no longer supported. Before committing a team to it, verify the licence terms on envkit.net, check that your antivirus policy allows the Defender exclusions the installer adds, and confirm the latest release tag actually ships an asset for your platform.

Frequently asked questions

Official sources

1. Env-Kit/envkit-releases on GitHub
2. Issues
3. Project website
4. README
5. Releases