Compare InkCMS
An honest matrix comparing InkCMS to WordPress, Contentful, Sanity, Squarespace, and Webflow. We name names and call out where competitors are stronger.
Read more§ About InkCMS
A CMS built by
someone who's built them for 30 years.
InkCMS is the seventh CMS we've written. The first six taught us what to keep. This one started with a question: what would we build if Claude was the senior editor?
§ 01 — Origin
Three decades of CMS. One AI-first reset.
We built our first CMS in 1995, before the term existed. The clients were Fortune 500. The shape was the same shape most CMSs still have today: a SQL database, a CRUD admin, content types, templates, publishing workflows, role-based permissions. Versions of that CMS power hundreds of sites around the world. It's robust, multi-server, high-security, high-speed — everything an enterprise stack should be.
It is also, in 2026, the wrong shape for the world we now work in.
The world we now work in has Claude in it. And Claude is not very good at SQL admin panels — but Claude is extraordinarily good at editing files. Markdown files. YAML files. Razor templates. CSS. The substrate of the web.
So we tore the old assumptions up and started over. InkCMS is a complete reconstruction of a traditional CMS, designed from the storage layer up to be edited by an AI. No database. No CRUD admin as the primary path. No content-type schema migrations. Just files — the shape Claude already understands.
The bet is simple: a developer with Visual Studio Code and Claude Code should be able to stand up a complete, functional website in a day. Starting from a small set of HTML and a brand brief. Or from Figma designs and a content drop. Or — once the site is live — from a marketing lead pasting raw notes into the admin chat and clicking Apply.
"This is the seventh CMS we've written. The first six taught us what to keep. This one is what we would build if Claude was the senior editor."
— Founder, InkCMS
The page editor with Claude beside you — the loop the rest of the product is built around.
§ 02 — Philosophy
Three principles. No exceptions.
Every design decision in InkCMS traces back to one of three rules. Where the rules conflicted with convenience, the rules won.
I · Filesystem first
Every byte of state is a file. No exceptions.
Pages, menus, entities, users, sessions, audit logs, AI conversations — all on disk as markdown, YAML, or JSON. An agent that knows the format for one file knows the format for all of them. A human can open any state in a text editor. A backup is tar. A disaster recovery is tar -x. A development workflow is git diff.
II · AI is a senior editor
The agent is a teammate, not a magic wand.
Claude reads. Claude proposes. The human approves. Every write surfaces as a pending-action card. Every action is in the audit log. The AI never has shell access, never sees source code, never holds secrets, never publishes without consent. That's how you trust an agent in production — by giving it nothing it shouldn't have.
III · Developers own the stack
It's your ASP.NET app. We just shipped it.
InkCMS is source-available. Customization is C#, Razor, and CSS — the same tools every .NET developer already uses. No plugin economy. No theme marketplace. No proprietary scripting language to learn. If you want a feature, you write the feature. If you want a different look, you write the CSS. Claude Code helps. The result is yours.
§ 03 — Product timeline
How we got here.
1995
First CMS — the SQL ancestor
A custom CMS for an enterprise client. SQL Server backend, .asp classic frontend. The shape that became conventional wisdom.
1998-2024
Five more generations
Each rewrite kept what worked, threw out what didn't. ASP.NET WebForms. ASP.NET MVC. ASP.NET Core. Hundreds of production sites. Custom portals, ecommerce engines, financial forecasting tools.
2025
The Claude experiment
Built agentic web tools for client sites. Watched Claude struggle with conventional admin UIs and excel at file editing. The penny dropped: the storage layer is the bottleneck.
2026 Q1
InkCMS — clean sheet
Filesystem-only storage. Markdown + YAML everywhere. Two AI surfaces — admin assistant + visitor advisor. Multi-provider. .NET 10. Single binary.
2026 Q2
v10.1 — public release
Versioning starts at 10.1.5 — InkCMS inherits the line numbering from its enterprise ancestor. A simple .zip with .cmd and the install process runs. All /custom edits are left alone during updates. Updates take a full snapshots for security then update core InkCMS functions. Source-available under a commercial subscription license — one site per subscription, full source for every customer to read, audit, and extend.
§ 04 — Boundaries
What InkCMS is not.
Knowing what InkCMS isn't is as important as knowing what it is. If any of the below describes what you need, InkCMS may not be the right tool.
×
Not a Squarespace alternative.
InkCMS is for sites where the content matters and the operator wants to own the stack. If you want drag-and-drop with no developer in the loop, you want something else.
×
Not headless.
Server-rendered Razor templates with embedded partials — because the AI authoring contract works better when the template IS the source of truth. Not when there's a JSON API hiding it from the AI.
×
Not WordPress at scale.
No plugin economy. No theme marketplace. Customization is C#, Razor, CSS — and Claude. If you depend on a thousand-plugin ecosystem, InkCMS will feel sparse on day one. But ask Claude to build what you need, and unreliable third-party plugins become custom applications you actually control.
×
Not an AI-on-top wrapper.
AI is the design center, not a bolted-on feature. The data model, storage shape, tool surface, and prompt contract were all designed to be edited by an LLM from day one.
See how InkCMS compares to the CMS you're already paying for.
Open the matrix →