Skip to content

LockraTwo-factor codes and passwords that stay on your devices.

An encrypted authenticator and password manager for Windows, macOS, Linux and Android, with a browser extension that fills your logins and their codes. Keep the same accounts on every device with end-to-end encrypted sync, move them from Google Authenticator or Microsoft Authenticator, and keep encrypted backups where you choose.

Runs on
Windows 10 and 11, macOS 11 or later (Apple silicon and Intel) and Linux, on x64 and ARM64, and ARM64 phones with Android 8 or later.
In sync
The same accounts on every device, end-to-end encrypted, through a relay or storage you control.
Your accounts
Codes and passwords in one encrypted file on each device. Lockra connects to GitHub for updates and, once you turn on sync, to the relay or storage you chose; to nothing else.
The Lockra codes page with a list of accounts, each with its current code and the time it has left.The Lockra codes page with a list of accounts, each with its current code and the time it has left.

Lockra in a minute ​

Signing up on a site with a password Lockra makes to its rules, turning on its two-step verification, and signing in page by page with the login and the code filled in; then the command palette (Ctrl K), the generator (Ctrl G) and the themes. Recorded with the real app and its browser extension, on a made-up site.

Passwords, filled in the browser ​

From version 0.10.0, Lockra keeps your logins beside the codes, in the same vault and the same backup, on the computer and on the phone. The browser extension for Chrome, Edge and Firefox fills a login and then its code, page by page when a sign-in asks for them one at a time, offers to save and update passwords, and makes a password to the site's rules on a sign-up form. It keeps no passwords itself: it asks Lockra on the same computer, over a connection encrypted between the two, and Lockra decides every fill. Logins come in from browsers and password managers, and go out to KeePass or a CSV file.

The Passwords page: the search field and Add login at the top, the filters, the logins in their groups, and the GitHub login in the pane on the right with its user name, its password as dots and the linked account's code.The Passwords page: the search field and Add login at the top, the filters, the logins in their groups, and the GitHub login in the pane on the right with its user name, its password as dots and the linked account's code.

Passwords · The browser extension · Importing and exporting logins

Every device, in sync ​

Lockra runs on Windows, macOS, Linux and Android, and sync keeps the same accounts, logins, groups and pinned accounts on all of them. Each device encrypts what it shares before it leaves; a relay you run, an S3-compatible bucket, a WebDAV folder or, between computers, a cloud drive folder keeps only that ciphertext. A phone joins by scanning the computer's QR code, and there is no Lockra account to create.

Lockra on a computer and on a phone, showing the same accounts with the same codes.Lockra on a computer and on a phone, showing the same accounts with the same codes.

Sync between devices · Install on Android

What Lockra does

Everything in the current release, with a link to the page that explains it.

Devices and sync

  • The same app on computers and phones, with installers for Windows, macOS and Linux on x64 and ARM64 and an APK for Android 8 or later.

  • End-to-end encrypted, on an S3-compatible bucket, a WebDAV folder or, between computers, a cloud drive folder of your own, or through a Lockra relay. Whatever keeps the space sees only encrypted files.

  • Run your own relay to keep the encrypted files without giving the server the keys that open them.

  • Show an invitation on a device of the space and scan it with the phone, or paste its pairing link. A recovery key brings the space back if every device is lost.

Codes

  • Click an account, or select it with the arrow keys and press Enter. The clipboard is cleared 30 seconds later if it still holds the code.

  • In a code's last five seconds the next one appears beside it, so you never type a code that is about to change.

  • Type to find an account, file accounts into groups, and pin the ones you use most to the top. Ctrl K finds any account and copies its code.

  • Fold groups one by one or all at once, give each account a colour or its own avatar text, and pin or edit from the row or a right-click.

  • Time-based (TOTP) and counter-based (HOTP) codes, SHA1, SHA256 or SHA512, 6 to 8 digits, any period.

Passwords

  • User names, passwords, sites, notes and fields of your own, with the account whose code goes with each, on the computer and on the phone.

  • Fill directly, ask for the master password or the system check first, or keep a login away from the browser extension.

  • Random passwords and passphrases, held to the password rules of known sites, with a history on the device.

  • Import from Chrome, Edge, Firefox, Safari, Bitwarden, 1Password, LastPass and KeePass; export to KeePass or a CSV file.

  • Fills logins and their codes on Windows, macOS and Linux, page after page when a sign-in takes several, and offers to save new passwords. Chrome, Edge and Brave load it from Lockra's release; the Firefox version waits for its store listing.

  • A key combination of your own brings up Lockra's command palette over any app, to copy a user name, a password or a code.

Moving accounts

  • Photograph or screenshot its export codes and drop the pictures on the window. Lockra says which codes of a batch are still missing.

  • The app has no export, but Lockra reads its database from a rooted Android phone. Work and school accounts cannot be moved.

  • Paste otpauth links, read them from the clipboard, or choose a list or a picture of any authenticator's QR code.

  • Migration codes for Google Authenticator, one code per account for Microsoft Authenticator, with the current codes beside them to check the phone.

Backups

  • Save the whole vault to a .lockrabackup file under the master password or a separate backup password.

  • A few seconds after every change, an encrypted backup goes to a folder you choose. Lockra keeps the newest few.

  • Merge a backup's accounts one by one, or replace them all. Before replacing, Lockra keeps a copy of the current vault.

