Security
What Geekbot can read, what it can change, where your code goes and how every run is contained and capped.
What each agent may do
The Reviewer is read-only by construction. Its runtime denies every tool except reading, searching and listing files, and the diff is computed before the agent starts, so it never runs git or any other command.
The Coder, the Bug Fixer and the Patcher write code, so they run in an isolated sandbox with their own checkout. They commit to a branch of their own and open a merge request. They never merge.
The Patcher decides what to update without the model: it reads your lockfiles and asks the public OSV vulnerability database, before the run and again after it, so the merge request lists only what the change provably fixed.
Chat writes nothing itself. Its tools call the Geekbot API as the person asking, and anything that changes code starts one of the agents above, with the same limits.
Where your code goes
In CI, the review runs on your own runner. The job exchanges a short-lived identity token from your forge for a model key, sends the diff and the files the agent reads to the model provider, and posts the review to your merge request. Your repository never reaches Geekbot’s servers. They receive the outcome: the verdict, the review as it was posted, who opened the merge request, its link and commit, and how long and how many tokens the run took.
With the GitHub App or the Bitbucket app, and for the Coder, the Bug Fixer and the Patcher, the run happens on Geekbot’s workers, in a sandbox that holds the checkout only as long as the run needs it.
Model requests go through OpenRouter to a provider of the model you picked that processes data in the EU, with zero data retention and no training on your data. If you point an agent at your own endpoint, those requests go there instead.
Keys and spending
Each run gets its own model key with a hard dollar limit, minted for that run and deleted after it. A runaway agent spends at most that limit.
Each organization has its own model workspace, so one customer’s usage never shares a budget with another’s.
Your organization owner sets monthly and daily limits for usage beyond the plan. Work stops at the limit rather than continuing on credit.
Credentials and data at rest
Tokens you connect (forges, trackers, error sources, MCP servers, model endpoints) are sealed with AES-256-GCM before they are stored and opened only when a run needs them.
Sign-in is through Google, GitHub, GitLab or Microsoft. Geekbot stores no passwords for customer accounts.
Changes to an organization’s configuration are recorded in an audit log.
Reporting a vulnerability
If you find a security issue, write to geekbot@geekcoders.cz. We will confirm we have it and keep you informed until it is fixed.