Zep — governance posture
https://www.getzep.com/product/agent-memory/
Bi-temporal knowledge graph preserves full lineage of every stored fact — every memory write traceable and auditable by graph schema, not bolted-on logging. SOC 2 Type II; HIPAA BAA available; BYOK + VPC-isolated deployment for data residency.
Active · Verified 2026-10-22 · fresh as of 2026-10-22 · 47 cited facts, 6 with a third-party source · 1 recorded change · Suggest a correction
At a glance
- Type
- Bi-temporal KG = structural provenance vendor fix
- Tier
- T1
- Created
- 2023 (Zep AI founded 2023; YC W24; bi-temporal governance posture described in product from 2024) third-party fix
- Latest release
- not applicable — not OSS fix
- License
- not applicable — not OSS fix
- GitHub
- not applicable — no GitHub repo fix
- Pricing
- Free 10k credits/mo; Flex ~$125/mo (50k credits); Flex Plus ~$375/mo (200k credits); Enterprise custom (third-party tracker, prices inconsistent — confirm on getzep.com/pricing) third-party fix
- Funding
- $500K pre-seed (YC W24 March 2024); total ~$3.5M third-party fix
- Freshness
- 2026-10-22 fix
- Layer
- agent-infra repo fix
- Licensing
- commercial third-party fix
- SDK languages
- go, python, typescript vendor fix
- Protocols
- mcp-server vendor fix
- Compliance
- hipaa, soc2-type2 vendor fix
Memory taxonomy
- storage
- graph
- retrieval
- graph-traversal
- persistence
- long-term
- update
- append-only
- unit
- fact
- governance
- auditable
- conflict
- bi-temporal
When to use
Optimised for: governance + compliance + audit + adversarial hardening
Anti-fit: not for hobbyist / non-production use cases
Pros & cons
Pros
Bi-temporal graph IS the governance story — every memory write traceable by graph schema, not bolted-on logging; SOC 2 Type II + HIPAA + BYOK.
Cons
Governance is a property of Zep's architecture, not a separate product — you don't get the governance without adopting Zep itself.
Claims & capabilities
Provenance is structural. Threat model: exfiltration, HIPAA/SOC 2 compliance, audit trail gaps, explainability failures.
Technical surface
- API surface
- REST (typical SaaS REST + first-party SDK pattern; see vendor docs for language coverage)
- Backend storage
- Postgres + Neo4j
- Deployment
- SaaS cloud; self-hosted (Graphiti OSS); Enterprise: BYOC VPC
- Embedding model
- multiple supported
- Multi-tenancy
- namespace
- MCP
- native (first-party) — Graphiti MCP
- A2A
- no data — searched getzep.com/product/agent-memory, help.getzep.com, docs.getzep.com; A2A protocol not advertised
- OpenTelemetry
- no data — searched getzep.com/product/agent-memory, help.getzep.com, docs.getzep.com; OpenTelemetry export not advertised
Alternatives to Zep — governance posture → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other memory governance, privacy & safety in the catalog, ranked by inbound references.
- Lakera Guard / Lakera Red T1
Acquired by Check Point Software (completed by 2025-11-11); being folded into Check Point's AI security platform. Screens every prompt, response, and retrieved document for indirect prompt injection — primary vector for memory poisoning. Treats memory as untrusted: anything written to or read from memory is adversarial until proven clean. Lakera Red provides "Agent Breaker" gamified red-teaming.
- Acuvity (now Proofpoint) T1
Acquired by Proofpoint (closed 2026-02-12). Runtime enforcement targeting memory poisoning, unauthorised execution, identity spoofing per the OWASP LLM threat list. Visibility/control over MCP servers and locally-installed AI tools — the infrastructure layer where memory is most exposed.
- Enkrypt AI T1
Applies guardrails at three points: (1) before write to vector DB, (2) before query reaches embedding model, (3) before response. Detects malicious instructions in stored memory before retrieval; scans for PII/PHI in/out. Text + image + voice modalities. Acquired by Anaconda (2026-08-04); Enkrypt AI is now sold as Anaconda's AI security and guardrails product.
- HiddenLayer AISec Platform 2.0 T1
AI security platform with four modules: AI asset discovery, supply-chain/model integrity validation, continuous attack simulation, and runtime detection/response, including protection of agents and MCP-based systems.
- Hyperconsciousness (hc) T3
Developer-alpha encrypted, append-only knowledge store for humans and agents, with CLI/MCP access and scoped, expiring grants. Traction: Submitted via intake issue #181
- Mem0 Security / OpenMemory T1
Commercial Mem0 ships SOC 2 / HIPAA, zero-trust access controls, BYOK encryption, real-time monitoring, audit logs and workspace governance as defaults (Trust Center at trust.mem0.ai). For privacy-first deployments the self-hosted path is now the Mem0 open-source server (REST API + dashboard via Docker Compose with pgvector Postgres, admin setup wizard, per-user API keys, request audit log). As of Oct 2026 OpenMemory itself is a hosted MCP service and its old local Docker variant is no longer in the repo.
Sources (46 cited facts, 6 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Bi-temporal KG = structural provenance vendor
- What it does & what's distinct Bi-temporal knowledge graph preserves full lineage of every stored fact — every memory w… vendor
- Claims / benefits Provenance is structural. Threat model: exfiltration, HIPAA/SOC 2 compliance, audit trai… vendor
- Modalities text vendor
- Created 2023 (Zep AI founded 2023; YC W24; bi-temporal governance posture described in product f… third-party
- Funding $500K pre-seed (YC W24 March 2024); total ~$3.5M third-party
- Pricing Free 10k credits/mo; Flex ~$125/mo (50k credits); Flex Plus ~$375/mo (200k credits); Ent… third-party
- Compliance SOC 2 Type II + HIPAA BAA (Enterprise); BYOK + VPC-isolated deployment vendor
- Data handling cloud-managed (default) or self-hosted Graphiti OSS + Neo4j; Enterprise: BYOK BYOM BYOC vendor
- Deployment SaaS cloud; self-hosted (Graphiti OSS); Enterprise: BYOC VPC vendor
- HQ San Francisco CA (Oakland area per some sources) third-party
- Founders / pedigree Zep AI (YC W24; Daniel Chalef) vendor
- Memory volume / scale no scale claim — bi-temporal KG (same backend as Zep/Graphiti) vendor
- Performance no public benchmark scores found — vendor does not publish quantitative perf metrics vendor
- API surface REST (typical SaaS REST + first-party SDK pattern; see vendor docs for language coverage) vendor
- Backend storage Postgres + Neo4j vendor
- Multi-tenancy namespace vendor
- Encryption at-rest + in-transit vendor
- SSO / RBAC SSO + RBAC vendor
- Embedding model multiple supported vendor
- Consistency not specified — vendor docs do not address this dimension vendor
- Versioning immutable append-log vendor
- Tombstoning append-only no delete vendor
- Schema evolution schema with migration vendor
- Namespace primitives per-tenant vendor
- Contradiction handling version both with timestamps vendor
- Forgetting policy none (permanent) vendor
- MCP support native (first-party) — Graphiti MCP repo
- Webhooks / events Yes — Webhooks documented under help.getzep.com (Compliance / Webhooks / Rate Limits sec… vendor
- Import / export JSON via REST (JSON-over-REST; CSV/Parquet export for analytical use) vendor
- Validated verticals regulated enterprise: financial-services, healthcare, government, legal vendor
- Time to running <1day to <1week (enterprise procurement + integration) vendor
- Anti-fit not for hobbyist / non-production use cases vendor
- Optimised for governance + compliance + audit + adversarial hardening vendor
- Adjacent infrastructure BYO agent stack; this layer guards it vendor
- Pros Bi-temporal graph IS the governance story — every memory write traceable by graph schema… vendor
- Cons Governance is a property of Zep's architecture, not a separate product — you don't get t… vendor
- Project & sources Zep agent memory vendor
- adoption-accelerator yc-w24 third-party
- architecture-deployment-locus cloud vendor
- licensing-bucket commercial third-party
- positioning-platform-vs-product platform vendor
- taxonomy-three-layer-rollup agent-infra repo
- compliance-certifications hipaa,soc2-type2 vendor
- sdk-languages go,python,typescript vendor
- protocol-support mcp-server vendor
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
Related systems
References (1)
- Neo4j depends on at runtime — backend-storage cell: Postgres + Neo4j