Our take
Activeregular commits and releases- Activity
- 82
- Community
- 51
- Issues
- 72
- Pull requests
- 50
+80 stars in the last 30 days
- Releases more often than 80% of the projects we track
- Merges more pull requests than 80% of the projects we track
FlyEnv is a broad, actively maintained native development environment, though its high contributor concentration is a meaningful continuity risk.
Good fit if
- You want a single desktop workspace for native runtimes, databases, web servers, and local sites across Windows, macOS, or Linux.
- Your local workflow benefits from per-project runtime versions, local HTTPS, or grouped service startup.
- You want to connect supported AI coding tools to selected local environment capabilities through MCP.
Look elsewhere if
- Your main goal is containerized reproducibility or production parity, which FlyEnv does not replace.
- Your team needs a project with broadly distributed contributor ownership, since most contributions come from one person.
- You require documented automated tests as part of the project's development workflow; the supplied repository data indicates none.
All health signals
| Last commit | 2026-10-27 (3 days ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 30 (latest v4.20.2, 2026-10-24) |
| Contributors | 77 (top contributor: 89% of commits) |
| Issues closed, last 90 days | 35+ (typically closed in 3 days) |
| Pull requests merged, last 90 days | 66 (typically merged in 2 days) |
| Project age | 6 years |
Checked on 2026-10-31 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
3,372Forks
399Change since Nov 17, 2026: +1 stars·+2 forks
Overview
FlyEnv is a native local development environment for Windows, macOS, and Linux, built as a TypeScript desktop application. It aims to replace the separate setup and management of tools such as XAMPP, MAMP, Laragon, or Laravel Herd with one workspace for runtimes, databases, web servers, local sites, HTTPS, and AI coding tools.
Its broad runtime and service coverage makes it relevant beyond PHP projects. FlyEnv runs services natively rather than requiring containers for everyday local development, while offering per-project runtime versions, local domains, and workflows for starting related services together.
Key Features
- Manage runtimes including PHP, Node.js, Python, Java, Go, Ruby, and others.
- Install and manage databases and services such as MySQL, PostgreSQL, Redis, RabbitMQ, Elasticsearch, and MinIO.
- Work with Nginx, Apache, Caddy, FrankenPHP, and other web or application servers.
- Switch runtime versions by project and configure project start commands and ports.
- Set up local domains, HTTPS certificates, and reverse proxies.
- Group projects and services into reusable startup workflows.
- Manage supported AI coding tools and expose selected local environment capabilities through the FlyEnv MCP Server.
Use Cases
- A PHP or Laravel developer wants a desktop-managed stack with PHP, a database, Redis, Node.js, and a web server.
- A developer working across Windows, macOS, and Linux wants similar native local-development workflows on each platform.
- A Python or Node.js developer needs local runtimes, databases, domains, and HTTPS without setting up containers for routine work.
- A developer using AI coding tools wants those tools to inspect selected local services, sites, configurations, or logs through MCP.
What you need
Detected in the repository
- Node.js >=18.0.0 (from package.json)
- Automated checks on GitHub Actions
License in plain words
BSD-3-Clausepermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice; the authors' names cannot endorse your product
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
On macOS, install with Homebrew:
brew install flyenv
For Windows and Linux downloads, platform-specific packages, and setup guidance, see the README and releases.
Considerations
The project is actively maintained, with frequent commits and releases and quick issue and pull-request handling. However, contribution is concentrated heavily in one person, so teams should weigh maintainer continuity when adopting it for important workflows. The repository data also indicates no automated tests. FlyEnv is intended for native local development, not as a substitute for container parity or a container-based deployment workflow.
Found this useful?
Share it with someone who would like FlyEnv.