I’ve worked quite a bit with GunDB over the years (including building its documentation platform and several P2P projects on top of it), so it’s always nice to see breakdowns like this one.

At some point I ended up building my own alternative, GenosDB, mostly because I needed a few things that differed from the traditional Gun model:

1. A more explicit API with stronger querying GenosDB keeps the distributed graph idea but uses a minimal API (put/get/map/link/remove) plus native Mongo-style queries, sorting, pagination, and recursive traversal with $edge for exploring full descendant trees in a graph .
2. Integrated RTC without running custom servers Gun uses DAM, but I needed real-time P2P with both data channels and AV streams directly from the DB layer. GenosDB includes GenosRTC: WebRTC + decentralized signaling over Nostr, dynamic relay fallback, PoW detection, and automatic mesh connectivity between peers .
3. A distributed security model with cryptographic verification Every operation is signed, and each node runs a local Security Manager that validates identities, roles, and permissions based on a shared constitution. No implicit trust between peers, even if a client tampers with its local UI. Superadmins are defined statically to ensure a secure trust root in the RBAC model .

The bundle is free for personal and commercial use, so if you already understand the GunDB approach and feel like comparing design choices or testing another P2P/RTC architecture, it might be interesting to try. If you’re curious about how these design choices look in practice, the implementation and specs are openly available on my GitHub profile estebanrfp/gdb.