ServiceCMS Beta Releases alongside EmdashCMS

Building in the open often feels like shouting into a void—until suddenly, everyone starts talking about the same thing at once.

Today, I’m incredibly excited to announce that ServiceCMS is officially entering Beta and is ready for you to deploy. But there’s a bit of a "coincidence" in the air: Cloudflare just put its weight behind emdash CMS, a project that feels like a long-lost sibling to what we’ve been building here.

You might ask: “isn’t it a bad thing for you that a giant like Cloudflare just launched a ‘competitor’ on the same day?”

Actually, it’s the best thing that could have happened. Here’s why.

Two Projects, One Vision (And No Competition)

The beauty of the open-source world is that we don’t have to fight over the same patch of grass. The launch of emdash isn’t a threat; it’s validation. It proves that the industry is finally tired of "plugin hell" and "theme bloat."

We are both moving toward a future where websites aren’t just static pages, but active participants in an AI-driven workflow. However, we’re solving two very different problems:

• emdash is aiming to be the WordPress of the future. It’s built for the creators, the bloggers, and the marketing teams who want a fast, beautiful site without the baggage of 2005-era PHP.
• ServiceCMS is aiming to be the TYPO3 of the future. We’re built for the "heavy lifting"—the B2B platforms, the complex e-commerce setups, and the service providers who need to coordinate staff, leads, and sessions across multiple domains.

While emdash manages your content, ServiceCMS manages your business logic.

What does "Agentic" actually mean for you?

We use the word "Agentic" a lot, but let’s bring it down to earth. Most CMS platforms are just digital filing cabinets—you put data in, you pull data out.

ServiceCMS is spec-driven. You define a content schema, and you attach instructions to it. Because we support MCP (Model Context Protocol) and REST, your coding agents (like Claude Code, Gemini-CLI, or your own local setups) don't have to "guess" how to use your data.

You can literally tell an agent: "Look at my service schema and build me a booking page that fits this logic." The agent understands the rules of your business because they are baked right into the CMS.

The "Supastack": Why we chose our tools

We didn’t want to reinvent the wheel; we wanted to build on the best tech available. We call our architecture the Supastack:

1. Cloudflare Workers: Like emdash, we run on the edge. Cloudflare is currently the undisputed king of "bang for your buck" and security. It keeps your site fast and safe globally.
2. Supabase: This is where we differ. We use Supabase (and its managed PostgreSQL) because, for a business, data integrity is everything. With features like Row Level Security (RLS) and custom auth hooks, your client data is locked down, searchable, and ready for complex enterprise requirements.

This combo gives you a blazingly fast frontend with a "grown-up" database layer that can scale as far as you need to go.

Get started in 5 minutes (for €0)

I know "enterprise-grade" usually sounds expensive and slow. ServiceCMS is neither.

I’ve included an easy install script that handles the heavy lifting for you. If you have a free Cloudflare and Supabase account, you can have a live, agent-ready instance running in about five minutes—without spending a cent.

The era of template-bloat is over. The era of the service-business is just beginning.

Let’s Chat

I’d love for you to take it for a spin. Check out the docs and the deploy button over at https://service-cms.com.

If you’re a developer or a business owner looking to automate your service workflows and you want to talk shop, don't be a stranger. Drop me a line at Jay@pluracon.org.

Let’s build something that actually works.