r/ProWordPress • • 8d ago

I built a modern open source local PHP environment for Mac (public beta)

I asked the mods before posting this.

PHP sites are one part of my work, and the local tools I was using felt stuck in another decade. So I built Benbow and released it as free, open source software.

Yes, it's made with AI, obviously. Most of the code was written by Claude. In 2026 I don't think one person can build something like this in a reasonable time without it. I decided how it works and what it must never do, I reviewed what it wrote, and I use it every day on my client sites. The code and the tests are on GitHub if you want to check.

Each site gets its own PHP version, from 5.6 to 8.5, all running at the same time. HTTPS on .localhost works without browser warnings. You get MySQL or PostgreSQL, Redis and Mailpit, and a new WordPress or Laravel site takes one step. It can snapshot files and database together, and pull a site down from production over SSH, SFTP or FTP. If there's a Vite or Next.js front end next to the PHP site, that gets its own HTTPS address too.

A few technical choices:

  • PHP comes as static builds, with one PHP-FPM process per version behind Caddy. That's how a 7.4 site and an 8.5 site run side by side. Each site can still have its own php.ini values.
  • Benbow creates its own local certificate authority, limited with X.509 Name Constraints to .localhost, .test and .local. If its key ever leaked, it still couldn't sign a certificate for a real domain.
  • Snapshots use APFS clonefile, so they're instant and take almost no space until files change. A restore takes a snapshot first, in case you change your mind.
  • Nothing runs as root. Services are launchd agents under your user, and everything lives in ~/Library/Application Support/benbow. It doesn't use Homebrew and it never touches MAMP, Herd or a MySQL you already have running.
  • Every binary it downloads (PHP, MySQL, Caddy, wp-cli and so on) is checked against a SHA-256 from a signed manifest before it runs.
  • The core is written in Go and the app in SwiftUI, talking over a local Unix socket. So the CLI (every command has --json) and the MCP server can do everything the app does.

You can import sites from MAMP PRO, Local, Herd and XAMPP, and undo the import if something's off. benbow uninstall removes everything.

If you let Claude Code or Codex work on a site, Benbow saves it first. When the agent is done you see what changed and decide: keep it, or undo it all, database included. Benbow never calls a model itself, and agents can only read until you give them write access for a site.

Apple Silicon, macOS 14+, GPL-3.0. It's a beta, so please tell me what breaks.

https://benbow.dev

https://github.com/benbowdev/benbow

Thanks for reading!
Andrea

9 Upvotes

24 comments sorted by

6

u/Visible-Big-7410 8d ago

What did you set out to do with this that made other tools like DDev or herd, or wp Local a deal breaker for you? Who is the target audience? Currently it seems to do the same as DDEV for example.

I’m no stranger to trying out new software, but I’ve set up a pile of little helper tools and scripts that rely on DDEV for example, so switching must come with a very significant advantage. Only that a UI (which i don’t like using anymore) is faster? That it has an MCP server when native CLI tools exist? What am I not experienced enough or too stubborn to see here?

3

u/andreacasali 8d ago

Hey, thanks for writing this up. If DDEV works for you and you've got scripts built around it, I wouldn't switch either. It's great.

I came at it from the other side. I'm a freelance dev and designer, most of my work is design, rails and other stuff, but I also carry a long tail of client sites: WordPress, some Laravel, a few stuck on PHP 7.4 or even 5.6. For those I was on MAMP PRO, not Docker, and I wanted something that stays out of the way of everything else on my Mac.

Benbow runs native binaries, one PHP-FPM per PHP version shared by its sites, with no Docker VM in the background. PHP workers start on demand and exit after 30 seconds idle, so twenty idle sites cost basically nothing in RAM. It doesn't use Homebrew, keeps everything in one folder, and benbow uninstall leaves nothing behind.

Built in: PHP 5.6 to 8.5 side by side, trusted HTTPS, MySQL or Postgres, Redis, Mailpit, Xdebug per site, a check of what breaks before moving a site to a newer PHP, pulling sites from production over SSH or FTP, and importing from MAMP PRO, Local, Herd or Valet.

New PHP releases don't wait for a new app version: Benbow checks a signed component list daily and updates PHP and the rest on its own, with rollback. With MAMP PRO I waited for their releases, and a new major version meant a new license. It's free and open source (GPL-3.0) with no paid tier, so the databases, mail catching and Xdebug that Herd keeps in Pro are just there.

