Give agents permission,not passwords.
Boundveil is a local encrypted vault evolving into a project access layer for agents. Exact-action approvals and redacted receipts remain behind published security gates.
- Local vault today
- Agent access in development
- Account ≠ vault key
- GitHub
- Vercel
- Cloudflare
- Supabase
- Codex
- Claude Code
The access boundary Boundveil is building toward.
The desktop vault is local today. Typed agent capabilities, exact approvals, provider execution, and receipts ship only after their security gates pass.
The hosted account is not your vault key.
Website login is separate from vault decryption. Plans, linked devices, teams, and approvals remain visibly unavailable until their authorities are connected.
- 01Rust cryptographic boundary
Vault keys, stored-secret reads, and TOTP output stay in Rust; the webview receives masked metadata and redacted copy receipts.
- 02No secret-returning agent tools
The current local bridge never returns stored secrets. Future agent actions must remain narrow and provider-aware.
- 03Honest revocation
Revocation blocks future authority; it never promises impossible remote erasure of copied data.
Local access stays yours. SaaS adds coordination.
Preliminary monthly packages for validation—billing is not live and prices are not final.
Your trusted execution layer belongs on your device.
Windows desktop first. A signed, direct-download Android APK follows after its secure-storage and update gates pass.