PLATFORM
AGPL-3.0 · SELF-HOSTED · YOUR KEYS

Inside the box

The platform all 54 applications are standing on.

The apps are the visible part. Underneath, the same pieces run for all of them — one cockpit, one queue, one credential vault, one set of databases. An app never ships its own copy; it reaches platform capability by declaring what it needs.

01 / The surface

Cockpit & ribbon

One shell for every app. The left ribbon is drawn from the app you opened, and the URL decides — never a cached preference.

Learn more →
02 / Connections

Connectors & the vault

308 hand-audited connector specs ship in the repo. Your token is encrypted per user, and the model never sees it.

Learn more →
03 / Work routing

Queues & the mesh

A request becomes a ticket, a ticket becomes phases, and phases are dispatched to accountable bot identities over durable streams.

Learn more →
04 / State

Databases

Four stores, each doing the job it is genuinely better at — and one of them is optional on purpose.

Learn more →
05 / Operations

Monitoring & self-healing

The stack watches itself, files its own incident tickets and does root-cause analysis on them — with the repair still gated on a human.

Observe-only by default Learn more →
06 / any-bot

Model harnesses

40 model providers wired in, hosted or local, on your keys — with a containment boundary that fails closed.

Learn more →
07 / Reach

Remote & edge nodes

A bot is an identity, not a location — and an identity can live on the desktop where your browser is already signed in.

Learn more →
08 / Interop

External agents (A2A)

Agents that are not yours can be given a scoped door into the swarm — and oshal bots can call out through the same protocol.

Shipped, default off Learn more →
09 / The wall

Security & isolation

Auth per route, credentials the model never sees, per-user data scoping, and a fail-closed gate between a commit and the public.

Learn more →