ArcadeDB vs Kuzu
ArcadeDB is a multiple database; Kuzu is a property graph database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #21 this month; Kuzu (2022-11, MIT, C++) ranks #13.
| Attribute | | |
|---|---|---|
| At a glance | ||
| Rank | #21 | #13 |
| Score | 57.8 | 60.2 |
| GitHub stars | 1.1k | 4k |
| Popularity | 56.1 | 65.9 |
| Activity | 80.8 | 45.0 |
| Community | 36.6 | 67.1 |
| Research | 70.3 | 95.5 |
| Fundamentals | ||
| Description | A multi-model database inspired by OrientDB, supporting graphs, documents, key-value, time-series, and search. Uses RAFT-based replication for high availability. | An embedded property graph database built for fast analytical workloads, developed as the successor to Graphflow. Archived in October 2025 after acquisition by Apple. Forked as LadybugDB and Bighorn. |
| Vendor | ArcadeDB | Kuzu Inc (acquired by Apple) |
| Model | Multiple | Property Graph |
| Kind | database | embedded |
| Category | Growing | Emerging |
| First released | 2021-09 | 2022-11 |
| Status | active | deprecated — Acquired by Apple in October 2025. Repository archived. Continued as LadybugDB and Bighorn forks. |
| License | Apache-2.0 | MIT |
| Written in | Java | C++ |
| Query languages | SQL, openCypher, Gremlin, GraphQL | openCypher |
| gdotv support | yes | yes |
Feature scores — not surveyed for Kuzu
| Feature | ArcadeDB | Kuzu |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | — |
| Commercial support | ✓ | — |
| Live community | ✓ | — |
| Open Source | ✓ | — |
| Pricing | ✓ | — |
| 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
- ArcadeDB · website · github · full profile
- Kuzu · website · github · full profile