[kantselovich]

I'm building an alternative called Lockstep: KeePass-like local-first password vault but with build sync https://github.com/lockstepvault-hq/lockstep

Sync requires a server, however server does not see any secret data, it is only used to relay encrypted hash-chained ops log between devices. It's intended to be self-hosting friendly - server is single binary backed by SQLite.

It's project is early-alfa, CLI app, Keepass import and sever/sync work for the most part, there is MacOS app in progress and plans for a iOS app and a browser extension.

Not ready for production and it's not audited.

I'm currently using KeepassXC/Keepasium with Syncting, but I want a better solution - something that supports trouble-free sync natively and allows me to own the system

[jrochkind1]

That sounds awesome, and I personally want to self-host nothing. I do enough of that at work.

[kantselovich]

I do not want to self host either, for exactly the same reasons.

However, I do want to have full control of my secret data beyond the secrets themselves, ideally w/out self hosting, i.e. I want to have crypto-proven control over whom I'm sharing secrets with, I want to have have cryto-level assurance that the service cannot use recovery/escrow mechanism to unlock my secrets data stored on the cloud w/out my consent.

Apple Passwords comes closest to what I want, but it's not cross platform.

[jemmyw]

I'm going to follow your project, it looks good. It's "alpha" btw. I wouldn't usually correct but as you're posting about something you want people to look at you might be interested in a correction.