COMPARE

Galactus DB vs Neo4j.

Galactus DB speaks Cypher and Bolt, so Neo4j applications and drivers can often move across with few changes. Here is how the two compare.

Galactus DB compared with Neo4j
Galactus DBNeo4j
Query languageCypher, with documented coverageCypher
ProtocolBolt 4.4 and 5.0–5.4; TCP, TLS and WebSocket on one portBolt
DriversOfficial Neo4j drivers, plus open source drivers (Apache-2.0) for C#, Rust, Java, Go, Node, C++ and PythonOfficial Neo4j drivers
Graph algorithmsBuilt in: centrality, communities, similarity, FastRP, pathfindingGraph Data Science library, installed as a plugin
APOCSelected functions and procedures built inAPOC library, installed as a plugin
IndexesRange, hash, composite, full-text, vector, point and spatial shapeRange, text, full-text, vector and point
DeploymentOne server per instance, with read-only replica databases on the same instance or another server, each promoted with one statement. The database image is about 5 MB to downloadSingle node in Community Edition; clustering in Enterprise Edition
WritesReads run together; one write executes at a timeConcurrent write transactions
Change data captureChange streams and subscriptions with label and property triggers in every edition, including Community. Same-instance replicas in every edition (in Community, a replica counts as a database)Change data capture in Enterprise Edition and Aura; clustering in Enterprise Edition
LicenceCommercial, with Galactus DB Community free for any use, including productionCommunity Edition under GPLv3; Enterprise Edition under a commercial licence
Moving data inReads Neo4j 4.x and 5.x .dump files directly—

Measured side by side.

Run it yourself

The same graph and the same queries, sent over Bolt by the same Python client: 100,000 people who each know two others, with an index on the person ID, and 8 CPUs and 4 GB of RAM for each container. The figures come from our open benchmark suite. Neo4j 5.26.32 Community, with the heap and page cache its own memory recommendation gives for 4 GB, was measured on 1 November 2026. Galactus DB 2.4.3 was measured on 14 November 2026 with the same suite, machine and limits; Neo4j was not re-run. Every answer was checked to match.

Shortest paths, median latency: shortest path 0.52 ms on Galactus DB Paged and 0.48 ms on Resident against 1.46 ms on Neo4j; all shortest paths 0.54 ms and 0.51 ms against 1.31 ms; weighted shortest path 23.1 ms and 22.9 ms against 26.1 ms.Lookups and traversals: index lookup 0.48 ms on Paged and 0.47 ms on Resident against 1.22 ms on Neo4j; friends of friends 0.48 ms against 1.13 ms; filtered scan of 100,000 people 8.3 ms on both Galactus DB engines against 14.9 ms; 4,103 and 4,117 lookups per second from 16 clients against 3,005.Memory: with the graph loaded, 169 MB on Galactus DB Paged and 97 MB on Resident against 3,043 MB on Neo4j; peak while loading 146 MB and 99 MB against 3,049 MB.Loading and start-up: 71,400 nodes per second on Galactus DB Paged and 77,800 on Resident against 38,100 on Neo4j; 58,600 and 88,200 relationships per second against 36,500; restart to the first answer 0.76 s and 0.75 s against 14.9 s.
Medians of three passes on an Intel Core i9-13900K. Galactus DB figures name the engine where the two differ: Paged is the default, Resident keeps the whole graph in memory.
WorkloadGalactus DBNeo4j
Shortest path, up to 6 hops0.48 ms (Resident), 0.52 ms (Paged)1.46 ms
All shortest paths, up to 6 hops0.51 ms (Resident), 0.54 ms (Paged)1.31 ms
Weighted shortest path (Dijkstra)22.9 ms (Resident), 23.1 ms (Paged)26.1 ms
Index lookup0.47 ms (Resident), 0.48 ms (Paged)1.22 ms
Friends of friends0.48 ms1.13 ms
Filtered scan of 100,000 people8.3 ms14.9 ms
16 concurrent clients, lookups per second4,117 (Resident), 4,103 (Paged)3,005
Bulk load, nodes per second77,800 (Resident), 71,400 (Paged)38,100
Bulk load, relationships per second88,200 (Resident), 58,600 (Paged)36,500
Memory with the graph loaded97 MB (Resident), 169 MB (Paged)3,043 MB
Restart to the first correct answer0.75 s (Resident), 0.76 s (Paged)14.9 s
Container image13 MB587 MB

