Updated
Hyperspell
Was a memory and context layer for AI agents. It connected your users' data sources, indexed their documents continuously and gave your agent the relevant context. It now sells a "company brain", a context graph of a company's own tools that internal agents read, by demo only.
Shut down / archived: Pivoted to a company brain for a business's own agents (book a demo, no pricing page). Its SDKs are still published, but it is no longer a memory API for your product's users. Source ↗
Profile checked
Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗
How makers use Hyperspell
What Hyperspell is used for
Agent Memory · Hosted memory API →Agents that needed memory and context drawn from their users' connected data sources.Trade-off: Pivoted to a "company brain" for a business's own agents; no longer a memory API for your product's users.
When to use Hyperspell, and when not
Something else fits better if
- You want to add user memory to an existing agent with a few API calls and a free tier to start: Mem0 or Supermemory.
- Memory must stay on your own infrastructure, built as a graph over your data: Cognee or Graphiti.
- Your agent needs dated facts that change over time, from business data as well as chats: Zep or Graphiti.
- You'd rather build the agent on a platform where memory is built in: Letta.
- You want memory as plain Markdown files you can read, edit and share across your own AI tools: Basic Memory.
Who uses it
No maker's live product on record yet.
We haven't found a product that uses Hyperspell yet.
None of these in makers' own words.
Alternatives to Hyperspell
All alternatives by situation →Questions makers ask about Hyperspell
Is Hyperspell open source or self-hostable?
Not open source, and hosted only.
Can AI coding agents work with Hyperspell?
No llms.txt, official MCP server or CLI found yet.
Who uses Hyperspell?
No tracked product yet. source ↗