ImageBramble
Get Bramble
Local-first password manager

Your passwords never leave your devices.

Bramble is a local-first password manager for your browser and phone. No account, no server holding your vault, no company to breach. You hold the vault, you hold the password.

macOS

A universal build for Apple silicon and Intel, signed and notarized. It checks for updates and installs them itself.

Download the .dmgVersion 0.6.0
or
brew install --cask bramble
  • No account
  • No tracking, ever
  • End-to-end encrypted
  • Open source

See it in action.

A look around Bramble. Open any shot, then use the arrows or your keyboard to browse.

  • Your vault

  • Pick a vault

  • Autofill on a page

  • Save a new login

  • Update an existing login

  • Editing an entry

  • Create a passkey

  • Sign in with a passkey

  • Settings

  • Unlock methods

  • Backups and import

  • Scheduled cloud backups

  • Device sync

Image

Everything a password manager should do. Nothing it shouldn't.

The same encrypted vault and the same Rust crypto core sit behind the browser extension and the mobile apps.

Encrypted on your device
Your master password derives the key with Argon2id, and every entry is sealed with AES-256-GCM. Encryption happens locally and derived keys are wiped after use.
No account, no server
Nothing to sign up for and no server holding your vault. There is no Bramble account to leak and no central database to breach.
Peer-to-peer sync
Share one vault across your devices directly, device-to-device, end-to-end encrypted. A relay only helps them find each other; it never sees your data.
Autofill everywhere
Detects login fields on the page in the browser, and registers as a native credential provider on iOS and Android so your logins show up in the keyboard.
Passkeys built in
Create and sign in with passkeys. They are stored as ordinary vault entries, so they sync between your devices along with everything else.
Biometric unlock
Unlock with Face ID, Touch ID, or Android biometrics, gated by the OS keystore, or fall back to your master password or a recovery code.
Breach check
Optionally check a password against Have I Been Pwned using k-anonymity, so only a partial hash ever leaves the device. Off by default.
Encrypted backups
Export an encrypted .bramble file any time, or point Bramble at Dropbox, any S3-compatible bucket, or your own WebDAV server. Only ciphertext ever leaves.
Private sync

Your devices sync straight to each other.

No cloud, no account, no middleman holding a copy of your vault. Pair two devices and they connect directly, exchanging the vault over an encrypted, mutually authenticated channel. The infrastructure that helps them find each other is yours to replace.

Direct and end-to-end encrypted
Your devices talk to each other over a direct, mutually authenticated channel. The vault stays encrypted under a key only they hold, so nothing readable ever crosses the wire.
Swap the signaling relay
Devices meet through a Nostr relay that only ever sees ciphertext and can't link it to you. Use the default, run your own, or point at any public relay that speaks the protocol.
Bring your own TURN
When a direct link is blocked, a STUN/TURN server relays the still-encrypted channel. Configure your own ICE servers, or stay strictly direct-only. Your call.
Backups

Backups you keep, on storage you already own.

Nobody else holds a copy of your vault, so keeping a backup is up to you, and Bramble makes it painless. Export an encrypted file by hand, or have it drop scheduled backups into storage you already run. Only ciphertext ever leaves your device, so the destination stores something it can't read and a stolen backup is useless without your master password.

Self-hosting? Point it at your own Nextcloud over WebDAV and your vault history never touches anyone else's servers.

Dropbox

Sign in once and let Bramble keep encrypted snapshots there on the schedule you pick.

Any S3-compatible bucket

Backblaze B2, Cloudflare R2, Storj, Wasabi, MinIO, and friends.

WebDAV, including Nextcloud

Your own Nextcloud, ownCloud, or Fastmail. Self-hosted, and answering only to you.

Or export by hand

Save an encrypted .bramble file anywhere: another drive, a USB stick, wherever you like.

One Rust crypto core

Serious cryptography, no backdoor.

Key derivation, encryption, and decryption all happen inside a single Rust core, compiled to WebAssembly in the browser and to a native library on iOS and Android. Because nobody else holds a copy of your vault, no one else can be compelled to hand it over.

Read the source

Argon2id

Memory-hard key derivation from your master password.

AES-256-GCM

Authenticated encryption for every entry in the vault.

Keys wiped after use

Derived keys are cleared from memory once the work is done.

Encrypted at rest

On mobile the vault lives on the native filesystem, encrypted, not in a webview database.

End-to-end sync

Devices authenticate each other; a dishonest relay can't read or alter anything.

Questions, answered.

Yes. Bramble is free and open source. There is no paid tier, no subscription, and no account to create.
Bramble holds no copy of your master password or the keys derived from it, so it cannot reset it for you. If you set up a recovery code or a security key you can use those to regain access. If you lose your master password and every recovery method, the vault cannot be decrypted by you, by us, or by anyone. That is the trade-off for there being no backdoor.
Only on your devices. In the browser that means your browser's private extension storage and/or a vault file you pick. On mobile it means the app's private, encrypted-at-rest storage. There is no Bramble cloud.
By default, nothing. Two optional features make network connections when you turn them on: the breach check (which sends only a partial password hash via k-anonymity) and device sync (whose signaling relay only helps your devices connect and never receives your vault, passwords, or keys).
Your devices connect directly to each other and exchange the vault over an encrypted, mutually authenticated channel. A signaling relay passes brief connection details so they can find each other, but the vault stays end-to-end encrypted under a key only your devices hold.
Yes, the whole thing. The code lives on GitHub, so you can read it, build it yourself, or point sync at your own relay.
Because we don't want to help normalise Google's lockdown of Android. The Android build carries no Play Services and nothing else from Google: it is a signed APK you install yourself, and every release is published on GitHub. The campaign against that lockdown makes the case better than we can: keepandroidopen.com

Follow along.

Occasional updates on new releases, features, and security. No account required, no tracking, and one click to unsubscribe.

Subscribing opens a Buttondown tab to confirm your address.

Image

Take your passwords back.

You hold the vault, you hold the password, and that's it. Free, open source, and yours.

Add to your browser Star it on GitHub