Liquid theme
02Layout, a template per type, a template per block. Server-rendered from live content.
The Studio
An editor made for their site.
They sign in to their own site and see only the content you modelled: every type a clean list to search, edit and publish. No settings to break, no design to knock over.
See what the client seesPrompt it, code it or import it.
Your agent, over MCP
Describe the site to Claude Code, Cursor or Codex and it models, writes and themes it: the whole platform as tools, scoped to one workspace. Every change it makes is versioned, so any document, theme or deployment rolls back in one step.
It's plain MCP, so any agent on any model can use it.
- Anthropic
- OpenAI
- Gemini
- Meta
- Mistral
- DeepSeek
$ claude mcp add --transport http contentive https://contentive.io/mcp/w/meridian-roasters
✓ connector registered · scope: workspace · oauth
$ claude "add a Peckham branch page and stage it"
→ describe_schema location
→ create_document Peckham
→ publish staging
Your developer, in code
Install the CLI from npm, pull the theme, edit it in your own editor and push it back to staging. It's Liquid, so any front-end dev is productive on day one, and every version is kept.
$
npm i -g @contentive/cliWant your own front end instead? Every content type is already a typed GraphQL API, with a playground and generated docs for your workspace.
<section class="hero" data-reveal>
<p class="eyebrow">{{ block.eyebrow }}</p>
<h1>{{ block.heading }}</h1>
{% if block.subheading %}
<p class="hero-sub">{{ block.subheading }}</p>
{% endif %}
{% if block.image %}
<img src="{{ block.image | image_url: width: 1200 }}" alt="">
{% endif %}
{% if block.ctaLabel %}
<a class="button" href="{{ block.ctaHref }}">
{{ block.ctaLabel }}
</a>
{% endif %}
</section>
Import a site you own
Paste the URL and the real thing is captured, markup, CSS and fonts, then rebuilt as a theme, with every heading, image and link turned into a field the client can edit. A per-page report shows what matched.
Move from any public site, including:
- WordPress
- Webflow
- Squarespace
- Wix
- Framer
- Ghost
https://meridianroasters.co.uk
Import
- ✓Pagesevery route, slugs kept exactly
- ✓Postswith authors, dates and categories
- ✓Contentheadings, copy and links as fields
- ✓Imagesre-hosted in your media library
- ✓Navigationmenus and footer links
- ✓Thememarkup, CSS and fonts rebuilt in Liquid
Ready to review on stagingOpen staging →
No page builder to fight.
Write the theme once, in templates and CSS, and it renders exactly as you wrote it.
Why we didn’t build a page builder
- ✓Clients can’t break the design. They edit content, never layout or styles.
- ✓Light pages. Only your CSS and scripts ship.
- ✓Clean markup. The HTML you wrote, not layers of divs.
- ✓One build, every screen. Not three, for desktop, tablet and mobile.
{
"colors": {
"primary": "#4F46E5",
"ink": "#121212"
},
"typography": {
"heading": {
"fontFamily": "Figtree",
"fontWeight": "700"
}
},
"radius": { "md": "12px" }
}
:root {
--color-primary: #4F46E5;
--color-ink: #121212;
--font-heading-family: Figtree;
--font-heading-weight: 700;
--radius-md: 12px;
}
Underneath,
a proper CMS.
However the site gets built, the content lives in a real content management system. You define the model, your client edits it in the Studio, and nothing is baked into the code.
Your own content types
Define the fields each type needs: text, rich text, images, references, dates. No plugin to bolt them on.
Rich text, done properly
A block editor for every long field, stored as structured content rather than HTML.
References between content
Link authors to posts or locations to regions, and query across them.
Pages built from blocks
Compose each page from reusable sections. Your client reorders them without touching code.
Global settings
Company details, header and footer live in one place and update everywhere they appear.
A media library
Every upload in one place, with alt text, tags and a focal point for smart cropping.
Drafts, history and scheduling
Save drafts, restore any earlier version, or schedule a publish for later.
Roles and languages
Give each client exactly the access they need, and publish in more than one language.
Everything else is an extension.
The core does content, themes and hosting. Bookings, reviews, search, chat and the rest are extensions you install per site, each with its own Studio screens, a tag for the theme, and tools your agent can use.
01 / 08
Analytics
Who visits and what they read, with no cookies and no consent banner.
Hosting, built in.
Not bolted on.
No host to buy, no staging to set up, no certificate to renew. Everything publishes to staging, your agent’s changes included, and production only moves when someone promotes it.
You or your agent
StagingReview · its own URL
Promotewhen you’re ready
ProductionLive · every version kept
Lightning fastfor every visitor, wherever they are
- You or your agentmake a change
- StagingReview · its own URL
- Promotewhen you’re ready
- ProductionLive · every version kept
- Lightning fastfor every visitor, wherever they are
Nothing of yours to patch
Workers and object storage: no server with a login, no admin on the site, no plugin surface. Scripts run from a per-site allowlist, never unsafe-inline.
DDoS is not your problem
Absorbed long before it reaches the site, on a network your client’s traffic was never going to trouble. Certificates issue and renew on their own.
Fast without a build
Pages are cached close to every visitor and refresh on publish, so changing a word costs what changing a word should cost.
Their domain, not ours
Apex and www, a staging URL per site, and a name you can claim the day the build starts.
Build for free.
Pay when it’s live.
One site is £10.99/mo. Building for clients, it’s £39/mo with three live sites included, then £10.99/mo each. Unlimited workspaces, unlimited seats, hosting included.
Your price never rises when you invite your client.
The full matrixYour monthly bill · Agency
£39.00/mo
How many sites are live?
Jump to:
Unlimitedworkspaces
Unlimitedseats, always free
Includedhosting
One model.
Every surface.
Define the content model once and everything else is generated from it. Add a field and the API gains it, the theme can use it, the agent can fill it and the client can edit it. One change, no redeploy.
{
"types": {
"location": {
"label": "Location",
"fields": [
{ "name": "title", "type": "string" },
{ "name": "address", "type": "string" },
{ "name": "region", "type": "reference" }
]
}
}
}
GraphQL API
03Typed the moment you save. Relay connections, filters, references. Use it or ignore it.
MCP tools
04The platform as tools for your agent, scoped to one workspace.
CLI
05Pull, preview against live content and push, through the same renderer production uses.
SDK
06A typed client for your own front end, with rich-text renderers and a Next.js adapter. MIT, on npm.
Studio
07The editor the client uses. Same model, so it fits the site exactly.
I’ve spent years building sites for clients on other people’s platforms, and none of them were good enough. Every build meant shoehorning in a page builder, piling on third-party plugins and paying for hosting somewhere else. Contentive is the platform I wanted instead: everything a client site needs, built in, with nothing to bolt on.
It’s in beta with a small number of agencies. No case studies yet. When there are, they’ll be real ones.
ZacFounder, Contentive
Before you put
a client on it.
Straight answers to what agencies ask first.
Is this ready for client work?
It’s in beta with a small number of agencies, and it hosts real sites today. We say “beta” because the extension catalogue and the Studio are still growing, not because the hosting is.
Who owns the site?
Your client owns their content and their domain. The workspace sits in your account, and you decide what they can see and edit.
Can my client pay for their own site?
Not yet. Today the agency holds the bill and charges the client however it likes. Billing transfer is on the roadmap.
What if we leave?
Your content is always available through the API, and the content model exports as a file. The theme files are yours too, though they’re written for Contentive’s renderer and would need rework to run elsewhere.
Can the Studio carry our brand?
On the Enterprise plan, yes: the Studio can carry your brand instead of ours. On Agency, clients sign in to a Contentive Studio that shows your workspace’s name.
Can an AI agent break a live site?
Not by accident. Agents, imports and theme pushes all land in staging first. Production only changes when it’s promoted, and every deployment can be rolled back.
Does it work with WordPress?
As a destination. Import a WordPress site and its pages, posts, images and URLs come across. It doesn’t run WordPress plugins; the extensions replace them.
What support do we get?
Direct chat with the customer success team.
Build your next
client site here.
Free to build and preview on staging. From £10.99/mo when it goes live, with hosting included.
Already have a workspace? Log in