Agent Identity
Know every agent, and who owns it.
- Agents found as they are used, not by survey
- An owner and a team on each one
- Every action attributed to a person
The AI governance control plane that finds every AI agent in your company, gives each one an owner and limits, and shows what it costs. Live in your browsers within an hour, and nothing anyone types leaves the device.
Works with
Every agent, and the stack it runs on
Agents are already in every team. Ownership, limits and findings are not.
Know every agent, and who owns it.
Decide what each agent may do.
Turn every violation into a finding.
The first scan
Install Lustena on one team. In a week it has found every agent that team uses, ranked what to govern first and shown where an official agent would pay off.
Lustena connects to the browsers, device management, frameworks and gateways you already run, so agents come under the same controls as your people.
Browsers & devices
Developer tools
Agent frameworks
AI gateways
Alerts & audit
I thought we had five agents. We have seven. Two of them can write to our CRM, and nobody owns them.
Whether an agent acts for an employee in a browser tab or runs on its own inside your stack, Lustena brings it under one identity layer, one set of limits and one audit trail.
Read the guide: what is an AI governance control plane?Made by anyone, without code, inside ChatGPT, Claude, Gemini or Copilot: a GPT for proposals, a project with the finance sheet, a connector to Gmail. IT never sees them being made.
Seen by the browser extension
01Where the agent acts · browser
02Lustena, in the path
03Systems reached
Lustena sits where agents already act and applies identity, limits, security and observability to every session.
Agents
Marketing, sales and finance put agents into production without a ticket queue and without hiring AI specialists to govern them. IT gets the answers that let it say yes: what is running, what it can reach and what it costs.
See it on your agentsPublish the extension policy in Google Admin, Intune or Jamf. Agents appear as they are used, attributed to the person using them, with no survey and no change to the agents.
Every session seen by the browser extension, the SDK or the MCP server is evaluated against its agent's limit, or the workspace default, from day one, with no setup per project.
Sessions per app, team and agent, with model and volume per agent. Cut unused licenses and give every token an owner.
Privacy and compliance by design
Teams that build and use agents connected to Lustena are in compliance while they work. Every agent has an owner and a limit before it ships, content stays on the device by default, and the evidence an auditor asks for is written as a by-product of every session, not reconstructed in a panic the week before.
After the fact
By design, with Lustena
Lustena prepares the evidence each framework asks for. Independent assessors certify; Lustena makes the assessment faster.
Content-free findings by default, a written lawful basis before any capture, retention limits and audited reads.
Trust Center →RegulationSupport for risk classification, an inventory with an owner for every agent, logging and human oversight evidence for each agent you run.
Read the guide →CertificationA governed agent inventory, declared limits and a decision history for the controls of your AI management system.
Read the guide →FrameworkGovern, map, measure and manage, with fleet-wide visibility, per-agent evaluation and runtime alerts.
Read the guide →CertificationEvidence across the six domains, from data and privacy to accountability, organized for an independent AIUC-1 assessment.
Read the guide →FrameworkRed-team scans with ten agent-native checks, each mapped to the risk it covers, attached to the agent.
See the scans →Compliance at Lustena
The control plane holds itself to the rule it enforces: by default, prompt text, file contents and file names are never stored or sent. Named standards are references; Lustena does not issue certifications and does not claim ones it does not hold.
Questions
A central layer that gives you identity, policy and audit over every AI agent your company runs, whether engineers built it or an employee assembled it inside ChatGPT. Lustena's control plane starts in the browser, where most of that use already happens, and extends to code-built agents through a Python SDK, an MCP server and a scanner.
In the browser: ChatGPT, Claude, Gemini and Copilot. On the desktop, on the Enterprise plan: the ChatGPT, Claude and Copilot apps. In code: CrewAI, LangGraph, Google ADK, Agno and anything that emits OpenTelemetry. In developer tools: Claude Code, Cursor and Codex through the MCP server. Each agent appears in one inventory under one policy layer.
The extension sees AI use as it happens on managed browsers, without content leaving the device. Each app, custom GPT or connector becomes an agent in the inventory with an owner. Developer tools register themselves when the MCP server is installed, and on the Enterprise plan the desktop collector covers the ChatGPT, Claude and Copilot desktop apps. What remains outside coverage is shown as a number, not hidden. Shadow AI is also a demand signal: the work people already bring to AI on their own shows where an official agent should go next.
As limits per agent across six dimensions: tools, MCP servers, hosts, data classes, autonomy level and schedule. Limits are versioned, and the history of what changed and who changed it is kept.
Every session is evaluated against the agent's limits. An externally run agent that crosses a limit is flagged with one sentence saying what crossed it, and alerts go out through webhooks. Agents running on the Lustena SDK runtime can be stopped before the call is made, and in the browser the Enterprise plan can warn, block or redact before a prompt is sent.
No. Devices enroll with an enrollment token and carry the employee's corporate email, and agents get their own identity on top of the people who use them. Platform access uses passwordless login, with SSO through your identity provider on the Enterprise plan.
Classification runs on the device and only content-free findings leave it. Content capture is off by default and, when turned on, requires a written lawful basis, is redacted on the device, encrypted at rest and audited on every read. Evidence packages map findings to GDPR, the EU AI Act, ISO/IEC 42001, NIST AI RMF, AIUC-1 and LGPD. Lustena prepares the evidence; independent assessors certify.
Most teams see their first agents within an hour: publish the extension policy in Google Admin, Intune or Jamf, and devices enroll on their own. Nothing changes in the agents themselves.
No. The browser extension needs nothing from the agent. For code-built agents, the Python SDK instruments your framework in a few lines, and the scanner only needs an endpoint you are authorized to test.
Yes. Lustena runs as a managed service on Google Cloud, and on the Enterprise plan the control plane can be deployed in your own cloud or on premises.