| Feature | gDown | Neo4j Community | AuraDB Professional | AuraDB Business Critical | Memgraph Community | FalkorDB | ArcadeDB |
|---|---|---|---|---|---|---|---|
| openCypher language gDown passes all 3,863 TCK scenarios. | Yes | Yes | Yes | Yes | Yes | Partial or plan-dependent | Yes |
| Bolt protocol gDown speaks Bolt up to 5.4. | Yes | Yes | Yes | Yes | Yes | Partial or plan-dependent | Yes |
| Several databases on one server Community: a single user database. Aura Professional: one database per instance; Business Critical: several. | Yes | No | No | Yes | No | Yes | Yes |
| Start and stop a database gDown: STOP DATABASE and START DATABASE, a stopped database refuses requests and keeps its files. Neo4j: the same commands, Enterprise only, not on Aura. ArcadeDB: the server commands close database and open database. | Yes | No | No | No | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) | Yes |
| Replicated cluster (high availability) gDown: Raft, any member accepts writes. Community: no clustering. Aura Professional: single zone, no SLA; Business Critical: multi-zone, 99.95% SLA. | Yes | No | Partial or plan-dependent | Yes | Partial or plan-dependent | Partial or plan-dependent | Yes |
| Roles and privileges per label and property Community has no custom roles; Aura Professional has no fine-grained access control; Business Critical has RBAC and property-based control. | Yes | No | No | Yes | Partial or plan-dependent | Partial or plan-dependent | Partial or plan-dependent |
| Single sign-on (OpenID Connect) Not in Community or Aura Professional; Business Critical offers SSO. | Yes | No | No | Yes | No | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) |
| Online backup gDown: GET /cluster/backup. Community: offline dump only. Aura: daily backups, kept 7 days (Professional) or 30 days with hourly point-in-time restore (Business Critical). | Yes | Partial or plan-dependent | Yes | Yes | Yes | Yes | Yes |
| Cypher queries published as REST APIs (OpenAPI) gDown generates the contracts, checks tokens, limits the rate and serves a Swagger UI. Neo4j and Aura offer HTTP query endpoints, not published contracts. | Yes | Partial or plan-dependent | Partial or plan-dependent | Partial or plan-dependent | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) | Partial or plan-dependent |
| Vector and full-text indexes All three; gDown's vector index is exact up to 2,000 vectors, then approximate (HNSW). | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| APOC procedures A subset in gDown and on Aura; Community through the APOC plugin. | Partial or plan-dependent | Yes | Partial or plan-dependent | Partial or plan-dependent | Not found in the documentation read (not the same as absent) | No | Not found in the documentation read (not the same as absent) |
| WebAssembly modules inside a database Sandboxed: no imports, bounded memory and compute. | Yes | No | No | No | No | No | No |
| Single native executable, no JVM gDown is a GraalVM native image; Neo4j runs on the JVM; Aura is managed. | Yes | No | Not applicable | Not applicable | Yes | Yes | Partial or plan-dependent |
| Memory given back by an idle database gDown: UNLOAD DATABASE, or automatic unloading after a delay; the database stays online and reloads on its first request. Neo4j: STOP DATABASE (Enterprise), which shuts the database down completely until START DATABASE; Community counts No. Aura, Memgraph, FalkorDB and ArcadeDB: nothing found in the documentation read. | Yes | No | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) | Not found in the documentation read (not the same as absent) |
| Runs on your own machines Aura is a managed cloud service. | Yes | Yes | No | No | Yes | Yes | Yes |
Neo4j Community and Aura entries follow Neo4j's public pricing and product pages (October 2026) and can change: check them before relying on them. gDown entries come from its README and tests. The entries of Memgraph (Community edition), FalkorDB and ArcadeDB follow their official documentation (October 2026).
Cypher coverage
The openCypher TCK (Technology Compatibility Kit) run against every base through its own client: the share of scenarios each one passes.
| Database | Passed / scenarios | Pass rate |
|---|---|---|
| gDown | 3,863 / 3,863 | 100.00 % |
| Neo4j | 3,859 / 3,863 | 99.90 % |
| ArcadeDB | 3,737 / 3,863 | 96.74 % |
| FalkorDB | 2,616 / 3,863 | 67.72 % |
| Memgraph | 2,559 / 3,863 | 66.24 % |
| Apache AGE | 2,324 / 3,863 | 60.16 % |
| TuGraph | 658 / 3,863 | 17.03 % |
Method: the same 3,863 scenarios for every base, run through our client for each one (Bolt, RESP for FalkorDB, JDBC for Apache AGE). AGE has no Cypher endpoint: we wrap its queries in cypher() ourselves. The scenarios that declare their own procedure (chapter CALL) need the TCK test procedures installed in each base through its extension mechanism; where a base cannot install them, they count as errors. An expected error is only checked to be raised; its kind is not compared. The weakest chapters count only the scenarios that ran.
Syntax compatibility with Neo4j 5.26
586 queries (syntax, functions, schema, procedures, expected errors) are put to Neo4j 5.26 and to gDown with EXPLAIN: each must be accepted or refused by both. The verdicts match for all but 10, listed below with their reason. The comparison runs in gDown's build (CorpusTest) against the verdicts recorded from Neo4j 5.26 Community.
| Query | Neo4j 5.26 | gDown | Why |
|---|---|---|---|
SHOW ROLESSHOW SERVERSCREATE DATABASE fooDROP DATABASE foo | refused | accepted | An administration command of the Enterprise edition: Community, the reference, refuses it; gDown accepts it as Enterprise does. |
PROFILE MATCH (n) RETURN nPROFILE MATCH (n:Person) RETURN count(n) | accepted | refused | An artefact of the test, not a gap: it prefixes EXPLAIN to the PROFILE query, which no server accepts; gDown runs a plain PROFILE. |
SHOW CURRENT USER PRIVILEGES | refused | accepted | gDown reads it as the privileges of the signed-in user; the reference refused it, either as a command of the Enterprise edition or for its spelling (Neo4j documents SHOW USER PRIVILEGES). |
CALL apoc.help('x')RETURN apoc.text.join(['a'], ',') | refused | accepted | The reference had no APOC installed; gDown has a built-in subset of APOC Core. |
RETURN vector([1,2], 2, INTEGER) | refused | accepted | The vector() function and the VECTOR type came after Neo4j 5.26; gDown has them. |
Not measured: result equality over that corpus, identical error messages, fine plan semantics, APOC functions. Not supported: LDAP/SAML, Bolt 5.5 and later.