Your code. Encrypted. Sovereign. Unreadable by anyone but you.

404 is a private code repository. No Git. No cloud. No one holding your keys but you. Every file encrypted with vetKeys before it ever leaves your device.

401 of 404 spots remaining

No credit card required. 100MB of encrypted storage included.

Why 404?

GitHub calls it private. We call that a setting.

On 404, private means your code is encrypted end to end, stored on sovereign onchain infrastructure, and mathematically inaccessible to us, to anyone.

Every file you store in 404 is encrypted before it leaves your device, using a system called vetKeys.

What vetKeys does

vetKeys are threshold derived cryptographic keys. Your data is locked with a key that no single node ever holds in full. The only way to decrypt your files is with your identity, and only you have that.

Why it matters

Unlike cloud storage where the provider holds the keys, 404 never has access to your plaintext data. Not us, not the infrastructure, not anyone with a subpoena.

NSP alignment

This architecture is designed to meet all six principles of NSP (Native Stack Privacy), verifiable, composable, and sovereign by default.

Your code is private the way keys are private. The encryption is not a feature. It is the foundation.

How it works

Create a private repo

Name your repository. It starts private by default, visible only to you.

Upload your code

Add files or import a zip archive. All content is encrypted with vetKeys before it leaves your device.

Share securely with vetKeys encryption

Grant access via encrypted, revocable invitations. You hold the keys. No one else does.

Built for security researchers, journalists, and privacy-native developers.