Skip to content

Apps

Lasbolt has one server and several clients. Pick the clients that you need. They all use the same vault.

There are no store releases yet. You use the web app in a browser. You build the other clients from source. Each page says how.

What each client can do

WebmacOSiOSAndroidExtensionCLI
Read itemsYesYesYesYesSearch, fillYes
Make and change itemsYesNoNoYesNoYes
E2E foldersYesYesYesYesYes, through the agentYes
AutoFillNoSafari extensionSystem AutoFill (paid team)BrowsersYesNo
Biometric unlockNoTouch ID (own build)Face IDFingerprint or faceNoNo
Decide approvalsYesNoYes (password login)Yes (password login)NoNo
Wait for an approval-Yes-YesYesYes (exit code 7)
Work offlineNoYesYesYesYes, through the agentYes
Manage shared spaces and teamsYesNoNoNoNoNo

Notes:

  • E2E folders. In the web app the server sends the code, so its E2E promise is weaker. See Web app.
  • AutoFill. The extension fills and does not save. Android also saves logins from the browser. The iOS extension fills items that are not in E2E folders and do not ask before each use.
  • Approvals. An item can ask before each use. Only the web app, and a phone that signed in with the master password, can decide. The macOS app and the CLI wait, and you decide in the web app.
  • Offline. The native clients keep a local copy and sync when the server is reachable. The browser extension uses the agent of the CLI or the macOS app.

Connect the clients

The macOS app, the extension and the CLI share one agent on the same computer. You sign in once. The phones sign in on their own. In the web app, use Settings, then Devices, to add a phone or to see and remove devices. See Devices and approvals.

Last updated on