The platform — what Witbitz provides
Every collaborative AI app needs the same things: a room people share, an assistant inside it, storage, sign-in, permissions, a way to use outside services safely. Witbitz provides them as one platform, so your app can be a static page. This page is the map; each line links to its page.
What the platform provides
Rooms
| Spaces | A persistent room: members, one shared thread, shared state, an assistant. Opened by link, gated by sign-in or invite. SDK |
| Members and admission | Open rooms, verified rooms (allow-listed emails or @usernames), owners and admins, members changed in place. Identity and admission |
| Embedding | A Space inside another site or app, talking to the page around it. Embed |
The assistant
| Turns | The assistant answers when members post; its reply streams into the room. How a turn runs |
| Tools and widgets | Your app's functions as tools; web search, places, files; results that render as maps, charts and your own widgets. How a turn runs |
| Private assistants | Each member's own assistant beside the shared room, crossing to it only with the member's approval. SDK — private lanes |
| Approvals | An effectful action is proposed; it runs only after a member approves. SDK — proposals |
| Outside agents | Claude Code, Grok and other agents talking to a member's assistant, and taking jobs from it. Outside agents |
| Cloud computers | A coding agent on the person's own computer in the cloud — an attested enclave only they can open, its files sealed, its hours on their key. SDK — cloud computers |
| Models | Frontier models in standard rooms; open-source models on confidential compute in confidential rooms. Privacy tiers |
Data
| Sealed storage | The conversation, documents and files, sealed to the room's key; the server holds ciphertext. Trust model |
| The room as a store | Rows in named collections, sealed like the conversation; the assistant queries them with SQL. SDK — the store |
Users
| Accounts | Email sign-in, the user's rooms on every device, an encrypted backup only they can open. Accounts and recovery |
| Connections | API keys, OAuth grants and MCP servers, kept in an attested enclave and spent through calls a member approves — or, for MCP tools granted auto, on their own. Connections |
| Voice | Press-to-talk dictation and reading replies aloud. SDK — voice input |
Trust
| The confidential tier | Turns inside a measured enclave the device verifies first; answers signed with what produced them. The confidential tier |
| A verifiable client | Reproducible releases logged in a public transparency log; every module pinned by hash. Verifying the client |
| Checks anyone can run | The admission gate, the egress lock, the sealed store, the reproducible build. Verify it yourself |
How it is built
In the browser, the app is split into realms the browser keeps apart — the vault that holds the account, the Kernel worker that holds room keys and does the cryptography, the frame that draws the screen — so a bug in the screen cannot reach a key. The app as an operating system.
On the server, a room's turns run in the standard tier or inside the confidential tier's enclave; credentials live in a separate always-on enclave, the Sentinel; storage holds only sealed records. The server can refuse service; it cannot read a room.
Your app is a static page that reaches only Witbitz. It is not backendless — Witbitz is the backend — but it is one backend, shared by every app, constrained and inspectable, instead of an opaque server per app.
The reference app: Spaces
Witbitz Spaces — a multiplayer AI room, on the web and installable on any device — is built on this same public surface. Its guide is the platform as its users see it.
What you can build
The shape of the rooms is often the product:
| Shape | For example |
|---|---|
| One governed room — an organisation's assistant serves a person, and the organisation cannot read the sessions | customer service, a bank advisor, telehealth intake |
| A professional with a private back room — a shared room with the client, a private one to confer | a teacher, a doctor and a scribe, a lawyer |
| Two sides, each with its own assistant — each prepares privately, they meet in a shared room | negotiation, procurement, mediation |
| Many people, one assistant | group planning, a family council, a community |
| A personal assistant that travels — your assistant joins others' rooms with scoped permissions | a personal assistant, a shopping agent |
Access
The SDK is open: any static page can open, read and post in a room. Creating rooms from your own site needs a tenant
(SDK — do I need a tenant?); the /v1 platform API is invite-only during the beta. Email
hello@witbitz.chat.
Machine-readable source: platform.md · Generated 2026-10-27T07:05:42Z · build f301388c · every doc in one fetch: llms-full.txt (HTML)