Where your code stays
The AI developers work on your team’s computers, or on a server you control. The code they read and change is your code, on your machines, in your GitHub or Bitbucket. The platform never receives it: no copy of your source is uploaded to us, and nothing of it is sent to anyone else.
Where the project record lives
The project record — the requests, the tasks, the decisions, the proof — is a set of plain files. Hosted, it lives at app.beegait.ai in a repository per project, mirrored one way to your own GitHub or Bitbucket so you always hold a full copy. On your own server, it never leaves the building. Either way, export is a copy of the files: nothing is locked in a database you cannot read.
The helper program on a developer’s computer
Beegait’s helper program (the product calls it the runner) is a small program installed on a developer’s computer, paired once with a short code. It only ever calls out to the platform; it opens no door into your network and accepts no incoming connection. It runs the AI developers on that person’s own subscription, with the tools they already have installed (Claude Code or Codex); its setup completes only once one of them is found on the machine. One helper program can serve the whole company from a server you control, and only your people can reach it.
What leaves your company
- Your organisation never stores an AI provider key on the platform. Your AI developers run on the credentials your developers’ machines hold.
- Our GitHub App reads repository names and registers deploy keys. It cannot read your files.
- Bitbucket: no Bitbucket credential is stored on Beegait — repository names are listed and keys registered by the helper program on your computer, with its own sign-in.
- The helper program opens no inbound port. It long-polls outbound, runs typed jobs, and its setup completes only when a supported AI tool — Claude Code or Codex — is found on the machine: it says what it looked for and offers a re-check.
- One job per project at a time. A collision is an honest refusal, never a silent retry.
- A workspace can forbid code quotes in what its AI developers send back: answers, summaries and progress lines describe the code instead of copying it, and the helper program replaces any code block before it leaves the machine.
- A repository can be connected runner-only: Beegait keeps its address and nothing else, no key and no token. Every check and every read of it happens on your own machines, with their own access — on the runners of the person who asked; a teammate’s machine never reads it for them.
- A crash report leaves only when someone clicks Send report in the helper program: an error number, the versions and the helper program’s own recent log, with every token removed on the computer first. Never a prompt, never an answer.
- Document ingestion quotes files, tokens and minutes before it reads anything.
- The hosted platform is served behind TLS by a single public front; the application and its database are not exposed.
- The free trial runs the same way as the paid plans: on your team’s own computers, never on a key of the platform.
Your own server
The same product installs on your server: an installer, a signed licence, and an updater that talks outbound only to the release channel. If the licence lapses, a curtain closes the product. It never blocks your files: your repositories keep serving, and your record stays yours.
Reading the source
The engine and runner ship as compiled binaries under the Beegait EULA. On an enterprise plan you can still have the code read: on request, an auditor you name reads the source of the version you run, under a non-disclosure agreement, on our premises or over a screen-share. No copy of the source is handed over, and there is no source escrow.
The full data-protection statement is on Data protection; the exact terms for your technical team are on For your technical team. Host controls: the list, with owners →