We build with the thing we built.
An agent platform written in Rust: a domain core that depends only on traits, capability-scoped WASM plugins, a workflow engine as the single execution path, and a LAN job mesh that spreads work across whatever machines are on the network.
- Deployment shells
- In-process: C-ABI, embedded in a host applicationDaemon: A long-running core nodewasm32: The plugin host, sandboxed
- Renderers
- React + Tauri: Windows, Linux, AndroidSwiftUI: macOS, iOS, iPadOS, in progressHeadless: Node core, CI
We did not set out to build a product. We kept hitting the same wall on agent work: no execution boundary, no evaluation gate, no way to scope what a tool could reach. Building the platform was cheaper than working around its absence. It is now how we deliver, and the clearest thing we can show you about how we think.
A core that depends on nothing
Domain logic sits behind traits for storage, inference, credentials, git and compute. Each environment supplies its own adapter, so swapping a backend is an adapter, not a migration.
Plugins beside the core, not inside it
Extensions are wasm32 components that speak through exactly one door. A plugin may call the host; it may not reach around it. What it may call is a capability grant, checked at call time.
One execution path
Every run goes through the workflow engine: validated graphs, resumable state, cancellation, and an event history you can read afterwards. There is no second way to execute something.
Work spreads across the network
Peers discover each other on a LAN, advertise free memory, take leases and stream results back. An unreachable machine drops out of scheduling instead of failing a job.
Work goes where there is capacity.
Peers find each other, advertise what they have free, and take leases on work. A machine that stops answering leaves the schedule instead of failing a job. The same scheduler runs across a room or across regions; this is the view from inside the app, projected onto a map.
A world map showing the Marbl3 fabric: one node connected to 9 others across Asia, Europe, the Americas, Africa and Oceania, 8 of them reachable, with 7 jobs in flight. Illustrative topology, not a list of offices.
Illustrative topology, drawn by the renderer from the Marbl3 desktop app with example nodes. It shows where the platform can place work, not offices we keep.
This is the evidence, in place of a client list.
We are early enough that our own platform is the most honest demonstration of how we work: where we draw boundaries, what we automate, and what we refuse to leave implicit.
Want a walkthrough?
We will happily give you an hour on the architecture: the plugin boundary, the workflow engine, the mesh. Whether or not there is an engagement in it.