Yerd review: a rootless local PHP environment in Rust for macOS and Linux
A powerful, developer-friendly tool for local PHP development
At a glance
- What is it?
- Yerd bundles a Rust daemon, a CLI and a tray GUI into one desktop app that serves .test sites with per-site PHP versions, native databases and a local CA. Here is what the repository and README actually promise, and where the design forces a trade-off.
- Who is it for?
- Adopt Yerd if you develop PHP or Laravel on macOS or Linux and want .test domains, per-site PHP versions and native MySQL, MariaDB, PostgreSQL or Redis without containers, and you accept a one-time privileged setup step. Do not adopt it if you are on Windows, since the README lists Windows as planned but not supported, or if you need a stack that is fully unprivileged from first launch.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 16, 2026, and from our analysis. They are not legal advice.
Star history
- forjedio/yerd549 ★ · +44
| Repository | 2026-09-21 | 2026-11-16 |
|---|---|---|
| forjedio/yerd | 505 | 549 |
44 Stars in the last 56 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What Yerd is for, and who should care
Yerd targets the everyday friction of running PHP projects locally: mapping hostnames, trusting certificates, switching interpreters and keeping databases alive. The README frames it as "Local PHP, without the friction" and describes a single desktop app for macOS and Linux that contains the daemon, the yerd CLI and a privileged one-shot helper, with nothing downloaded at runtime. The intended user is a PHP or Laravel developer working on a laptop or workstation who wants sites reachable at <name>.test without maintaining Docker images, a VM or a Homebrew stack. The pitch is narrow on purpose: it is not a deployment tool, not a CI runner and not a general container runtime. It solves the local loop only, and it solves it for two operating systems. Windows is listed in the comparison table with a footnote that it is planned, which means the project is honest about the gap rather than pretending parity.
The Rust workspace behind the daemon
The Cargo workspace in the repository makes the architecture legible. Members include crates/yerd-core, crates/yerd-ipc, crates/yerd-config, crates/yerd-tls, crates/yerd-platform, crates/yerd-dns, crates/yerd-supervise, crates/yerd-php, crates/yerd-services, crates/yerd-tunnel, crates/yerd-proxy, crates/yerd-doctor, crates/yerd-mail, crates/yerd-mcp, crates/yerd-update and crates/yerd-release-manifest, plus the three binaries in bin/yerd-helper, bin/yerdd and bin/yerd, and the Tauri app under apps/yerd-gui/src-tauri. Read that list as a map of responsibilities: DNS resolution, TLS certificate handling, a proxy, process supervision, PHP version management, service management for databases and caches, tunneling, mail capture and diagnostics each live in their own crate. The workspace pins rust-version = 1.77 and edition = 2021, and the version field is 2.1.0-rc.1, matching the most recent release tag. The README states the daemon is roughly 8 MB and that the GUI is a thin client over it, with every button mapping to the same daemon the CLI drives. That is the central design decision: one control plane, two front ends. It also explains why the CLI can be trusted to reflect GUI state, and why a bug in the daemon surfaces in both places at once.
Installing Yerd and serving a first site
Yerd ships as a single desktop app, so installation is a package step rather than a build step. The README points to the releases page and lists the artifacts per platform. On Debian or Ubuntu x86-64 the documented command is:
sudo apt install ./Yerd_Linux_x86_64_v<ver>.debOn Arch the README warns that a leftover /usr/bin/yerd from the old v1 Go project must be removed first, because pacman refuses to install over a file it does not own, and it advises running pacman -Syu beforehand so the WebKit and GTK libraries match. Fedora users install the .rpm with dnf, and macOS users open the .dmg and drag the app to Applications. After the first launch the app starts its bundled daemon, then walks through a one-time setup step that raises privileges. From the terminal that same step is:
sudo yerd elevate # trust the CA · route *.test · allow 80/443The comment in that command is the README's own. It trusts the local CA, routes *.test and binds ports 80 and 443. Everything after that runs as your user. On Linux the .deb and .pkg.tar.zst put yerd on your PATH; on macOS you open Settings, then Terminal CLI, then Install. The quick start is GUI-first: install a PHP version, then drop a project into a parked folder and it is live at <name>.test with the framework web root auto-detected. If the machine cannot route .test, the README gives a fallback URL shape, http://localhost:8080/~<name>.test, which is worth knowing before you conclude DNS setup failed.
Where the rootless model breaks down
The word rootless needs qualification. The README says setup raises privileges once to trust the local CA, route *.test and bind ports 80 and 443, and that daily use never does. So the first run is privileged, and anyone who cannot run sudo on the machine, or who works inside a locked-down corporate image, hits a wall at that step. The fallback URL on port 8080 mitigates the routing problem but the README does not say it removes the need for the CA trust step, and it does not document a fully unprivileged install path. A second limitation is platform scope. macOS and Linux only, with Windows marked as planned. A third is that the README does not document rollback or uninstall, so the state the setup step writes (a trusted CA, DNS routing, port bindings) has no described reversal procedure. Treat that as an operational gap to resolve before installing on a shared or managed machine. Finally, the newest release is a release candidate, v2.1.0-rc.1, so teams that avoid RCs should look at the v2.0.4 stable line instead.
How Yerd differs from Lerd and Laravel Herd
The README's comparison table is the clearest statement of positioning. Laravel Herd is free with a paid Pro tier, closed source, macOS and Windows, and uses nginx plus dnsmasq under the hood. Lerd is open source, supports Linux and macOS, and runs the stack in containers through rootless Podman, which the README notes makes database and cache services easy to add but means pulling and running container images. Yerd is open source under MIT, macOS and Linux, and uses a native Rust rustls proxy with embedded DNS. The practical difference is what runs on your machine: containers and images with Lerd, native processes with Yerd. That choice buys startup characteristics and a smaller disk footprint, and it costs the isolation a container boundary gives you. If you already depend on container images to pin exact service builds, Lerd's model matches that expectation more directly. The README also notes that Yerd reuses none of Valet's framework drivers and requires no Homebrew, which matters if your current setup is Valet-based and you want to know what you are replacing.
Maintenance, licence and upgrade cost
The repository is not archived, and the last push was on 2026-08-19, so the project is being worked on rather than frozen. The release cadence visible in the repository is tight: v2.0.4-rc.3 and v2.0.4 both landed on 2026-07-25, and v2.1.0-rc.1 followed on 2026-08-15. That pattern, a stable release followed by a new RC line, suggests the project uses release candidates as a gate before promoting a version, which is a reasonable thing to see in a tool that writes a trusted CA and binds privileged ports. The upgrade cost is not documented in the README; there is a crates/yerd-update member in the workspace and a crates/yerd-release-manifest member, and the Cargo workspace depends on minisign-verify and minisign, which implies signed release artifacts and an in-app update path, but the README does not spell out the upgrade procedure or whether an upgrade re-runs the privilege step. The licence is MIT, declared in Cargo.toml and in LICENSE.md, which permits commercial and closed-source use with the usual attribution and warranty terms. That is a summary of the licence identifier, not legal advice; read LICENSE.md before relying on it.
Editorial conclusion
Adopt Yerd if you develop PHP or Laravel on macOS or Linux and want .test domains, per-site PHP versions and native MySQL, MariaDB, PostgreSQL or Redis without containers, and you accept a one-time privileged setup step. Do not adopt it if you are on Windows, since the README lists Windows as planned but not supported, or if you need a stack that is fully unprivileged from first launch. Before committing, verify which PHP versions the app offers, confirm the Cloudflare Tunnel sharing path against your own network policy, and check whether the v2.1.0-rc.1 release candidate or the stable v2.0.4 line is the right starting point for your team.
Frequently asked questions
Does Yerd require sudo to run?
Setup runs sudo yerd elevate once, to trust the local CA, route *.test and bind ports 80 and 443. After that, the README states daily use runs as your user and never as root.
Which platforms does Yerd support?
macOS and Linux, with packages for Debian/Ubuntu, Arch and Fedora plus a macOS .dmg. Windows is listed in the comparison table as planned, so it is not supported today.
Does Yerd need Docker?
No. The README states Yerd requires no Docker, Podman or containers, and runs MySQL, MariaDB, PostgreSQL and Redis as native services under a single daemon of roughly 8 MB.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/forjedio-yerd)Star history chart for your README
[](https://hysenlabs.com/projects/forjedio-yerd)Was this useful?