Gaffer vs Neptune
Gaffer is a other database; Neptune is a multiple database. Gaffer (2015-12, Apache-2.0, Java) ranks #66 this month; Neptune (2017-11, Proprietary, C++) ranks #14. They differ on 27 of 46 surveyed features.
| Attribute | Gaffer | Neptune |
|---|---|---|
| At a glance | ||
| Rank | #66 | #14 |
| Score | 44.4 | 61.1 |
| GitHub stars | 1.8k | — |
| Popularity | 57.9 | 61.0 |
| Activity | 42.8 | 60.9 |
| Community | 30.3 | 61.8 |
| Research | — | 60.4 |
| Fundamentals | ||
| Description | A graph database framework with pluggable storage backends (Accumulo, HBase, Parquet). Developed by GCHQ for large-scale graph analysis with built-in timestamp management. | A fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries). |
| Vendor | GCHQ | Amazon Web Services |
| Model | Other | Multiple |
| Kind | query-engine | database |
| Category | Established | Enterprise |
| First released | 2015-12 | 2017-11 |
| Status | deprecated — Repository archived by GCHQ; last change June 2025. | active |
| License | Apache-2.0 | Proprietary |
| Written in | Java | C++ |
| Query languages | Custom API | Gremlin, SPARQL, openCypher |
| gdotv support | no | yes |
Feature scores 27 of 46 rows differ
| Feature | Gaffer | Neptune |
|---|---|---|
| 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 | ✓ | 0.5 |
| Replication support | ✓ | ✓ |
| Developer Experience | ||
| Data types defined | 0.5 | 0.5 |
| 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 | ✓ | 0.5 |
| Secondary indexes | · | ✓ |
| Server side procedures | · | · |
| Triggers | · | · |
| Authentication | ✓ | ✓ |
| Authorization | ✓ | ✓ |
| Data encryption | · | ✓ |
Links
- Gaffer · website · github · full profile
- Neptune · website · full profile