Statamic Sherpa: The Piece That Was Missing for WordPress Builders

In the Statamic community many of us have had a version of the same conversation for years now. Someone who builds WordPress sites for a living, and builds them well, asks what else is out there. We tell them about Statamic. They like what they hear. Flat file, so there is no database sitting there waiting to be injected. No plugin update roulette every Tuesday morning. A control panel without a giant left sidebar admin menu with over 45 links in some undefined random order. Then they go to try it, hit a docs page that opens with composer create-project, and that is where the experiment ends.

That is not a knock on them. WordPress won an enormous amount of ground on installation alone. You click a button in a hundred different hosting services and you have a site. Every serious alternative asked you to install PHP, install Composer, understand what a local development environment is, and get comfortable in a terminal before you saw a single screen of the product. For a designer or an implementer or a marketing person who knows content modeling cold but has never run a command line tool, that is not a small ask. It is the whole reason they never left.

On Monday the Statamic team released the first public alpha of Sherpa, a free native Mac app that creates, previews, and deploys Statamic sites without opening a terminal. By Tuesday it was on version 0.3.1. That tells you something about how seriously they are treating it.

What it actually does

You download a signed DMG, drag it to Applications, and open it. Sherpa bundles its own PHP and Composer, so there is nothing to install first. If you already run Laravel Herd, it detects that and uses your existing setup instead.

From there you pick a starter kit or start blank, and Sherpa scaffolds the project. Your site runs locally over HTTPS at a real address like alpine-outfitters.test, with no server configuration on your part. The Control Panel opens from the app. Addons install from the Statamic Marketplace with a click, which means Composer is doing the work in the background and you never see it.

Git is built in. You commit and push to GitHub, GitLab, or Bitbucket from inside the app. Deployment is a single click, with dynamic sites going to Laravel Cloud and static builds shipping to Netlify or Cloudflare Pages. The static generator output is fast: the marketing site shows a 214 page build finishing in a little over three seconds.

Two details I appreciate as someone who has cleaned up after other people's mistakes. API tokens and deploy keys live in the macOS Keychain rather than getting written into your project, so they cannot accidentally end up committed to a public repo. And as of 0.3.1, local and Laravel Cloud environment variables are edited separately, so a development value like APP_DEBUG cannot ride along to production.

It also works with Statamic sites you already have. Point it at a folder, and it detects the version, installs dependencies, and starts serving. Version 0.2.0 added bulk import, so you can scan ~/Herd or ~/Sites and pull in everything at once.

Why this is important for the WordPress side of the room

There is a large group of people who build websites professionally and are not developers in the way that word usually gets used. They understand information architecture. They know how to structure a content type. They have opinions about editorial workflow that are better than most engineers' opinions about editorial workflow. What they do not do is run build tools.

For that group, the argument against WordPress has been available for years and has not been actionable. You can explain that the plugin model creates a security surface you do not control, that every third party plugin is a dependency with its own update schedule and its own maintainer who may or may not still be around, and that the reason WordPress sites get compromised is almost never WordPress core. All true. All useless if the alternative requires a skill set the person does not have and does not want.

Sherpa closes that gap. Not entirely, and I will get to the caveats, but enough that "try building your next small site on Statamic instead" becomes a reasonable suggestion to make to someone who has never opened Terminal.

This is not a no-code product and it is not pretending to be one. Statamic's Control Panel handles content. Building the front end still means templates, whether you write them yourself or start from a kit like Peak. What Sherpa removes is the tooling barrier, not the design and development work. Someone who currently assembles WordPress sites from a page builder will still need a plan for the front end. Someone who currently hands off to a developer will find that handoff a lot cleaner.

That front end work is also the part where AI agents have gotten genuinely useful, and Statamic happens to be shaped well for them. Everything is a file. Collections, blueprints, and fieldsets are YAML. Entries are Markdown with YAML front matter. There is no database to introspect and no admin UI state to reverse engineer, so an agent can read your whole content model by reading your repository, and scaffolding a new collection with the right fields is a matter of writing a file to the right path. Compare that to WordPress, where the equivalent work means custom post type registration in PHP, an ACF field group stored as serialized data, and a theme that may or may not follow any convention. Statamic also ships with Tailwind and Vite, and Tailwind is about as well represented in training data as any front end tool gets, so asking for a template and getting back markup that actually works is a reasonable expectation rather than a coin flip.

A few caveats

It is alpha software. Version 0.3.2 today, as I'm writing this article. The changelog from the past week includes fixes for site rows collapsing, duplicate imports, and a first run failure on hardened macOS. Things will break. So I would use caution before you decide to launch a client site to production with it in the next month.

It is Mac only, and specifically macOS 14 or later on Apple silicon. The team has said Windows and Linux are not on the immediate roadmap and that they would rather do one platform well. If your team is on Windows, then this obviously doesn't help you.

Deployment targets are currently Laravel Cloud for dynamic sites and Netlify or Cloudflare Pages for static builds. More are promised. If you are committed to a particular host, check that list before you get attached.

And licensing is unchanged by any of this. Statamic's Solo tier is free and usable in production for a single user site. Pro is a one time $349 per site, with $99 per year afterward for continued updates and support, following the increase that took effect in May. Compared against a stack of annual plugin subscriptions on a WordPress build, that math usually favors Statamic, but it is a cost that you'll need to factor in.

What I would do with it

If you have been curious about Statamic and stalled at the setup, install Sherpa this week and build something small and personal. A portfolio, a recipe site, a landing page for something you already own. Give yourself a Saturday morning. The point is to find out whether the authoring experience and the flat file model fit how you think, and now you can answer that question without a prerequisite.

If you already build in Statamic, the value here is different. It is a faster on ramp for the clients and collaborators you have been unable to bring along, and it is a much shorter answer when someone asks what it takes to get started.

Statamic has spent years being the CMS that Laravel developers recommend and non-developers struggle to reach. Sherpa opens the door to a new set of web developers to try and fall in love with Statamic just as I have.

We build custom sites on Statamic, Drupal, and Laravel, including migrations off WordPress for organizations that have outgrown it. If you are weighing a platform change and want a straight assessment of whether Statamic fits how your team works, get in touch. No pitch deck, just a conversation.