HelixDB – A Graph Database built on Object-storage
Graph-vector-FTS in one database, but Weaviate and Neo4j already offer hybrid search.
Turbopuffer-inspired vector DB with RaBitQ quantization running on plain S3.
Developers building search systems, engineers learning vector DB internals
Turbopuffer · Pinecone · Weaviate
I wanted to share this in case there are people who had the same idea or wanted to see something like this.
Graph-vector-FTS in one database, but Weaviate and Neo4j already offer hybrid search.
Eight database engines in one Rust binary using io_uring and thread-per-core architecture.
Apache Iceberg for observability data cuts costs versus Datadog and Honeycomb pricing.
Self-managed vector DB in Rust with <5ms queries; Pinecone/Weaviate already own this space.
Zero-config single-file persistence plus two query styles (Mongo-like dicts or a Pythonic Q builder) makes everyday prototyping painless. The built-in Studio UI and auto-index hints are thoughtful extras for inspecting data and nudging performance, though this competes with established tiny DBs and SQLite/JSON patterns — great for side projects, but check concurrency and durability needs first.
Unified SQL, graph, and vector engine when Neon and pgvector already split these concerns.