Arbiter is alive: the orchestration layer, now running
Arbiter is a working proprietary alpha: a local brain on your own GPU, configured multi-provider routing, durable interruption handling, and configurable remote control. Public binary release preparation is underway, and there is an 8-minute walkthrough.
A few weeks ago we wrote that Arbiter was in active development and not shipping yet. That was honest then. It isn’t accurate anymore. The orchestration layer is no longer a blueprint. It’s a daemon running on real hardware, and you can watch it work.
What actually runs now
- A brain on your own GPU. The model that decides how to route a task runs locally, on your machine. The decision layer makes no cloud call. It triages incoming work and answers what it can on-device.
- Provider-agnostic, by construction. Arbiter applies configured routing and scheduling policy to the accounts you connect. Add providers and the available routing choices expand, with nothing load-bearing.
- Work that survives a power cut. Long-running jobs are accounted and recoverable. Pull the plug mid-flight and the state isn’t gone. It’s preserved and picked back up, with the riskier kinds of work held for your explicit say-so rather than silently resumed.
- Configured remote control. Supported channel adapters can expose status, approvals, and stop actions when you configure them for your environment.
- A real command center. A native desktop GUI and a terminal dashboard show live status. Local IPC is the default surface; an authenticated HTTP control plane is optional.
Safety policy stays in the route
Routing can be constrained by configured safety policy so sensitive work is not decided on cost alone. The learned optimization layer is still being hardened for release.
Watch it run
Words only go so far for an orchestration layer. Here’s an unedited 8-minute walkthrough of the running daemon on a real machine: the routing, the live runs, and the approvals.
Prefer YouTube? Watch the walkthrough there instead.
Where it stands
Arbiter is a working proprietary alpha in IP hardening, licensing, and public binary packaging preparation. The agnostic-by-construction design, all the way down to a local decision brain, is the part we will not compromise.
It’s the layer that dispatches Warden, orchestrates TheAuditor, and leans on Curator for memory and BenchProctor for proof. The full scope is in Introducing Arbiter, the public release channel, or the RSS feed.