supermemory/apps/docs/overview/use-cases.mdx
MaheshtheDev 5258cb74c8 chore(web): reduce the app to a redirect shell, drop the browser extension (#1651)
chore(web): reduce the app to a redirect shell, drop the browser extension

app.supermemory.ai now forwards everything to the console: plugin, OAuth and invite paths get an immediate 308 with the query intact, everything else shows a short notice first. Removes the browser extension workspace.

chore(web): give the moved notice a proper design

Hostnames become the headline, one primary action, a draining line for the countdown, DM Sans and the dot-grid backdrop from the brand.

chore(docs): point docs and README at the console, drop stale sections

Docs and both READMEs now link to console.supermemory.ai for API keys. Removed the company-brain docs tab with a redirect, and trimmed the README app section.

chore(web): give the redirect five seconds
2026-09-07 19:56:46 +00:00

73 lines
2.9 KiB
Text
Raw 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.
</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 container’s 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) |
| 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>