An operating system for the physical world.
Abstract.
Samoza OS is a distributed runtime for Spaces — sandboxed
WebAssembly programs that read sensors, drive actuators, persist data,
coordinate with AI agents, and present user interfaces. Spaces are
packaged as MEX archives, scheduled across a mesh of
cloud and edge zhosts, and operated through zshell.
The whole stack is open and built by Samoza Research.
Build apps. Run a cluster.
The docs split cleanly. If you write apps that run on Samoza OS, head right. If you operate the cluster they run on, head left. Most teams do both.
Five ideas. Everything else is depth.
You don't need the full reference to start. Five concepts carry the model; the rest of the docs builds on them.
SPACE
A sandboxed WebAssembly process. Each space has a type — UI, IO, DATA, CHAT, CALL — that constrains what it can do.
TOPOLOGY
A collection of spaces and the paths that connect them. Topologies are the unit of deployment.
MEX
The portable, signed archive that packages a topology, its WASM binaries, UI assets, and spatial layout into one file.
ZHOST
A physical or virtual host running the Samoza stack. Zhosts mesh together; one is elected super node, others run workloads.
MESH
The peer-to-peer network connecting zhosts. Routes messages between spaces wherever they happen to run.
ZSHELL
The operator's interface. status, mesh ping, topo submit, cluster zhosts, spaces.
Samoza OS is open. Anglish is open. Everything you ship is signed.
The Samoza OS specification is open — the MEX format, the Guest ABI, the mesh protocol, the topology schema. Anyone can implement against them. Samoza Research builds the reference implementation in Go (with TinyGo for guests), and ships it under an open license.
The high-level authoring story is Anglish — the language between code and prompt. Anglish compiles down to MEX, so everything Anglish authors becomes a normal Samoza OS deployment.