Your code stays on your machines.
Agents run on computers you control. Patchkin carries a terminal view and small records between them and your browser. Here is exactly what goes where.
A plain table.
| Data | Where it lives | Does Patchkin see it? |
|---|---|---|
| Your source code | On your machines and your git host | Not stored. File names and line counts only, and only when governance is on. |
| What you type | In the terminal on your machine | Streamed to your browser over TLS. Not recorded. With end-to-end encryption on, Patchkin’s servers cannot read it. |
| What an agent prints | In the terminal on your machine | Streamed to your browser over TLS and not stored, with the two short exceptions below. With end-to-end encryption on, Patchkin’s servers cannot read it. |
| Waiting alerts | Sent by your machine when an agent stops on a question | Up to 200 characters of the question, with password-like values replaced. Kept up to 30 minutes so the web app can show it to your team, and never put in notifications. Machines with end-to-end encryption send nothing. |
| Continue elsewhere | Read from your machine when you move a session | The recent output (about 6,000 characters) and, for Claude Code, the conversation file are passed through Patchkin to the other machine. Held in memory for the transfer, not stored. Only the fact of the handover is recorded. Machines with end-to-end encryption are skipped. |
| Commits | Your git host | Branch, commit id and subject, author, changed file names and counts. |
| Secrets in diffs | Your git host | The kind and the place. The value is never stored. |
| Test and lint runs | Your machine | Pass or fail and timing. Never the output. |
| MCP and instruction files | Your machine | Server names and commands with secrets removed. Never file contents, environment variables or headers. |
| Usage | The tool that reports it | Cost and token counts. Never prompts or responses. |
Designed to need very little trust.
Outbound only
The program on each machine opens an encrypted connection out to Patchkin. You open no inbound ports and need no VPN.
Encrypted in transit
All traffic uses TLS. Turn on end-to-end encryption for a machine and the terminal is unreadable to Patchkin’s servers.
Sign-in you control
Two-factor sign-in, OpenID Connect and SAML single sign-on, SCIM provisioning, and roles for owners, admins and developers.
An activity log
Administrative actions in the product are logged, so you can answer who changed what.
Scoped tokens
Tokens for pipelines and for usage reporting can do one thing only: ask the governance question, or report usage. They cannot read your data.
Verified updates
The program checks each update against a published checksum and confirms its version before swapping itself, and keeps the old one if anything fails.
Governance that respects the team.
Visible to developers
Your organization has to confirm it told people what is recorded. Developers see that notice and always see their own activity.
Encrypted machines are left out by default
If you chose end-to-end encryption to keep a machine private, governance does not record its git activity unless your organization explicitly opts in.
Security questions.
Can Patchkin run commands on my machines?
Only when you or a teammate you have given access starts or drives a session from the web app, which is the point of the product. The program only accepts instructions from your organization’s connection.
What if a teammate leaves?
Remove them in the app, or let your identity provider do it through SCIM. Their access ends.
What happens to our data if we stop?
Remove your machines and turn governance off, which removes the hooks. Ask us about deleting your organization’s records.
Can we review the design?
Yes. Talk to us and we will walk you through it.
Have a security questionnaire?
Send it over. We would rather answer it than have you guess.