Macrocontent
Early Access waitlist

Website management.
Content first.

Macrocontent is a layer over your existing site — not a replacement CMS. Inline editing and SDK today; hosting, analytics, and a site database as optional parts of the same platform.

Documentation Roadmap How it works

Join the waitlist

Early Access is not available yet. Leave your email — we notify in waves when you can try Macrocontent.

By submitting, you agree to be contacted about the options you selected. See our privacy policy.

Platform

One platform, four layers

Content is the entry point. Hosting, analytics, and a site database extend the same stack — each optional, none required to start.

Content layer

SDK, overlay, and inline editing on your live site. Mark regions, draft, publish — without redeploying for every copy change.

Inline on the live page

Hosting

Run your site on Macrocontent edge with your domains and deploy pipeline. Optional — your repo and stack stay portable.

your-site.com → Macrocontent edge
your repo stays portable

Analytics

Measure events and usage through the SDK on the real page. Start simple, extend over time — evidence, not black-box scores.

Site database

Structured records next to page content: form submissions, leads, and site-specific data. Manage in the dashboard, query via API.

contacts · leads · records
{ "email": "…", "source": "form" }

Product

What you get with content

Edit, integrate, and manage — on top of the site you already built.

Inline editing

Change copy and media on the real page — in context, not in a separate CMS screen.

SDK & setup

Drop in the SDK, mark editable regions, and connect your site.

Team & permissions

Multiple people, clear roles — developers keep structural control.

Locales

Content per language without rebuilding keys for every locale.

How to get started

Four steps from SDK to optional Site Agent at the edge.

  1. 01

    Add the SDK

    Configure macro.config.js with frontend keys only — like adding analytics, not replacing your app.

  2. 02

    Mark editable regions

    Set data-macro-key on the elements you want editable. Routing and design stay yours.

  3. 03

    Edit on the live site

    Your team opens the overlay, saves drafts, and publishes — in the real layout.

  4. 04

    Run Site Agent (optional)

    Edge proxy in front of your app: draft preview, private blocks stripped at the edge, and bake jobs back to your repo.

Built for your team

Developers

Skip building a CMS backend — marking, SDK, and APIs instead.

Agencies

Make client sites editable without a deploy loop for every text tweak.

Marketing teams

Update copy yourself — no dev ticket for every headline change.