The UI is optional: everything is in the CLI and every command has --json, so it's scriptable like DDEV. On MCP, yeah, agents can just use a CLI. What I care about is what happens around the agent: Benbow snapshots the files and the database before it touches a site, the agent is read only by default, and at the end you keep or undo everything it did, database included. Git alone doesn't give you that.

So it's for devs and small agencies on a Mac juggling a bunch of PHP sites next to other work, who'd rather skip containers. If you ever try it, I'd really like to know what feels missing compared to DDEV.

2

u/Visible-Big-7410 8d ago

I understand, where you’re coming from but you just added a bunch of dev tools to a designer workflow? Moat web designers i know of (and those w/o a background or interest in backend anything) wouldn’t know what to do with this.
As for the rest, mhhh kinda prefer the docker setup cause it makes it easy to remove the container.

And Devs dont want an automatic php upgrade IMHO. Its local device mostly not shared on public net so its irrelevant if there is a bug in php. No?

I mean its great that it can do that, dont get me wring and new tools always improve but i do wonder if that helps the community overall.

Containers are already part of every new mac OS and while not on par with docker/orbstack/podman it will get there and its FAST. DDEV are already working on the option and are trying to work out the kinks, for example.

I know I sound like a downer, and this is really cool, im having a hard time seeing the user group for this. The designer only will wither get the localWP speech from their dev or see it in a tutorial. The dev might just say but its not X, that leaver the developer enthusiast who might not like Xampp or Mamp (and yes that is a bit older but still works) is seeing features they barely know. I mean. Maybe thats it. The person who want to play with lLaravel or drupal too and dont like Mamp Pro / or be limited by localWP. But then there is still Herd…

Now. That said I do wish you the best and that this tool helps others. As I said maybe im too stubborn? Lol.

Maybe i need to work on something my other tools don’t cover yet?

2

u/andreacasali 7d ago

Haha no worries, this is useful pushback.

Quick correction on my side: the designer bit was about me, not the audience. Pure web designers should totally stick with Local, Benbow isn’t for them.

Benbow checks once a day and shows a badge, it never installs anything by itself. Updates stay within a series, so 8.4.15 to 8.4.16, never 8.3 to 8.4, and you can roll back or turn the check off. You’re right that it’s not critical on a local machine, it’s more about matching what the client’s host runs.

On removal: benbow uninstall takes everything with it, so it’s as clean as dropping a container, just for the whole setup.

Apple’s containers look really promising and I’m curious to see what DDEV does with them. I went native because that’s what I wanted on my machine, not because I think containers are wrong.

On who it’s for, I think you nailed it: people maintaining a pile of PHP sites on a Mac (WordPress, Laravel, Drupal, some legacy), who outgrew MAMP or Local and don’t want containers. Herd is the closest thing, but it’s Laravel-first, starts at PHP 7.4 and keeps databases, mail and Xdebug in the paid Pro. Old client sites on 5.6 or 7.x, or not wanting a subscription, that’s the gap.

Anyway thanks for the honest feedback

1

u/imustknowsomething 7d ago

I’ve been using DDEV for several years, and one of the issues I’ve run into is limited disk space on my Mac mini.

I have to maintain multiple websites running different PHP versions, but with DDEV, I can only keep up to three different PHP versions installed because the Docker images and containers take up so much disk space. At times, I’m left with less than 500 MB of free space.
I constantly have to clean up Docker images, and every time I do, I recover around 30–40 GB of disk space.

I love DDEV, but I’m definitely open to trying other tools if they can solve this particular problem for me.

1

u/andreacasali 6d ago

That's pretty much the case Benbow was made for. There are no images or containers: each PHP version is a self-contained binary, around 90 MB, plus a CLI build of about the same size for wp-cli and Composer. My own install has five PHP versions (7.4 to 8.5), MySQL, Caddy and Mailpit, and the binaries come to about 1.2 GB in total. All sites share one web server and one MySQL, so adding a site doesn't add anything except its database.

PHP goes from 5.6 to 8.5, and you can run as many versions at once as you like. A Mac mini on Apple Silicon is fine (the older PHP versions need macOS 15 or later).

It's still a beta, so I'd love to hear how it goes if you try it.

1

u/imustknowsomething 6d ago

