Skip to main content
Supermemory is one context engine. These are the shapes teams ship on top of it.

Agents that remember

Personal assistants

Preferences, people, projects, and decisions across sessions — without replaying the entire chat history into every prompt.

Customer support agents

Account history, past tickets, and product facts at answer time. Isolate each customer with a container tag.

Sales & success copilots

Remember the account, stakeholders, and last commitments. Profiles keep “always know” context warm.

Coding agents

Project conventions, past decisions, and repo context via API, MCP, or plugins (Claude Code, Codex, OpenClaw, and more).

Knowledge and retrieval

Chat with your stack

Drive, Notion, Gmail, OneDrive, S3, GitHub, web crawler — sync sources, then ask questions with managed SuperRAG.

Company knowledge hubs

Policies, wikis, and internal docs as shared memory for the team — API or Company Brain.

Research & analysis

Papers, notes, and long documents with multimodal ingestion (PDF, images, audio/video) and hybrid search.

Legal & compliance search

Contracts and policy corpora with strict isolation and audit-friendly deletion paths. See Security.

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, user profiles).

Surfaces (same engine)

What is Supermemory?

Product overview and mental model.

Developer Platform

Concepts, API guides, and integrations.