# Omnia vs Zep

> Omnia redacts before anything reaches memory, honours consent revocation, and runs in your own cluster. Zep is a temporal knowledge graph for agent memory.

Category: Memory. Checked against Zep’s published material on 2026-10-22. Canonical page: https://www.altairalabs.ai/vs/zep/

## Zep stores what the agent learns. Omnia redacts it before it’s stored.

Omnia’s memory runs in your own cluster, as part of the platform that runs the agent, and redacts personal data before it’s stored. Zep is a temporal knowledge graph that invalidates old facts as new ones arrive.

## When it matters: A caller reads out their card number while asking about a refund.

**On Omnia:** The session recording keeps the refund request with the number redacted, and the redactor runs again before anything is committed to long-term memory. The agent remembers that this customer asked for a refund. (Omnia docs: https://omnia.altairalabs.ai/how-to/privacy/configure-privacy-policies/)

**On Zep:** Content policies are in closed beta, aren’t available for BYOC, and don’t filter, redact or rewrite the text you send. (source: https://help.getzep.com/v4/content-policies.md)

## Redaction before memory

Replace, hash or mask detected values, or encrypt them, before they reach the session or memory. A built-in self-test writes a test card number and fails if it comes back readable. *(enterprise)* (Omnia docs: https://omnia.altairalabs.ai/how-to/privacy/configure-privacy-policies/)

Zep: Content policies flag; they don’t redact. (source: https://help.getzep.com/v4/content-policies.md)

## Self-hosted, supported

Memory runs on Postgres and pgvector in your cluster, as part of a platform you install with Helm. (Omnia docs: https://omnia.altairalabs.ai/explanation/agents/memory/)

Zep: Community Edition is deprecated and no longer supported; BYOC runs inside your VPC. (source: https://help.getzep.com/v4/faq.md)

## Withdrawing consent

When a user withdraws consent, it applies to memories already stored. Erasure runs as a data subject request, with each step in the audit trail. *(enterprise)* (Omnia docs: https://omnia.altairalabs.ai/how-to/privacy/manage-user-consent/)

Zep: Deleting a user cascades to their threads and graph, asynchronously. (source: https://help.getzep.com/v4/deleting-data-from-the-graph.md)

## At a glance

| Topic | Omnia | Omnia docs | Zep | Zep docs | Source |
|---|---|---|---|---|---|
| Newer facts win | Precedence and supersession. | https://omnia.altairalabs.ai/explanation/agents/memory/ | Bi-temporal invalidation. | documented | https://help.getzep.com/v4/facts.md |
| Workspace isolation | Workspaces with RBAC and network isolation. | https://omnia.altairalabs.ai/how-to/workspaces/manage-workspaces/ | Account and project isolation, RBAC and ABAC. | documented | https://help.getzep.com/v4/governance.md |
| PII redaction | Before sessions and memory. *(enterprise)* | https://omnia.altairalabs.ai/how-to/privacy/configure-privacy-policies/ | Flags only, closed beta. | partly documented | https://help.getzep.com/v4/content-policies.md |
| Consent | Revocation reaches stored memory. | https://omnia.altairalabs.ai/how-to/privacy/manage-user-consent/ | Not documented. | not documented | https://help.getzep.com/v4/deleting-data-from-the-graph.md |
| Self-hosted | Every edition. | https://omnia.altairalabs.ai/how-to/workspaces/manage-workspaces/ | BYOC; Community Edition deprecated. | partly documented | https://www.getzep.com/pricing |
| Runs and tests the agent | Yes. | https://promptarena.altairalabs.ai/arena/explanation/scenario-design/ | A memory and context service. | not documented | https://www.getzep.com/ |

## Questions

**Is Graphiti open source?**

Yes, Graphiti is Apache 2.0. Zep Cloud is proprietary.