Evokoa

pgGraph

PostgreSQL extension adding graph search, traversal and shortest-path over your existing tables — a derived graph index queried from plain SQL, no separate graph DB or query language. Rust.

898 76 Rust NOASSERTIONupdated 3 days ago

knowledge-graphs rag

View on GitHubDispute this mapping →

Curator's take

The zero-migration bet: your tables stay the source of truth and the graph is a derived index, which makes it the cheapest possible on-ramp to GraphRAG over data already in Postgres. When NOT: the license is NOASSERTION with a managed-service funnel (polygres.com) — read the terms before production; graph-native workloads at scale still favor a dedicated store; ★898 and v1.0-young.

Mapped by ShipWithAI editors · links verified

README.md

pgGraph

Graph database superpowers for your existing Postgres data.

pgGraph is a PostgreSQL extension for running graph search, traversal, shortest path, and relationship queries directly against ordinary PostgreSQL tables.

Your tables stay the source of truth. pgGraph builds a derived graph index and lets you query it from SQL using functions in the graph schema.

[!TIP] Looking for a managed version? We have launched a managed version of pgGraph on polygres.com for full high performance GraphRAG on Postgres.

Why pgGraph?

PostgreSQL is great at relational queries, but graph-style questions often require custom recursive SQL for each schema:

“Find records related to Alice within 2 hops.”
“Find the shortest path between this person and this company.”
“Search nodes across registered tables.”

pgGraph adds graph queries on top of your existing PostgreSQL tables, without requiring a separate graph database, graph-specific storage system, or a new query language.

Quickstart

The repository quickstart builds a disposable PostgreSQL 17 image:

git clone https://github.com/evokoa

Continue your stack

What teams reach for next — and why each earns a place beside pgGraph. Ranked by curator confidence.

Alternative to See all + compare →

ontobricks

Turns Databricks Unity Catalog tables into a materialized knowledge graph: OWL ontology design, R2RML mapping, OWL 2 RL/SWRL/SHACL reasoning, auto-generated GraphQL — exposed to agents over MCP.

Why it fitsBoth build a knowledge graph over relational data you already govern. OntoBricks maps Unity Catalog with OWL reasoning inside Databricks; pgGraph is one CREATE EXTENSION on plain Postgres.

omnigraph

Lakehouse graph database for agent context — graph, vector and full-text retrieval fused in one runtime on branchable Lance/S3 storage; agent fleets write on isolated branches and merge Git-style.

Why it fitsGraph context for agents, opposite deployment bets: omnigraph is a standalone lakehouse runtime on Lance/S3; pgGraph lives inside the Postgres you already run.