How Aegara works

Your AI systems do their work. Aegara records what each action touched, checks the values inside it where those values already are, and keeps the record of both.

Three steps

Aegara sits alongside your AI systems and keeps a structured record of every action they take.

Step one

Your AI takes an action

It reads an email, drafts a reply, calls an API, writes to a database. Anything it normally does.

Step two

Aegara records it

Through the SDK, a LangChain callback, or the API. The record says what happened, what it touched, and what it did not touch.

Step three

You see it

Actions appear in the Trace Portal. Filter by system, by person, by sensitivity, by what the action did.

What leaves your environment

The values inside your AI's tool calls are checked where they already are, on your own machines. Only the verdict is sent.

Aegara's rules run here, on your machine.

The values never move.

The verdict, and nothing else. Never the number, a piece of it, or a hash of it.

the boundaryYour environmentAegaracrm.contactsdocs.policiesfinance.forecastbilling_refthe values in your AI's tool callsbilling_ref held a card numberhigh confidence, payment data
Your environmentthe values in your AI's tool callscrm.contactsdocs.policiesfinance.forecastbilling_refthe boundaryAegarabilling_ref held a card numberhigh confidence, payment data

Think of a smoke alarm. The manufacturer decided what smoke looks like. The alarm sits in your house, monitors your air, and if it finds smoke it sends one signal. The manufacturer never smelled your air.

What one trace looks like

Someone asks their assistant to summarize an email thread and draft a reply. Four actions, and this is all of what Aegara keeps about them. An example, with the shape and the fields a real one has.

trace 4c9e17 · email-copilot1.42s
READ Twelve messages from one thread0.00s Subject, sender, date and body. No attachments opened.
TRANSFORM Summarized the thread into five points0.44s No call left the machine.
READ billing_ref from the finance system0.91s The value held a card number. Checked on your machine; the number stayed there.
WRITE Saved a reply as a draft1.42s Saved, not sent. Nothing addressed outside the organization.

Three of those four rows say what did not happen. That is the half a log cannot give you: a log records what an action did, and the question after an incident is almost always what else it touched.

What you get

Value inspection

The values inside your AI's tool calls are checked for sensitive data inside your own environment. Only the verdict is sent: which field, which pattern matched, how sensitive.

Seats

An organization is people, not a shared password. Owners manage the team; every member sees the record.

Audit trail

Who did what inside your organization, downloadable on every plan and kept for a year.

API reference: every endpoint, its schema and an example