Lockrs

Open source · Offline · No telemetry

Passwords you can
actually verify.

Lockrs keeps your vault on your machine — encrypted, auditable, and free from the cloud vendors who treat your credentials like recurring revenue.

  • Open source
  • Rust + Tauri
  • Argon2id · AES-256-GCM · zeroize

Your vault. Your device. Not their datacenter.

One master password unlocks AES-256-GCM encrypted entries. Panic locks instantly. Copy-to-clipboard clears memory with zeroize in Rust — no trust-me slide deck required.

What you get when a company is not in the middle

Lockrs is not nicer marketing on the same cloud model. It is a different shape: local file, open code, zero account.

No server copy

The vault is a file on your drive. Nobody else hosts it for you.

Readable source

Check the repo if you want proof, not a landing page promise.

No subscription

Free software. You own the hardware; you should not pay monthly to access your own passwords.

Reviewable updates

See what changed before you install a new build.

Panic button

One click to lock, clear the clipboard, and wipe secrets from memory.

Small project

Built by one developer. No enterprise upsell path.

Security you can read, not just believe

Local-first

The vault lives on your machine. No account, no sync server, no telemetry.

Master password

Lockrs stores an Argon2id fingerprint, not your password.

Encrypted vault

Entries are AES-256-GCM encrypted before they are written to disk.

Import

Move passwords in from another manager instead of typing them again.

Hashes

Save hashes for API keys and tokens — not only login passwords.

Wiped from RAM

After copy, values are zeroized in memory. Panic clears the clipboard and wipes what is left in RAM.

Offline

No network required. Data stays on the device.

Panic button

Locks instantly, clears the clipboard, and wipes sensitive memory. Your vault file on disk stays put.

Industry reality

Why most vaults push the cloud

Subscriptions and sync are how the big products make money. A file on your SSD does not fit that model.

  • Closed clients

    You get a binary and a FAQ. You do not get the full picture of what runs on your PC.

  • Extra copies

    Sync puts ciphertext on someone else's hardware. That is another thing to protect forever.

  • Audit PDFs

    Compliance reports help companies buy software. They are not a substitute for reading code.

  • Free plans

    Cheap entry, painful exit once everything is already inside.

  • Upsells

    Lockrs does not need your email or a family bundle. It writes an encrypted file and stops.

Compared to cloud vaults

Same category, opposite incentives. These products are not evil cartoons — they are rational businesses. Rational for them. Expensive for your threat model.

Privacy-branded cloud vault

vs. Proton Pass

Good privacy story. Still built around sync when you turn it on.

LockrsProton Pass
Vault locationYour diskProton when sync is on
Client codeOpen repoOpen core only
AccountNot requiredProton account
Offline defaultYesSync is the main path

Anything that syncs still depends on their servers. Local-only is a different tradeoff.

Enterprise password manager

vs. 1Password

Polished app, closed source, paid plans.

Lockrs1Password
Source codePublicClosed
Verify cryptoClone the repoTrust the vendor
PriceFree softwareSubscription
Hosted vaultNoneYes

Their business is subscriptions and teams. You get a product; you do not get full transparency.

Sync across devices is coming to Lockrs — not available yet. For now, the vault stays on one machine.

Help build Lockrs

The project is open source. PRs, bug reports, and testing all help — and people who stick around can earn roles on our Discord.

  • Send a pull request on GitHub (Rust backend, Tauri UI)
  • Open issues with clear repro steps
  • Join the support server to test builds and talk through ideas
Open GitHub

Download Lockrs

Windows, macOS, and Linux builds are on the way.

Coming soon

Installers will show up on GitHub. No waitlist.

Track on GitHub

Security write-ups on the site match what is in GitHub.