Latet
Coming soon

Latet Enterprise

Latet replaces the secrets and personal data in your AI agents' requests with realistic fakes before they leave. Latet Enterprise puts your security team in charge. The team sets rules nobody can lower, decides on any change that would weaken them, and gets events and reports for its SIEM and its audits. Everything runs on a server inside your network.

Join the waitlist Write to info@latet.ai

Where it runs

Latet Enterprise runs on your own server, inside your network. There is no Latet cloud, and the server never calls home.

Your network
Computers Claude Code, Codex, OpenCode and other agents
CI and programs each with its own API key
Latet server masks every request and puts the real values back in every answer
AI providers the ones your agents already use
Direct connection: blocked
Firewall
With the firewall rule in place, only the Latet server reaches the AI providers.
  • The server does the masking. Computers and programs send their AI requests to the Latet server over HTTPS, and the server masks each one itself. It never relies on a computer to do it.
  • No calls home. The server connects to the AI providers and to the systems you link it to, such as your identity provider and your SIEM. The license is a signed file, checked offline.
  • Your control point, with your firewall. The server becomes your control point once your firewall lets only the server reach the AI providers. A computer that reaches them directly goes around the server. The documentation shows an example of the firewall rule, but Latet does not check that it is in place.
Technical details
  • Deployment. The server runs as stateless instances behind your load balancer, with PostgreSQL and Valkey, in a container or as a systemd or Windows service.
  • Encryption. In PostgreSQL, the values, texts and images of each person and each API key are sealed with a key of their own, and those keys are sealed with a master key. Account names and email addresses are stored unencrypted.
  • The master key. The server reads it from a file or an environment variable. Keep a copy of it separate from the database's backups.
  • Builds. Each release is built by a workflow that adds build provenance attestations and a CycloneDX SBOM.

Control

Your security team sets the rules for everyone in one place, with a floor nobody can go below, and decides on the changes that would lower protection.

Rules for everyone

  • Set once, for everyone. Terms, lists, recognizers, field rules and protection levels are set on the server and apply to every person and API key; each person adds their own on top.
  • A floor, not a ceiling. Everyone's own settings build on top of your policy. A change that would go below the policy is refused, whether it comes from the dashboard, the command line or an import. The refusal names the setting your company locked.
  • Visible to everyone. People see the locked settings with a lock in their dashboard.
  • On the server, at once. The policy lives in the server's database and applies at once to every person and every API key.
Technical details
  • Format. The policy uses the format of Latet's rules file, so you can start from an export of the rules you already use.
  • Without a server. Your device management tool installs a policy file where only administrators can write: C:\ProgramData\Latet\policy.yaml, /Library/Application Support/Latet/policy.yaml or /etc/latet/policy.yaml.
  • The limit of a file. Someone who is an administrator of their own computer can delete it. For a floor that holds, use the server together with the firewall rule.

Central approvals

  • Decided by your security team. When your policy says so, a change that would lower protection goes to the people with the security role. Such changes include letting a value through unmasked or turning a rule off.
  • No values in the request. An approval request names the setting it would change, never a value.
  • Clear for the person waiting. Whoever asked sees who decides.
  • The Live Reviewer, if you choose. The Live Reviewer holds each new text until someone approves it. Your company can have the security team approve these texts instead of each person, and people are told about it.

Evidence

Latet Enterprise sends events to your SIEM and produces reports for your audits. They contain counts and categories, never a value.

Events for your SIEM

  • Splunk. Events go to Splunk's HTTP Event Collector (HEC).
  • Syslog. Events go as RFC 5424 messages over TLS to rsyslog, syslog-ng or a collector in front of Microsoft Sentinel.
  • Webhook. Each event goes as JSON over HTTPS to an address you choose, with the headers the receiver needs. This works for Elastic, for Microsoft Sentinel through a Logic App, and for collectors such as Vector or Fluent Bit.
  • Never in the way. Sending an event never holds up an agent's request. Events wait in a queue and are retried when your SIEM does not answer.
