1time – Zero-knowledge secret sharing with E2E encryption
1time – Zero-knowledge secret sharing with E2E encryption
I started this 8 years ago to learn Go. The idea was simple: a secret sharing tool where you don't have to trust the server at all. Secrets are encrypted in your browser (AES-256-GCM) before anything leaves your device. The key lives in the URL fragment (#), which browsers never send to the server. Key derivation uses HKDF-SHA256 with separate keys for encryption and auth. No tracking, no cookies, no accounts. Open source (MIT). Runs on a $10 VPS — Go stdlib, Redis, static Next.js. CLI included: printf 'db_password' | 1time send Self-hosting: 4-line Docker Compose (amd64 + arm64). Would love feedback on the crypto approach and UX. Live: https://1time.io | Source: https://github.com/shingrus/1time
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Incorrect prediction on native model
Similar products
Zero-Knowledge Proofs in WebAssembly
A zero-knowledge VM with only one instruction
Semantic AI with Zero-Knowledge Encryption Absolute Privacy
Occson – a zero-knowledge configuration store
Zero Knowledge Documents (on Dropbox)
Zkshare – PIN protected secret sharing with client-side encryption
The FPGA Zero-Knowledge Playground
Orchid Mantis – A PoC in Rust for Zero Knowledge Proofs of Exploit
RocketShare – Zero-knowledge encrypted file sharing
Zero-knowledge encrypted file sharing