Protection

  • The vault is encrypted with a key derived from your master password. Repeated wrong passwords slow down further attempts.

  • Optionally keep a key in the system keychain so that unlocking needs no password on this computer.

  • Ask for your fingerprint, or Windows Hello, before the remembered key unlocks.

  • Locks itselfAvailable

    After five idle minutes by default, and at once with Ctrl L.

  • Showing a secret or an export code asks for the master password again (or, on the phone, the fingerprint) and hides it after two minutes. On Windows and macOS, screenshots show the window black meanwhile.

  • The title bar tells you when a new version is out; with automatic updates on, Lockra downloads it at start and every 4 hours while it runs, and installs only a package that carries its signature.

Move your accounts in four steps

  1. Create the vault

    Start Lockra and choose a master password. It encrypts everything and cannot be recovered.

  2. Export from the phone

    In Google Authenticator, open Transfer accounts and Export accounts, and take photos of the codes with another device.

  3. Import the photos

    Drop the pictures on Lockra's window. A preview lists every account; confirm it and they are saved.

  4. Copy a code

    CtrlK

    Find an account and press Enter, or click it in the list. The code is on the clipboard.

Bring your accounts, and take them back ​

Google Authenticator exports its accounts as QR codes that Lockra reads from photos or screenshots, several at once. Microsoft Authenticator has no export; on a rooted Android phone, Lockra reads its database instead. Any other authenticator can hand over otpauth links or QR codes.

Moving the other way, Lockra shows migration codes for Google Authenticator and one code per account for Microsoft Authenticator, with each account's current code beside them so you can check the phone. Logins come from browsers and password managers through the same preview, and go out to a KeePass database or a CSV file.

Google Authenticator · Microsoft Authenticator · Other apps · Logins

AppInto LockraBack to the app
Google Authenticator30-second or counter-based, 6 or 8 digitsPhotos or screenshots of its export codesMigration codes, up to 10 accounts each
Microsoft AuthenticatorSHA1, 6 digits, 30 secondsIts database from a rooted Android phoneOne standard code per account
Other authenticatorsotpauth links, lists and QR imagesA plain list of otpauth links
LockraA backup file and its passwordA backup file
Browsers and password managersTheir password exports, and KeePass databasesA KeePass database or a CSV file

Before anything is saved, the preview marks each account as new, already in the vault, sharing a name with a different account, or unsupported, with the reason.

Backups you never have to remember ​

Turn on automatic backups once and choose a folder. A few seconds after each change Lockra writes an encrypted copy there and keeps only the newest few. A folder of OneDrive, Google Drive or iCloud carries the copies to your other devices without Lockra going online, and sync keeps the accounts themselves the same on every device, through a Lockra relay or storage of your own.

Restoring merges a backup into your accounts through the same preview as an import, or replaces them after saving a copy of the vault you had.

Backups and restore · Sync between devices

Encrypted like the vault
A backup file can sit in any folder or cloud drive. It opens only with the password it was made under.
Automatic
Three seconds after the last change, into the folder you chose, keeping the newest 10 by default.
Safe to restore
Merge goes through the import preview; replace first saves a copy of the current vault.

Built to keep secrets ​

The vault is one encrypted file. Without the master password it is unreadable, and changing a single byte of it is detected. Lockra locks itself when idle, clears the codes and passwords it copied, and shows an account's secret, or the password of a login set to Verify first, only after you enter the master password again (or, on the phone, verify your fingerprint).

How Lockra protects your accounts · Privacy

Key derivation
Argon2id with 64 MiB of memory and three passes turns the master password into a key.
Encryption
XChaCha20-Poly1305 encrypts the accounts; any change to the file, even one byte, is detected.
The clipboard
Copied codes are marked to stay out of clipboard history and are cleared after 30 seconds.
Your OS account
With Remember on this device, the vault opens for anyone who can sign in to this computer.

Platforms

Lockra is the same app on Windows, macOS and Linux, and on Android phones; an app for iPhone and iPad is planned. The platform notes list what differs between them.

PlatformPackagesRemember on this deviceBlocks screenshots of secrets
Windows 10 and 11AvailableInstaller or MSI for x64, installer for ARM64Credential ManagerYes
macOS 11 or laterAvailableA dmg for Apple silicon and one for IntelKeychainYes
LinuxAvailable.deb, .rpm or AppImage, x64 and ARM64Secret Service (GNOME Keyring, KWallet)No
Android 8 or laterAvailableAn APK for ARM64With the fingerprint onlyAlways
iPhone and iPadPlanned———

The packages are not code-signed yet, so Windows and macOS ask before the first start.

What leaves your computer

Nothing, unless you move it yourself or turn on sync.

Your accounts

Where it isIn one file on this computer

Encrypted with a key derived from your master password. Lockra never sends it anywhere.

Backups

Where it isWhere you save them

Encrypted the same way. Automatic backups go only to the folder you chose; if that folder syncs, the encrypted file syncs with it.

Sync

Where it isA relay or your own storage, if you turn it on

Each device writes encrypted files to the Lockra relay, bucket or WebDAV folder you set up. None of them can read an account, a secret or a device name.

The network

Where it isUpdates and your sync

Lockra asks GitHub for the newest version when you check, or at start and every 4 hours while it runs if you turn on automatic updates; nothing from your accounts goes with it. There is no Lockra account or telemetry, and fonts and images ship with the app.

The browser extension

Where it isLockra on this computer only

It asks Lockra on the same computer, over a connection encrypted between the two, keeps no passwords and sends nothing over the network.

Install ​

Packages for every platform, with checksums and build attestations, are on the releases page. The install guide covers each platform, including the first start of an unsigned app.

Deliberately left out

Lockra keeps your codes and passwords on your devices.

  • An account, or a server that can read your accounts. Sync needs no account, and the relay or storage holds encrypted files only.
  • Non-standard codes such as Steam Guard.

Lockra is released under the Apache License 2.0. Part of FirLab. Content from lockra@5a5a5de.