Build confidential AI apps on Witbitz.
Witbitz is the backend for confidential, multiplayer AI apps. You ship a static page; Witbitz runs the shared room, its members, the assistant, storage, sign-in and approvals — sealed so that neither Witbitz nor you can read your users' rooms, and built so that anyone can check that.
What Witbitz gives you, and how it works.
What the platform provides, a complete app in ten lines, and what happens in a room when someone speaks.
A static page is a complete app.
One module your page imports, and one for your server. Start with the SDK page; the rest is there when your app needs it. Every call: the reference.
SDK
Load it, the ten-line app, the examples, and a map of the pages.
RoomsRooms and messages
Create and open a room; read, send, reply and react; attachments; live updates.
The assistantThe assistant
Its instructions and model, when it answers, a turn you can hold, tools, voice.
AuthorityApprovals
The assistant proposes; a member approves; only then does anything run.
MembersPeople
Sign-in, gated rooms, admins and owners, direct chats, changing members in place.
KeysWhere the keys live
The confidential tier and its proofs, split-key rooms, vault mode.
Privacy you can check, not just claims.
Neither Witbitz nor the app's own builder can read the users' rooms — a property you check from the code, not a promise you take. Each page says what is Production, Beta, Implemented or Design; the whole map is Status, and the checks run in your own terminal on Verify it yourself.
Trust model
The double blind: what is sealed, what each side checks, and what is not hidden.
The choicesPrivacy tiers
What every room gets, the choice between confidential and standard, and the protections you can switch on.
In useThe confidential tier
A room's turns inside a measured enclave the device verifies first; every answer signed with what produced it.
The clientVerifying the client
Reproducible, logged releases; every module pinned; the server checking the client.
In the browserThe app as an OS
The vault, the key worker and the screen kept apart, so a bug in the screen cannot reach a key.
The accountAccounts and recovery
Keys made on the device, a backup only its owner opens, and the ways back.
Who may enterIdentity and admission
The link, gated rooms, signed entries, owners and admins, changing members.
Spent, never seenConnections
An API key, an OAuth grant or an MCP server, sealed in an attested enclave and spent only through an approved call.
Other agentsOutside agents
Claude Code, Grok and others reaching a member's assistant over A2A or MCP — the member decides.
Run it wherever you need.
The same reproducible runtime, hosted by Witbitz or in a boundary you control. What is Production, Beta, Implemented or Design: Status.
Deployment options
Hosted, in your own cloud or on-premises, and with no outside network at all.
The mapStatus
Every capability, its status and where it is documented, in one table.
Hosted by Witbitz
Access, tenant keys, the public OpenAPI, and the evidence you can check.
Your boundaryEnterprise and on-premises
The runtime with your own model, storage, records, secrets and identity provider.
Zero egressAir-gap mode
What AIRGAP=1 changes, what still works, and what needs a local replacement.