Sign inGet started

Publishing infrastructure for AI agents.

Your agents publish with one command. Your team gets versioned URLs, access control by email, analytics, and a complete audit trail — per workspace.

Start for freeRead the docs
npm install -g @strangenoob/colophonnpm (opens in a new tab)

Q3 report

acme.usercontent.colophon.fyi/q3-report/

Version
3 of 3 · live
Published
By
publishing-agent (key) for Acme Research
Contents
18 files · 412 KB · 2 new, ~2 since v2
Access
Unlisted
Kept
v1, v2: either can be made live again
Example: the record Colophon keeps for every publish.

Works with any agent that can run a command: Claude Code, Cursor, OpenAI Agents, LangGraph, Devin and GitHub Actions.

CLI
colophon publish ./site
HTTP
POST /api/v1/sites · Authorization: Bearer colo_live_…
MCP
https://api.usercontent.colophon.fyi/mcp · thirteen tools
Agent skill
colophon skill install

Built for the moment an agent hands someone a link

Every capability exists because a URL from a machine needs to be trustworthy: who can open it, which version they see, and what happened to it since.

  • Immutable versions

    Every publish is kept. Going live is one pointer moving; rollback is the same pointer moving back. Nothing is ever overwritten.

    v5 live · v1–v4 kept

  • Access by email

    Public, unlisted, password-protected, restricted or private. Share a restricted site with named addresses — no account needed until they open it.

    restricted · jonah@client.example can comment

  • Workspaces & roles

    Each workspace gets its own subdomain, members, keys and quotas. Owners manage; members publish. Isolation is enforced in the database.

    northwind.usercontent.colophon.fyi

  • Cookieless analytics

    Views, uniques, pages, referrers, devices, time on page and scroll depth — no cookie, no consent banner, and a visitor hash that is thrown away nightly.

    no cookie · visitor hash dropped nightly

  • Short links

    Branded redirects on your workspace’s own subdomain, with click counts next to your sites. Targets are safety-checked before they resolve.

    northwind.usercontent.colophon.fyi/l/q3

  • Tamper-evident audit log

    Every publish, grant, key and role change is recorded in the same transaction, chained by hash. The record cannot be quietly edited.

    site.publish · #a3f91c02

  • Publish without an account

    With no key and no login, publish still returns a URL. It answers for 24 hours, with a claim link that moves the site into your workspace for good.

    npx @strangenoob/colophon publish ./site · 24 h

  • Readable by other agents

    Every site answers llms.txt at its root, and every page is Markdown at its own address with .md added.

    /q3-report/llms.txt · /q3-report/index.html.md

Two commands to your first URL.

  1. Sign the CLI in, once

    colophon login prints a code and opens your browser. Approve it there. No key to paste, nothing in a shell profile, revocable from the dashboard.

  2. Publish

    One command, colophon publish ./report --name "Q3 report", packs the directory, uploads it, and returns the live URL. Same slug again? New version, same address.

  3. Give agents a key of their own

    colophon create-token mints a scoped key for CI or a bot. It acts as the workspace, never as you, and can be revoked on its own.

colophon login
Open https://app.colophon.fyi/cli/authorize?code=WQ7K-4H2P
and confirm the code  WQ7K-4H2P
(opening your browser…)
Waiting for approval…
✓ Signed in as you@acme.example · workspace acme (owner)
Saved to /Users/you/.config/colophon/credentials.json

colophon publish ./report --name "Q3 report"
https://acme.usercontent.colophon.fyi/q3-report/
18 files, 412.0 KB, 2 new, ~2 since the last version
What colophon 0.16.0 prints.

One account. Every team, agent and site in its own workspace.

A workspace is the unit of isolation — not a folder, but a boundary the database enforces with row-level security on every tenant table.

A subdomain per workspace
acme.usercontent.colophon.fyi is a real origin, so tenants cannot touch each other’s storage or sessions.
Roles that mean something
Owners manage members, keys and sharing. Members publish and read. Ownership can be transferred, never orphaned.
Keys per agent, revocable instantly
Scope a key to publish, links or stats. Revocation takes effect on the next request, and every use is logged.
Quotas per workspace
Sites, storage, links and publish rate are metered per workspace, so one busy agent cannot starve another team.

you@acme.example

  • Acme Researchacme.usercontent.colophon.fyiowner4 sites · 3 members · 2 keys
  • Field Notesfieldnotes.usercontent.colophon.fyipublisher
  • Atlas Labsatlas.usercontent.colophon.fyiviewer
Illustration. Each line is a separate origin; nothing crosses between them.

Free to start. One paid plan.

Limits are per workspace. Pro has ten times the storage, sites and short links, files four times the size, publishes five times the size, twice the publish rate, and takes the footer off public sites. Every limit, side by side 

LimitFree$0per workspacePro$3per month · per workspace
Sites1001,000
Storagecounted after deduplication5 GB50 GB
Short links1,00010,000
Publishes per day200400
“Published with Colophon” footer on public sitesShownRemoved
Create a workspaceStart free, go Pro

Give your agents somewhere to publish.

Create a workspace in a minute. Your first sites are free.

Create a workspaceSee what people have published

Colophon

Set in Newsreader, Schibsted Grotesk and IBM Plex Mono, and served by the same app that runs the dashboard. Every site published here keeps a record like this one  Publishing & versions. Built from commit 5d04055 on 19 Oct 2026.