A LiveKit-like realtime application platform built on MoQ over WebTransport

Tablebox cannot be used yet: its hosted service is not open. The documentation describes what it does and how to build with it.

Read the documentation

What Tablebox is

With MoQ, participants (people and apps) publish data and media at any path, and read them.
With the PaaS, developers decide who may read and write which paths, manage them, and see usage.

Tablebox also runs five programs for every project, which read and publish the way participants do: Ingress, Egress, Aggregation, Persistence and Agent.

What Tablebox adds to MoQ

Connection and rights

With MoQ alone: a relay only decides a connection by token.

With Tablebox: projects and keys, links, who may read and write which paths, set by tokens or by rules that need no backend, and the reasons for a refusal.

Connecting

Management

With MoQ alone: none.

With Tablebox: a management API and Console for projects, keys, environment variables, removing participants, closing a range of paths, usage and limits.

Managing projects

Aggregation

With MoQ alone: one writer per path.

With Tablebox: shared state that many people change at once is merged, so everyone reads the same thing, and each writer learns whether its change was applied.

Aggregation

Persistence

With MoQ alone: only the latest content, while its publisher is there.

With Tablebox: chosen content is saved to the developer's storage and given back to people who come later, even after everyone has left.

Persistence

Egress

With MoQ alone: content flows and is not kept, and nothing reaches what does not speak MoQ.

With Tablebox: audio and video are recorded to the developer's storage and sent to streaming services.

Egress

Agent

With MoQ alone: none.

With Tablebox: an AI people talk to by voice or text and can interrupt, running on the developer's AI provider account.

Agent

Ingress

With MoQ alone: devices that do not speak MoQ cannot publish.

With Tablebox: streams from streaming software and broadcast equipment are taken in and published at a path.

Ingress

Guarantees

Removed people, and the people connected to a range of paths that was closed, are cut off. Use stops when it reaches the limits the developer set.
Exchanges keep going while the management side is down.

Scale

Adding servers adds the people and paths that can be handled. People who read and write the same paths work together whichever server they are connected to.
100,000 people can connect to one range of paths. What each person receives depends on what that person reads, not on how many people there are.