End-to-end encrypted source control

Your code stays a secret.

GitE2E encrypts commits, file paths, and branch names on your machine before they reach this remote. Use the familiar Git workflow while the server stores ciphertext.

Sign in Request access →

AES-256-GCM · X25519 key sharing · zero plaintext on the remote

zsh — ~/acme/payments

➜ gite2e init # create an encrypted repo ✓ generated repository key AES-256-GCM ✓ local identity wrapped with X25519   ➜ gite2e push origin main → encrypting commits, paths, and refs → uploading ciphertext objects ✓ remote updated · plaintext never left device

The remote is blind

Repository content is encrypted by the GitE2E client before upload. A remote breach yields ciphertext.

Git stays familiar

Clone, add, commit, push, and pull with a workflow designed to feel native to existing teams.

Keys belong to teams

Per-repository keys can be granted, rotated, and revoked without sharing a server-held password.