Hi Product Hunt ! I’m Wojtek (Voyteck), the creator of dbzero. As Python developers, we’ve been trained to think that if we want data safety, we must accept the overhead of a database. We spend hours configuring Postgres, mapping objects to ORMs, and dealing with network latency - even when we just want to persist local state. I built dbzero to break that trade-off. It’s based on the DISTIC model, giving you ACID guarantees without the external infrastructure. The "Superpower": Algorithmic Freedom Traditional databases force you into their structures (Rows, Documents, Key-Pairs). Because dbzero persists native Python objects, you can build custom data structures optimized for your specific use case.We've seen applications jump from O(log N) to O(1) performance simply because they could use the exact right structure for the job, rather than fighting a database's limitations. You get the speed of in-memory execution with the durability of a disk-backed engine. Why use it? - Zero Infra: No servers to scale or containers to manage. - Low Latency: Zero round-trips. Your data is right there. - Transactional: Full isolation and integrity. I’d love to hear your thoughts on the DISTIC approach and how you might use this to simplify your stack! I'll be here all day to answer questions. Happy coding!

dbzero

Zero-latency persistence: Speed of RAM with safety of a DB.

Zero-latency persistence: Speed of RAM with safety of a DB.