Security
Know how Envlet handles every value.
Each variable is encrypted on its own, resolution tokens are narrowed to one environment, and every resolution is recorded without placing values in the audit log. Encryption keys can rotate, organizations can require TOTP, and deletion keeps resolution history for 13 months.
Protection at storage, access, and resolution
Trace the path from stored ciphertext to the command that receives a resolved environment.
Encryption
Each variable has its own ciphertext
Envlet encrypts every value with AES-256-GCM under a per-project data key.
Context binding
Ciphertext cannot move between contexts
Envlet binds each encrypted value to its project, environment, and variable name. Decryption fails if it moves to a different context.
Key rotation
Rotation keeps every project on the current encryption key
Envlet rotates encryption keys while each project's encrypted variable values stay in place.
Token storage
Raw tokens appear once
Envlet shows a raw token only when it is created. The database stores its digest. Every resolution token is scoped to one project and one environment, and every token expires.
Two-factor access
Require TOTP for every organization member
An organization can require each member to enroll an authenticator app. A member who has not completed TOTP cannot access an organization that requires it.
Resolution audit
Audit records identify keys, not values
Every resolution records the identity, project, environment, source, timestamp, and key names. Secret values never enter the audit record.
Audit retention
Keep resolution history for 13 months after deletion
Before an organization is deleted, Envlet archives its resolution records as JSONL without secret values. The archive expires after 13 months.
One-time shares
A share closes by first read or by deadline
Send one value or a small set without creating an account for the recipient. You choose the expiry when you create the share: it closes after the first successful read, or it stays readable until a deadline you set.
Current boundaries
Use the limits in your security decision
These capabilities do not exist today.
No self-hosting
Envlet cannot run inside your own infrastructure today. Do not plan a self-hosted deployment for version 1.
No SSO or SCIM
Enterprise SSO and SCIM provisioning are not available today. Plan identity administration without them.