Blueprint
Collaboration
Local-first collaboration: every device holds a full replica, works offline, and the server never decides the order of content.
Updated
Three ways to work together
All three use the same data and the same merge rules. The only difference is when the merge happens.
| Mode | Who | How it merges |
|---|---|---|
| Real-time | People with people, people with AI | Merges automatically; you see others’ changes as they type |
| Offline, then merge | Someone offline, or one person on several devices | On reconnect, each side fills in what the other is missing, then merges automatically |
| Draft | AI works on a draft, a person reviews | Merges when the person accepts it, keeping everyone else’s changes made in the meantime |
Four layers of merging
| Layer | What it does | Example |
|---|---|---|
| ① Automatic merge | Merges by field type (see Data model) | Two people type in the same paragraph; both are kept |
| ② Deterministic repair | Fixes anything invalid after the merge with fixed rules, so every replica computes the same result | Two clips on a timeline overlap and get pushed apart by rule |
| ③ Conflict object | Leaves what can’t be repaired, and needs judgment, for a person to choose | Two people rewrote the same page while offline |
| ④ Lease | Things that can’t merge at all are claimed briefly before editing | Two people painting the same pixels on the same layer |
The server does as little as possible
- Every device has a full replica. Working alone needs no server at all.
- The sync server handles members, permissions, persistence, assets and history compaction. It does not decide the order of content: changes merge deterministically on every device, so they end up identical whatever order they arrive in.
- That keeps the server light. It is Kition Server: run it on your own machines, or let Kition host it for you as Kition Cloud. The sync protocol,
kition-sync/1, is open. - Clients are not trusted: the server checks every change’s author, write permission and format.
Details designed for people
- Per-person undo: undo reverts only your changes, not your teammates’; where a teammate edited after you, their value stays.
- Presence: teammates’ and AI cursors and selections show in real time but never enter history.
- Permissions: each person edits, comments or only views.
Where collaboration comes from
Real-time co-editing runs through Kition Server or Kition Cloud. It is the paid part of Kition; everything else in the kits is free.
- Kition Cloud: hosted, billed by usage in Kition credits. See developer.kition.ai/collaboration.
- Kition Server on your own machines: free for companies of up to 8 people, with no key.
- Kition Server plans: Business $3,000 a year, Enterprise $15,000 a year. See developer.kition.ai/pricing.
- Kition One, the self-hosted team workspace, is built on the same kits: free for up to 8 people. See one.kition.ai.
The protocol itself, the Kit Harness Protocol (KHP), lives at kitharness.org.