An item is picked
The lane on your machine pulls the backlog and cuts a fresh working copy for the item.
// self-hosted · any ai · your machines, your keys
The Farm runs the AI of your choice on machines you own. The AI writes the code; your machine tests it and pushes it. Your git credentials never reach the AI.
runs onyour hardware
git tokenyour machine only
aiclaude · codex · gemini · +
Every item runs on a machine you own, in a working copy of its own. The AI session can edit and commit there — nothing more. Testing, merging and pushing to your repository are done afterwards by the farm itself, with a token only the machine can read.
The lane on your machine pulls the backlog and cuts a fresh working copy for the item.
After the session ends, the farm re-runs your gate, rebases onto main and pushes — with the one credential that never left the machine.
Builds, tests and working copies live on your Linux, Mac and Windows machines. We never host your code.
Git tokens and AI keys sit in owner-only files on the host. Never in git, a log or the hub — the hub can hand a key over, never keep it.
A change the gate fails never reaches main. It waits on a branch for you, with the session that made it.
Sign in with the subscription you have, or paste an API key. Choose the AI per machine, per project, even per item — and switch from the panel without touching a lane.
Anthropic. The farm’s full feature set: remote control from your phone, usage metering, per-file access rules.
Runs in its own workspace sandbox. Sign in with ChatGPT or an OpenAI key.
Sign in with your Google account or a Gemini API key.
Grok, Mistral, DeepSeek, OpenRouter — or a model on your own GPU through Ollama, LM Studio, llama.cpp or vLLM.
one farm · claude for the app · codex for the api · a local model for the docs
aider · goose · qwen code — coming
Your tokens are your money, so the farm spends them carefully. Routine items run on a lighter model and step up only when a retry needs it. Every session has a context and turn budget. A small scout maps the code before the main session reads anything, and big files and images are handled in short sessions of their own. Nothing sits polling while it waits. And a usage governor pauses the lanes before your weekly allowance runs out.