We're hiring! Come build with us →
Zep
Vertical agents

Build agents that
know how your industry works

Give your agents domain knowledge and isolated customer context.

Start building

Shared domain knowledge, separate customer context

  1. Start from your domain knowledge

    Agents for every customer draw on the same regulations and reference material.

  2. Keep each customer separate

    Policies limit what each agent can access.

  3. Log every request

    Each fact links to its source, and API logs show every request with the policy decision behind it.

SOC 2 Type II CertifiedHIPAA Compliant
A contract agent is asked whether Northwind can accept a 12-month liability cap and answers yes, for vendors under $1M. The answer uses two graphs in Zep: the shared clause library, which every customer's agent reads, and Northwind's negotiation playbook, which only Northwind's agent can read.

Control where data goes and how long it stays

Retention

Set retention rules

Retention policies delete idle context on a schedule, with legal hold when required.

BYOK

Encrypt with your own keys

Zep encrypts data at rest with your AWS KMS key. You can revoke access at any time.

BYOM

Use your own model provider

Zep's model calls run on your provider account, under your compliance terms.

Read about security and compliance
Context Lake

One graph for the domain, one for each customer

The Context Lake unifies business data into governed context for agents.

1 Load

Add your domain corpus

Bulk-load regulations and reference documents into a shared graph.

  • SharePointRegulations
  • Google DriveReference documents
  • Slack#general
2 Separate

Give each customer a graph

Each customer's records and conversations go into their own graph.

3 Retrieve

Combine both per request

Agents query the shared graph and their customer's graph through the Zep SDKs.

When is Harbor Credit Union's KYC refresh due?

Policy filter
Account: Harbor Credit Union
Review: KYC refresh due 2026-11-15
Rule: enhanced due diligence
Source: onboarding file
Explore the Context Lake
Recognition

Context infrastructure for the enterprise

S&P GlobalMarketIntelligence

Zep tackles agent memory limitations through its temporal context graph.

S&P Global Market Intelligence · April 2026
“We can easily see Zep becoming a de facto partner in this layer of the enterprise agent stack.”
— Melissa Incera, S&P Global Market Intelligence
FAQ

Questions about vertical agents

Does Zep authorize what agents do in other systems?

No. Zep policies decide which context an agent can read or change. Your application authorizes its tool calls and actions.

Can each customer have its own entity types?

Yes. Entity and edge types set for the project apply to every graph, and one customer's graph can override them.

Can an early-stage company get the Enterprise controls?

Companies that have raised $1M to $10M can apply to the emerging companies program, which includes Enterprise for $13,000 in year one.

Build your vertical agent on Zep

Start with one workflow and one customer. We'll help map its domain sources and customer graphs.

Read the HIPAA guideExplore governanceCustomize your graph
Start free