A CMS where every publish leaves a receipt

Write, review and ship your site's articles, then see exactly what went live, when it went live, and where readers saw it.

See the source

Ways to connect: REST, GraphQL, the TypeScript SDK, the CLI and an MCP server

  • REST
  • GraphQL
  • TypeScript SDK
  • CLI
  • MCP server

Why Colophon

  • Lose nothing

    Pull the plug mid-save and your work is still there. A publish lands once and completely, or not at all.

    Crash-safe
  • Replayable bugs

    Every failing test run hands back a seed number. Replay that seed and get the exact same failure.

    Deterministic tests
  • Time travel

    Read any past release, minus what was taken down since. Going back is simply a new release.

    Release history
  • Honest status

    A release is verified only once a site check sees it. Until then it shows published or pending, never verified.

    Delivery receipts
  • Roles down to a field

    Decide who can read, edit or publish, down to a field. Access changes land in an append-only audit log.

    Permissions
  • Agents draft, people approve

    Scripts and AI agents work through scoped tokens. They can draft and propose changes, never approve.

    Safe automation

FAQ

Questions
answered

A content management system for writing, reviewing and publishing a website's articles, built so you always know which version readers are seeing.

Printed books end with a colophon: a short note on how, when and by whom the book was made. Colophon gives a website that same kind of record.

Yes, inside limits you set. Agents work through scoped tokens with spending caps and request quotas, and nothing they submit can be approved by another token.

Your saved work survives, and the half-finished publish never reaches readers. Crash recovery is tested on every change.

Not yet. It is still being built, and the builder's own site goes first. The five demo sites in the repository show how it works in the meantime.

Follow the build.
Mistakes included

Colophon is being built in public, one write-up at a time. Read along as it comes together, or poke around the demo sites.

Read the build log