Runs on
your servers
One Go binary on your machine, your cluster or your cloud. Your code stays in your environment.
Homebrew
brew tap qf-studio/pilot && brew install pilotInstall script
curl -fsSL https://raw.githubusercontent.com/qf-studio/pilot/main/install.sh | bashDocker
docker pull ghcr.io/qf-studio/pilot:latestThen run pilot doctor to check the setup.
Where it runs
From one laptop to a production cluster.
What stays yours
Your code, your keys and your logs.
Your code stays with you
Pilot runs where you deploy it. It calls only your tracker, your code host and the model API.
Docs →One worktree per ticket
Each ticket works in its own git worktree, away from your main checkout.
Docs →Destructive command guard
A hook blocks commands like rm -rf / and git push --force. It is a speed bump, not a sandbox.
Docs →Self-hosted or Pilot Cloud
The same Pilot. Run it yourself, or let us run it for you on a box only you use.
Self-hosted
Your code stays in your environment. Who reviews the PR: you.
Pilot Cloud
Your code and keys stay on a dedicated box only you use. We never share compute between customers. Who reviews the PR: you, from the Review needed lane.
License
Source-available. Read the code, run it and audit what it does.
BSL 1.1
- Use Pilot in production inside your organisation at no cost.
- Do not offer it to others as a paid hosted or embedded product that competes with Pilot Cloud.
- Organisations with fewer than 10 employees can use it for any purpose, hosted services too, until 90 days after they reach 10 employees.
- Each version becomes Apache 2.0 four years after its release.
Start
Run Pilot free in your terminal, or move the team to Pilot Cloud.