lerd-env/lerd: Open-source, Herd-like local PHP development environment for Linux and macOS. Automatic .test domains, per-project PHP/Node isolation, one-command TLS. Podman-native, rootless. · GitHub

Open-source Herd-like local PHP development environment for Linux and macOS,
with Windows supported via WSL2 (beta). Podman-native, rootless, with a
built-in Web UI.

Lerd runs Nginx, PHP-FPM, and your services as rootless Podman containers,
designed for PHP developers on Linux and macOS, and on Windows through WSL2 (beta).
No Docker. No sudo. No system pollution. Just lerd link and your project
is live at project.test with HTTPS.

Lerd is built for PHP developers on Linux who want frictionless local development: automatic .test domains, per-project PHP versions, one-click HTTPS, zero Docker. Works with Laravel, Symfony, WordPress, Drupal, Magento, CakePHP, Statamic, and any custom PHP framework.

• 🌐 Automatic .test domains. One command gives a project a hostname and TLS that reissues before it expires, with no dnsmasq, no system resolver tweak and no sudo for the DNS bits. You can opt out of lerd-managed DNS for *.localhost, or toggle it later with dns:enable / dns:disable / dns:repair.

• 🔗 Site groups. Group related sites so a main site owns a base domain and the rest occupy its subdomains, with a shared or separate database per secondary.

• 🧱 Host-proxy sites. Run a Node, Python, Go or any non-PHP dev server on the host and have nginx serve it at a .test domain with HTTPS, git worktrees included. A wedged dev server can be bounced from the site header without reaching for a terminal.

• 🌳 First-class git worktrees. Auto-detected branch domains, per-worktree PHP and Node versions, optional database isolation, wildcard cert SANs for *.branch.site.test, and a per-branch Vite worker on the host. Add and remove them from a dashboard modal without touching the CLI.

• 🌍 Share a site. On your LAN with a stable port and a QR code, or publicly through ngrok, cloudflared, Expose, serveo or localhost.run, from the CLI or the dashboard’s share menu. Set a Cloudflare base domain once and every share is served on ., so a webhook or OAuth callback keeps its URL between runs, and ngrok runs from its published image on a machine that never installed it.

• 🎨 Dev servers on the site’s own domain. A running Vite serves its assets and its hot-reload socket under the site’s .test hostname instead of advertising localhost:5173, so a shared, LAN-opened or worktree page arrives styled. Nothing in the project is edited and nothing is declared per framework.

• 🐘 Per-project PHP version. 8.1 to 8.5, plus a frozen 7.4 / 8.0 legacy tier for projects hosted on the old stack, switched with one click. Custom PHP extensions and Alpine packages are declared once and applied to every image lerd builds, so changing a site’s version never silently drops what you asked for.

• ⚡ FrankenPHP runtime. Per site, as an alternative to shared PHP-FPM, with Laravel Octane and Symfony Runtime worker mode.

• 📦 Node.js isolation. Node 22 or 24 per project, through the bundled fnm or an nvm you already have, switchable from the dashboard. Or bun as the JS runtime on the host and, opt-in, inside the container.

• 🪄 No per-framework setup. Workers, env values and the nginx vhost are all configured for you when you link a project.

• 🧩 Framework store. Community definitions for Laravel, Symfony, WordPress, Drupal, Magento, CakePHP and Statamic with versioned auto-detection, back to the majors that still run on PHP 7.4.

• 🗄️ One-click services. MySQL, PostgreSQL, Redis, Meilisearch, RustFS, Mailpit, Reverb, OpenSearch and more, the default stack built in and every add-on fetched from a store that updates without a new lerd release. Browse, create and drop an engine’s databases from its service page, with snapshots, export and import.

• 🧷 IDE database wiring for JetBrains. A project gets one data source pointed at its own lerd database on the host port it actually answers on, written on link and refreshed as the project’s database changes, leaving every data source lerd doesn’t own untouched.

