Duplicates breed
Someone can't find the page — or doesn't look — so they start a new one. Every failed search becomes a duplicate, and every duplicate makes the next search worse.
The knowledge base for teams who create with AI
Describe what you need and Claude builds it — documents, slide decks, clickable prototypes, controlled policies, contracts to sign — far quicker and more expressive than typing into a wiki box. Then it all lives in one place engineered to stay current, findable, and trustworthy, instead of decaying into a swamp of stale pages nobody believes.
Have a room link? Open it and sign in with your work email. No link yet? Ask whoever invited you.
Every wiki starts tidy and ends a swamp. Not from neglect — from how they work. Three failures compound until nobody trusts what's inside.
Someone can't find the page — or doesn't look — so they start a new one. Every failed search becomes a duplicate, and every duplicate makes the next search worse.
"I know we wrote this down." Search returns ten pages and no way to tell which one is current. So people stop trusting the answer and interrupt a colleague instead.
Nothing knows which docs are unread, unowned, or superseded — so nobody archives anything, the "cleanup sprint" is never scheduled, and entropy wins.
Bolting an AI search box onto a swamp just answers confidently from stale pages. The fix has to start earlier — where the knowledge is made.
A wiki gives you a text field and asks you to do the rest. Rooms gives you Claude as the writer: you say what you want in plain words and get a finished, on-brand artifact — with a live preview — in the time it takes to explain it.
The same sentence can become far more than a page:
youYou
aiAssistant
No other knowledge platform is present at the moment a document is born. Rooms is — so it prevents the decay at the source instead of cleaning it up later.
As you start a doc, the system recognizes when one already exists and steers you to it.
"This looks like the doc Alice started in March — continue hers instead?"
Ask in plain English and get the current answer with its source cited — scoped to exactly what you're allowed to see. If it doesn't know, it says so.
A live picture of your content's health — what's verified, owned, fresh, or dead — with a one-click curation queue to fix what isn't.
Ownership is captured when a doc is made. When someone leaves, the system flags every document they owned and prompts you to reassign it — health never depends on one person staying.
Not a black box. Every suggestion carries a visible reason, every automated action is logged and reversible, and you set how far the system goes on its own. Humans stay sovereign over their knowledge.
Because Claude is there the moment a document is born, everything you make is captured as structured knowledge from the first keystroke: the finished page for people, and the plain text and meaning behind it for AI. One corpus, written and read by the same intelligence.
Documents, decks, policies, contracts — created in plain words.
captured as text + meaning, indexed the moment it's saved
Open a link, confirm an email code, and read the on-brand document — nothing to install.
Pull the relevant text — not whole files — scoped to exactly what that person is allowed to see.
The same knowledge, created once — projected to whoever's reading, human or machine.
Why it matters: search and answers are fast and trustworthy because the meaning is already there — and the AI tools your team already uses can reason over your rooms without dragging whole documents around.
Rooms is a new shape of tool: a small web console with Claude connected as the writer. Three places you touch it — and most people only ever touch one.
Connect once, then ask in plain words. Claude drafts your documents and decks with a live preview and saves them into the right room. This is the one place content is created or changed.
Needs Claude. Nothing to design or format yourself.
A light web app is where you run the place: create rooms, invite people and set who can do what, apply your brand, track share links, watch what's read, and drive review and sign-off.
Opens in any browser. Sign in with your work email.
A room is a private web page. Invited people open a link, confirm their email with a one-time code, and read the finished documents — nothing to install, no account to create.
Needs only a browser and an invited email.
No servers, no logins to hand out, no IT project. Claude writes, the console runs it, the browser reads — all hosted at the edge, so a room is just a fast, private web page.
The new medium, in full. From a one-pager to a signed contract, make it, brand it, control it, and share it in plain words — no technical know-how, no design tools. All of this is live today.
Create
Tell Claude what you need — a one-pager, a guide, a polished report — and it writes and formats it for you, refining as you talk. Start blank or from notes you already have.
Describe a deck and get a full-screen, on-brand slideshow you step through with the arrow keys — present it live or share it like any other document.
Show a prospect "here's what we'd build" with a working HTML mockup — clearly marked "illustrative only" so no one mistakes it for the finished product.
Everyone gets a personal workspace only they can see. When a draft is ready, move or copy it into the right room in one step — it picks up that room's brand and rules automatically.
Sales & marketing, prospect, and client rooms hold documents, decks, and prototypes side by side — the right collateral for wherever a deal is.
Set your colors, fonts, and logo once and every document and deck picks them up. Change the brand and everything re-skins at once — or derive a palette from your website.
Control & prove
Define exactly how your brand reads and looks as versioned standards. Point each room at the right one, and they're applied as Claude writes and corrected on save — so everything stays on-brand without anyone policing it.
Let edits go live instantly, or hold them as drafts until you press publish — your choice per room. Every version is kept, and readers only ever get the one you meant.
Make a controlled room: documents are versioned and move through review, approval, and recorded acknowledgement. Reviewers are notified the moment work is waiting and see it all in one My tasks list.
Name your audiences once, then distribute a published policy in one step — by Slack or email. The record shows exactly who it went to, who's acknowledged, and who's overdue. The answer an auditor actually asks for.
Spin up a deal room per client, describe an NDA, MSA, or SOW, and send it for signature. Everyone signs in the browser with a one-time code — and when the last party signs you get an executed PDF and a certificate of completion.
Leave notes, questions, and change requests on a draft — anchored to the text — that readers never see. Feedback stays with the team until you're ready to publish.
Share & see
Add people by email and they're in — confirmed with a one-time code each visit, no accounts and no passwords. You decide who opens each room and can change the list anytime.
Get one document to someone outside the room with a private link that opens with no sign-in. Name each link, see how often it's opened, and switch it off anytime.
Know how much your content is opened — by room, document, and shared link — and, for signed-in readers, exactly who has read it and when.
A room is closed until you open it. You decide who reads each one, share single pages without giving away the room, and take any of it back whenever you want.
Every room starts private. Add people by email, decide who can open each one, and change the list at any time. Nobody sees a thing until you let them.
Readers confirm their work email with a one-time code each visit. Nothing to create, nothing to reset, nothing for you to hand out — external partners included.
Send a single document by a private link that opens with no sign-in — then switch it off the moment you want it gone. A link can never expose the rest of the room.
Turn a room into a controlled one and every change is versioned and runs through review, approval, and acknowledgement — then prove exactly who a policy went to, who read it, and when.
The things people ask before their first room.
You don't type into a box and format by hand — you describe what you want and get a finished, on-brand document, deck, prototype, or contract. And it's built to stay trustworthy as it grows, instead of filling up with stale, duplicate pages.
Yes — trust-weighted search and cited answers in plain English, scoped to exactly what you're allowed to see, so verified and current content outranks the graveyard. If it doesn't know, it says so rather than guessing.
No. They open your link and confirm their email with a one-time code. Nothing to install, no password to manage, no sign-up.
To write content by chatting, yes — you connect Rooms to your Claude app once. To run rooms, invite people, brand them, and share, you just use the web console in any browser.
Only the people you add. Every room stays private until you invite someone, and you can change who's in it — or remove anyone — at any time.
Make a controlled room. Documents are versioned and move through review, approval, and recorded acknowledgement, with re-review you can schedule — then distribute the published version to a named audience and get a per-person record.
Yes. A deal room lets you describe an NDA, MSA, or SOW, then send it for e-signature. Everyone signs in the browser with a one-time email code, and you get an executed PDF and a certificate of completion when the last party signs.
As private web pages served from the edge on Engineering11's infrastructure — fast to open anywhere, with nothing for you to host or maintain.
Describe it to Claude, run it from the console, and your people open it in any browser. No design tools, no accounts, no IT project.
Have a room link? Open it and sign in with your work email.