KyGit: a Git remote that cannot read your code
KyGit is a Git remote that cannot read your code. Your history is encrypted on your own machine before it leaves, under a key we never receive. What reaches us is ciphertext and a signed head, and all we can do with it is store it. You keep GitHub or GitLab as your primary, with collaboration, CI, reviews, and pull requests unchanged, and add KyGit as a second remote: a complete, continuously updated copy of your history that the storage provider itself cannot read. One install, then plain git push.
Why a remote that cannot read
Every major code host today belongs to a company whose models get better when it reads code. That is not an accusation about any particular host. It is a conflict of interest built into ownership, and ownership changes. Under a future policy, an acquisition, a training pipeline, a subpoena, or a breach, readable code is usable code, by anyone who can read it. You cannot fix that with a policy, because policies change hands with the company. You fix it with a key that never leaves your machine. Your unlaunched work stays unlaunched, and every app you have in the market has a copy that nobody can index, learn from, or be compelled to hand over.
What we cannot do with your code
Most hosting pages list what the host can do. KyGit is defined by what it can't, and each of these is a property of the design, not a line in a policy. We can't read it: run402 cannot decrypt your gitvault or repository history, so there is nothing on our side to index, train a model on, sell, or hand to whoever asks next. We can't hold it: with the mirror configured, your ciphertext replicates to a bucket you own, and if we disappeared tomorrow your repository is recoverable from a bucket listing and your keys, with an open-source tool and no server required. We can't change our minds: policies change hands with the company that wrote them, and ours cannot matter, including a future us after an acquisition, because we hold no key to change our minds with.
Built for your agents
Most privacy products are anti-AI, and most AI products are anti-privacy. KyGit is for your AI and against everyone else's. Your coding agent holds its own key envelope and works normally: plain git, no dashboard, no human in the loop. Everyone else's AI, including ours, sees ciphertext. And because the vault is durable, agents can do things with it. One agent can hand its exact repository state, dirty tree and all, to a different agent on a different machine, model, or vendor, with two commands and one pasted key. A working agent can invite a second one into the same state while it keeps working. The alternative was a human copying diffs between chats.
It's live
Install it with npm i -g @kychee/kygit, run kygit create, then push. The free floor is 1 GB of encrypted vaults with unlimited repos, and it never expires. There is no separate KyGit price: a vault's bytes count against a run402 tier's own vault quota. Like everything we build, KyGit runs on run402. The client is open source at github.com/kychee-com/run402, and an independently built verifier in Rust shares no code with it, so you never take our client's word. Start at kygit.com.
Kychee builds AI-native voice products and Open SaaS. Write to info@kychee.com.