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   ➜

Trusted-client migration

Bring repositories in without exposing their contents.

Install the GitE2E migration skill to scan every ref, move large files into encrypted LFS, and push ciphertext from your own machine. GitHub or GitLab credentials and repository plaintext never enter this server.

Read the migration contract

public skill · checksum verified Copy

$ curl -fsSL https://platform.gite2e.com/skills/gite2e-repository-migration/install.sh | sh

1. 01
   Run the installer. It downloads the public skill and verifies its pinned checksums.
2. 02
   Restart Codex. Configure https://platform.gite2e.com/mcp with a local bearer token that has write:repository.
3. 03
   Start the import. Invoke $gite2e-repository-migration and follow the encrypted migration checks.

Never paste a provider token, repository key, or plaintext into MCP.

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.