Features

Lattice PM synchronizes supported KeePass KDBX vaults between devices that already trust each other. The synchronization engine is the product; infrastructure services are optional.

KDBX synchronization

• Semantic merge. Groups, entries, standard and custom string fields, protected fields, tags, expiry settings, standard icons, entry history, binary attachments, custom icons, and recycle-bin moves synchronize as typed records.
• Signed revision graph. Each revision binds the vault, the exact membership document, epoch, author device, monotonic author sequence, causal parents, a full-state commitment, and changed record descriptors.
• Fail-closed writes. Unknown or unmodeled KeePass XML, unsupported KDBX variants, and any exposed field that cannot be written back without loss stop the write.
• Journaled materialization. Remote KDBX writes bind the exact preimage and postimage to the intended state, so an interrupted write can be completed or discarded after restart.

Conflict resolution

• Concurrent edits produce redacted conflict descriptors instead of silent data loss.
• A resolution commits a signed, journaled revision. Exact retries are idempotent, and stale peers cannot resurrect a resolved conflict.
• Losing payloads remain in an encrypted quarantine for historical delivery until a proof-gated pruning operation retires them.

Membership and access

• Access is granted by admin-signed membership documents created through invite and join.
• Discovery alone grants no access. A peer must prove its device key belongs to the vault membership epoch.
• Member removal advances the membership epoch and rotates repository and epoch secrets.
• Roles cover admin, writer, and helper. Helper replicas serve availability without local revision authorship.

Recovery

• Encrypted, vault-bound offline backup of the sole-admin membership identity.
• Constrained secondary recovery authority for a lost primary admin.
• Same-key recovery for lost anti-rollback state from an admin-signed, target-encrypted package.
• Fresh-key replacement for a lost non-admin writer identity.
• Anti-rollback floors persist in encrypted state and survive membership cutovers and restarts.

Networking and availability

• Direct transport uses libp2p over TCP with Noise/Yamux and QUIC with TLS 1.3.
• Discovery uses mDNS on the local network, membership-authorized cached addresses, and optional epoch-scoped rendezvous.
• AutoNAT confirms reachability, Circuit Relay v2 is the fallback, and DCUtR attempts a direct upgrade after a relayed connection exists.
• An optional mailbox service carries short-lived encrypted head hints, and optional object storage holds immutable epoch-encrypted bundles for all-devices-offline catch-up.

Supported vaults

Supported:

• KDBX4.1 vaults with password-only, password-plus-key-file, or key-file-only credentials.
• Integrity-checked XML v2 key files whose four-byte hash matches the decoded key data.
• Standard groups, entries, fields, tags, history, attachments, and custom icons.

Not supported, and intentionally not written:

• Unknown or unmodeled KeePass XML elements, attributes, or envelope data.
• Non-KDBX4.1 files and writer-unsupported KDBX variants.
• Any exposed field that cannot be written back without loss.