Lim Damien

Today, we’re launching pgGraph: an Apache open-source graph traversal engine for Postgres, written in Rust 🦀 When we started Evokoa, we kept running into the same wall every serious agent team eventually hits: > Agents need to reason across relationships. > But graph DBs are expensive AF, and suck to use. So, we built pgGraph around a simple, single idea: Postgres should stay the source of truth, and the graph engine should live beside it. pgGraph does something different. > It keeps the rows in Postgres, > Compiles the topology around them, > Creates a virtual graph layer using CSR-style adjacency arrays. We're making your existing postgres database graph-traversable for agents without any of the usual BS. > No recursive join hell. > No ETL pipeline. > No second source of truth. > Blazing fast performance pgGraph is already live in production workflows across RevOps, healthcare, and visa services. We’re open-sourcing it because graph traversal should become a default primitive in the agent stack, not an enterprise migration project. Treat Postgres as a graph. Zero data migration. This is what Apache AGE should have been. Docs + Repo below.

Today, we’re launching pgGraph: an Apache open-source graph traversal engine for Postgres, written in Rust 🦀 When we started Evokoa, we kept running into the same wall every serious agent team eventually hits: > Agents need to reason across relationships. > But graph DBs are expensive AF, and suck to use. So, we built pgGraph around a simple, single idea: Postgres should stay the source of truth, and the graph engine should live beside it. pgGraph does something different. > It keeps the rows in Postgres, > Compiles the topology around them, > Creates a virtual graph layer using CSR-style adjacency arrays. We're making your existing postgres database graph-traversable for agents without any of the usual BS. > No recursive join hell. > No ETL pipeline. > No second source of truth. > Blazing fast performance pgGraph is already live in production workflows across RevOps, healthcare, and visa services. We’re open-sourcing it because graph traversal should become a default primitive in the agent stack, not an enterprise migration project. Treat Postgres as a graph. Zero data migration. This is what Apache AGE should have been. Docs + Repo below.

Today, we’re launching pgGraph: an Apache open-source graph traversal engine for Postgres, written in Rust 🦀 When we started Evokoa, we kept running into the same wall every serious agent team eventually hits: > Agents need to reason across relationships. > But graph DBs are expensive AF, and suck to use. So, we built pgGraph around a simple, single idea: Postgres should stay the source of truth, and the graph engine should live beside it. pgGraph does something different. > It keeps the rows in Postgres, > Compiles the topology around them, > Creates a virtual graph layer using CSR-style adjacency arrays. We're making your existing postgres database graph-traversable for agents without any of the usual BS. > No recursive join hell. > No ETL pipeline. > No second source of truth. > Blazing fast performance pgGraph is already live in production workflows across RevOps, healthcare, and visa services. We’re open-sourcing it because graph traversal should become a default primitive in the agent stack, not an enterprise migration project. Treat Postgres as a graph. Zero data migration. This is what Apache AGE should have been. Docs + Repo below.

Introducing Evokoa: a new breakthrough unified context system, designed for enterprise workloads & AI agents. Every enterprise building agents hits this wall: how do I provide vast amounts of relational context to my ai agents? To do this today, > You have to spin up a separate expensive graph DB > Build heavy ETL data pipelines that break down > OR use a duct-tape solution like Apache AGE that breaks down at enterprise scale. If you're not an enteprise company > Pray to the rng gods, you get the right context > Use some slow hacked together bs > Basically. You're screwed. So, we invented Evokoa. Evokoa is an entirely new virtual graph layer that was built from the ground up for ai. > No data migration (keep your daya in your main DB) > Zero-ETL (it auto-discovers schemas) > Up to 34X less ram than neo4j w/ comparable speeds > Oh, it's also built in rust so its fast as f*ck 🦀🦀 You connect your ai agent to evokoa's MCP, and connect evokoa to everything else. Swap between models anytime (model-agnostic), and its magnitudes cheaper than a traditional graph DB. And it uses mathematics, not ai, to create the graph, so everything is fully auditable and deterministic. Evokoa is already being deployed around the world in high-intensity workflows and agents that need accurate context, with no compromise. This includes healthcare, international enterprise, visa services and more. Sign up to our beta 👇