https://github.com/potusaiteja/graphdatabases
Reference catalog for graph databases, knowledge graphs, RDF/SPARQL stores, and vector-search support.
https://github.com/potusaiteja/graphdatabases
List: graphdatabases
awesome-list cypher database-comparison graph graph-database graphdb graphql knowledge-graph knowledge-representation linked-data multi-model-database ontology property-graph rdf semantic-web sparql triple-store
Last synced: about 17 hours ago
JSON representation
Reference catalog for graph databases, knowledge graphs, RDF/SPARQL stores, and vector-search support.
- Host: GitHub
- URL: https://github.com/potusaiteja/graphdatabases
- Owner: POTUSAITEJA
- License: mit
- Created: 2026-04-10T12:59:30.000Z (17 days ago)
- Default Branch: main
- Last Pushed: 2026-04-10T13:53:29.000Z (17 days ago)
- Last Synced: 2026-04-10T15:09:07.895Z (17 days ago)
- Topics: awesome-list, cypher, database-comparison, graph, graph-database, graphdb, graphql, knowledge-graph, knowledge-representation, linked-data, multi-model-database, ontology, property-graph, rdf, semantic-web, sparql, triple-store
- Language: JavaScript
- Homepage: https://potusaiteja.github.io/GraphDatabases/
- Size: 180 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Graph Database Resource Catalog
### The curated, primary-source reference for graph databases, RDF triple stores, property graph systems, and vector-capable graph engines.
**A curated reference covering 70 graph databases — Neo4j, Apache Jena, Stardog, ArangoDB, Memgraph, TigerGraph, Dgraph, Virtuoso, GraphDB, Amazon Neptune, Oracle Graph, Google Spanner Graph, SAP HANA Graph, and more — with explicit vector-search classification for every entry.**
---
## About
The **Graph Database Resource Catalog** is a curated, primary-source reference for every graph database, RDF triple store, SPARQL engine, label property graph database, multi-model engine, and graph-plus-vector system worth considering for production use. It answers one question honestly:
> **Which graph databases actually support vector search, and how?**
Every one of the 70 entries is anchored to official documentation, product pages, or source repositories. The catalog distinguishes native vector support from connector-based, paired-extension, and sibling-service patterns — and where the public docs are ambiguous, the entry is marked `unclear` instead of being inflated.
**Topics covered:** graph database · RDF database · SPARQL · property graph · label property graph · LPG · knowledge graph · semantic graph · triple store · Cypher · Gremlin · GQL · SQL/PGQ · Datalog · vector search · HNSW · GraphRAG · multi-model database · graph analytics · graph OLTP · graph OLAP · knowledge graph engineering · semantic web
**Databases in the catalog include:** Neo4j, Apache Jena, Fuseki, Virtuoso, Stardog, GraphDB, Amazon Neptune, RDFox, MarkLogic, Oxigraph, QLever, Blazegraph, TerminusDB, SurrealDB, ArangoDB, ArcadeDB, Memgraph, TigerGraph, Dgraph, JanusGraph, NebulaGraph, Apache HugeGraph, Apache AGE, OrientDB, TypeDB, Azure Cosmos DB for Gremlin, PuppyGraph, Kuzu, Ultipa, FalkorDB, Aerospike Graph, Tarantool Graph DB, TuGraph, AgensGraph, Fluree, RedisGraph, CozoDB, Oracle Graph, Google Spanner Graph, Gel (formerly EdgeDB), Datomic, HyperGraphDB, AnzoGraph DB, Weaviate, Cayley, DataStax Enterprise Graph, Eclipse RDF4J, AtomicServer, HelixDB, Dydra, Alibaba Cloud GDB, IBM Db2 Graph, Huawei Graph Engine Service, ONgDB, Ontop, Apache Marmotta, RelationalAI, Raphtory, Katana Graph, Trovares xGT, Apache S2Graph, PoolParty, TopBraid EDG, IndraDB, HGraphDB, SAP HANA Graph, and more.
## What makes it different
- **One canonical dataset.** Everything — the live UI, the per-database profiles, the validation pipeline — reads from [`databases/databases.json`](databases/databases.json). There is no second copy to drift out of sync.
- **A real vector-strategy taxonomy.** Six explicit categories (`native`, `integrated`, `paired`, `sibling`, `none`, `unclear`) instead of a single boolean that hides nuance.
- **Primary-source discipline.** If a claim does not survive a trip to the official docs, it gets downgraded — not argued up.
- **Scope clarity.** Model (`rdf` / `property` / `multi` / `specialized`), maturity (`production` / `emerging` / `legacy`), and vector strategy are separate fields instead of collapsed into an arbitrary tier letter.
## Vector strategy taxonomy
| Strategy | Meaning |
|---|---|
| **Native** | Vector indexing and query are documented in the same engine |
| **Integrated** | Vector capability depends on an integrated search subsystem or connector |
| **Paired** | The documented pattern pairs the graph engine with an extension, toolkit, or sibling component |
| **Sibling** | A separate managed service or API in the same vendor platform provides vector search |
| **None** | No documented vector capability in the graph engine |
| **Unclear** | AI or semantic-search claims exist, but current public docs do not expose a clear general-purpose vector implementation |
## Catalog at a glance
**By model**
- **17** RDF / SPARQL-native stores
- **27** Label property graph databases
- **17** Multi-model systems with a real graph layer
- **9** Specialized graph-adjacent systems
**By vector strategy**
- **21** Native (in-engine)
- **5** Integrated
- **5** Paired
- **2** Sibling-service
- **32** None
- **5** Unclear
## Highlights
- [**Neo4j**](databases/neo4j/README.md) — LPG, native HNSW inside Cypher
- [**ArangoDB**](databases/arangodb/README.md) — multi-model with native vector indexes in AQL since 3.12
- [**SurrealDB**](databases/surrealdb/README.md) — multi-model with `DEFINE INDEX ... HNSW` in SurrealQL
- [**CozoDB**](databases/cozo/README.md) — Datalog + native HNSW, relational-graph-vector in one engine
- [**Oracle Graph**](databases/oracle-graph/README.md) — dual RDF + LPG inside Oracle Database 23ai with AI Vector Search
- [**Google Spanner Graph**](databases/spanner-graph/README.md) — ISO GQL with ScaNN-backed ANN
- [**Stardog**](databases/stardog/README.md) — commercial RDF with in-engine vector search
- [**Dgraph**](databases/dgraph/README.md) — native `float32vector` and HNSW indexes in DQL
Full list in [`databases/databases.json`](databases/databases.json) and the [live catalog](https://potusaiteja.github.io/GraphDatabases/).
## Quick start
```bash
git clone https://github.com/POTUSAITEJA/GraphDatabases.git
cd GraphDatabases
npm install
npm run dev
```
Then open `http://localhost:3000`.
### Everyday commands
```bash
npm run dev # start the local dev server
npm run validate # validate the catalog and required docs
npm run lint # lint source and scripts
npm run build # validate + build the static site
npm run preview # preview the built site
npm run check # validate + lint + build
```
## Tech stack
| Layer | Choice |
|---|---|
| Data | A single `databases/databases.json` with a JSON-schema-style validator |
| UI | React 18 + Vite, single self-contained `src/App.jsx` |
| Typography | IBM Plex Sans + Instrument Serif + JetBrains Mono |
| Hosting | Static build, deploys to GitHub Pages via Actions |
| Validation | Node script (`scripts/validate-data.mjs`) enforcing required fields, enums, HTTPS URLs, and profile README presence |
## Repository layout
```text
databases/
databases.json Canonical dataset (single source of truth)
/README.md Per-database profile and primary-source notes
src/
App.jsx Single-file React UI
main.jsx React entry point
scripts/
validate-data.mjs Catalog validator
.github/
workflows/ Validation + Pages deploy
ISSUE_TEMPLATE/ Correction and new-database templates
index.html HTML shell with fonts and base styles
```
## Contributing
**All contributions are welcome.** Whether you're a database maintainer correcting an overstated claim, an engineer who evaluated one of these systems in production, or someone who noticed a database missing entirely — please open an issue or a pull request.
### What counts as a good contribution
**Additions**
- A graph database that belongs in scope but isn't listed
- A new primary-source URL for an existing entry
- A missing query interface or deployment option
**Corrections**
- A vector-strategy label that no longer matches current docs
- An overstated claim without primary-source backing
- A status update (`emerging` → `production`, new version, etc.)
### How to contribute
1. **Open an issue first** for anything larger than a typo — it lets us agree on scope before you spend time. Use the [correction](.github/ISSUE_TEMPLATE/correction.md) or [new database](.github/ISSUE_TEMPLATE/new-database.md) template.
2. **Fork and branch** from `main`.
3. **Edit the data:**
- Update the row in [`databases/databases.json`](databases/databases.json)
- Add or update the profile at `databases//README.md`
4. **Verify locally:**
```bash
npm run check
```
(This runs validate + lint + build — all three must pass.)
5. **Open a pull request.** Describe what changed, why the previous state was incomplete or wrong, and link the primary sources that back the correction.
### Source requirements
Primary sources only, wherever possible:
**Accepted:** official documentation, official product pages, official release notes, official source repositories.
**Not accepted:** marketing blogs without technical detail, third-party reviews.
If the public docs are not strong enough for a firm claim, **downgrade the claim** rather than inflating it. The catalog earns its usefulness by being conservative where the evidence is thin.
### Adding a new database
A new entry must include:
| Field | Required |
|---|---|
| `id` | Lowercase, dash-separated slug (used as directory name) |
| `name` | Display name |
| `model` | `rdf` / `property` / `multi` / `specialized` |
| `status` | `production` / `emerging` / `legacy` |
| `license` + `license_type` | Human label + taxonomy value |
| `website` | HTTPS URL |
| `query_interfaces` | Non-empty array |
| `vector_strategy` + `vector_summary` | Taxonomy value + one-sentence justification |
| `ha`, `deployment`, `best_fit`, `notes` | Short factual strings |
| `source_urls` | At least one HTTPS primary-source URL |
| `profile` | Path to `databases//README.md` (must exist) |
The validator enforces all of the above. See any existing entry in [`databases/databases.json`](databases/databases.json) for the exact shape.
### Reporting inaccuracies
If you work on, maintain, or have production experience with one of the listed systems and something looks wrong, please file an issue — we'd rather correct an overstated or outdated entry than leave it in place.
## Related documents
- [CONTRIBUTING.md](CONTRIBUTING.md) — short-form contribution guide
- [DISCLAIMER.md](DISCLAIMER.md) — scope, limits, and intent
## License
Released under the [MIT License](LICENSE). The underlying facts about each product belong to the respective vendors and projects.
## Acknowledgements
Thanks to the maintainers of every database in the catalog — and to anyone who has ever filed a correction issue on a technical reference like this one. Independent, primary-source catalogs only stay useful when people who know the systems best take the time to push back.
---