Alternatives
Products that do what We built a type-safe Python ORM for RedisGraph/FalkorDB does
We were tired of writing raw Cypher — escaping quotes, zero autocomplete, refactoring nightmares — so we built GraphORM: a type-safe Python ORM for RedisGraph/FalkorDB using pure Python objects. What it does Instead of fragile Cypher: query = """ MATCH (a:User {user_id: 1})-[r1:FRIEND]->(b:User)-[r2:FRIEND]->(c:User) WHERE c.user_id <> 1 AND b.active = true WITH b, count(r2) as friend_count WHERE friend_count > 5 RETURN c, friend_count ORDER BY friend_count DESC LIMIT 10 """ You write type-safe Python: stmt = select().match( (UserA, FRIEND.alias("r1"), UserB), (UserB,…
- 1PA
2017 · github.com
- 2GF
2015 · github.com
- 3TT
Hi HN, I built TypeGraph, a type-safe knowledge graph library that runs on your existing Postgres or SQLite. After years of building knowledge graphs and other graphy things, I had the same issues whenever an application’s relationship modeling (permissions, RAG context, recommendations) outgrew standard ORMs: deploy a dedicated graph database (heavy ops, separate infra, data syncing headaches), or roll a graph-in-SQL implementation by hand. I've hand-rolled enough of these to know the drill: same table structures, same traversal boilerplate, same performance surprises. I wanted graph…
Feb 2026 · typegraph.dev
- 4GG
2016 · graphene-python.org
- 5AE
2020 · github.com
- 6FO
Hey HN, I’m Roi, one of the co-creators of FalkorDB. We’re a growing team working on a graph database designed for production workloads and GraphRAG systems. The new release (v4.10.0) is out, and I wanted to share some of the updates and ask for feedback from folks who care about performance, memory efficiency in graph-heavy systems. FalkorDB is an open-source property graph database that supports OpenCypher (with our own extensions) and is used under the hood for retrieval-augmented generation setups where accuracy matters. The big problem we’re working on is scaling graph databases without…
2025
- 7SB
2020 · splitgraph.com
- 88R
2019 · 8base.com
- 9AR
2017 · github.com
- 10RU
2019 · github.com
- 11GD
2016 · github.com
- 12AO
2020 · github.com
- 13GQ
2017 · github.com
- 14AP
2018 · github.com
- 15BS
Hello HN After becoming allergic to SQL, I opened 120+ issues in Dgraph, Typedb and surrealdb looking for the perfect graphDB. None of them was built for agents nor were they the perfect fit for what we wanted to achieve: fully ditching the SQL legacy to properly model reality. So we decided to build BlitzGraph In BlitzGraph, records (units) can belong to multiple types (kinds) and evolve through time. Also polymorphic relations are first class and multiple kinds can play the same role. This design helps to escape the old table paradigm and track entities throughout their lifecycle without…
Jun 2026 · blitzgraph.com
- 16PA
2015 · bitbucket.org
- 17AO
2017 · github.com
- 18MG
2016 · github.com
- 19WT
2020 · wundergraph.com
- 20RC
2016 · github.com
- 21PR
2015 · github.com
- 22OA
2015 · orator-orm.com
- 23

- 24KA
2017 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →