One memory layer for every AI surface
Re:Yi keeps durable context available to chats, agents, editors, local tools, and future MCP clients without forcing one app to own everything.
Universal memory for every AI workflow
Re:Yi
Local-first memory for AI tools, built to keep long-running work available without turning private knowledge into someone else's cloud database.
The Re:Yi official site provides product information, downloads, docs, and early access. User memories and API keys stay outside the online service by default.
Local-firstMemories, files, vectors, graphs, and jobs stay on infrastructure you control.
BYO APIUse your own LLM and embedding providers. The online service does not need model keys.
Universal by designRe:Yi is built for chat, code, documents, books, cases, notes, and future sources.
Product
Universal memory that does not reset when tools change.
Memory infrastructure should be understandable in the first minute. Re:Yi keeps that clarity while making the local-first boundary, downloads, docs, and connection readiness visible before a user commits.
Local custody before cloud convenience
Private memory, source files, embeddings, graph state, jobs, and model keys stay on infrastructure the owner controls by default.
Retrieval built for long-running work
Context can come from notes, documents, code, conversations, projects, cases, and research trails instead of a single short chat window.
Designed for personal and enterprise rollout
The same core boundary works for one person, a research group, a product team, or a self-hosted organization with stricter governance.
Why Re:Yi exists
AI tools change. Your memory should not reset every time.
Today your context is scattered across chats, editors, notes, files, and agents. Recall Core gives that context a durable home, so projects, characters, legal records, research threads, and code decisions can follow you into the next trusted tool.
Writers and researchers
Carry long stories, papers, cases, notes, and conversations across the AI tools you already use.
Builders and teams
Give agents, editors, notebooks, local MCP clients, and Provider Gateway apps the same durable memory boundary.
Private and self-hosted work
Run local-first, bring your own model APIs, and keep sensitive knowledge out of the online service backend.
Developers
Start locally, then connect tools deliberately.
Public Re:Yi starts with Control Center, docs, Local MCP, and Provider Gateway. These delivered paths keep setup, permissions, diagnostics, and shutdown explicit and reversible.
- 01Install Control Center
- 02Choose local sources
- 03Connect MCP or API clients
- 04Audit what each tool can access
How it should feel
Start locally. Connect deliberately. Expand when you are ready.
Re:Yi provides product information, Control Center distribution, docs, account access, and trusted downloads. Admin stays private, while Recall Core and user memory remain inside the local boundary.
- 01Install Re:Yi Control Center
- 02Connect local apps and MCP clients
- 03Choose what should become durable memory
- 04Use the same memory from every trusted AI surface
Research
Benchmark work should improve the general memory system.
Recall Core tracks long-context retrieval behavior, context packaging, and answer grounding without turning public marketing pages into benchmark claims that the product cannot support yet.
Current access path
Start Re:Yi through Control Center.
The online service manages account access, applications, and trusted downloads. Control Center owns local install, repair, start, stop, and data custody. Current connections are Local MCP and Provider Gateway.