One ID. Your own tools.

Replaces: Google Meet · MS Teams · Zoom

The only way to make a call sovereign is to own the media path. Jitsi does SFU video on your hardware; TURN is what makes it work behind a firewall.

self-hosted web app · Jitsi Meet + coturn (TURN/STUN) on the customer's own network

Recording to disk + the existing /api/chat/speech-to-text endpoint gives transcription without a third party.

Hard part: TURN capacity, bandwidth, and browser permissions. No email-native path: a live call cannot be a reply.

Replaces: Otter · Gemini notes · Teams recap

A recording becomes a transcript, then notes, decisions and action items, then a page in your vault. No new app: you email the file and get the summary back.

email-native · NGARi ID + /api/chat/speech-to-text + the vault

This is the one meeting capability that is genuinely ours and already wired.

Hard part: Speaker diarisation and long-recording chunking are not solved yet.

Replaces: Google Docs · Word online

Real-time multi-cursor co-authoring is a decade of work. We do not have parity and will not pretend a textarea is Google Docs.

install (Collabora Online) · Nextcloud + Collabora Online (CODE) for real-time co-authoring

What we DO have is drafting and rewriting by email, which covers most documents that are written once and reviewed twice.

Hard part: OT/CRDT co-editing, comments, suggestions, and the docx fidelity problem.

Replaces: Google Drive · SharePoint

File sync, sharing and versioning are commodity — buy the commodity, own the disk.

install (Nextcloud) · Nextcloud on customer storage; optional S3-compatible backend

The vault already ingests and indexes documents per identity; Nextcloud would own bytes, the vault owns meaning.

Hard part: External sharing links, mobile background sync, and ransomware recovery.

Replaces: Airtable · Notion databases

This is where we should win rather than clone: Airtable sells a grid, we can sell a record that has a receipt chain, a commission attached, and an agent that maintains it from email.

email-native + web · Our CRM/PM core over the existing work ledger (BOS) and contacts census

Already real underneath: 983 contacts, the commission ledger, proposals with a verify gate, and a nightly research agent. Missing: the grid UI and permissions.

Hard part: Views, formulas, automations and permissions — the boring 80% of Airtable.

Replaces: Notion pages · Confluence

A page is a document with a title and links; we already write those from email.

email-native (WIKI command) · The vault's page writer (WIKI) + static publishing

WIKI command is live in the identity service; the reading surface is not.

Hard part: Nested pages, backlinks and search across identities.

Replaces: HubSpot · Salesforce (lite)

A CRM is a list plus a history plus a next action. Ours already records the commission consequence of each step, which no CRM we know of does.

email-native · Contacts + commission ledger + pipeline stages over BOS

The census, the 90-day attribution window and the Corps bridge exist.

Hard part: Email sync, deal stages, and not becoming a spreadsheet.

Replaces: Monday · Asana · Linear (lite)

A task without a definition of done is a wish; ours refuses to start one. That is a feature Monday cannot copy without changing its model.

email-native · BOS work ledger with done_when, blocked_at and the proposal gate

work.py, proposals.py and the nightly research staging are live.

Hard part: Board/kanban views and dependency graphs.