Vault
Each machine has an encrypted credential vault (AES-256-GCM). The key is held by the platform, not stored on the machine's disk.
Agents use credentials without seeing them:
browser_loginfills and submits a login form, matching the credential by URL, and handles TOTP codes.vault_type_secrettypes a username, password or TOTP code into the focused desktop app.vault_listreturns names, URLs and usernames only.
#REST
| Method | Path | |
|---|---|---|
GET |
/api/machines/{id}/vault |
List credentials (no secrets) |
PUT |
/api/machines/{id}/vault/{name} |
Create or update: url, username, password, totpSecret, notes |
DELETE |
/api/machines/{id}/vault/{name} |
Delete |
GET |
/api/machines/{id}/certificates |
Client certificates in the browser: holder, validity, auto-select sites (no keys) |
DELETE |
/api/machines/{id}/certificates/{name} |
Remove a certificate |
GET |
/api/machines/{id}/extensions |
Browser extensions: ID, name, version, source |
DELETE |
/api/machines/{id}/extensions/{id} |
Uninstall an extension (an ID, or the slot of an uploaded one) |
curl -X PUT https://burrowbox.dev/api/machines/2f6aeedcd3/vault/github \
-H "Authorization: Bearer $BURROWBOX_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://github.com/login", "username": "bot@acme.com", "password": "…", "totpSecret": "JBSWY3DPEHPK3PXP"}'
In the dashboard, the Vault panel of a machine lists its credentials (and whether each has a password or 2FA), its certificates and its browser extensions, and deletes any of them. Secrets themselves are never shown.
For platforms: store each customer's credentials in that customer's machine. They never leave it.
Digital certificates (.pfx, e.g. ICP-Brasil A1) are stored the same way. See Digital certificates.