Managed Zep Hosting — production-ready from $11 a month
Long-term memory store for AI assistants that recalls and extracts facts from chats. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Zep, no lock-in.
Zep on ManageStacks is an open-source long-term memory service for AI assistants, deployed to your own AWS, Azure or GCP region with flat per-app pricing from $11 a month ($25 on the Standard production plan). Developers use it to store chat histories and recall relevant facts, instead of building memory layers themselves or relying on a hosted memory service.
What does Zep do, and why do teams deploy it?
Zep gives AI assistants a memory that outlasts a single conversation. It stores chat histories, can summarise them, and extracts structured information so an application can recall what a user said earlier. The server is written in Go and released under the Apache-2.0 licence, and your application talks to it through an API and client libraries. Teams building chatbots and agents use it to keep context consistent across sessions, while keeping conversation data in their own environment.
- Persistent storage of chat message histories per session
- Automatic summarisation of long conversations
- Recall of relevant past messages for a new prompt
- Extraction of structured data from conversation text
- Per-user and per-session organisation of memory
- API and client libraries for common AI frameworks
Long-term memory store for AI assistants that recalls and extracts facts from chats
Zep as a self-hosted alternative to Mem0 and Pinecone
Instead of paying per-seat fees to a SaaS vendor, teams self-host Zep to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Zep hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Zep the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Zep at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Zep run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Zep in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Zep on ManageStacks
What is Zep on ManageStacks?
Zep is an open-source long-term memory service for AI assistants. ManageStacks deploys and runs it in your own AWS, Azure, or GCP account, so the conversation histories and extracted facts your assistants rely on stay on infrastructure that you control.
How does Zep compare to a hosted memory service?
A hosted memory service stores your users' conversations on a vendor's systems. Zep can be run by you, so the data remains in your own account. You also avoid building your own storage and recall layer, which is the main reason teams adopt it.
What does Zep do with chat histories?
Zep stores messages by session, can summarise long exchanges, and lets your application fetch relevant context to include in the next prompt to a language model. It can also pull structured details from the conversation, which helps assistants stay consistent over time.
Can I keep my existing conversation data?
Yes. Zep stores conversation data in your own cloud account, so you keep ownership of it. If you already run Zep, you can migrate by moving its database, and you can load earlier chat logs into it through its API.
How does my AI application connect to Zep?
Your application calls Zep through its API, typically using an official client library inside your agent or chatbot code. ManageStacks provides the endpoint behind SSL, and you decide how your application authenticates and which models or frameworks it uses.
Other ai & ml tools on ManageStacks
OpenClaw
Personal AI assistant that runs on any OS and platform, formerly known as Clawdbot
LobeChat
Open-source chat framework for running a private ChatGPT-style app with many LLM providers
Hermes
Self-improving AI agent from Nous Research with a built-in learning loop
AnythingLLM
All-in-one AI application with document chat, RAG, and configurable AI agents
Run Zep without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $11/mo.