FlyEnv is a native, cross-platform desktop application that installs and manages a complete local development stack — language runtimes, databases, web servers, local sites with HTTPS, and AI coding tools — directly on Windows, macOS, and Linux, for developers who want a working local environment without container orchestration.

What it is

FlyEnv is an open-source local development environment written in TypeScript and licensed under BSD-3-Clause. It runs as a desktop application on Windows, macOS, and Linux and brings the tools normally managed separately into one workspace: runtimes, databases, web servers, queues, search, object storage, local sites, and developer utilities. The project is published from flyenv.com.

The concrete problem it solves is stack sprawl and per-project version drift. Instead of operating a container setup for everyday local development, FlyEnv runs installed services directly on the host operating system and lets each project choose its runtime versions, ports, start and stop commands, local domain, and reverse proxy. It replaces the workflow that XAMPP, MAMP, Laragon, and Laravel Herd occupy, while extending beyond PHP and Laravel to Node.js, Python, Java, Go, and a wider set of services.

Key capabilities

• Per-project runtime switching across PHP, Node.js, Python, Java, Go, .NET, Flutter, Ruby, Rust, Erlang, Bun, Deno, and Zig.
• Database management for MySQL, MariaDB, PostgreSQL, MongoDB, ClickHouse, Neo4j, and Qdrant.
• Web and application servers including Nginx, Apache, Caddy, FrankenPHP, and Tomcat.
• Local sites such as myapp.test with HTTPS certificates and reverse proxy configuration, plus in-app access to configs and logs.
• Cache, messaging, search, and storage services: Redis, Memcached, RabbitMQ, Elasticsearch, Meilisearch, Typesense, ZincSearch, MinIO, and RustFS.
• Built-in FlyEnv MCP Server plus management of AI coding clients — Claude Code, Codex, OpenCode, Kimi, and GitHub Copilot CLI — alongside Ollama, n8n, and CLIProxyAPI.
• Utility tools including Cloudflare Tunnel, Mailpit, Cron Jobs, Git, MkCert, DNS Server, FTP Server, and Static HTTP Server, groupable with projects into reusable startup workflows.

Who uses it and how

• Laravel teams running PHP, MySQL or PostgreSQL, Redis, Node.js, and Nginx with HTTPS on one workstation.
• Python and Django developers assembling Python, PostgreSQL, Redis, and Nginx without writing a compose file.
• ERPNext operators combining Python, MariaDB, Redis, and Nginx, and Gitea operators running Gitea with MySQL, Nginx, and HTTPS.
• AI-assisted developers who register the built-in MCP server so supported clients can inspect selected services, sites, configs, logs, versions, and lifecycle actions.
• Cross-platform teams that want the same environment on Windows, macOS, and Linux machines.

Getting started

Getting started means downloading the FlyEnv desktop application from flyenv.com, where the README also points to demos and a quick start guide. The README names no package manager command, Docker image, or compose file — installation is the hosted desktop download.

How it compares

FlyEnv sits where XAMPP, MAMP, Laragon, and Laravel Herd sit, but covers a broader stack, and the README is explicit that Docker and FlyEnv solve overlapping rather than identical problems. Its guidance is to use Docker when containerized reproducibility or production parity is the goal, and to use FlyEnv when the goal is a native local workspace with less setup overhead.

When to use it — and when not to

A self-hoster runs everything natively on the host, so the runtimes, databases, web server, Redis or RabbitMQ, MinIO or RustFS storage, Mailpit, DNS, and FTP components are that person's to install, update, and troubleshoot, with no container boundary to contain a misconfiguration. Teams needing reproducible parity with production, or working in environments built around containers, should stay on Docker rather than adopt FlyEnv. The project is actively maintained with 37 open issues and a stated BSD-3-Clause licence, but the README excerpt here is thin on command-level install detail, so expect to follow the website's quick start rather than a documented CLI flow.

brew install flyenv

git clone [email protected]:xpf0000/FlyEnv.git
cd FlyEnv
yarn install
yarn run dev