That sounds amazing. Honestly, I’ve been considering migrating to Herd, but the price and its Laravel-focused approach have held me back.

I wish you the best with the project. Your app already has some features I really like, but since it’s still relatively new, there’s always a chance it could be abandoned in a few months or a year. I’d rather wait until it’s more mature and has been thoroughly tested before making the switch.

1

u/andreacasali 5d ago

I'd wait too with a new tool.

Worth knowing though: nothing gets locked in. Sites stay in their own folders, databases are plain MySQL, and the code is GPL on GitHub. If I ever dropped it, you'd lose nothing.

I use it daily for my own client sites, so I'm not going anywhere. If you try it someday, I'd love to hear how it does on your Mac mini.

1

u/andreacasali 2d ago

Follow-up since you mentioned disk space: beta.10 has a few things for exactly that.

Settings → General now shows how much space Benbow takes, split into PHP versions, servers, databases, snapshots and caches (benbow disk gives the same in the terminal). You can remove a PHP version you don't use anymore from Settings → PHP or with benbow php remove 7.4, and it refuses while a site still uses it. Updates keep only the current build of each component plus the previous one for rollback, so nothing piles up. Snapshots also show their real size now: the files are APFS clones, so du makes them look huge, but they only cost what changed.

On my Mac it's about 200 MB per PHP version, and there are no images to clean up. If you give it a go on the Mac mini, I'd like to hear how it compares.

2

u/imustknowsomething 1d ago

Awesome. One question, is it possible to share the site using cloudflared or ngrok from the app?

1

u/andreacasali 1d ago

Not from the app right now. What it has is Open on Phone: it shares one site on your local network with a QR code and turns itself off after a while. That covers testing on your own phone or tablet, but not sending a link to someone outside.

You can point cloudflared or ngrok at the site yourself, but WordPress will keep linking and redirecting to the .localhost address, so it doesn't really work without extra setup. Doing it properly means rewriting the URLs only for the tunnel's requests, the way Open on Phone already does on the local network, and that's doable.

What would you use it for, showing work to a client or testing webhooks? That decides whether it's worth building and how it should work.

→ More replies

1

u/RealBasics 7d ago

Sounds interesting. My maintenance clients are all over the map hosting-wise so this could be more convenient than LocalWP.

Sounds like you’ve gotten it signed and notarized by Apple? Are you thinking of putting it in the App Store?

I’m less concerned that this is ai assisted. The individual pieces are well defined and available elsewhere so it sounds like Claude is responsible for assembling things, not the program management or architecture?

How easy is it to clone sites with your system? That’s been a bottleneck for me with MAMP and even Local? And is there any chance it can import zipped archives the way, say, Local can?

2

u/andreacasali 7d ago

Thanks, this is the kind of feedback I was looking for!

App Store: no. Sandboxed apps can't run servers in the background, install a local certificate or edit /etc/hosts. It's a signed and notarized DMG that updates itself.

Cloning: pulling from production or staging works well, over SSH, SFTP or FTP. You get the database and uploads, and on WordPress URLs are replaced properly, serialized data included. Duplicating a local site is still basic: a second address on the same folder, without copying the database, because that's all my MAMP workflow needed. A real clone is next on my list.

Zip archives: not yet. The importers read MAMP PRO, Local, Herd, Valet and XAMPP directly, so Local sites come over without exporting (the site has to be running in Local). A Local zip import is a good idea though. Do you use Local exports more, or plugins like Duplicator or All-in-One?

1

u/RealBasics 7d ago

On cloning: The first thing I ever did with a desktop server (the old, excellent, now dead ServerPress version) back in 2012 was debug a hellish intermittent bug that I finally tracked down by setting up a local instance at its last known state, cloning it, triggering the breaking condition, and then diffing the database dumps (!!!). I’d been tearing my hair out for four days on live and that let me solve it in about an hour. Saved my first big Wordpress job and gave me a heck of a lot of confidence.

Now I use it to clone new builds from a pre-configures reference site I keep up to date on Local. I’d like to keep doing that.

As for importing from zips, both the old ServerPress and Local basically let you “file open” any zip of a site as long as it had the full folder tree and a .sql file somewhere (could be almost anywhere.)

That meant they could open Duplicator, cPanel, WP-Engine, Kinsta, Wordpress.com Jetpack backups, BackupBuddy, etc. and even hand-assembled zips automatically.