• 🛰️ Debug window. Intercepts every dump() / dd() and streams it to the dashboard, TUI, MCP and lerd dump tail, scoped per site and per worktree branch. The same window captures SQL with N+1 and slow-query detection, plus mail, views, events, queued jobs and outgoing HTTP, on Laravel and Symfony.

• 🔥 SPX profiler with one-click on/off. Every PHP-FPM request becomes a flame graph viewable in a same-origin Profiler view in the dashboard, with no FPM restart and no code changes, and lerd profile run profiles a one-shot artisan or CLI command.

• 📈 Request timing analytics. A durable per-site view of typical and p95 response times, throughput, error rate, and the slowest routes ranked by recent p95 with one-click profiling. Agents get the same signal over MCP with route_timing and optimize_route.

• 🧪 Tinker tab. An in-browser PHP REPL per site with project-aware autocomplete, hover and diagnostics powered by phpantom_lsp, so your models and Builder chains resolve alongside composer helpers. Works on Laravel, Symfony, and any composer project.

• 🖥️ Built-in Web UI. Sites and services dashboards, live widgets, a global Cmd+K command palette, and install/remove of PHP and Node versions from the System page. Available in fourteen languages.

• 💻 Terminal dashboard (lerd tui). A btop-style TUI with live status, site detail pane, inline domain and version editing, shell drop-in, log tailing, and filter/sort, the same operations surface as the web UI, for tmux and SSH workflows.

• ✏️ Edit config in the browser. Per-site and global nginx, php.ini with the version’s own file and the shared scope side by side, .env files, and database/service runtime tuning, each validated (nginx -t where it applies), with timestamped backups and one-click restore.

• 📋 Live logs for PHP-FPM, Queue, Schedule and Reverb, per site, rendered in the colour the tool actually emits (artisan, composer, vite, pest) and with a button that hands any log to a real terminal so a long tail survives closing the tab.

• 🔔 Notifications for the things worth interrupting you, delivered to open dashboards, to subscribed browsers over Web Push, or to your desktop’s native notification daemon. Every one also lands in the dashboard’s sidebar bell, which keeps the last 50 with an unread count across reloads.

• 🤖 MCP server. Let AI assistants (Claude Code, Cursor, JetBrains Junie, Codex CLI, Gemini CLI, GitHub Copilot, Google Antigravity, Windsurf) manage your environment directly.

• 🧰 Environment doctor (lerd doctor). Checks the host lerd itself depends on and repairs what it safely can with --fix: missing directories, linger, a missing PHP image, the DNS wiring. Anything needing sudo is printed as a command and never run for you, and --dry-run shows it first.

• 🩺 Site doctor. Health checks that apply to any project (env drift, application key, composer and node install state, security audits, database presence, PHP version range) plus extra checks for your framework, with one-click fixes. From the web UI, the TUI, lerd site:doctor and MCP.

• ⚒️ Worker self-heal. Failed queue, schedule, horizon, reverb and stripe workers are surfaced everywhere (CLI, dashboard banner, TUI, MCP) and recovered with one click or lerd worker heal.

• 💤 Idle-suspend. Activity-driven suspension of a site’s workers (queue, schedule, horizon, reverb, stripe, Vite) after a configurable idle timeout, resumed on the next request, CLI command, MCP call or file save, with per-site pinning.

• 📌 Pinned host tools. Composer, fnm and mkcert are pinned behind a published manifest rather than whatever releases/latest served that day, so an upstream release cannot break a fresh install overnight, and the System page reports each against its pin and applies the update on the card that flagged it.

• 🔒 Rootless and daemonless. Podman-native, no Docker required, dual-stack IPv4 + IPv6.

Lerd ships a built-in Model Context Protocol server. Connect it to Claude Code, Cursor, JetBrains Junie, Codex CLI, Gemini CLI, GitHub Copilot, Google Antigravity, Windsurf, or any MCP-compatible AI assistant and manage your dev environment without leaving the chat.

