NamiDB
Open source · Built on object storage

The bucket is the database.

NamiDB is a graph database that lives in your S3 bucket. Graph, vectors, and search in one engine, running on storage you already pay for. Nothing to run.

Get startedStar on GitHub
$pip install namidbv2.0.0
A figure holding a glowing network of nodes above a city of data.

Starred by engineers from

  • Cloudflare
  • AT&T
  • Fly.io
  • Artium AI
  • Microsoft
  • Intel
  • Red Hat
  • Dropbox
  • Alibaba
  • Tencent
  • Weaviate
  • University of Washington

Engineers from these teams gave NamiDB a star. Add yours on GitHub.

Why it works

Object storage grew up.

In 2024, S3 added the last primitive it was missing. Now your bucket can be a real database: durable, coordinated, with no servers to keep alive. So we built the graph engine for it.

A graph overflowing from a single bucket into object storage, one namespace per tenant.
Durable by default. Multi-tenant by namespace. Scale to zero when idle.
One engine

Graph, vectors, and search.
One engine, one query.

Most teams glue a graph database, a vector store, and a search index together, then babysit three systems that drift out of sync. NamiDB keeps all three in the same files, so one query does graph traversal, vector ranking, and keyword search at once.

Cypher queries

Walk relationships with Cypher, sync or async from Python. GQL is on the roadmap.

client.cypher(...)

Vector search

Rank by meaning with cosine similarity over embeddings stored as node properties.

cosine_similarity(p.emb, $q)

Hybrid search

Keyword relevance and vector similarity in one ranked result, fused with reciprocal rank fusion.

bm25(p.body, $kw)

Graph algorithms

PageRank, connected components, triangle counting, and shortest path, inside the engine.

CALL algo.pagerank()
Obsidian + MCP

Your notes, in your agent.
A graph it can actually query.

Point NamiDB at an Obsidian or Markdown folder and it becomes a live graph: every note a node, every wikilink an edge, every tag a branch. It even ships as a Claude Code skill, so the agent syncs your vault on command, then queries it back over MCP.

01

Sync your vault

One command turns your Obsidian or Markdown folder into a real graph. Notes become :Note, [[wikilinks]] become LINKS_TO, #tags become a :Tag tree. Your files stay the source of truth.

terminal
# get an API key in your NamiDB dashboard, keep it in the env
export NAMIDB_API_KEY=nk_live_...
 
# sync an Obsidian or Markdown folder to a queryable graph
npx namidb-vault@latest --vault ./notes --namespace my-vault --watch
02

Point your agent at it

Add the hosted MCP endpoint to your agent config, authed by the same key. No extra server to run. Claude Code, Cursor, and any MCP client connect.

.mcp.json · hosted MCP
{
  "mcpServers": {
    "namidb": {
      "type": "http",
      "url": "https://api.namidb.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${NAMIDB_API_KEY}",
        "X-NamiDB-Namespace": "my-vault"
      }
    }
  }
}
03

Ask it in plain English

Your agent gets read-only tools: semantic search, backlinks, neighbors, orphans, shared tags, and raw Cypher. It traverses the graph instead of guessing.

claude code
# you:
> what links to "Project X", and what's related to it?
 
# the agent calls, read-only over MCP:
backlinks(note: "Project X")
vault_search(query: "Project X")
Works withClaude CodeCursorCodex

npx namidb-vault is open source. Prefer fully local? Run namidb load-vault with the namidb-mcp server.

The product

One engine. Three deployments.
Open from day one.

v2.0.0 shipped

Server

A single Rust binary, on your bucket.

Run one Rust binary in front of your bucket. No volumes, no state to migrate, no consensus cluster to keep alive. Restart it anywhere; your data was never on the box. It serves a REST API and a Bolt endpoint, so an HTTP client, a Neo4j driver, or cypher-shell connects with nothing new to install.

  • AWS S3
  • Cloudflare R2
  • GCS
  • Azure Blob
  • MinIO
  • Tigris
$ docker run namidb-server
v2.0.0 shipped

Embedded

