xpf0000

FlyEnv: Manage Native Local Development Stacks

FlyEnv is a cross-platform desktop app for running and managing local development runtimes, databases, web servers, and project sites. It suits developers who want a native alternative to containers for everyday local work, with project-level runtime switching and optional AI and MCP workflows.

TypeScriptBSD-3-ClauseDeveloper ToolsDesktop AppCross Platform
View on GitHub Compare
Stars
3.3k
Forks
378
Stars, last 7 days
+16

Our take

Health score

62/100

How it is scored
Activity
82
Community
48
Issues
68
Pull requests
49

+16 stars in the last 7 days

  • Releases more often than 80% of the projects we track
  • Merges more pull requests than 77% of the projects we track

Overview

FlyEnv brings local development services into one desktop workspace for Windows, macOS, and Linux. It helps developers install and manage runtimes, databases, web servers, and project sites without requiring container setup for everyday local development.

It is most useful when you want to assemble and switch between local project stacks from a graphical app. It also includes local domains, HTTPS, and integrations for AI coding tools and its MCP Server. It is not a substitute for containers when containerized reproducibility or production parity is needed.

Key Features

  • Manage language runtimes including PHP, Node.js, Python, Java, and Go.
  • Run and manage databases and services such as MySQL, PostgreSQL, Redis, MongoDB, and RabbitMQ.
  • Configure web servers, local sites, domains, HTTPS certificates, and reverse proxies.
  • Switch runtime versions by project and define project start and stop workflows.
  • Group projects and services into reusable startup workflows.
  • Manage supported AI coding clients and expose selected local environment capabilities through the FlyEnv MCP Server.
  • Available for Windows, macOS, and Linux.

Use Cases

  • A web developer wants a local PHP or Node.js stack with a database and web server, without setting up containers for routine work.
  • A developer maintaining projects with different runtime versions needs to switch environments on a per-project basis.
  • A team member wants local test sites with custom domains and HTTPS before deploying.
  • A developer using supported AI coding tools wants selected local services, configurations, or logs accessible through FlyEnv's MCP Server.

Getting Started

On macOS, install with Homebrew:

brew install flyenv

For other installation options and setup guidance, see the README and Quick Start guide.

Considerations

  • FlyEnv runs services natively, so its workflow differs from container-based environments. Use containers when you need containerized reproducibility or production parity.
  • The project supports Windows, macOS, and Linux, but installation packages and setup steps vary by platform.
  • The breadth of managed services does not mean every project requires or benefits from using FlyEnv. Choose only the components needed for your local workflow.

Found this useful?

Share it with someone who would like FlyEnv.