Different audience
A general app memory platform can make sense when you are adding memory to an AI product you are building for users.
Compare Zep
Palace vs Zep for AI memory
engineering recall
Zep is a memory platform for AI applications. Palace focuses on self-hosted memory for coding agents and engineering teams using MCP.
Runs on your infrastructure, not Palace's cloud.
Local ONNX embeddings: no third-party embedding API required.
Ed25519-signed licenses verify offline for air-gapped operation.
Palace vs Zep for AI memory
| Feature | Palace | Zep |
|---|---|---|
| MCP native | First-class palace_* tools | API / SDK oriented; not MCP-first |
| Coding-agent workflow | Session protocol, diaries, KG facts | App and conversation memory patterns |
| Team memory | Self-hosted shared engineering recall | Product / user memory for AI apps |
| Self-hosted | Local MIT core + paid team server | Depends on product offering |
| Code / project context | Wings, rooms, drawers, project status | Session and user-memory oriented |
| Provenance | Source-grounded recall for agents | Memory records for applications |
| Local embeddings / air-gap | Local ONNX + offline license path | Not the primary product posture |
| Primary focus | Coding agents and eng teams | AI application memory platforms |
Where Palace fits
Palace targets internal engineering work: agent sessions, codebase conventions, prior fixes, project decisions, and shared team recall.
Decision point
Choose Palace when the memory needs to be private, source-grounded, MCP-accessible, and owned by the engineering team. For the search-intent overview, see the Zep alternative page.