Anything that touches plaintext is open source
The encryption engine, the daemon, and every language package can see secrets in plaintext - so all of them are MIT-licensed and auditable before any sales conversation. No NDA, no trust-us.
Audit the code, not the marketing
Kryptic's security model is designed to be verified, not believed: everything that can see a secret in plaintext is open source, and the server-side platform only ever stores ciphertext.
Principles
The rules the architecture is built on
No custom cryptography
AES-256-GCM, P-256 ECDH, and Argon2id from platform crypto libraries, composed - never reimplemented. The engineering lives in the key hierarchy, envelope format, and rotation behavior.
Our servers cannot read your secrets
Values are encrypted end-to-end: your browser, daemon, or CI runner holds the org key, and the server stores only ciphertext and key grants sealed to your devices. There is no server-side decrypt path to misuse.
Memory-only on the client
The daemon holds secrets in memory with a 5-minute TTL and serves them over a local OS socket that never crosses a network. Nothing is written to disk on developer machines.
Cryptography
What protects your secrets
End-to-endEach organization has a 256-bit org key that exists only on your clients. It reaches your browser, daemons, and CI machines as P-256 sealed-box grants; the server stores ciphertext it cannot open.
At restSecret values are AES-256-GCM envelopes (96-bit nonces, 128-bit tags) encrypted client-side under the org key before they are sent to us.
Context bindingEvery ciphertext is bound to its secret and environment via associated data - rows cannot be swapped in storage undetected.
Key rotationOrg keys rotate client-side: an admin’s browser re-encrypts every value under a fresh key and re-grants it to active devices in one atomic change. Lost passphrases recover via a one-time recovery code.
Passwords & machine secretsArgon2id (64 MiB, 3 iterations), versioned parameters, constant-time verification. Refresh and invitation tokens are stored only as SHA-256 hashes.
In transitTLS 1.3 to the platform; local daemon-to-package delivery over a unix socket (macOS/Linux) or named pipe (Windows) with user-only permissions.
Sessions15-minute access tokens, rotating refresh tokens, org-configurable absolute session expiry, per-device revocation.
Verify it
The open-source boundary
The encryption engine ships with a SECURITY.md describing the full key hierarchy - what is derived from what, where each key lives, and exactly what the server can and cannot see - plus the test vectors that prove it. The daemon, the CLI and all seven language packages (.NET, Node.js, Python, Java, Go, Ruby, C++) are MIT-licensed in the same organization.
Read the code on GitHubAudits
We publish what our audits find
Trust should be earned in public. We run adversarial reviews of the code that runs on your machine and publish every finding alongside the fix we shipped, including the issues we had to correct. It is the clearest way to show that we are actively hunting for weaknesses rather than waiting for someone else to.
See the latest auditDisclosure
Reporting a vulnerability
Report suspected vulnerabilities to [email protected]. We acknowledge within 48 hours, keep you informed while we fix, and credit reporters who want to be credited. Please do not open public issues for security reports.