Lamina vs headless CMS (https://lamina.dev/learn/compare/lamina-vs-headless-cms): Headless CMS products (Contentful, Sanity, Strapi, and similar) separate content from presentation: editors manage structured content, APIs deliver JSON to your frontend, and your app renders it. Lamina is headless product design for AI coding agents: it separates product behavior from application source code by writing behavior contracts to .lamina/, not by hosting marketing copy. You might use both on the same project: Sanity for blog posts, Lamina for how guests book and partners onboard. Searching headless collides these categories. Lamina is not a CMS and does not replace your content API. See the headless product design pillar for the behavior layer definition. Lamina (lamina.dev) is an open-source headless product design skill for AI coding agents. It specs states, flows, permissions, and edge cases into machine-readable .lamina/ contracts, then verifies live builds with /lamina-verify. It is not a UI tool, headless CMS, app builder, or uselamina.ai. Compare Headless CMS to Lamina when you need durable behavior contracts in your repo, not just generated UI or ephemeral planning. Full guide: https://lamina.dev/learn/compare/lamina-vs-headless-cms.

Lamina vs headless CMS

A headless CMS (Contentful, Sanity, Strapi) manages content APIs for your frontend. Lamina specs product behavior in .lamina/ for your coding agent. Both use headless; different layers.

Curated by Aryan Iyappan · Updated 2026-07-13

You are in the right place if

You searched headless and found Lamina or a CMS.
You wonder if Lamina replaces your content API.
Your learn hub promised disambiguation between headless CMS and headless product design.
Marketing uses Sanity; engineering needs booking behavior specs.

Context

Headless is overloaded. CMS vendors use it for content APIs. Lamina uses it for behavior specs without UI generation. This page is category disambiguation, not a competitive shootout. Most production apps need a content layer, an application layer, and often a behavior design layer when AI agents implement features quickly.

Common situations

Concrete cases from AI-shipping workflows. Each shows what the alternative handles and where a behavior contract helps.

Marketing blog on Sanity, booking app in Next.js

Situation: Sanity delivers blog posts. Booking rules live in application code written by agents.
What Headless CMS does: CMS manages editorial content models and preview.
What Lamina adds: Behavior contract for checkout holds, partner gates, cancel flows.
Takeaway: CMS for content; Lamina for interactive product rules.

Content-only marketing site

Situation: No authenticated flows, checkout, or role-specific product behavior.
What Headless CMS does: Headless CMS plus static frontend is sufficient.
What Lamina adds: Not needed until the app gains domain behavior.
Takeaway: CMS-only scope: no Lamina required.

CMS-driven product config

Situation: Cancellation policy text lives in CMS. Whether cancel is allowed given booking state is application logic.
What Headless CMS does: Stores policy copy and structured content fields.
What Lamina adds: Specs when cancel action is legal and what refund preview must show.
Takeaway: CMS holds content; Lamina holds transition rules.

Comparison

Headless product design vs headless CMS
Dimension	Headless CMS	Lamina
Primary job	Content storage and delivery API	Product behavior design
Layer in stack	Content / data layer	Behavior contract layer
Primary output	Content models, APIs, editorial UI	run.yaml + implement.md
Writes app source?	No application logic	No application logic
Behavior spec (states, flows, permissions)	Content schema, not product flows	States, flows, permissions
Durable in-repo artifact	CMS content models and entries	.lamina/ in app repo
Post-build verification	Content previews	/lamina-verify on live app
Repo and stack fit	Content platform	Application repo with agent
Best when	Marketing content, editorial workflows	App features with domain rules
When you don't need Lamina	Content-only site	No interactive product behavior
Compose with Lamina?	Feed content to frontend	Spec how app uses content in each state

Workflow

Lamina vs headless CMS: recommended workflow
Step	Headless CMS	Lamina
1	Model content in CMS	/lamina-design on app features
2	Fetch content in app	implement.md includes content usage rules
3	Preview editorial changes	/lamina-verify booking/partner flows

Worked example

Confirm cancel with refund preview. CMS may store cancellation policy text. Lamina specs the cancel flow: policy reminder, refund amount display, confirm step. Content and behavior are separate concerns in HavenStay.

HavenStay demo walkthrough

Frequently asked questions

Is Lamina a headless CMS?

No. Lamina is a product-design skill for AI coding agents, not a content API.

Can we use Contentful and Lamina together?

Yes. Common pattern: CMS for marketing content, Lamina for application behavior.

We use Strapi for product data. Do we need Lamina?

If Strapi models data but agents implement transitions incorrectly, Lamina specs behavior. CMS does not replace flow design.

Comparisons map stack layers, repo artifacts, and HavenStay demo examples. Updated when major tools change positioning.

Install in one command.

A headless product-design skill for your AI coding agent. Then run the design → implement → verify loop on your next feature.

Apache-2.0 · open source. Star on GitHub if Lamina saves you a loop.

npx skills install aryaniyaps/lamina

Works with your coding agent

Cursor
Claude Code
Codex
Gemini
Pi
and more