How Optizen protects your credentials and keeps dangerous actions explicit.
Your master password encrypts all credentials stored on disk. Optizen never stores it in plaintext: it keeps only a slow scrypt hash, and five wrong attempts lock out that IP address for 15 minutes. Sessions expire based on the duration you set in Settings.
When re-auth is enabled, dangerous actions — deploys, rollbacks, deletes, env writes, and proxy reloads — require a fresh password check. Enable this in Settings → Session security.
After a successful re-auth, Optizen trusts that session for a configurable window (default: 15 minutes). You will not be prompted again within that window unless you restart.
Optizen never stores your private key — only the file path on the host where Optizen is running. Make sure that path is correct and the key has the right permissions (chmod 600).
Session elevations, security setting changes, and sensitive value reveals all appear in the security audit trail in Settings. Use it as an operator logbook, not just a compliance checkbox.
Turns on in Settings. Masks sensitive values across the dashboard — useful when screen-sharing or recording. Actual data is not changed, just hidden in the UI.
Swaps all dashboards to safe sample data — fake servers, projects, deploys, and telemetry. Useful for walkthroughs or screenshots without touching live infrastructure.
Every env and proxy file save creates a remote backup before overwriting the live file. Revision history is available in the file editor. If something breaks, you can restore the previous version.
Session duration, re-auth requirements, demo privacy, and demo mode are all in Settings. The audit trail is at the bottom of that page.