Compare / Laravel Valet

Rig vs Laravel Valet

Laravel Valet is a free, minimal PHP environment for macOS that serves your projects on .test domains using nginx and dnsmasq. Rig is a desktop app that starts, watches and restarts every process around those sites. Keep Valet for serving PHP; add Rig when Vite, queues and an AI agent join the project.

Last updated:

The short answer

Keep Valet for *.test. Add Rig for groups, logs, ports, MCP and sharing. Rig is built to sit beside Valet, not instead of it.

Side by side

Where Valet wins, it says so

Swipe sideways to see Rig vs Valet

FeatureRigLaravel Valet
Primary jobRun and watch every processnginx and DNS for PHP sites on .test
PlatformsmacOS 13+, Windows 11 (beta)macOS only
Detect Valet URLs and open the siteRig reads what Valet already parksYesYes
Per-site PHP versionvalet isolateNoYes
Queue, Horizon and schedule sidecarsYesNo
Merged logs, ports and restartsYesNo
MCP for Claude Code, Cursor, CodexYesNo
Minimal footprintValet is a command-line tool with no windowPartialYes
PriceFree on your computerFree and open source

When to choose Laravel Valet

Stay with Valet alone when all you need is PHP sites on pretty URLs. Valet is free and open source, installs through Composer and Homebrew, and runs nginx and dnsmasq in the background so every folder you park becomes a .test site without per-project configuration. It can secure a site with a local TLS certificate, pin a site to a PHP version, and share a site through a tunnel. It uses very little memory and has no window to manage, which is exactly what many Laravel developers want. If your projects are PHP only, you start the occasional queue worker by hand, and you are comfortable in the terminal, Valet is a complete answer and Rig adds an app you may not need. Valet runs on macOS only.

When to choose Rig

Add Rig when a Valet site is only the first of several processes. Rig detects Laravel projects and their Valet URLs, so Open Site goes to the same .test address, and then runs what Valet does not: Vite, queue:work, Horizon, the scheduler, Reverb and any Node service, in one project group with a merged, colour-coded log. Crashed workers restart with backoff, ports are tracked, and storage/logs/laravel.log is tailed into the same view. The local MCP hub lets Claude Code, Cursor or Codex see which artisan processes are healthy and restart one, instead of guessing from a pasted stack trace. If you also work on a Windows PC, Rig runs there too and finds PHP from Herd or Laragon. Rig is free on your computer.

Choose Rig if

  • You already park sites in Valet and juggle artisan and Vite terminals
  • You want Claude Code or Cursor tied to the live project
  • You also run Node services or a Windows PC

Stay with Valet if

  • You only need a parked PHP site and you are happy in the terminal
  • You do not want another desktop app

Running both

Valet keeps
nginx and DNS for *.testPHP versions per siteLocal TLS for parked sites
Rig takes
Vite, queues, Horizon and the schedulerMerged logs, ports and restartsMCP and Live Links

Rig reads the sites Valet parks. Neither tool needs to be reconfigured for the other.

Questions

Do I still need Valet if I use Rig?

Usually yes for parked .test PHP sites. Rig detects and opens those URLs, but it does not run nginx or DNS and does not manage PHP versions.

Does Rig work with Valet on Windows?

Valet is macOS only. On Windows, Rig finds PHP from Laravel Herd, Laragon, scoop or XAMPP, and Herd or Laragon serve the .test sites.

Can Rig run Horizon and queue workers next to a Valet site?

Yes. Rig runs artisan sidecars such as queue:work, Horizon, the scheduler and Reverb as named processes, with merged logs and restarts after a crash.

Sources

Facts about Laravel Valet were checked against these public pages on 4 November 2026. Prices and features change, so check their site before you decide.

Keep Valet. Add Rig.

Free forever on your computer. Open Site still goes to your *.test URL.

Download

Works with

Available for any MCP client — including