supermemory/apps/docs/overview/use-cases.mdx
Dhravya Shah f882f1104d
docs: restructure documentation site and update integration UI (#1331)
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
2026-07-21 20:19:30 -07:00

74 lines
3 KiB
Text
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
title: "Use cases"
description: "What teams build with Supermemory — agents, knowledge, multi-tenant products, and tools."
sidebarTitle: "Use cases"
icon: "lightbulb"
---
Supermemory is one context engine. These are the shapes teams ship on top of it.
## Agents that remember
<CardGroup cols={2}>
<Card title="Personal assistants" icon="message-circle">
Preferences, people, projects, and decisions across sessions — without replaying the entire chat history into every prompt.
</Card>
<Card title="Customer support agents" icon="headphones">
Account history, past tickets, and product facts at answer time. Isolate each customer with a container tag.
</Card>
<Card title="Sales & success copilots" icon="handshake">
Remember the account, stakeholders, and last commitments. Profiles keep “always know” context warm.
</Card>
<Card title="Coding agents" icon="terminal">
Project conventions, past decisions, and repo context via API, MCP, or plugins (Claude Code, Codex, OpenClaw, and more).
</Card>
</CardGroup>
## Knowledge and retrieval
<CardGroup cols={2}>
<Card title="Chat with your stack" icon="files">
Drive, Notion, Gmail, OneDrive, S3, GitHub, web crawler — sync sources, then ask questions with managed SuperRAG.
</Card>
<Card title="Company knowledge hubs" icon="building-2">
Policies, wikis, and internal docs as shared memory for the team — API or Company Brain.
</Card>
<Card title="Research & analysis" icon="search">
Papers, notes, and long documents with multimodal ingestion (PDF, images, audio/video) and hybrid search.
</Card>
<Card title="Legal & compliance search" icon="scale">
Contracts and policy corpora with strict isolation and audit-friendly deletion paths. See [Security](/overview/security).
</Card>
</CardGroup>
## Multi-tenant products
If you are building a SaaS that needs memory **per end user** (or per workspace):
1. Map each user/workspace to a **container tag**
2. Ingest conversations and files into that tag
3. Search / load **profiles** only inside that tag
4. Issue **scoped keys** when the client must not cross tenants
5. On account deletion, erase that containers data
Deep dive lives in Developer Platform concepts ([container tags](/concepts/container-tags), [user profiles](/concepts/user-profiles)).
## Surfaces (same engine)
| If you want to… | Start here |
|---|---|
| Call the Memory API from your app | [Quickstart](/quickstart) |
| Use Claude / Cursor / coding agents | [Plugins & MCP](/supermemory-mcp/mcp) |
| Give the whole company a knowledge brain | Company Brain (from [docs home](/)) |
| Keep data on your machines | [Self-hosting](/self-hosting/overview) |
## Related
<CardGroup cols={2}>
<Card title="What is Supermemory?" icon="book-open" href="/overview/what-is-supermemory">
Product overview and mental model.
</Card>
<Card title="Developer Platform" icon="code" href="/overview/what-is-supermemory">
Concepts, API guides, and integrations.
</Card>
</CardGroup>