FalkorDB vs TuringDB
Both are property graph databases queried with openCypher. FalkorDB (2018-07, SSPL-1.0, C) ranks #5 this month; TuringDB (2025, BUSL-1.1, C++) ranks #39. They differ on 24 of 46 surveyed features.
| Attribute | FalkorDB | TuringDB |
|---|---|---|
| At a glance | ||
| Rank | #5 | #39 |
| Score | 69.8 | 49.6 |
| GitHub stars | 10.5k | 188 |
| Popularity | 68.1 | 41.5 |
| Activity | 78.6 | 76.1 |
| Community | 69.8 | 50.5 |
| Research | 55.3 | 50.0 |
| Fundamentals | ||
| Description | A property graph database that runs as a Redis module, formerly RedisGraph. Uses GraphBLAS sparse matrix operations for query execution, enabling parallel graph traversal. | An in-memory, column-oriented property graph database engine focused on analytical and read-intensive workloads over large graphs. |
| Vendor | FalkorDB | Turing Biosystems |
| Model | Property Graph | Property Graph |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2018-07 | 2025 |
| Status | active | active |
| License | SSPL-1.0 | BUSL-1.1 |
| Written in | C | C++ |
| Query languages | openCypher | openCypher |
| gdotv support | yes | no |
Feature scores 24 of 46 rows differ
| Feature | FalkorDB | TuringDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | ✓ |
| Open Source | ✓ | · |
| Pricing | ✓ | 0.5 |
| Trendiness | 0.5 | 0.25 |
| Deployment | ||
| Containerization | ✓ | ✓ |
| Work as dedicated instance | ✓ | ✓ |
| Work as embedded | · | ✓ |
| Testing in-memory version | ✓ | ✓ |
| Platform | ||
| Operating on Linux | ✓ | ✓ |
| Operating on Windows | 0.75 | · |
| SaaS offering | · | ✓ |
| Operations | ||
| Automatic updates | · | · |
| Client side caching | 0.5 | · |
| Data versioning support | · | ✓ |
| Live backups | 0.5 | · |
| Distribution | ||
| Cluster Re-balancing | · | · |
| Data Distribution | · | ✓ |
| High-Availability | 0.5 | ✓ |
| Query Distribution | · | · |
| Replication support | ✓ | · |
| Developer Experience | ||
| Data types defined | ✓ | ✓ |
| Logging/Auditing | 0.5 | ✓ |
| Object-Graph Mapper | ✓ | · |
| Reactive programming | 0.5 | · |
| 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 | 0.5 | · |
| Authentication | 0.5 | ✓ |
| Authorization | 0.5 | ✓ |
| Data encryption | 0.5 | · |
Links
- FalkorDB · website · github · full profile
- TuringDB · website · github · full profile