Local-first agent access

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
BOUNDVEIL / ACTION REQUESTDESIGN TARGET
CX
Codexrequests a provider action
req_8f42
ACTIONDeploy preview to Vercel

nimbus-dashboard · preview · eu-central

Repository
acme/nimbus
Branch
fix/auth-flow
Environment
PREVIEW
Expires
in 08:42
PARAMETER BINDINGsha256: 7d18…c04b

The credential stays on the trusted device.

PLANNED INTEGRATIONS
  • GitHub
  • Vercel
  • Cloudflare
  • Supabase
  • Codex
  • Claude Code
Access without exposure

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.

01
Project context, not a credential drawer

Organize access by client, project, and environment so humans and agents operate inside the same boundary.

02
Approvals bound to the exact action

Actor, tool, provider, resource, parameters, time, and budget are hashed into one immutable approval record.

03
Receipts without secret leakage

See who requested, approved, and executed an action—plus its result—without logging reusable credentials.

  1. 01Agent requestNarrow typed operation
  2. 02Exact approvalImmutable parameter hash
  3. 03Local executionCredential never returned
  4. 04Redacted receiptResult without secret data
Security model

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.

Read the threat model
  1. 01
    Rust cryptographic boundary

    Vault keys, stored-secret reads, and TOTP output stay in Rust; the webview receives masked metadata and redacted copy receipts.

  2. 02
    No secret-returning agent tools

    The current local bridge never returns stored secrets. Future agent actions must remain narrow and provider-aware.

  3. 03
    Honest revocation

    Revocation blocks future authority; it never promises impossible remote erasure of copied data.

Pricing hypothesis

Local access stays yours. SaaS adds coordination.

Preliminary monthly packages for validation—billing is not live and prices are not final.

Local
$0

Your encrypted local vault and essential offline workflows.

  • Encrypted desktop vault
  • Plaintext local merge export
  • One primary device
Pro
MOST USEFUL
~$15/ month

Planned: one user · encrypted sync · approval workflows

  • Planned encrypted sync
  • Planned approval workflows
  • Planned expanded history
Studio
~$49/ month

Planned: up to five seats · client workspaces · policy routing

  • Planned five-seat limit
  • Planned shared workspaces
  • Planned policy templates
Desktop first

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.

macOS · Linux · Android later