Files
mem0/docs/open-source/features/overview.mdx
T
rudrajmehta-mem0 8296c06206 docs: remove deprecated Graph Memory references
Graph Memory was deprecated on April 16, 2026. This removes remaining
mentions across docs that could mislead readers into thinking it is still
a supported feature.

- Platform pages (overview, quickstart, faqs, platform-vs-oss, vibecoding):
  remove graph memory from feature lists, comparison table, and intro copy
- Platform features (platform-overview, mcp-integration,
  advanced-memory-operations): rephrase "graph-powered retrieval" to
  "advanced retrieval"; drop "Enable graph memories" tip; remove graph-edge
  verification step from the metadata example
- Core concepts (add, search, memory-types, memory-evaluation): remove
  "optional graph storage" / "graph features" / "graph writes" / "graph
  toggles"; drop "graph" from Entity Search description; remove outdated
  add/search architecture diagrams (replacement pending)
- Open source features (overview, rest-api): remove "graph relationships"
  and "graph backend(s)" from REST server config narrative
- API reference (organizations-projects): drop "graph settings" from
  Update Project Settings description
- Cookbooks: remove "Graph Memory on Neptune" card (page removed) and
  Neptune mention from AWS Bedrock card; remove "Graph Capabilities"
  bullet from Gemini cookbook; remove graph-memory conditional bullet from
  controlling-memory-ingestion
- CLI: remove --graph / --no-graph flags from mem0 add / mem0 search
  flag tables and MEM0_ENABLE_GRAPH env var
- Images: delete orphan add_architecture.png and search_architecture.png
2026-05-27 18:26:36 -07:00

64 lines
2.3 KiB
Plaintext

---
title: "Overview"
description: "Self-hosting features that extend Mem0 beyond basic memory storage"
icon: "list"
---
# Self-Hosting Features Overview
Mem0 Open Source ships with capabilities that adapt memory behavior for production workloads—async operations, multimodal inputs, and fine-tuned retrieval. Configure these features with code or YAML to match your application's needs.
<Info>
Start with the <Link href="/open-source/python-quickstart">Python quickstart</Link> to validate basic memory operations, then enable the features below when you need them.
</Info>
## Choose your path
<CardGroup cols={3}>
<Card title="Advanced Metadata Filtering" icon="filter" href="/open-source/features/metadata-filtering">
Query with logical operators and nested conditions.
</Card>
<Card title="Search with Reranking" icon="ranking-star" href="/open-source/features/reranker-search">
Boost search relevance with specialized models.
</Card>
<Card title="Async Memory Operations" icon="bolt" href="/open-source/features/async-memory">
Non-blocking operations for high-throughput apps.
</Card>
<Card title="Multimodal Support" icon="image" href="/open-source/features/multimodal-support">
Process images, audio, and video memories.
</Card>
<Card title="Custom Instructions" icon="wand-magic-sparkles" href="/open-source/features/custom-instructions">
Tailor how facts are extracted from text.
</Card>
</CardGroup>
<CardGroup cols={2}>
<Card title="REST API" icon="code" href="/open-source/features/rest-api">
HTTP endpoints for language-agnostic integrations.
</Card>
<Card title="OpenAI Compatibility" icon="message-bot" href="/open-source/features/openai_compatibility">
Drop-in replacement for OpenAI chat endpoints.
</Card>
</CardGroup>
<Tip>
Looking for managed features instead? Compare self-hosting vs managed in the <Link href="/platform/platform-vs-oss">Platform vs OSS guide</Link>.
</Tip>
## Keep going
<CardGroup cols={2}>
<Card
title="Configure Components"
description="Choose your LLM, embedder, vector store, and reranker with YAML or code."
icon="sliders"
href="/open-source/configuration"
/>
<Card
title="Explore Cookbooks"
description="Follow production-ready examples that combine multiple features."
icon="book"
href="/cookbooks/overview"
/>
</CardGroup>