DeltaSync
Encrypted KeePass sync — requires your own self-hosted server.
新版本 0.4.2
Self-hosting on a local network, and a phone can now start on its own.
• A server on your own network can be reached over plain HTTP. The app refused unencrypted connections outright, which ruled out the setup it exists for — a NAS or a box on the LAN with no certificate. The enrollment screen marks an http:// address as unencrypted while you type it, so the choice is yours to make knowingly. What travels is encrypted vault data and a token either way.
• You can create a database from the phone
• A server on your own network can be reached over plain HTTP. The app refused unencrypted connections outright, which ruled out the setup it exists for — a NAS or a box on the LAN with no certificate. The enrollment screen marks an http:// address as unencrypted while you type it, so the choice is yours to make knowingly. What travels is encrypted vault data and a token either way.
• You can create a database from the phone
⚠ REQUIRES YOUR OWN SERVER. DeltaSync does nothing on its own. You must first
install and run the self-hosted DeltaSync server (PHP + PostgreSQL), or have
access to someone else's, and enrol this device against it. There is no public
or default server — without one, this app has nothing to sync and cannot even
be set up. If you just want a standalone KeePass app, this is not it: use
KeePass2Android or KeePassDX instead.
DeltaSync keeps a KeePass (.kdbx) database synchronised across your devices
through a server that only ever sees encrypted blobs. Your master password
never leaves the device, and the server cannot read entry titles, usernames,
passwords, notes or attachments — even if it is compromised.
How it differs from other KeePass sync solutions:
• Entry-level deltas: only changed entries cross the wire, not the whole
.kdbx file. Fewer bytes uploaded, fewer wholesale conflicts.
• Real end-to-end encryption: per-entry XChaCha20-Poly1305 with a key
derived from your master password via Argon2id and HKDF-SHA256. The
server stores opaque ciphertext.
• Concurrent edits merge: two devices editing different entries (or even
different fields of the same entry) merge cleanly. Field-level
last-writer-wins on conflicts.
• Multi-user sharing without key escrow: NaCl sealed-box wraps the
database master key to each recipient's device public key. The server
sees who has access, not what they can decrypt.
• Open source from end to end: the AGPL-3.0 server (PHP/PostgreSQL),
GPL-3.0 desktop client (Go), and this GPL-3.0 Android client are all
published. You can self-host the server, or use someone else's.
This app pairs with KeePass2Android or KeePassDX as your editor — DeltaSync
itself is a background sync service and does not display your passwords.
You point it at a .kdbx file on the device, supply the master password
once, and it keeps the file in sync with the server through WorkManager.
Project: https://gitlab.com/Star95/keepass-deltasync
Website: https://deltasync.bjoerck-braun.dk
Groups sync too: group structure and which group each entry belongs to stay
in sync across devices, alongside the entry contents.
Status: v0.4 — the sync layer (entries + groups) is feature-complete and
tested; the UI is functional but still minimal. Treat as beta.
install and run the self-hosted DeltaSync server (PHP + PostgreSQL), or have
access to someone else's, and enrol this device against it. There is no public
or default server — without one, this app has nothing to sync and cannot even
be set up. If you just want a standalone KeePass app, this is not it: use
KeePass2Android or KeePassDX instead.
DeltaSync keeps a KeePass (.kdbx) database synchronised across your devices
through a server that only ever sees encrypted blobs. Your master password
never leaves the device, and the server cannot read entry titles, usernames,
passwords, notes or attachments — even if it is compromised.
How it differs from other KeePass sync solutions:
• Entry-level deltas: only changed entries cross the wire, not the whole
.kdbx file. Fewer bytes uploaded, fewer wholesale conflicts.
• Real end-to-end encryption: per-entry XChaCha20-Poly1305 with a key
derived from your master password via Argon2id and HKDF-SHA256. The
server stores opaque ciphertext.
• Concurrent edits merge: two devices editing different entries (or even
different fields of the same entry) merge cleanly. Field-level
last-writer-wins on conflicts.
• Multi-user sharing without key escrow: NaCl sealed-box wraps the
database master key to each recipient's device public key. The server
sees who has access, not what they can decrypt.
• Open source from end to end: the AGPL-3.0 server (PHP/PostgreSQL),
GPL-3.0 desktop client (Go), and this GPL-3.0 Android client are all
published. You can self-host the server, or use someone else's.
This app pairs with KeePass2Android or KeePassDX as your editor — DeltaSync
itself is a background sync service and does not display your passwords.
You point it at a .kdbx file on the device, supply the master password
once, and it keeps the file in sync with the server through WorkManager.
Project: https://gitlab.com/Star95/keepass-deltasync
Website: https://deltasync.bjoerck-braun.dk
Groups sync too: group structure and which group each entry belongs to stay
in sync across devices, alongside the entry contents.
Status: v0.4 — the sync layer (entries + groups) is feature-complete and
tested; the UI is functional but still minimal. Treat as beta.
- 作者: Hans Bjørck-Braun
- 授權條款: GNU General Public License v3.0 or later
- 網站
- 問題追蹤系統
- 原始碼
- 更新紀錄
- 建置詮釋資料
- 可重現建置狀態
版本
雖然在下方可選擇下載 APK 檔案，但要留意這樣的安裝方式將不會收到更新通知，是一種較不安全的下載方法。建議您先安裝 F-Droid 用戶端使用。
下載 F-Droid-
arm64-v8aarmeabi-v7ax86x86_64此版本需要 Android 6.0 或更高的版本。
此套件包由原開發者建置和簽署，並保證與此原始碼 Tarball 保持一致。