DuckDB for graphs.

Import the library, point it at a bucket, run Cypher inside your process. Notebooks, scripts, local dev, CI fixtures: same engine, same files. Open the same s3:// path your server uses and the graph is right there.

$ pip install namidb
Closed beta

Cloud

Namespace per tenant. Scale to zero.

Managed and multi-tenant on namidb.com, run by NamiDB, Inc. Namespace per project, per agent, per customer. Scale to zero when idle. Object-storage pricing: pay for what you store, not for headroom you don't use.

One engine, any bucket. Switch deployments or backends without a rewrite.

The cost story

Pay for storage.
Not for the headroom.

Legacy graph databases price by RAM. Double your hot set, double your bill, even if your data didn't grow. NamiDB stores in object storage at object-storage prices. Compute is yours to size. Storage is what you actually use.

Up to 100x less expensive than managed graph databases priced by RAM.

Object-storage pricing versus the RAM tiers of managed graph databases at equivalent sizes. We publish real per-tenant costs when the cloud opens.

Scale to zero

Idle namespaces cost nothing.

Compute scales to zero when nobody queries, per namespace, per tenant, per agent. You pay for the bytes at rest, not for a server keeping them warm at 3 a.m.

Zero-egress on R2

Run it on Cloudflare R2.

R2 charges no egress and ships full S3-compatible conditional writes. If your app lives on Workers, Fly.io, your VPS, or your laptop, R2 is almost always the right call, and the same engine still works against AWS, GCS, Azure, or MinIO whenever you need it.

Backups are a copy

aws s3 sync and you're done.

Your database is just files in your bucket. Snapshots are object versions. DR is a second bucket. There is no proprietary dump format, no exporter to maintain, no vendor in the path.

The principles

Source on day one.
Apache in three years.

Every architectural decision lives in an RFC. Every benchmark is published, including the ones that don't go our way. The engine is source-available from day one under BSL 1.1, and each release converts to Apache 2.0 three years later. A commercial license is available for teams that redistribute it as a managed service or embed it in closed-source products.

Browse the source
github.com/namidb/namidb
Read the research
namidb.com/research
See the benchmarks
namidb.com/benchmarks
A scholar at work, drawing a graph engine into being above an open book
We are building this because nobody else is going to.
Matías Fonseca, Founder
Partners

The teams we build
alongside.

NamiDB runs where the stakes are real. We partner with teams that keep critical systems online at scale, and shape the engine around what they actually carry.

See how we partner, and who vouches for us
Radical, GRD Corporation
Featured partner

Radical

Cybersecurity and critical infrastructure across Latin America

For 25 years Radical has been the technological shield behind more than 3,000 organizations across 8 countries. A security operations center that never sleeps, its own CERT, Tier III data centers held to 99.99 percent uptime, defense grade C4ISR systems, and the full stack of ISO certifications most vendors only talk about. Banks, governments, hospitals, and insurers trust them to stay standing when seconds carry real cost.

Years operating
25

Years operating

Countries
8

Countries

Organizations protected
3,000+

Organizations protected

SOC and CERT
24/7

SOC and CERT

Visit Radical

Partners and clients

  • Fonles

    Fonles · Partner

  • Universe ID

    Universe ID · Client

  • Alhelí

    Alhelí · Client

Want to become a partner?

Building on NamiDB, or bringing it to your own customers? Tell us what you have in mind and a real person writes back. Every request lands in info@namidb.com.

Become a partner
Cloud waitlist

The engine is here. Now we're opening the Cloud.

The engine itself is open source and shipped. Install it from GitHub and point it at your bucket today. The waitlist below is for NamiDB Cloud: managed multi-tenant SaaS on namidb.com, with namespace-per-tenant, scale-to-zero, and object-storage pricing. We are onboarding design partners in waves.

  • One email per wave. No spam.
  • Your data stays in your bucket. Always.
  • Unsubscribe in one click.
NamiDB emblem

The graph is the shapeof how things relate.

We're giving it a database
worthy of the decade ahead.

Read the docsJoin the Cloud waitlist