Technical details
  • Event types. exchange, stopped, approval, change, policy, sync, sign-in, license, and admin for the administration log.
  • Delivery. Events are delivered at least once and in order, in batches of up to 500, by one instance at a time. If a batch fails halfway through, part of it may arrive twice, and each event's id tells the copies apart.
  • Retries. A receiver that does not answer is asked again after 5 seconds, 10 seconds, 30 seconds and a minute, then every 5 minutes. Events wait in order, across restarts.
  • Secrets. Tokens and keys are sealed in the server's database. A webhook with a secret is signed (x-latet-signature), and an http:// address is refused unless it points to the server itself.
An event: counts, never a value
{
  "v": 1,
  "id": "3f9a0c1d2e4b4c6f8a1b2c3d4e5f6071",
  "ts": "2026-11-03T09:12:44Z",
  "type": "exchange",
  "identity": null,
  "kind": "person",
  "group": "g_payments",
  "agent": "claude-code",
  "project": "billing-api",
  "masked": {"EMAIL": 3, "IBAN": 1},
  "stopped": 0,
  "reason": null,
  "outcome": null,
  "by": null,
  "rule": null
}

Three email addresses and one IBAN were masked in this exchange. The event says how many and of which type, never which ones. By default, reports are by group, and while they are, identity stays null.

Reports

  • In the dashboard. Filter by period, group, project, agent or category, follow the trend over time, and export as CSV or JSON.
  • Independent of the history. Reports come from an event log of their own, with its own retention, so they work even when the history is turned off.

Administration log

  • Who did what. The log records every administrative action: who did what, on what, when and from which address. It never records a value. Entries are kept for 365 days unless you choose otherwise.
  • Changes are visible. Each entry carries the hash of the one before it. An hourly check, latet server log verify and latet server status tell you whether the chain is intact.
  • Also in your SIEM. A hash chain shows a change but cannot prevent one, because someone who can write to the database can rewrite the whole chain. That is why the log also goes to your SIEM.
  • On every server. The log is part of every Latet server, in the Community Edition too. Enterprise adds it to the reports and the SIEM.

Your company's own names

Latet finds what has a recognizable format: keys, email addresses, IBANs, ID numbers. Your customers' names and your projects' code names have none. Latet Enterprise takes them from your own systems and masks them like any other value, without anyone typing them in.

  • From a file or a URL. Latet reads a CSV, JSON or YAML list on a schedule, and any system can produce one.
  • From Microsoft Entra ID. Latet reads people's names and email addresses, and group names, through Microsoft Graph.
  • From LDAP and Active Directory. Latet reads names straight from your directory.
  • From a CRM, on request. HubSpot or Salesforce are added when a company asks for them.
Technical details
  • Term types. Each source maps its fields to types such as CLIENT, PERSON and PROJECT.
  • Sealed. Synced terms are kept sealed in PostgreSQL, not in a settings file: a list of customers is sensitive in itself.
  • Removed at the source. A term that disappears from its source stays masked, marked as no longer there, until someone with the security role removes it.

Sign-in and roles

People sign in with your identity provider, which also manages their accounts.

  • Single sign-on with OIDC. It works with Microsoft Entra ID, Google, Okta, Keycloak, Authentik, Auth0 and other OIDC providers. SAML 2.0 is available on request.
  • Accounts through SCIM 2.0. Your identity provider creates and disables accounts. Only the members of the group you choose, such as latet-users, get one.
  • Disabled means signed out. Disabling someone's account ends their sessions and revokes their tokens at once, on every instance, and frees their seat.
  • Groups and roles. Groups come from your identity provider or are made by hand. Roles go to people or to groups.
Technical details
  • OIDC. Latet uses the authorization code flow with PKCE. The client secret is sealed with the master key, and groups in the token map to Latet's groups.
  • SCIM. The server exposes /scim/v2/Users and /scim/v2/Groups, the part of SCIM 2.0 that Entra ID and Okta use.
