zep
Zep is an Apache-2.0 licensed repository containing examples, integrations, and tools for building agent memory with Zep Cloud, a managed platform for temporal knowledge graphs. The repo itself is not the product but provides sample code and framework connectors across Python, TypeScript, and Go for developers integrating agent memory capabilities.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | getzep/zep |
| Owner | getzep |
| Primary language | Python |
| License | Apache-2.0 — OSI-approved |
| Stars | 4.7k |
| Forks | 637 |
| Open issues | 15 |
| Latest release | zep-crewai-v1.1.1 (2025-09-11) |
| Last updated | 2026-07-08 |
| Source | https://github.com/getzep/zep |
What zep is
This is an integration and examples repository for Zep Cloud, featuring agent-framework bindings (CrewAI, LangGraph, AutoGen, etc.), temporal knowledge graph utilities, evaluation harnesses, and benchmark suites. The actual Zep service is cloud-hosted; this repo provides client-side SDKs, integration packages, and reference implementations.
Get the zep source
Clone the repository and explore it locally.
git clone https://github.com/getzep/zep.gitcd zep# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Choose the appropriate official SDK (zep-cloud for Python, @getzep/zep-cloud for TypeScript, zep-go/v3 for Go) and integrate via the framework connector that matches your agent stack.
- Review the examples/ directory for your language and framework to understand authentication, session management, and memory retrieval patterns.
- Understand that this repo is integration examples, not the Zep service itself; sign up at getzep.com and consult help.getzep.com for API credentials and service configuration.
- Evaluate memory retrieval performance and cost using the benchmarks/ (LoCoMo, LongMemEval) and zep-eval-harness before scaling to production.
- Legacy/ folder contains deprecated Community Edition code; do not use for new projects—rely only on current Zep Cloud integrations.
When to avoid it — and what to weigh
- No managed cloud budget — Zep Cloud is a paid SaaS platform. This repo only provides integrations and examples. The open-source temporal knowledge graph framework (Graphiti) is separate; consider that for on-premise needs.
- Require full on-premise control — Zep Cloud is managed and hosted externally. This repo is tooling only and does not include self-hosted Zep service deployments.
- Early-stage agent projects with uncertain scope — Adding external managed dependencies early increases operational surface area. Prototype agent memory locally first; adopt Zep when requirements stabilize.
- Strict data residency or air-gapped environments — Zep Cloud is a third-party SaaS. If data residency, compliance, or network isolation is non-negotiable, this solution is not viable.
License & commercial use
Apache License 2.0. This is a permissive OSI-approved license allowing commercial use, modification, and distribution under the same terms, with liability disclaimers. See LICENSE file for full text.
Apache-2.0 permits commercial use of the example code and integrations in this repository. However, Zep Cloud itself is a commercial SaaS service requiring a paid account and separate terms of service. Evaluate Zep Cloud's commercial terms at getzep.com independently; this license covers only the integration code.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
This repo contains integration glue code; security posture depends on Zep Cloud service itself (not documented here). Ensure API keys and credentials are never committed to version control. Review Zep Cloud's data privacy, encryption, and compliance policies independently. Integrations should validate authentication tokens and handle secrets via environment variables or secure credential managers.
Alternatives to consider
LangChain Memory / LangGraph (self-managed)
Open-source, self-hosted memory management. Less abstraction, more control, but requires operational ownership of storage and retrieval infrastructure.
Graphiti (open-source temporal knowledge graphs)
The underlying framework powering Zep, available separately for on-premise deployments. Trades managed cloud convenience for operational control.
Pinecone / Weaviate + custom orchestration
Vector DB + custom agent memory layer. More flexible, lower managed-service cost, but requires bespoke integration and maintenance effort.
Build on zep with DEV.co software developers
Sign up for Zep Cloud at getzep.com, install the appropriate SDK, and explore the integrations/ examples for your framework. Review benchmarks/ to validate memory quality before production.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
zep FAQ
Is this the Zep product or service?
Can I self-host Zep using code in this repo?
What frameworks and languages are supported?
Is the legacy/ Community Edition still supported?
Software developers & web developers for hire
DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If zep is part of your ai frameworks roadmap, our team can implement, customize, migrate, and maintain it.
Ready to add persistent memory to your agents?
Sign up for Zep Cloud at getzep.com, install the appropriate SDK, and explore the integrations/ examples for your framework. Review benchmarks/ to validate memory quality before production.