A calm editorial layer for modern Git-backed websites.
Surface CMS gives teams a focused way to edit Markdown and MDX content without moving it out of the repository.
No content database. No parallel source of truth. No fragile copy-paste into code. Just your site, your files, your Git history — surfaced into a safer workspace for writers, editors, SEO teams, and localization partners.
Why file-first teams need this
Markdown and MDX repositories are excellent for engineers and terrible for everyone else. The moment a non-developer needs to ship a small edit, the workflow breaks: branches, pull requests, rebuilds, frontmatter quirks, and components that look like code.
Surface gives those teams a calm interface over the same repository — without replacing it, mirroring it, or extracting content into another system.
Draft
A focused writing surface for clean, distraction-light prose.
Paste
Bring in messy copy and let it land as well-formed Markdown.
Generate
AI-assisted composition that respects your existing voice and structure.
Optimize
Metadata, headings, and quality cues, surfaced where editors actually look.
Regionalize
Localization and drift review across regional variants of the same content.
One repository
Every Surface writes back to the same Markdown and MDX files in Git.
What Surface protects
Your Git history
Git remains the source of truth. Surface writes back to the same files your build already uses, so history, review, and deploys stay exactly where your team expects them.
Your MDX structure
Developer-owned MDX components, frontmatter, and structured blocks are protected. Editors get a safe interface; engineers keep the schema they wrote.
Your build pipeline
No content database. No new runtime. No parallel CMS to keep in sync. Surface stays out of the way of your existing static or hybrid build.
Your team's focus
Each Surface is scoped to a single editorial mode, so writers, SEO, and localization can work without seeing everything at once.
What early access is for
Surface CMS is being built for teams with real Git-backed content workflows. Early access is intentionally small — it's for teams whose repositories, editorial pain, and content shape help us shape the product before it opens more broadly.
If your team writes Markdown or MDX in Git and the human side of that is hurting, we'd like to hear from you.