Keep memory in Luthn.
Keep raw context behind the boundary.

THE MEMORYProtected memory
THE BOUNDARYRaw stays local
THE PATHOnly what is needed

01 / THE MEMORY LAYER

Luthn stays sealed,
only needed memory crosses.

Let one task become context for the next. Luthn keeps raw context inside a local boundary and returns only a small policy-approved context pack to the next agent.

Stays inside the local boundary
  • Sensitive records
  • Private messages
  • Credentials
  • Operational data
Crosses the boundary
  • Reviewed summaries
  • Redacted references
  • Approved context
  • Bounded recall

CONNECTORS / DATA INTAKE

Bring context from where work happens,
keep memory inside the boundary.

Connect Messenger, Document, and Mail where work already happens. Luthn keeps the full source closed and carries only the context needed for the next task.

01

MESSENGER

Context from the conversation

Carry message threads and decisions into reusable project memory.

02

DOCUMENT

Standards kept in documents

Turn rules, decisions, and references in files into usable context.

03

MAIL

The important thread

Continue only the requests and agreements needed for the next task.

02 / THE PROTECTIVE FIELD

Make the force that guards memory,
quiet by design.

A quiet layer between
agents and sensitive context.

01

CLASSIFY / REDACT

Seal the raw context. Keep safe memory.

Classify and redact turn capsules and project context first. Agents see only policy-approved summaries and references.

02

SHARED MEMORY

Give every agent the same context.

Connected agents can reuse the same project memory while their hooks and connection state remain independent.

03

AUTO-RECALL

Only when needed, only what is needed.

Fetch a small context pack when a new task or topic begins. Bounded recall keeps the flow quiet and focused.

04

AUDIT / APPROVAL

Record every boundary. Open by approval.

Track what was stored, shared, and retrieved. External publication stays behind a separate explicit approval path.

03 / THE PATH FORWARD

One Luthn,
three paths ahead.

NOW · OPEN SOURCE01

Luthn OSS

Run your own self-hosted shared memory on Docker and PostgreSQL.

SELF-HOSTED · DOCKER + POSTGRESQL
NEXT LAYER02

Luthn Cloud

A managed memory layer where connected agents share the same safe context for your team.

TEAM MEMORY · NEXT
FAR HORIZON03

Luthn Ontology

An ontology layer that connects enterprise knowledge structures and policies to agent-safe context.

ORG CONTEXT · LATER

04 / QUIET QUESTIONS

When the boundary is clear,
memory can remain.

What is Luthn?

Luthn is a self-hosted shared memory and safe context layer for AI agents. It gives multiple agents reusable project memory while separating sensitive raw data from their default context.

Does sensitive data reach the agent?

Not as raw records. Keep the source inside a local private boundary and expose only reviewed summaries, redacted references, and approved project context.

How does it scale for teams and enterprise?

Luthn Cloud is planned for team-only shared memory, while Luthn Ontology is the next enterprise layer for knowledge structures, policy, and domain context.

ENTER THE BOUNDARY

For the next task,
protect the memory.

Luthn makes long-term agent memory more useful and the data boundary more explicit.

Open Luthn on GitHub