Database guides
Memgraph
In-memory graph that speaks Bolt and Cypher, so it rides the same driver as Neo4j — with no password by default.
Memgraph is wire-compatible with Neo4j: same Bolt protocol, same Cypher. AddisDB drives it with the same driver, so node labels appear in the sidebar and results land in the grid identically.
Who it is for
Memgraph keeps the graph in memory and is built for streaming: it ingests from Kafka and friends and can run triggers as data arrives, so the graph reflects what is happening now rather than what happened last night.
In-memory is the defining constraint in both directions. Traversals are fast because there is no page cache to miss, and the working set has to fit in RAM — durability comes from snapshots and a write-ahead log rather than from the data living on disk in the first place.
It fits real-time fraud and anomaly detection, live network and infrastructure topology, and dynamic routing — cases where a graph query needs to answer against data that is seconds old.
Set up the database
- Local: docker run -p 7687:7687 -p 7444:7444 memgraph/memgraph-platform, which also brings up the Memgraph Lab web UI.
- Managed: Memgraph Cloud. Create a project and copy the host, port and credentials.
- A default local install has authentication disabled — there is no username or password to supply.
- Enable authentication before exposing an instance to anything but your laptop.
- Size the machine for the graph plus its indexes; an instance that cannot hold the dataset will not silently spill to disk.
Connect from AddisDB
- New Connection → Memgraph under Graph. Port prefills to 7687 and the database to memgraph.
- Leave Username and Password blank for a default local instance — Memgraph ships with auth off.
- For Memgraph Cloud, fill in the credentials from the console and set SSL mode to require.
- Test, then Save.
Cypher, with its own accent
The language is Neo4j’s, but not every procedure is. Memgraph implements its own MAGE library rather than APOC, so a query copied from a Neo4j answer that calls apoc.* will not resolve. Graph algorithms live under names like pagerank and community_detection instead.
CALL pagerank.get()
YIELD node, rank
RETURN node.name AS name, rank
ORDER BY rank DESC
LIMIT 10;
What AddisDB gives you
- Node labels in the sidebar, read with the same Cypher introspection used for Neo4j.
- Cypher results in the grid, with the JSON tab for full nodes and relationships.
- Read-only enforcement for mutating Cypher clauses.
- The Chart view, ⌘K search, and AI chat that writes Cypher against your labels.
- The Live Monitor over SHOW TRANSACTIONS, with per-label node counts.