4.1Notes & wiki

A wiki your whole team edits together, in the same second.

Docs and a company wiki with live, multi-cursor co-editing. Link a note to a task, a person, or another page, and keep the thinking next to the work it produced.

Start free Read the docs

app.elliptic.com/wiki/launch-runbook

Launch runbookWiki

Ada

Theo

5 editing now, synced

YjsConflict-free CRDT co-editing

MultiCursor presence, in real time

[[ ]]Wikilinks across the workspace

SSESynced over one realtime relay

4.2How it works

A document that keeps up with the room. Co-editing, links, and one live relay underneath.

Here is what each part looks like in practice.

4.2.1Co-editing

Many cursors, one document. No merge conflicts, ever.

Co-editing runs on Yjs, a CRDT, over a realtime relay that lives next to the API. Everyone sees everyone's cursor and edits as they happen, and concurrent changes merge without a conflict, even after a spell offline.

Conflict-free editing on a CRDT (Yjs)
Live cursors and presence for every editor
Concurrent edits merge cleanly, offline then online

app.elliptic.com/wiki/launch-runbook

Launch runbookWiki

Ada

Theo

5 editing now, synced

FIG 4.1

4.2.2Wikilinks

Everything links to everything. Notes, tasks, people, and pages, one graph.

Reference a task, a person, or another page with a mention. The link is bidirectional, so a task knows which notes discuss it, and a note knows which tasks it spawned. Knowledge stops being a dead end.

Mentions and wikilinks across the workspace
Bidirectional backlinks, kept in sync
A note can become the source of a task

launch-runbook.md

# Launch runbook

Owner: @ada  ·  Tracking: [[DEMO-42]]

When CI is green on [[DEMO-42]], flip the
launch flag and post in #launch.

---
backlinks
  <- DEMO-42 (task)
  <- Weekly platform sync (meeting)

FIG 4.2

4.2.3One relay

The same sync that powers the page powers the board and the inbox too.

The realtime relay runs in-process next to the API and fans changes out over server-sent events. The mechanism that keeps two cursors in step is the mechanism that keeps every surface in Elliptic live.

One relay behind notes, boards, and inboxes
Updates pushed over SSE, never polled
Everything stays org-scoped and private

realtime

// a keystroke becomes a CRDT update
doc.transact(() => title.insert(7, "today"))

// the relay fans it out over SSE
event: doc.update
data: { "doc": "launch-runbook",
        "actor": "ada", "v": 5142 }

FIG 4.3

4.3Capabilities

Knowledge that stays connected, instead of rotting in a folder somewhere.

Live co-editing

Multi-cursor editing on Yjs, with presence, so a doc is never locked to one person.

Wiki and docs

A structured company wiki and free-form notes, both first-class and searchable.

Mentions and wikilinks

Link a note to a task, a person, or another page, and the reference stays live.

Bidirectional backlinks

Every page knows what links to it, so context is never one-directional.

Notes as sources

Turn a note into the source of a task, keeping the thinking next to the work.

Org-scoped and private

Every page carries an org id, so a note can only ever be seen inside its workspace.

4.4For agents

Agents read and write the wiki over MCP. The same pages your team keeps, kept current.

An agent can read a page for context, draft a new one, or update a runbook, all over the MCP server and all scoped to one organization.

company-brain MCP

get_note(note="launch-runbook")        # read for context
create_note(title="Postmortem: 1.0 launch",
            body="## Timeline ...")
update_note(note="on-call", body="...")    # keep it current

Built for the way your agents and team work. Available today.

Start free Talk to us