CMS · Your stack, your content, anyone edits

Edit your website, polish by AI, commit to git

Your developer keeps the stack. Whoever writes the copy gets a visual editor — with an AI assistant that rewrites, restructures, and polishes drafts, staging every change for your review before it commits.

Join the waitlist Read docs →

AI Assistant for rewrites, tone, and structure Every save is a real git commit Works on any static site Your devs keep schema control

CMS › Pages › e-commerce.md

Save Publish

▾ SEO

Page Title

E-commerce solutions

Page Description

0 / 160

AI Assist

Ask the assistant to draft, tighten, or fix copy.

Ask AI Assist… Send

Who it's for

Built for teams that already ship static sites

Engineers · Solo devs · Marketing teams

Astro / Hugo / Eleventy sites

Your developer already picked the SSG. We add a visual editor on top so the marketing team can update copy, swap hero images, and add blog posts — without touching a Markdown file.

Marketing · Content · Growth

Marketing sites with frequent edits

Hero copy, pricing tiers, FAQs — the bits that change weekly. Edit them in a visual editor, hit publish, your CI deploys. No Slack message to engineering, no PR review queue.

Agencies · Freelancers · Consultancies

Agencies maintaining client sites

Build the site, hand the editor to the client, walk away. Their edits commit to their own GitHub. When you leave, your client keeps everything — content, history, schema. No exit fee.

DevRel · Docs teams · Technical writers

Documentation & knowledge bases

Pages, sections, code blocks, callouts — modeled as schema-driven blocks. Authors edit through the visual editor; engineers update the schema when a new block lands. No JIRA ticket per copy change.

Holdings · Multi-brand · Internal landing pages

Multi-site portfolios

One Norcube login, many sites. Each site stays in its own GitHub repo with its own deploy. Schema and content stay independent — no shared database, no cross-site drift.

Startups · SaaS · Solo founders

Headless-curious teams skipping the headless tax

You don't need API-first if your front-end is already static. Skip the headless CMS, skip the database, skip the API contract. Edit files in a visual editor; let your existing build pick them up.

What it does

A visual editor on top of your git repo

Git-based, in your repo

Connect a GitHub repo via the Norcube GitHub App. Every edit lands as a real commit on the branch you pick — content, history, and schema all stay in git.

Schema-driven blocks

Pages are markdown frontmatter with a `content_blocks` array; each block has a typed schema. Authors see the right fields for the right block; engineers control the type system.

`$ref` shared blocks

Define `button` once in `blocks/button.yml`, reference it via `$ref: button` from every block that has buttons. One edit propagates everywhere.

AI schema scaffolding

Connect a repo with existing markdown. The AI agent samples your pages, infers blocks, extracts shared shapes, and commits a starter `.norcube/cms/` in one go.

Field history from git

Every field has a clock icon that shows when each value was edited and who edited it — sourced directly from git blame on the underlying YAML.

Drafts before publish

Edits sit in a per-user draft until you hit Publish. Nothing reaches your branch while you write — review, then ship.

Discussions on every field

Drop a comment on any field — marketing asks a question, engineering answers without a context-switch into Slack. Threads live alongside the content.

Media uploads with signed URLs

Drag an image into a field; we upload via a signed URL straight to your configured storage. Image paths get written back into the markdown.

AI Assist for content edits

Ask the AI assistant to rewrite, shorten, or restructure any part of a page. Proposed edits stage as a draft so you review before publishing.

No vendor lock-in

Your content was always in your repo. When you stop paying us, you keep your content, schema, and history. No export step, no migration, no exit fee.

our promise

Your content is yours. Always

We built Norcube CMS the way we'd want a CMS to work after watching too many of them lock customers in. These are the rules we follow — no exceptions.

principle 01

Your content lives in your repo

Not in our database. Every edit is a real commit on your branch. Cancel and you keep everything — content, schema, history — because it was always yours.

principle 02

Schema is code, content is git

Engineers control the type system in `.norcube/cms/`. Authors edit through the visual editor. Same source of truth, no API contract to keep in sync.

principle 03

No per-seat pricing

Invite your whole team. Engineers, marketers, freelancers — everyone. We charge for sites and storage, not people added.

Pricing

Free during the private beta. Public pricing when we hit GA

Norcube CMS is in private beta. Join the waitlist and we onboard you personally — free, no credit card, full feature set. Paid tiers and quotas land when we move out of beta; we will publish them here before anything changes for early users.

Free tier: Everything

