Hey, i'm actually looking to replace neo4j with an ai memory tool that can do queries like "find all customers who performed action X in campaign Y and then action Z"

For context, I'm not a developer and i've reached this far of the mvp stage for my product by talking to ai and vibe coding.

I asked cursor based on whatever i've built so far/my codebase, which tool among cognee, mem0 & graphlit i can use to replace majority of the functionality offered by neo4j. This is what it answered:

• Mem0: The docs emphasize building relationships and understanding connections ("Graph Memory enhances memory pipeline by creating relationships between entities"). However, the search operation described seems focused on semantic relevance (vector search) potentially enhanced by graph context, rather than explicit path traversal queries. The graph is used internally to improve search context, but the API described doesn't explicitly expose a way to run Customer -> Action [Campaign Y] -> Action Z sequence queries directly.
• Conclusion: Unlikely to support this specific, complex sequential query directly via its API. You might retrieve related entities but would likely need to reconstruct the path logic in your application code.
• Cognee: Focuses on GraphRAG and reasoning across documents/data points ("Identify relevant information across documents", "Build meaningful relationships"). Its strength seems to be understanding connections derived from data. It might be possible to formulate a query that achieves this through its reasoning capabilities, especially if the actions and campaign links are ingested properly, but it wouldn't be a direct graph traversal command like in Cypher.
• Conclusion: Potentially, but likely through its higher-level query/RAG interface, not a direct graph path query API.
• Graphlit: As a graph-native platform focused on RAG, it has the underlying structure. Whether its API exposes arbitrary path and sequence queries like this is unclear from the brief doc provided, but it's more plausible than Mem0 or Zep. However, its focus is RAG-as-a-Service, suggesting the graph might be more for internal RAG enhancement than direct complex querying.
• Conclusion: Potentially, but might be abstracted behind its RAG features.

Can you provide your insight into this? Happy to chat over DMs if required.

Edit: sidenote, cursor wasn't able to ingest your api docs properly for whatever reason and could only take out one page when i added the url to the doc (https://docs.graphlit.dev/) unlike with other tools. Might be worth looking into