KGLite vs Neo4j
Both are property graph databases queried with openCypher. KGLite (2026-06, MIT, Rust) ranks #133 this month; Neo4j (2007, GPL-3.0, Java) ranks #1.
| Attribute | KGLite | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #133 | #1 |
| Score | 22.0 | 83.3 |
| GitHub stars | 37 | 17.2k |
| Popularity | 29.8 | 97.3 |
| Activity | 84.4 | 86.7 |
| Community | 30.6 | 90.2 |
| Research | 49.6 | 98.6 |
| Fundamentals | ||
| Description | An embedded knowledge graph for Python written in Rust. Speaks openCypher, ships with three storage modes (in-memory, mmap, disk-backed CSR), pandas DataFrame I/O, a code_tree parser that turns source trees into call graphs across 9 languages, and a bundled MCP server for LLM agents. | A property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library. |
| Vendor | Kristian dF Kollsgård | Neo4j Inc |
| Model | Property Graph | Property Graph |
| Kind | embedded | database |
| Category | Emerging | Established |
| First released | 2026-06 | 2007 |
| Status | active | active |
| License | MIT | GPL-3.0 |
| Written in | Rust | Java |
| Query languages | openCypher, Custom API | Cypher, GQL |
| gdotv support | no | yes |
Feature scores — not surveyed for KGLite
| Feature | KGLite | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | — | ✓ |
| Commercial support | — | ✓ |
| Live community | — | ✓ |
| Open Source | — | ✓ |
| Pricing | — | 0.5 |
| Trendiness | — | ✓ |
| Deployment | ||
| Containerization | — | ✓ |
| Work as dedicated instance | — | ✓ |
| Work as embedded | — | ✓ |
| Testing in-memory version | — | ✓ |
| Platform | ||
| Operating on Linux | — | ✓ |
| Operating on Windows | — | ✓ |
| SaaS offering | — | ✓ |
| Operations | ||
| Automatic updates | — | · |
| Client side caching | — | · |
| Data versioning support | — | · |
| Live backups | — | ✓ |
| Distribution | ||
| Cluster Re-balancing | — | · |
| Data Distribution | — | ✓ |
| High-Availability | — | ✓ |
| Query Distribution | — | ✓ |
| Replication support | — | ✓ |
| Developer Experience | ||
| Data types defined | — | ✓ |
| Logging/Auditing | — | ✓ |
| Object-Graph Mapper | — | ✓ |
| Reactive programming | — | ✓ |
| Documentation up-to-date | — | ✓ |
| Binary protocol | — | ✓ |
| CLI | — | ✓ |
| GUI | — | ✓ |
| Data Model | ||
| Multi-database | — | ✓ |
| Graph-native data | — | ✓ |
| REST API | — | ✓ |
| Query Language | — | ✓ |
| Transactions | ||
| Granular locking | — | ✓ |
| Multiple isolation levels | — | ✓ |
| Read committed transaction | — | ✓ |
| Transaction support | — | ✓ |
| Schema & Security | ||
| Constraints | — | ✓ |
| Schema support | — | ✓ |
| Secondary indexes | — | ✓ |
| Server side procedures | — | ✓ |
| Triggers | — | ✓ |
| Authentication | — | ✓ |
| Authorization | — | ✓ |
| Data encryption | — | · |
Links
- KGLite · website · github · full profile
- Neo4j · website · github · full profile