A 3-second deployment tool for the small infrastructure tasks that happen all day.
When a favorite Forge companion app moved toward a pricier plan and I needed a few more features, I built Anvil: a NativePHP menu-bar app that puts deployments, servers, logs, environment files, and common recovery actions where I already work.
Role
Creator and desktop app developer
Context
Personal Laravel Forge deployment workflow
Disclosure
Personal project
The problem
The problem
The small infrastructure actions that interrupt a development day add up: find the right Forge site, wait for the web UI, open a terminal, remember the server, then do one thing. A tool called F-Bar had shown how useful a nearby control surface could be. When it no longer fit my feature needs or budget, I made a version designed around my own deployment routine.
The interaction model
The menu is the product.
Environment → server → site → action. The real app reduces a deployment chore to the one path that matters, without surfacing private infrastructure names here.
Studio ›
Personal ›
Client sites ›
Settings…
Quit Anvil
Engineering ›
Product ›
Operations ›
Production app ›
Queue workers ›
Web application ›
Cache ›
Analytics ›
Refresh servers
Deploy
View logs in editor ›
View/Edit .env
Open server terminal
Restart services
What I built
The system, not just the screen.
A deployment control surface in the menu bar
Built a native macOS menu-bar experience around the Forge sites and servers I touch most. Favorited sites make the useful targets available immediately, rather than requiring a browser tab, a search, and a series of clicks.
The actions that remove the most friction
Wrapped the Laravel Forge API for deployments, SSH access, logs, environment-file viewing and editing, service restarts, and server status. A task that used to take 30 seconds to a minute becomes a two- or three-second action.
A NativePHP proving ground that became a daily tool
Used the project to test NativePHP with tools and patterns I already know from Laravel. The goal was never a general DevOps platform; it was a purpose-built personal app, and it became good enough to keep using every day.
System sketch
How the system works.
A simplified view of the system boundary and the work it moves through.
Forge API
Local app state
Favorited site
Menu-bar action
Deploy, SSH, or recovery
Key decisions
Key decisions
Use the menu bar for glanceable, frequent actions instead of recreating the full Forge web dashboard on the desktop.
Optimize for the repeated little tasks where a few saved clicks and seconds become meaningful over a workday.
Keep it opinionated and personal rather than expanding it into a multi-user infrastructure product.
What it enables
What it enables
Anvil turns scattered infrastructure chores into tiny interruptions: find a favorite site, take the action, and return to the work. It is probably a tool of one, which is exactly why it has the right shape for me.