We lost our ~~Sanity~~ — waiting 4 seconds for a CMS to think. So we built one that doesn't.

The content runtime for the edge.

Author once. AI-assisted, human-approved. Delivered globally in milliseconds.

Inspired by Ink & Switch's Upwelling research →

LIVE · The editor in motion

Quarterly Review · Issue 12

Post-quantum cryptography enters the procurement checklist

The shift from lab concern to board-level requirement happened quietly. First came inventory requests, then vendor attestations, then the harder question: which archives need to survive a future decryption event?

The teams moving fastest are not replacing every primitive at once. They are mapping systems, shortening certificate lifetimes, and choosing migration paths that can be audited by people outside the security group.

For publishers, the lesson is familiar: durable records need visible provenance. The edit trail matters because memory eventually becomes infrastructure.

Agents propose on branches. You merge what's worth merging.

The Three Differentiators

Branching, governance, edge.

01 / BRANCHING

An issue is a branch.

Fork the live site. Edit privately. Merge when it's ready. CRDT-guaranteed convergence — no merge conflicts, no lost work, no "who edited this?" Slack threads.

02 / GOVERNANCE

AI proposes. You publish.

Translation agents, SEO agents, editorial agents — they all work on branches. Nothing goes live without a human merge. Your content stays yours, even when AI helps write it.

03 / EDGE

Read in milliseconds. Anywhere.

Built on Cloudflare's 330+ point-of-presence network. Your content is cached at the edge nearest your reader, served from a Worker that cold-starts in zero milliseconds. No origin. No regions. No waiting.

AI should propose. Not publish.

Other platforms hand AI the keys to your content. We don't. Every AI-generated change lands as a proposal on a branch — visible, reviewable, reversible. Your editorial standards stay yours. Your voice stays yours. Your name on the byline still means something.

proposed reviewed merged

Built for engineers. And for editors.

One platform. Two front doors.

// engineers

// schema.ts
import { defineSchema, field } from '@eoxscriptum/core';

export const article = defineSchema({
  name: 'article',
  fields: {
    title: field.string({ required: true }),
    body: field.richtext({ editor: 'tiptap' }),
    cover: field.image({ r2: true }),
    seo: field.seo({ autogenerate: true }),
  },
});

Type-safe schemas. Edge-deployed in seconds.

// editors

Branch: issue-12

An interview that took 14 days

The best edits arrived after everyone stopped trying to publish first.

Familiar editing. Powerful publishing. No git required.

Performance receipts

Fast where readers actually are.

<5ms KV read latency

330+ edge PoPs

~0ms cold start

99.99% SLA

Latencies measured from our staging deployment. Your mileage will vary by region — but not by much.

Compared to Sanity

Governance and edge delivery, built in.

Capability	EOXScriptum	Sanity	Contentful
Edge-native delivery	Yes	No	No
CRDT branching	Yes	No	No
AI governance built-in	Yes	No	No
Self-hostable	Yes	Partial	No
Multi-tenant by design	Yes	No	Partial
Pricing model	Flat	Verify before ship	Verify before ship

Compared in good faith. If we got something wrong, tell us.

article draftedslug optimizedtags assignedimage uploadedsitemap updatedschema validateddraft savedmedia optimizedblog post publishedcache invalidatededge-deliveredSEO metadata generatedcontent syncedpost scheduledcanonical URLog imagelocale awareversioned draft

versioned draftlocale awareog imagecanonical URLpost scheduledcontent syncedSEO metadata generatededge-deliveredcache invalidatedblog post publishedmedia optimizeddraft savedschema validatedsitemap updatedimage uploadedtags assignedslug optimizedarticle drafted

Ready to ship?

Free during preview. No credit card. Self-host whenever you want.

Start building → Talk to us