Interesting work. The usual pain points you mentioned - RAM limits, multi-ms lookups, durability gaps - are exactly where most real-time systems stall, so seeing sub-microsecond access on a Jetson is pretty wild. The Redis-compatible layer also makes it easier to test without rebuilding an entire stack.
Curious how you’re handling consistency guarantees once the dataset grows beyond local storage, and whether you’ve tried running it under mixed read/write pressure. Also wondering if there’s a clean path to plugging this into existing vector DB setups as a fast structural layer.
Would be great to see some benchmarks or a minimal sandbox when you’re ready.
I might disappoint you, but almost all text content in 2025 is written by AI and edited by humans. So, almost 100% of the emails you receive are AI-generated, so your inbox should be squeaky clean.