A open-source graph database that lives in your S3 bucket
NamiDB is an open-source graph database designed to operate directly within S3 buckets. It offers three deployment options: as an embedded library, a standalone HTTP server, or through a hosted cloud service. The database leverages conditional writes to ensure data integrity without the need for additional coordination tools.
- ▪NamiDB allows users to write Cypher queries, which are then stored as columnar files in an S3 bucket.
- ▪The database operates without requiring Raft, ZooKeeper, or etcd, simplifying its architecture.
- ▪NamiDB is open-sourced to fill the gap left by the archived Kùzu project, which was the only maintained columnar graph engine.
2 outlets in our directory ran this story, first to last over 15 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/namidb/namidb |
| Publication time | Thu, 21 May 2026 20:48:48 +0000 |
| Retrieval time | 2026-05-21T21:01:35.754Z |
| Last seen | 2026-05-21T21:01:35.754Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | wa-q901OiNPL · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
NamiDB A graph database that lives in your S3 bucket. It embeds like DuckDB, runs as a standalone HTTP server, or sits on our hosted cloud. Same engine in all three, and the bucket is always the source of truth. Website · Documentation · RFCs · Request early access NamiDB is a graph database engine built around object storage. You write Cypher, it lays your nodes and edges out as columnar files in a bucket, and that bucket is the only source of truth. There's nothing else to run and nothing to coordinate outside the bucket itself. The same engine ships three ways: embedded as a library, as an HTTP server, or on our hosted cloud. Why now A few things had to line up before this made sense. S3 finally got conditional writes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.