lerd mcp:enable-global   # register once, works in every project

Then just ask:

You: set up the project I just cloned
AI:  → site(action: "link")
     → exec(action: "composer", args: ["install"])
     → env(action: "setup")        # detects MySQL + Redis, starts them, creates DB, generates APP_KEY
     → framework(action: "setup")  # storage:link + migrate for Laravel, doctrine:migrations:migrate for Symfony
     ✓  myapp → https://myapp.test ready

Twelve grouped tools, each driven by an action: site, service, db, env, runtime, worker, exec, framework, diag, logs, workspace, and worktree. Scaffold projects, run migrations, manage services, toggle workers, tail and search logs, enable Xdebug, manage databases and PHP extensions, park directories, switch runtimes between PHP-FPM and FrankenPHP, and more, all from your AI assistant.

📖 MCP documentation

🟡 DDEV runs on Docker by default and can also use Podman as an alternative runtime; Lerd is built exclusively for rootless Podman.

🧪 Lerd’s Windows support runs inside WSL2 and is currently beta, see the Windows (WSL2) guide. Laragon runs natively on Windows and has no Linux or macOS build, see Laragon for Linux if that is what brought you here.

curl -fsSL https://lerd.sh/install.sh | bash

Update later with:

sudo add-apt-repository ppa:lerd/lerd
sudo apt update
sudo apt install lerd

curl -fsSL https://lerd.sh/install.sh | bash

Update later with:

The installer needs the podman CLI; it will offer to brew install podman if it’s missing.

brew install lerd-env/lerd/lerd
lerd install

NixOS has its own flake, since its declarative model doesn’t fit the one-line installer’s imperative DNS and self-install steps.

nix run github:lerd-env/lerd-nixos -- --help

The lerd-nixos flake packages the binary and ships the configuration.nix blocks the stack needs. See the NixOS guide for the full runbook.

Prefer a dedicated window to a browser tab? Lerd Desktop wraps the dashboard in a native app with native desktop notifications for captured mail, worker failures, and finished operations, no browser needed. Linux, shipped as a Flatpak:

flatpak install --user https://lerd.sh/lerd.flatpakref

Once it’s installed, lerd dashboard opens the app instead of the browser.

cd my-laravel-project
lerd link
# → https://my-laravel-project.test

lerd install already starts everything for you on first run, so you can lerd link immediately. Day-to-day:

lerd start          # boot DNS, nginx, PHP-FPM, services, workers, UI
lerd stop           # stop containers and workers (UI and watcher stay up)
lerd quit           # full shutdown including UI, watcher, and tray
lerd autostart enable   # boot lerd on every login
lerd status         # health snapshot

See Start, Stop & Autostart for the full lifecycle reference.

Install community framework definitions from lerd-env/frameworks:

lerd framework search                   # list all available
lerd framework install symfony          # auto-detects version from composer.lock
lerd framework install drupal@11        # explicit version
lerd framework list --check             # compare local vs store

Frameworks auto-detect when you lerd link a project, and its workers, env values, nginx proxy and setup commands are configured from there.

Services work the same way. Lerd ships the default stack, and every add-on lives in lerd-env/services, so a new service reaches you without updating lerd:

lerd service search                     # browse the store
lerd service preset pgadmin             # install a store-only preset

📖 lerd.sh

Lerd stands on a set of excellent open-source projects it bundles or fetches to power the experience:

• phpantom_lsp – the PHP language server behind tinker autocomplete, diagnostics and semantic highlighting
• Monaco – the editor engine for every in-browser editing surface
• php-spx – the profiler behind the SPX flame graphs
• mkcert – the local CA that backs .test HTTPS
• fnm – the per-project Node version manager
• Composer – fetched on the host for dependency operations
• Starship – the prompt in the container shell drop-in

MIT