Codex
Security & ownership

Your knowledge stays yours. Finance stays behind a lock.

The Codex is designed around two ideas: sensitive knowledge should be genuinely restricted, and your company should own its data outright. Both are enforced, not promised.

SSO, not passwords

Sign in with your company identity provider (Microsoft Entra ID). Access is restricted to your verified email domain — outsiders never reach the door.

Role-based access

Read and edit grants are defined per folder and cascade down. Roles map people to what they can see. Admins see all; everyone else sees exactly what they're granted.

Enforced on the server

Permissions are applied before data ever leaves the server — not hidden with CSS. Restricted notes are never sent to a browser that shouldn't have them.

The AI inherits your rules

The assistant is handed only the notes the current user may read. It can't search, cite, or leak anything outside that boundary.

You own the data

Everything is plain Markdown in a vault you control — git-versioned and synced through your own OneDrive. Cancel anything and you still have all your knowledge.

Local-first privacy

The desktop app reads straight off your disk. No upload, no middleman — your notes stay on your machine, and it works with no network at all.

Trust model

Two front doors, one set of rules.

The web wiki and the desktop app share the same knowledge but suit different needs — and neither weakens the other.

Web wiki

Hosted and multi-user. SSO plus server-enforced role-based access means many people share one deployment and each sees only what they're allowed to.

Desktop app

Single-user and local-first. It reads the copy of the vault you already have on disk — private by construction, fast, and fully offline.

Own your knowledge. Control who sees it.

Sign in with your company identity, or run the Codex privately on your Mac.