Oarbank documentation
Oarbank spreads batch jobs across the computers you already own: Macs, Linux machines and Windows PCs, mixed in one fleet. A coordinator plans the work and an agent on every node runs it, while host protection keeps each computer usable for the people who use it. What the jobs compute is defined by modules, built with the open-source module SDK (Apache-2.0), which talk to Oarbank’s source-available core only through the versioned public contracts documented here. The Oarbank product page gives the overview, and the guide How to run batch jobs on the idle computers you own compares the ways to spread work across your own machines.
The current release is Oarbank 2.11.1, with module SDK 1.8.0: installers for macOS, Linux and Windows are on the release page, and Get started sets up a fleet. The source is public: the core is at roeehrl/oarbank and the module SDK at roeehrl/oarbank-sdk.
Choose your path
Section titled “Choose your path”Platforms
Section titled “Platforms”Nodes and the coordinator run on these platforms.
| Versions | Architectures | |
|---|---|---|
| macOS | 15 or later | Apple silicon; Intel for nodes |
| Linux | systemd, glibc 2.39+, Linux 6.2 or later | x86_64, arm64 |
| Windows nodes | 10 version 1809 or later, 11 | x64, ARM64 |
| Windows coordinator | x64: 10 version 1809 / Server 2019 or later; ARM64: 11 | x64, ARM64 |
A module declares the platforms its runner supports as tokens: darwin-arm64, linux-amd64, linux-arm64,
windows-amd64 and windows-arm64. What each computer needs is in
Requirements; the token rules, portable paths and per-platform declarations are in
Platforms.
Learn more
Section titled “Learn more”- How Oarbank works: coordinator, nodes, modules, certification, sandboxing, host protection and signing.
- Specification: the normative public contracts between modules and the core.
- Manifest fields and JSON Schemas: generated from the SDK’s typed models.