Comprehensive per-component release notes, product release milestones, and platform version history.
| Release | Date Range | Components & Versions | Actions |
|---|---|---|---|
| R4 | 2026-09-17 | Chrome Extension: 1.4.1Firefox Extension: 1.4.1Android App: 1.4.1Python CLI: 1.1.0 |
|
| R3 | 2026-08-11 | Chrome Extension: 1.3.0 NoneFirefox Extension: 1.3.0 NoneAndroid App: 1.3.0 NonePython CLI: 1.0.1 None |
|
| R2 | 2026-07-26 to 2026-07-30 | Chrome Extension: 1.2.0 NoneFirefox Extension: 1.2.0 NoneAndroid App: 1.1.0, 1.2.0 None |
|
| R1 | 2026-07-24 | Chrome Extension: 1.1.0 NoneFirefox Extension: 1.1.0 NoneAndroid App: 1.0.0 NonePython CLI: 1.0.0 None |
Deletions now sync properly across your devices, and importing from another password
manager shows you exactly what it is about to use.
everywhere, instead of reappearing the next time another device syncs.
device while editing it on another, Keygrain shows you both and lets you decide, rather
than silently picking a winner.
the address read from your export next to the site Keygrain derived from it, because the
site is what generates your password โ if the two disagree, you need to know before you
rotate a real password, not after.
address (github.com rather than https://github.com) fell back to the entry title, so
a "GitHub" entry was imported as github instead of github.com. That produced a
different password than adding the same account by hand, and autofill never matched it.
If you already migrated from such an export, check the Site field on those entries.
with no address at all say so.
No algorithm changes โ every password, code, key and seed is byte-identical to before
(SPEC v4).
Deletions now sync properly across your devices, and importing from another password
manager shows you exactly what it is about to use.
everywhere, instead of reappearing the next time another device syncs.
device while editing it on another, Keygrain shows you both and lets you decide, rather
than silently picking a winner.
the address read from your export next to the site Keygrain derived from it, because the
site is what generates your password โ if the two disagree, you need to know before you
rotate a real password, not after.
address (github.com rather than https://github.com) fell back to the entry title, so
a "GitHub" entry was imported as github instead of github.com. That produced a
different password than adding the same account by hand, and autofill never matched it.
If you already migrated from such an export, check the Site field on those entries.
with no address at all say so.
No algorithm changes โ every password, code, key and seed is byte-identical to before
(SPEC v4).
No algorithm changes โ every password, code, key and seed is byte-identical (SPEC v4).
No algorithm changes โ every password, code, key and seed is byte-identical (SPEC v4).
The biggest Keygrain update yet: autofill, one-time codes, and full control over your
account and synced data.
sites, so you can fill credentials in place.
keyboard shortcut, or the right-click menu. No separate authenticator app.
for the fill shortcut.
from the menu or the lock screen.
option to keep a local copy on this device.
device's account.
No algorithm changes โ every password, code, key, and seed is byte-identical to before
(SPEC v4).
The biggest Keygrain update yet: autofill, one-time codes, and full control over your
account and synced data.
sites, so you can fill credentials in place.
keyboard shortcut, or the right-click menu. No separate authenticator app.
for the fill shortcut.
from the menu or the lock screen.
option to keep a local copy on this device.
device's account.
No algorithm changes โ every password, code, key, and seed is byte-identical to before
(SPEC v4).
Keygrain arrives on Google Play. One master secret derives every password, TOTP code,
SSH key, and wallet seed. Derived passwords are not stored; service configuration is stored locally and can be synced in encrypted form.
The app's package id is com.secbytech.keygrain.
No algorithm changes โ every password, code, key, and seed is byte-identical to before
(SPEC v4).
Keygrain is now on PyPI: pip install keygrain.
reproducible wheels and PEP 740 provenance attestations.
seeds, and SSH material from your synced configuration.
as a CLI and an importable library.
No algorithm changes โ output is byte-identical across all Keygrain platforms (SPEC v4).