Build a distributed system
by describing it in English.

OfficeSpeak turns a plain-English description into a small, always-on team of software workers — an office — that passes messages, keeps state, and reacts to the world. No programming needed to try it. Runs on the DisSysLab engine.

This site has examples of many offices

See examples of different types of offices.

30+
example offices, running today
24 gallery apps + 9 direct examples — real code, actually run
Connections
sources & sinks
External data sources and sinks plus 500+ MCP servers
Snapshots
crash-recovery
global snapshots — no lost or duplicate messages on resume
English
for building and debugging
describe it, correct it, and later ask it to explain a checkpoint or a run — all in plain English

A gallery of examples

A sample of what's in DisSysLab's gallery — see FEATURES.md for the full, categorized list.

Built-in distributed-systems features

The properties every generated office has.

🔁

Distributed termination detection

Detects termination in networks that may have feedback loops.

📸

Consistent checkpoint & resume

Periodic global-snapshots — dsl run --snapshot-interval N.

🕵️

Explain a run, in English

dsl explain-trace merges every agent's activity log, ordered by a physical-time based logical clock, into one causal story — narrated by Claude, not a template.

🗂️

Explain a checkpoint, in English

dsl show-checkpoint — what every worker's memory held, and what messages were still in transit, at one instant.

🧪

Isolated worker testing

Test one computational worker alone on hand-picked inputs to localize a bug — no concurrency in the picture.

Two stages. First stage requires only Claude

Stage 1

Describe it

No installation, no Python, no terminal. A conversation with Claude on claude.ai builds your office, explains it back — including what it assumed — and lets you correct it in plain English.

▶ Watch the 2-minute tour
Stage 2

Run it for real

Turns your description into a running system. Needs Python.

▶ Watch the 2-minute tour