Witbitz · an app built on the platform

Witbitz Spaces

A room that keeps going. People post when they can; the AI agent answers on its own time. Share a link and someone is in — no account, nothing to install. Spaces is an application built on Witbitz — through the same public API anyone else would use, which makes it the working proof that the platform carries a real product.

What it does

Conversation that persistsAn encrypted ledger, not a session. Come back days later and it's there.
An agent that actsIt reads documents you share, searches, plans, and answers when it can.
DocumentsPDF, Word, Excel and CSV read as text — and it can generate a shareable PDF back.
Maps and placesA real vector basemap with English labels, place search, and routes.
Charts and diagramsRendered inline as widgets, not screenshots.
Bring a conversation inSeed a Space from an existing chat export.
Credentials it can use, not seeAttach an API token once; it lives in a measured enclave. The agent proposes a call, you approve, the enclave adds the secret. The model never holds it.
Talk to it from Siri"Hey Siri, Witbitz" — dictated text lands in the Space you name, sealed before it leaves the enclave that answered the call.

Every one of those is an ordinary platform capability — collections, artifacts, agent tools, widgets. Nothing in Spaces is a special case, and nothing here is reachable only because we built it. That's the point of showing it.

A coding agent you drive from your phone

On your own computerCode runs the coding agent (OpenCode) on your laptop or desktop. You start sessions, watch it work and approve each command or edit from the Spaces app, over a relay that carries only sealed bytes. Set it up
Or on a cloud computerNo computer of your own? A cloud computer is a virtual machine in an attested enclave that only you can open, with its files saved encrypted. Part of the Plus plan; open to invited accounts during early access.
A browser you can watchThe agent can open its own web browser. Watch it from your phone or computer, or take the controls yourself; on a cloud computer, the agent cannot see or use it while you hold them.
Private browsingTurn on private browsing, on a cloud computer or your own, and the agent's browser forgets cookies, logins and history every time it opens or closes.

How it works, what the connector will and will not do, and what Witbitz can see: Code — all the details.

Who can get in

A Space's identity, members and keys live in the link, not in an account server. On top of that you choose admission when you create it: open to anyone with the link, a specific list of Google accounts, or an emailed six-digit code. People can also be named by their @username — a public address they choose, so an invite or an allow-list never needs their email — and a verified Space lists its Members by the identity the server saw, never a typed name. Whether your email can be looked up at all is a switch in your settings.

The link alone is deliberately not enough on a gated Space — reads and writes are both refused without an allow-listed identity, even for someone holding the room key. That's the first thing you can verify yourself.

What the operator can see

Only your room's key can open the conversation — and Witbitz never holds that key. Read the store with full administrator access and you get bytes the platform can't unlock. Not "we won't look" — we can't.

What is not hidden, stated plainly: that a room exists, when it changes, and roughly how big each write is. Content is sealed; shape is not. And the model provider receives the text of a turn, because that is what the agent is for. The full scope →