Oarbank
Spread batch jobs across the computers you already own
- macOS
- Linux
- Windows
Add a node in one line · Node · macOS and Linux
curl -fsSL https://github.com/roeehrl/oarbank/releases/latest/download/oarbank-install.sh | sudo sh Self-hosted · No telemetry · Source-available, free for noncommercial use · Version 2.11.1
One computer runs the coordinator; the others become nodes that take its jobs and report results. Everything runs on your network: no Codonic service, no telemetry. Source-available: free for personal and noncommercial use; commercial use needs a licence from Codonic.
Inside the app
A look inside
-
One campaign, every operating system.
A campaign’s jobs spread to every node with room. Someone is using the Mac, so its share waits.
Made-up computers from the project’s demo fleet.
-
Results from every node, checked.
Each result names its node and system.
A node’s results count only after it passes each module’s doctor and golden jobs, whose answers are known.
-
Your own work comes first.
This per-node rule pauses fleet work on Studio while TextEdit is in front.
Protection only ever acts on the fleet’s own jobs.
-
Modules, certified before they count.
Each kind of work is a module.
Nothing is enabled on install: review its sandbox grants, try it on one node, then promote it.
Built for the job
Who Oarbank is for
Owners of a few mixed computers
Idle computers, and batch work that splits: parameter sweeps, simulations, renders, benchmarks, test matrices.
Module authors
Package work once with the open-source Python SDK; any Oarbank fleet can install it.
Small teams that keep work in house
Data stays on your computers and network; commercial use needs a Codonic licence.
Capabilities
What it does
Mac, Linux and Windows nodes
Jobs go to the node with the CPU, memory and tools they need.
Host protection
A memory guard, per-node caps and app rules keep the owner’s own work first.
Every job in a sandbox
Seatbelt, Landlock and seccomp, or AppContainers confine each job to its own files and approved hosts.
Certified nodes, checked results
Nodes pass each module’s doctor and golden jobs before their results count; replicas catch drift.
GPU and AI batch work
Jobs go to nodes with the GPU API they need: Metal, CUDA, ROCm, Vulkan, OpenCL, DirectML.
Signed by you, end to end
Nodes talk over mutual TLS and refuse releases, updates or coordinator moves you didn’t sign.
Practical guides
Start with what you want to do
How to use the idle computers you own for batch jobs
9 minute read → PythonHow to run a Python script on multiple computers
7 minute read → Batch jobsBOINC or HTCondor for your own computers: what it takes
7 minute read → GPUHow to use your gaming PC’s GPU from your laptop for batch jobs
7 minute read →Version 2.11.1
Get Oarbank
Other downloads
Other downloads
Other downloads
curl -fsSL https://github.com/roeehrl/oarbank/releases/latest/download/oarbank-install.sh | sudo sh Downloads, checks the SHA-256 checksum, installs and joins. Fleet, Add machine… shows this command with your join code.irm https://github.com/roeehrl/oarbank/releases/latest/download/oarbank-install.ps1 | iex Same steps as the macOS and Linux script. Add machine… also gives Intune and Group Policy settings.For an Intel Mac
- Intel Mac x86_64
For ARM64
The short answers
Questions about Oarbank
How do I install Oarbank?
Install the coordinator package on one computer, open Oarbank Coordinator, choose Open web app and follow the setup wizard. Then, for each computer that runs jobs, Fleet, Add machine… in the console gives a join code and install commands. Full guide: docs.codonic.dev/oarbank/get-started.
What do I need to start?
Two or more computers that can reach one another: one Mac, Linux machine or Windows PC as coordinator, the others as nodes. The coordinator can be a node too.
Is Oarbank free and open source?
It’s free for personal and noncommercial use, and source-available, not open source. Commercial use needs a licence from Codonic (support@codonic.dev). The module SDK is open source under the Apache License 2.0.
Does Oarbank need the internet or a Codonic account?
No. The coordinator and nodes talk over your own network — a LAN, Tailscale, ZeroTier or any VPN — with no Codonic account or service. Modules reach only the internet hosts you approved.
Will it slow down my computer?
It’s built not to. A memory guard stops taking jobs, then evicts the fleet’s own, when free memory runs low, and you can cap cores, memory, jobs and hours. Nodes also back off while you work, on battery, and when hot on macOS and Linux.
Can a job read my files?
No. Every job runs in the operating system’s sandbox, reads only its inputs and module, and writes only its own folders. Network hosts, host tools, the GPU and containers are grants you approve per module version.
What kinds of work can it run?
Batch work that splits into independent jobs: local LLM batches and evaluations, image generation, transcription, renders, test suites, coding-agent sandboxes, parameter sweeps, simulations, benchmarks and data processing. Each kind of work is a module.
Does Oarbank use my GPU?
Yes, for modules you approve. GPU jobs go only to nodes that report a usable API: Metal, CUDA, ROCm, Vulkan, OpenCL or DirectML. Containers can use the GPU on Linux, on Windows through WSL, and through Vulkan on Apple silicon Macs. Tested hardware: docs.codonic.dev/oarbank/operate/compatibility.
Which platforms does it run on?
Nodes: macOS 15+ on Apple silicon or Intel; Linux 6.2+ (6.12 for the full sandbox) with systemd and glibc 2.39+; Windows 10 1809+ or 11. The coordinator runs on all three (Apple silicon on macOS). Opt-in Windows container jobs need virtualization on and WSL 2.9.3+.
What happens if a node goes offline in the middle of a job?
Its lease on the job runs out and the coordinator gives the job to another node. When the node comes back it takes new work, and an answer from the lease it lost is not counted.
How do I add many computers at once?
Fleet, Add machine… makes a limited-use join code for many machines. Its MDM tab gives a macOS profile, Intune and Group Policy (ADMX) settings, a Linux policy file and an Ansible example. Each machine waits for your approval unless auto-approve is on.
Can I use Oarbank with Claude Code, Codex or another AI agent?
Yes. The Oarbank skill teaches an agent to install, run, troubleshoot and build modules for Oarbank, asking before it changes anything. Install with npx skills add roeehrl/oarbank-sdk --skill oarbank -g, or oarbank@codonic from the roeehrl/oarbank-sdk marketplace in Claude Code or Codex. Agents without it: docs.codonic.dev/oarbank/llms.txt.
What happens when I replace the coordinator machine?
You move it. The new computer installs a standby from a build you signed, takes over after a time lock you choose, and every node verifies the move and follows it by itself.
Privacy by design
What Oarbank knows about you
- Oarbank collects nothing about you. There is no Codonic account, no analytics, no telemetry and no crash reporting.
- It runs entirely on your own computers and your own network. Nothing passes through Codonic.
- Your jobs, results, logs and settings stay on the coordinator and the nodes you run.