Roles
Role Sees Decides
User their own data, and the API keys they control their own settings, above the floor, and those of the API keys they control
Group lead the reports of their groups nothing
Security every report the policy, the terms, the approvals, the SIEM
Auditor the reports, the policy's history and the administration log, read-only nothing
Admin people, groups and API keys sign-in, roles, the license, API keys and who controls them

Privacy inside the company

Latet keeps the values people send hidden from the AI providers, and from your administrators too.

  • Each person's data is their own. Nobody sees another person's values or texts, administrators included. Each person's vault, history and approvals are theirs alone.
  • Reports without content. Reports and SIEM events carry counts, categories, rule IDs, agent, project, group and outcome, but never a value, a text or a fake.
  • One exception, chosen openly. If the security team approves the Live Reviewer's texts, the approver sees each text, values included. Your company chooses it and tells people.
  • Reports by group, by default. Your company can turn on reports by person, under a pseudonym or by name. Where the law requires an agreement with employees, the company needs one first.
Technical details
  • Where the law asks for an agreement. In Italy, art. 4 of the Statuto dei lavoratori (L. 300/1970); in Germany, the works council's co-determination (BetrVG §87(1) no. 6).

What an auditor gets

This is what your auditors can check for themselves.

  • A read-only role. Auditors see the reports, the policy's history and the administration log, and change nothing.
  • Numbers by period. Reports show how many values were masked and of which types, how many requests were stopped and how many changes were approved, by group, project and agent. They never show a value.
  • Who changed what. The policy's history, the administration log and the approval events show who changed which rule and who approved it.
  • A log you can verify. The hash chain can be checked with latet server log verify.
  • Material for a DPIA. The documentation says what Latet keeps, where and for how long, and what is sealed and what is not.
What it is evidence for
Framework Articles and controls
GDPR Pseudonymisation (art. 4(5)), data protection by design (art. 25), security of processing (art. 32(1)(a))
ISO/IEC 27001:2022, Annex A 8.11 data masking, 8.12 data leakage prevention, 8.15 logging, 8.16 monitoring activities

Latet reduces exposure. Your own controls decide whether you comply.

The license

The server is in the Community Edition, free for every company, with an administration log. Latet Enterprise adds everything else on this page, rules set for everyone included.

Who needs it. A company that uses the Enterprise features in production needs a Latet Enterprise license. Developing and testing with them is free, and the Community Edition, the server included, stays free for every company, whatever its size.

Checked by the Enterprise features alone. The Community Edition has no license keys and never checks anything. Only the Enterprise features read the license file, offline.

Who counts

As in Jira, every enabled account with access to Latet counts, whether or not it was used that month. A person counts once, however many computers and groups they have. Each enabled API key counts as one user. Disabling an account frees its seat at once.

The license file

The file is signed with Ed25519 and checked offline, with no activation. It names your company, the number of users bought, the features and the end date. You can see them with latet license show and latet doctor.

The trial

Developing and testing with the Enterprise features needs no license. To try them on real work first, a company can ask for a trial license file, valid for 32 days.

If a renewal is late

  1. 30 days before the end A notice

    Administrators see a notice in the dashboard and in latet doctor.

  2. The end date Nothing changes yet

    For 30 more days, everything keeps working as before.

  3. 30 days after the end New output pauses

    Latet stops making new reports and exports, sending SIEM events and syncing terms. Terms already synced stay masked.

  • Protection never pauses. Locked rules stay locked, approvals still follow the same route, and everyone can still sign in.
  • More users than you bought. The notice comes at once, followed by the same 30 days and the same pause.

Latet keeps protecting so that nobody is left exposed, but the license is still needed. A company that keeps using Latet Enterprise after the end date needs to renew it, and one with more users than it bought needs to buy the extra ones.

The full terms

Contact

To talk about your company's case, write to info@latet.ai. Say how many people would use Latet, which identity provider and SIEM you have, and which agents your company uses.

Hear when Latet Enterprise is available

Leave your email address. You will get one message when Latet Enterprise is available, and nothing else.

How the address is kept

Questions about Latet Enterprise?

Write to this address:

info@latet.ai

Write an email