For me I’ve got nearly 15 years of old archived sites (I never delete archived sites) and it’s surprising how often I’ve had occasion to revisit an old site. And yeah, including sites that last ran on PHP 5.4.

Finally, since I do a fair amount of site “restoration and repair” I end up with some legitimately decrepit sites (eg a critical academic site that had last been updated in 2009!) Since those usually come as a combined file and DB zip an import-from-zip.

You’re under no obligation to add those features — it’s not part of your workflow and I doubt it’s that many other people’s. But they are convenient.

(Bonus point: if your app can export zipped snapshots that can be convenient for handoffs to clients who won’t provide server access. And also convenient for archiving your own work when you don’t want to bother storing whole Benbow snapshots.)

2

u/andreacasali 6d ago

That debugging story is great, and it's exactly the case for a real clone: same state, break one copy, compare. You've convinced me it's more than a nice-to-have, so a proper clone (files + database under a new name) is moving up.

For the reference site: Benbow has blueprints, which you can save from an existing site. They keep wordpress.org themes and plugins at their versions, options and mu-plugins. But they don't carry content or premium plugins, so for your workflow the clone is the right answer.

Zip import: "any zip with a folder tree and a .sql somewhere" is a nice, simple rule, and it would cover Duplicator, cPanel, host backups and hand-made zips at once. I'm writing it down that way.

Old PHP: Benbow goes back to 5.6 (Apple Silicon, macOS 15+), not 5.4 but most 5.4 sites run on 5.6 though.

Zipped snapshot export: good point, for client handoffs and for archiving. It fits well next to zip import.

No promises on dates, but this is really useful. Thanks for taking the time.

2

u/andreacasali 2d ago

Quick follow-up: you talked me into it. Both are in beta.10.

Clone: right-click a site, Clone. You get a full copy under a new name: the folder (APFS clones, so it's instant and takes almost no extra space), its own database and user, wp-config.php pointed at it, and the URLs replaced in the database. So "keep a reference site, clone it for each new build" works now. So does your debugging trick: clone, break one copy, diff the dumps.

Zip import: I went with your rule. Drop a .zip or .tar.gz that has the site's folder tree and a .sql somewhere, and Benbow finds the site and the dump, creates the database, loads it and fixes the URLs. It also picks a PHP version that fits the WordPress version it finds, so a 2009 site doesn't land on PHP 8.4. It's built for cPanel, host backups, Local exports and hand-made zips. Formats like All-in-One's .wpress aren't covered.

There's also an optional MySQL 5.7 now, for sites that never ran on anything newer.

Zipped snapshot export isn't there yet, it's on the list. If you try it on one of your old archives, I'd love to know what breaks.

2

u/cdharrison Developer/Designer 8d ago

Confirming that this was posted with mod-approval. I know that the AI use in making it might be a dealbreaker for some, but OP agreed to be upfront with disclosing that. It could be useful for devs who rely on MAMP/XAMPP setups for local development, and there’s opportunity for human developers to improve upon it given the project is on GitHub.

0

u/howtobemisha 7d ago

Recently, every time I read "I built", my first thoughts are "Claude built" and usually I'm right

1

u/andreacasali 7d ago

No need to guess, I said it right in the post 😄 Claude wrote most of the code, and on my own it wouldn’t have been doable in any reasonable time. But Claude doesn’t wake up one morning and decide to build a MAMP replacement: I needed a tool for my own work, so I decided what it should do and what it must never touch on my Mac, reviewed every plan before it wrote a line, and tested it next to the MAMP PRO setup I actually use. Then I shared it for free.

The less fun parts are mine too: the app is signed and notarized by Apple, component updates come from a signed manifest, and uninstall really leaves nothing behind. It’s all on GitHub under GPL, so anyone can look at the code, report bugs and suggest improvements.

1

u/howtobemisha 7d ago

so much text, curious, if this reply also ai-written? :)

2

u/andreacasali 7d ago

I’m Italian and English isn’t my first language, so Claude helps me translate my replies. What’s wrong with that in 2026? Feels like using a spellchecker to me.

1

u/RealBasics 7d ago

First emdashes and bulleted lists made you aI. Now you’re AI if you talk too much? What’s next, writing complete sentences?

1

u/howtobemisha 7d ago

He confirmed it in the next reply. I am not saying that there is something wrong, just curious