How it works

Three roles. One workspace. Every deck on brand.

Codexroom holds your brand in code, hands your agent a typed library, and ships a watermarked link to your recipient.

The brand work your designers do once is the work the whole company reuses for a year.

Designers & brand owners

Author the tokens, templates, and chrome, then publish the library. Every deck reads from what they published.

Team members & agents

Compose decks from the library over a scoped key. The system rejects anything that drifts off-brand.

Recipients

Open a link watermarked to them, gated if you said so. The analytics show you who read what.

The walkthrough

Four steps, from brand book to read receipt.

Step 1 · Govern

Designers author the library. Codexroom enforces it.

Your designers open the governor IDE and define your brand in three layers. Tokens carry the raw values, the colour ramps, the fonts, the spacing units. Slot types define the typed contract every slide reads from: headline, metric, logo, quote, chart, body text. Slide templates carry the HTML scaffold, the per-template CSS, and the slot placeholders. A deck template wraps every slide with the chrome the brand wants to see on every page.

Every layer versions. Every change writes an audit log entry. Past decks render the way they rendered the day they shipped, even after the templates move on.

governance / tokensv4 · published
  • --token-accent#006DD5
  • --token-bg-canvas#0F2440
  • --token-font-display"Tiempos Headline"
  • --token-radius-card12px
  • --token-accent-soft#7FB3E8#5A9BDDdraft v5

d.okafor published tokens v4 · 12 templates re-rendered

audit log · every change versioned, nothing overwritten

Step 2 · Hand over

Your agent gets a scoped key and a typed library.

Codexroom runs a Model Context Protocol server. Your agent (Claude, Cursor, your internal stack) connects through OAuth. The user authorising the grant picks the scopes: read on tokens, read on assets, read on templates, write on decks, write on shares. That grant lets the agent compose and send, and stops it from changing the brand.

Example. A sales lead in Claude Desktop says, "Build me a 12-slide pitch for Acme, lead with the healthcare case study, password the share, expire it Friday." The agent calls Codexroom seven times. The reply is a link.

Claudecodexroom · connected

Build the Series B board deck from our Q3 numbers.

On it — pulling your Q3 metrics and composing on the board template.

Searched the data room · 3 sources
Composed 14 slides · board template
Validated · 0 brand drift

Series B — Board Deck

14 slides · ready to share

Reply to Claude…
Step 3 · Send

One link per recipient. One watermark per share. Up to five gates.

The recipient opens the link. The viewer renders the deck slide by slide in a sandboxed iframe, with their name in the bottom-right of every slide. They see this share only, and it expires when you said it would.

Set any of five gates per share before you send it: password, IP allowlist, origin allowlist, country allowlist, email verification, and a view cap. Each gate runs server-side, fails closed, and writes every rejection to the audit log. Underneath, three invisible channels fingerprint the HTML, so a leaked file decodes back to the share that produced it.

decks / fund-iii · new share

Recipient

Emma Walsh
emma@northfund.com

Access

Public
Password
Email verified

Visible watermark

Confidential
Leak traceabilityInvisible fingerprinting in the export
codexroom.com/v/9f3a…Save
Step 4 · Read

The deck reports back.

Every open writes an event. Every slide view writes an event. Every completion writes an event. Your analytics page shows a per-share session timeline and a per-slide engagement chart across every recipient. The deck that gets skipped on slide 4 is the deck you fix first.

analytics · fund-iii-decklive

24

Opens

4m 12s

Avg time

78%

Completion

Attention by slide

slide 1slide 7 · held 64s12

emma@northfund.comfinished · lingered on slide 7

deal-team@apex.vcslide 9 of 12

Optional · exports

Export when the recipient wants a file.

PDF rendering uses headless Chromium, so the result is pixel accurate to the viewer, the visible watermark stays in, and the share's fingerprint is written into the PDF metadata. PPTX uses structured generation, with the conversion limits called out on the download. Either format reaches the recipient who lives in PowerPoint.
viewer · codexroom.com/v/9f3a
3 / 12Download

Download as

PDF

High-fidelity print. Renders exactly what you see.

PowerPoint (.pptx)

Editable. Best-effort conversion — formatting may differ.

Getting started

One brand, or a portfolio of them.

However your team is shaped, you start the same way: encode the brand once, then let everyone compose from it.

In-house teams

One brand, one workspace. Your design team governs the library, your team and agents compose from it, and recipients open links watermarked to them. Start free and invite your team.

Start a workspace

Agencies

A workspace per client brand, billed together under one agency account. Govern each brand, compose for it, then hand the finished workspace to the client at the end of the engagement.

Talk to us about agency