Web console

The console at stillvault does everything the CLI does, in the browser. Browse the secret registry as a path tree, store a secret, review and approve release requests, and manage your team, devices, policies, audit log, and billing — all from one place.

Vendor-blind in the browser

The work that must happen client-side happens client-side. When you store a secret, the value is encrypted in your browser before anything leaves the page. The console only ever handles ciphertext and public keys. We hold nothing that can read a secret — the guarantee that holds in the CLI holds in the UI too.

What you can do

• Browse the registry as a path tree and inspect any secret’s metadata.
• Store a secret — sealed in the browser, sealed to your approvers.
• Review and approve release requests by role, so nothing is released until a named approver acts.
• Manage your team, devices, and policies.
• Read the audit log and handle billing.

Where the lines are drawn

A lease is granted to an agent only after the release it depends on is approved. The console shows you the request, who must approve it, and what the agent will be allowed to read — and records every step in the audit log.