Galactus DB led on every workload in the run. Shortest paths came back in about a third of Neo4j's time, and index lookups and two-hop traversals in under half. It scanned 100,000 people in 8.3 ms against 14.9 ms, and loaded nodes at about twice the rate. Both ran the same Graph Data Science call for weighted paths, from a projection built once. Neo4j's memory reflects the 2 GB heap and 512 MB page cache it recommends for a 4 GB machine. Galactus DB ran its default buffered durability, which syncs the commit log every 50 ms.

Choose Galactus DB when…

  • You want Cypher and your Neo4j drivers on a database that is small to run.
  • Bulk loads, indexed lookups and short traversals dominate the workload.
  • You want graph algorithms and APOC utilities without managing plugins.
  • The graph will outgrow memory and still needs to serve production traffic.
  • You want change data capture, and read replicas on the same server, without an Enterprise licence.

What you can leave out

  • A JVM heap and page cache to size and tune.
  • Plugins for graph algorithms, APOC or vector search.
  • A separate licence for change streams and subscriptions.
  • An account before you start: Community is free, in production too.
  • Third-party runtime packages in the drivers.

Moving from Neo4j.

Questions

Is Galactus DB a drop-in replacement for Neo4j?

For many applications, yes. Galactus DB speaks Cypher over Bolt 4.4 and 5.0–5.4, accepts the official Neo4j drivers and includes graph algorithms and selected APOC procedures. Check your queries against the compatibility guide, and recreate indexes and constraints after moving your data.

Can I use the Neo4j drivers with Galactus DB?

Yes. The official Neo4j drivers connect with bolt://, bolt+s:// and neo4j:// URLs. The Python driver only accepts servers that identify as Neo4j, so start Galactus DB with GDB_NEO4J_AGENT=true when you use it. Open source Galactus DB drivers, under Apache-2.0, are also available for C#, Rust, Java, Go, Node, C++ and Python.

Can I import an existing Neo4j database?

Yes. Galactus DB reads offline Neo4j 4.x and 5.x .dump files directly, from Explorer or with CALL gdb.neo4j.import. Nodes, labels, properties and relationships are imported in one atomic statement. Schema, indexes, constraints and users are not imported, so recreate those afterwards.

Does Galactus DB support clustering?

Each Galactus DB instance runs on one server, and replicas carry the rest. Since 1.4.0 it can keep read-only replica databases on the same instance, and since 1.6.5 on another server (the source needs an Enterprise licence), including delayed replicas you can pause, resync or promote, and stream every change to subscribers. Replicas follow their source within a few milliseconds with group durability, or about 60 ms with the default buffered mode. Routing drivers are given a single-node routing table. Failover is a PROMOTE statement that you run, so you decide when a replica takes over.

How is Galactus DB licensed?

Galactus DB is commercial software with a free Community edition for any use, including production and business use. A fresh instance runs Community with no account or licence key, on any number of cores with three active user databases. Commercial adds any number of databases and native backup and restore at $400 (€370, £320) per core, per instance, per year, with discounts for longer prepaid terms. The drivers are open source under Apache-2.0.

Neo4j is a registered trademark of Neo4j, Inc. Galactus DB is not affiliated with Neo4j, Inc. Neo4j details are from its public documentation; check the current Neo4j documentation for your version.

Measure it on your own workload.

Community is free for any use and needs no account or licence key. Bring your queries, or a Neo4j dump, and see how they run.