# memgraph

> High-performance open-source in-memory graph database for GraphRAG, AI memory, agentic AI, and real-time graph analytics. Cypher-compatible, built in C++.

- **URL**: https://www.freshcrate.ai/projects/memgraph
- **Author**: memgraph
- **Category**: Databases
- **Latest version**: `v3.10.1` (2026-05-15)
- **License**: NOASSERTION
- **Source**: https://github.com/memgraph/memgraph
- **Homepage**: https://memgraph.com
- **Language**: C++
- **GitHub**: 3,934 stars, 220 forks
- **Registry**: github
- **Tags**: `ai`, `ai-agents`, `ai-memory`, `c++`, `context-graph`, `cypher`, `enterprise-context`, `graph`, `graph-algorithms`

## Description

High-performance open-source in-memory graph database for GraphRAG, AI memory, agentic AI, and real-time graph analytics. Cypher-compatible, built in C++.

## Recent releases

| Version | Date | Urgency | Changes |
| --- | --- | --- | --- |
| `v3.10.1` | 2026-05-15 | High | # Memgraph v3.10.1 - May 15th, 2026  ## 🐞 Bug fixes  - Fixed Memgraph and MAGE Docker containers failing to start when there are no command line arguments provided, e.g. `docker run -it memgraph/memgraph:3.10.0`.  [#4145](https://github.com/memgraph/memgraph/pull/4145) |
| `v3.10.0` | 2026-05-13 | High | # Memgraph v3.10.0 - May 13th, 2026  ## ⚠️ Breaking changes  - Coordinators ignore periodic storage snapshots (no user data to snapshot), and `--init-file` / `--init-data-file` are rejected on coordinators and on data instances that join an HA cluster (`--management-port` set). Remove those flags from coordinator and HA data-instance configs before upgrading, and run any bootstrap Cypher against the MAIN after the cluster is formed instead of relying on startup init files.  [#4035](https://g |
| `v3.9.0` | 2026-03-25 | Medium | # Memgraph v3.9.0 - March 25th, 2026  ## ⚠️ Breaking changes  - HA coordinator data directories from previous versions contain corrupted cluster configuration log entries that cannot be recovered. When upgrading to 3.9, all coordinator data directories must be cleaned and coordinators restarted fresh; run setup queries again on the new coordinator leader. Data instances are not affected. See the [migration guide](/clustering/high-availability/migrating-to-v3-9-ha). [#3900](https://github.com |
| `v3.8.1` | 2026-02-17 | Low | # Memgraph v3.8.1 - February 17th, 2026  ## 🐞 Bug fixes  - Fixed using `LOAD CSV` via SSL, by adding missing `ca-certificates` package to the Memgraph Docker image  [#3793](https://github.com/memgraph/memgraph/pull/3793)  - A data instance could've get into a deadlock state when some specific timings are triggered. This is now fixed so users should be able to always start a data instance without any deadlocks occurring. [#3787](https://github.com/memgraph/memgraph/pull/3787)  - Fix so t |
| `v3.8.0` | 2026-02-11 | Low | # Memgraph v3.8.0 - February 11th, 2026  ## ⚠️ Breaking changes  - Switching to analytical mode now fails if constraints exist. Creating constraints or text indexes in analytical mode is now blocked. Workflows that relied on these operations will need to be updated. [#3461](https://github.com/memgraph/memgraph/pull/3461) - Removed deprecated flags `--auth-module-executable`, `--bolt_session_inactivity_timeout`, and `--storage_parallel_index_recovery`. Users should migrate to `--auth-module- |
| `v3.7.2` | 2025-12-23 | Low | # Memgraph v3.7.2 - December 23rd, 2025  ## 🐞 Bug fixes - Vector index recovery can now run in parallel, with additional improvements to index resizing and safer entry removal logic. This results in faster startup and schema recovery for databases with large vector indexes. Users can enable this behavior by starting Memgraph with `--storage-parallel-schema-recovery=true`. [#3562](https://github.com/memgraph/memgraph/pull/3562) - Complete shutdown of coordinators and Settings held locally un |
| `v3.7.1` | 2025-11-25 | Low | # Memgraph v3.7.1 - November 25th, 2025  ## ⚠️ Breaking changes  - Changed: Uses documented grammar for fine-grained edge permissions, such as `GRANT READ ON EDGES OF TYPE :FOLLOWS TO alice` or `GRANT UPDATE ON EDGES OF TYPE * TO bob`. Due to the new syntax, this is a breaking change.[#3457](https://github.com/memgraph/memgraph/pull/3457)  ## 🛠️ Improvements  - Forced the GC to acquire a shared lock in analytical mode, preventing unnecessary blocking of other transactions and improving |
| `v3.7.0` | 2025-11-19 | Low | # Memgraph v3.7.0 - November 19th, 2025  ## ⚠️ Breaking changes  - IMPORTANT: Changed fine-grained access configuration syntax and semantics to be more flexible. Permissions can be set on groups of labels matching any or exactly what is set in the `GRANT` statement. `CREATE`, `READ`, `UPDATE`, and `DELETE` permissions are no longer organised in a hierarchy and can be granted or revoked independently. This is a breaking change, and the fine-grained access syntax and semantics of Memgraph 3.6 |
| `v3.6.2` | 2025-11-04 | Low | # Memgraph v3.6.2 - November 4th, 2025  - Version bump to v3.6.2 to match the latest MAGE version. |
| `v3.6.1` | 2025-10-16 | Low | # Memgraph v3.6.1 - October 16th, 2025  ## ⚠️ Breaking changes  - Changed the behaviour of calls like `datetime({timezone:"Europe/Brussels"})`. Such calls return the current clock time. If you need the previous behaviour, then explicitly state one or more numeric fields as `0`, e.g, `datetime({year: 0, timezone:"Europe/Brussels"}`. [#3339](https://github.com/memgraph/memgraph/pull/3339)   ## 🐞 Bug fixes  - Fixed `convert_c.to_tree()` memory leak. Using `to_tree` will not indefinably inc |

## Citation

- HTML: https://www.freshcrate.ai/projects/memgraph
- Markdown: https://www.freshcrate.ai/projects/memgraph.md
- Dependencies JSON: https://www.freshcrate.ai/api/projects/memgraph/deps

_Generated by freshcrate.ai. Indexes github releases for AI-agent ecosystem packages._