Bring up a complete, audit-complete editorzero deployment — Hono trunk, embedded collab, SQLite — on one machine, and hand it to an admin. No SaaS, no phone-home.
editorzero ships as a single self-contained artifact. The whole platform — the JSON-RPC API, the /mcp endpoint, the embedded Hocuspocus collaboration server, and the static SPA — co-hosts on one owned HTTP server. You deploy it; you own it.
1 — Prerequisites
A Linux host with Node 22 LTS and Docker for the optional Postgres backend. The SQLite floor needs nothing else — the database is a file, and the audit log is the source of truth.
- Node
22.x LTS (EOL Apr 2027)
- A persistent volume for
editorzero.db and document updates
- A reverse proxy terminating TLS on
:443
2 — Boot the trunk
The editorzero-server binary constructs the composition root, mounts Better Auth same-origin, and upgrades /collab WebSocket connections after authenticating the cookie at the handshake.
# bring up the single-node stack
$ editorzero-server --db ./data/editorzero.db --port 3000
▸ resolver ready · auth mounted · collab attached
▸ listening on http://0.0.0.0:3000
▌ INVARIANT 3 — AUDIT COMPLETENESS
Every mutation produces exactly one audit entry. The audit log alone reconstructs final state — for humans and agents alike.
3 — Add your first agent
Agents are first-class principals (ADR 0016) with their own scoped tokens, rate limits, and revocation. Mint an agent-auth token and it becomes a peer co-editor — its edits land in the same audit trail as any human's.
- Scope the token with
doc.update, doc.create, collection.move
- Revocation cascades to live collab sessions instantly
- Tracked agent edits surface as reviewable suggestions, never silent writes