GitHub - ikwattro/neo4j-virtual-graph-playground: Docker playground for Neo4j's Virtual Graph feature

Docker playground for Neo4j's Virtual Graph feature - ikwattro/neo4j-virtual-graph-playground

GitHub

NEW: sulpher

sulpher v0.2.0 is out — a Cypher graph query language parser written in Go.

This release completes openCypher 9 coverage and adds several Neo4j 5+ idioms:

✓ CALL {} subquery blocks (with variable scope clause and IN TRANSACTIONS)
✓ COUNT {} / COLLECT {} subquery expressions
✓ Label boolean expressions: (n:Person&Employee), (n:!Bot)
✓ LOAD CSV, pattern comprehensions, reduce(), quantified paths {n,m}
✓ Hex/octal literals, || GQL string concatenation
✓ 45-file corpus, 269 queries, 100% pass rate

Compatibility: openCypher 9 100% · Neo4j 5 ~85% · Neo4j 25 ~65%

https://github.com/ha1tch/sulpher

#Go #Golang #Neo4j #Cypher #GraphDatabase #OpenSource #Parser #FOSS #Sulpher

GitHub - ha1tch/sulpher: A Cypher-compatible parser implemented in Go

A Cypher-compatible parser implemented in Go. Contribute to ha1tch/sulpher development by creating an account on GitHub.

GitHub

I updated CodeMeridian’s positioning a bit. The core idea is clearer now:

CodeMeridian is a local graph memory layer for AI coding agents.

It indexes your codebase into Neo4j and exposes precise repo context through MCP, so tools like Copilot, Claude Code, Continue.dev, Cline, or local agents can ask what matters before editing.

The part I like most: this may help small/local coding models even more, because every token matters.

https://github.com/Driftya/code-meridian

#MCP #AIagents #LocalAI #Neo4j #DotNet

GitHub - Driftya/code-meridian: A persistent code knowledge graph that gives GitHub Copilot a grounded, structural understanding of your codebase. It acts as the **deterministic context layer** — so Copilot doesn't drift or forget your architecture when working on large projects.

A persistent code knowledge graph that gives GitHub Copilot a grounded, structural understanding of your codebase. It acts as the **deterministic context layer** — so Copilot doesn't drift or f...

GitHub

AI coding agents feel sharp when a project is small.

Around MVP size, they start guessing: nearby files, stale docs, missed callers, forgotten architecture rules.

Source guardrails help, but they are still instructions.

CodeMeridian adds facts: a local Neo4j graph + MCP tools so the agent can ask what calls what, what tests cover it, and whether context is stale.

A red line before the edit.

https://github.com/Driftya/code-meridian

#OpenSource #DotNet #Neo4j #MCP

GitHub - Driftya/code-meridian: A persistent code knowledge graph that gives GitHub Copilot a grounded, structural understanding of your codebase. It acts as the **deterministic context layer** — so Copilot doesn't drift or forget your architecture when working on large projects.

A persistent code knowledge graph that gives GitHub Copilot a grounded, structural understanding of your codebase. It acts as the **deterministic context layer** — so Copilot doesn't drift or f...

GitHub
Palantir ohne Blackbox: Neo4j kündigt offene Alternative an

Aus dem Zusammenschluss der Datenanalyseplattform Neo4j und der Polizeisoftware Hume von GraphAware soll eine offene Alternative zu Palantir entstehen.

heise online
From Rows to Rivalries: Graph Analytics on the 2026 World Cup

YouTube

Did I have a bit of fun here, turning SQL to Cypher to SQL ad-infinitum? Might be.

#Neo4j

https://github.com/neo4j/neo4j-jdbc/releases/tag/6.13.0

Release 6.13.0 · neo4j/neo4j-jdbc

What's Changed Happy to announce that version 6.13.0 of our JDBC Driver is now compatible with Neo4 Virtual Graphs. This affects especially the meta data that we retrieve from the Neo4j instance (w...

GitHub
SurrealDB 3.x by the numbers | Blog | SurrealDB

Fresh SurrealDB 3.x benchmarks: 141k ops/s CRUD, scans 164× faster than 2.x, and head-to-head numbers vs. Postgres, Mongo, Neo4j, and Redis.

SurrealDB

For #Neo4j #VirtualGraph we made massive use of #JDBC. A technology that is older than many colleagues.

“How old are you again?”–“From your perspective about 346 years.” 😅

Virtual graphs sourced from relational databases: this is what a great team and I have been occupied with at #Neo4j the last months. For me, it’s kind of full circle: #SQL, #Cypher and now SQL again behind the scenes. Somewhat a journey over a decade for me and still a topic near and dear to my heart.

https://neo4j.com/blog/graph-database/introducing-neo4j-virtual-graph-graph-reasoning-on-the-data-you-already-have/

Introducing Neo4j Virtual Graph: Graph reasoning on the data you already have - Graph Database & Analytics

Over the past few quarters, we’ve seen tremendous growth in enterprise adoption of agentic workflows. Large enterprises are realizing that GraphRAG delivers more accurate results than traditional RAG, multi-hop reasoning is essential for many high-value use cases, and memory and… Read more →

Graph Database & Analytics