Witbitz docs HomeTrustAll docs

Overview — build confidential AI apps around Spaces

Witbitz is the backend for confidential, multiplayer AI apps. You ship a static page; Witbitz runs the rest — the shared room, its members, the AI 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.

html
<script type="module">
  import { Witbitz } from 'https://witbitz-spaces.pages.dev/sdk/3.10.0/witbitz-sdk.js'

  const space = await new Witbitz({ tenant: 't_…' }).createSpace({   // your tenant id
    agent: { name: 'Helper', instructions: 'You help a small group plan and decide together.' }
  })
  space.on('message', (m) => console.log(m.from, m.text))  // everyone's messages, the assistant's too
  await space.send('Plan us a weekend in Kyoto')
  console.log('Share this:', space.shareLink)              // the link is the invitation
</script>

That page is a complete private, multiplayer AI app: no server of your own, no database, no key handling. Creating rooms needs a free tenant and the page's origin declared once (Do I need a tenant?); opening a room someone shared needs neither.


What you get

A room — the Space People, your app and an AI assistant together; one shared thread and shared state; members by link, sign-in or invite.
An assistant that acts Tools, web search, maps and files; results that render as widgets; a private assistant for each member.
A coding agent The person's own cloud computer: a coding agent in an attested enclave only they can open, its sessions and approvals in your app.
Storage The conversation, documents and your app's own records, sealed to the room.
Accounts Sign-in by email, the user's rooms on every device, a backup only they can open.
Connections Your users' API keys, logins and MCP servers, spent by the assistant but never seen — each call approved by a member, unless you let a server's read-only tools run on their own.
Proof Reproducible, logged releases; an attested enclave for confidential rooms; checks anyone can run.

The whole map: the platform.

The guarantee

Privacy you can check. Rooms are sealed to keys made on the user's device; your page has no backend and reaches only Witbitz; every release is a reproducible build of published source. Neither Witbitz nor the app's builder can read the users' rooms — and you can verify it yourself.

Each room runs in one of two tiers, chosen by the app:

Confidential Standard
Where a turn runs A measured enclave your device verifies first Witbitz's server, while a member is active
The model Open-source models on confidential compute Frontier models; the turn reaches their vendor

Details: privacy tiers.

Next

  1. Build — the SDK: the example above, then members, tools, the store and private assistants.
  2. Understand — the platform · the trust model.
  3. Check — verify it yourself.

Machine-readable source: overview.md · Generated 2026-10-27T07:05:42Z · build f301388c · every doc in one fetch: llms-full.txt (HTML)