Beta means everything is free: unlimited sites, unlimited authors, unlimited drafts, AI scaffolding, AI Assist, discussions, field history. The only thing we ask in return is feedback when something feels off.

Beta access — Free during the private beta. No credit card. Full feature set.

Sites Unlimited

Authors per site Unlimited

AI scaffolding runs Unlimited

AI Assist edits Unlimited

Media uploads Generous beta limits

Discussions & drafts Unlimited

Common questions

Questions, answered

Quick answers to what teams ask us most about Norcube CMS. Need something else? Email [email protected].

Which static site generators does Norcube CMS work with?

Any SSG that reads markdown with YAML / TOML frontmatter — that's Astro, Hugo, Eleventy, Jekyll, Hexo, Zola, and a long tail of others. We do not require an SDK, a build plugin, or any framework-specific integration. The CMS edits the same files your existing build already consumes.

Where does my content live?

In the GitHub repo you connect. Pages are markdown files at the path you configure (typically src/content/pages/ or similar). The schema lives next to your content under .norcube/cms/. Cancel your Norcube account tomorrow and your content stays exactly where it always was — in your repo, fully readable without us.

What does the AI scaffolding actually do?

When you connect a repo that already has markdown pages, the AI agent samples up to 120 files from your pages directory, infers the frontmatter shape, identifies block-like patterns (anything with a _type: or _component: discriminator), extracts shared shapes like buttons so they're defined once, and commits a complete .norcube/cms/ starter in a single bundled commit. You can re-run it to refine; existing schema files get cleanly overwritten.

How are edits saved?

Your edits live in a server-side draft per user, so the editor doesn't lose work on tab close, but nothing reaches your branch until you hit Publish. Publishing commits your staged edits with a generated commit message; a page and its tracking metadata land atomically via the Git Trees API.

Can multiple people edit the same page at once?

Yes. Each author has their own draft per file, so concurrent edits don't stomp each other. If the file changed on the branch between your draft and your publish, the commit is rejected instead of silently overwriting the other author's work — you re-apply on the fresh version. Discussions let you ask questions on a specific field instead of fighting over an edit.

Is there a live preview?

Roadmap. The plan is a sandboxed container per site running your actual dev server, with unsaved edits streamed via WebSocket so the iframe updates in real time. The longer-term goal is preview-first editing — click an element in the rendered page, edit it inline. Current beta ships the visual editor without live preview; you preview by hitting Publish and waiting for your existing CI deploy.

How does this compare to CloudCannon, Decap, or Tina?

All three are git-based CMSes — closest to what we do. We diverge on AI scaffolding (we generate the schema from your existing markdown instead of making you write it), strict $ref enforcement so shared blocks can't drift, and no per-seat pricing. See the per-product head-to-heads: CloudCannon, Decap, Tina, Keystatic, Sanity, Contentful, and Ghost.

Quickstart

Connect a repo, scaffold a schema, edit your first page — all in under ten minutes

Three steps if your repo already has markdown content; the AI does the schema work for you.

About 10 min

Join the waitlist and install the GitHub App

Norcube CMS is in private beta — join the waitlist and we onboard you personally. Once you have access, install the Norcube GitHub App on the repo you want to edit. Scope it to a single repo if you prefer — we only see what you grant.
Connect a site

In the Norcube dashboard, point at the repo and the branch (usually `main`). Pick the directory where your pages live (we will auto-detect `src/content/pages/`, `content/`, and the other common SSG conventions).
Run AI scaffolding (if no `.norcube/cms/` yet)

Hit "Analyze repo" on the settings page. The AI agent samples your existing pages, infers a schema, extracts shared blocks, and commits `.norcube/cms/` in one bundled commit. Iterate by re-running if the first pass needs refinement.
Open a page in the editor

Pick any page from the Pages tab. Every frontmatter field renders as a typed input. Edit, save (drafts persist), then hit Publish to commit to your branch.
Hand the editor to non-technical teammates

Invite your marketing team. They edit through the visual UI; you keep schema control in git. Their commits look like everybody elseʼs — co-author on PR review, GitHub blame on every line.

Other products on the platform

Norcube CMS is one piece of the Norcube platform. Same dashboard, same login, same pay-as-you-go pricing.

LangSync

Get early access to Norcube CMS, free during the private beta

Join the waitlist and we onboard you personally. Then: install the GitHub App, point at a repo with markdown pages, let the AI scaffold the schema — first page edited in under ten minutes.

Join the waitlist Read the docs

Private beta Free, no credit card

Git-based Content lives in your repo

No vendor lock-in Cancel and keep everything

AI scaffolding Schema from your content