From Inclusivity to Autonomy: Why We are Building ServiceCMS

The "WordPress Trap" is a frustration most of us know too well. For twenty years, we have stuck with it because of the plugin ecosystem. But by 2026, that promise usually leads to a mess of bloated databases, constant security updates, and a site that feels heavy and slow. On the other hand, modern headless tools are fast, but they feel like they were built only for developers. If a non-technical writer wants to change a layout, they are usually stuck waiting for a pull request.

We are building ServiceCMS to change that. We are in the early stages, but the core engine is ready, and we are working to make it the modern, agentic alternative the web actually needs.

Our History: Born from a real-world challenge

ServiceCMS didn't start as a business plan. It was born from the work my colleague and I were doing at a social startup focused on inclusivity.

We had a difficult task. We needed to build one solid backend that could feed content to many different types of frontends. We were designing for very diverse user groups, each with their own accessibility needs and design philosophies. We needed a way to let our content writers build pages for a high-contrast accessibility portal and a modern SvelteKit site at the same time, using the same data, without getting trapped in rigid themes or technical jargon.

We realized that the bottleneck was always the "glue" between the content and the code. We wanted to build something that removed that friction for good.

What is an Agentic CMS?

Most CMS platforms are just digital filing cabinets. You put text in, and it sits there. ServiceCMS is different because it is "active."

The core backend is built on Hono and supports the Model Context Protocol (MCP). This means the CMS doesn't just store your data; it can actually talk to the AI agents that help build your site. It is designed for a world where tools like Claude or specialized coding agents handle the repetitive work of setting up frontends and managing content workflows.

How it works We are refining a process that makes the jump from an idea to a live site much faster:

• The Brain: You use our schema editor to define your content blocks. You add simple, human-style instructions that tell an AI agent how that content should be handled.
• The Agent: You pick your framework, like SvelteKit or Next.js. ServiceCMS provides the instructions, and a coding agent builds the frontend and connects it back to the backend automatically.
• The Builder: Once the setup is done, the user gets a simple, block-based editor. It feels as easy as the WordPress Gutenberg builder, but it’s running on a professional, high-performance stack.

Why Open Source?

We believe you should own your tools. ServiceCMS is open source because we want to prevent vendor lock-in. You own your data and you own your backend.

We are still in the early days. The core repository is finished, and we are now focused on building out an "Agentic Plugin Store." Instead of just downloading a code snippet, you’ll be able to deploy an autonomous workflow, like an agent that manages your SEO or your lead generation.

ServiceCMS is for the people who are tired of the bloat of the past but don't want the complexity of the present. We are building this for a smarter, more inclusive web, and we would love for you to join us.