The agent acts as the person, never as Frailen.
Frailen holds no key it could use to sign on anyone's behalf. Every change goes out with the identity of whoever asked for it, passes through your product's permissions and is written down.
Identity
Your product already knows who each person is and what they can do. Frailen builds on that; it doesn't replace it.
Your backend signs the session
With an asymmetric key that belongs to you. Frailen only receives the public key: it can't sign a session, so it can't act for anyone who doesn't have one.The permissions are your product's
The agent reads and writes in your API with a short-lived token for that person. If they can't do something, neither can the agent.The token isn't stored
It lives in memory for as long as the call lasts. It never goes to the database, the logs or a URL.Panel actions ask for a passkey
Approving a tool, publishing a configuration or turning the agent on asks for the passkey of whoever does it, right then.
Your data
What Frailen stores, what for and for how long.
Your spec stays with you
Only the skeleton of what the agent can touch is uploaded from your OpenAPI. The source stays on your side.Every company, isolated
Everything stored is tagged with its company, and the database won't let anyone read another's: not even Frailen's own engine can get around that rule.A log that only grows
Every action, on whose behalf and how the read-back went. The database won't let it be changed or deleted.Models in a fixed region
Models run on Google Cloud in a single region, not on the global endpoint, with caching turned off.
What the agent won't be talked into
Defenses that don't depend on the model behaving.
Instructions hidden in the data
If a response from your API carries text that tries to give orders, the turn loses trust and everything it writes from then on asks for confirmation.Receipts signed by your API
Your API can sign a receipt for every write. If what ran isn't what was asked for, the case goes to a person.
What we don't have yet
So you know before you ask.
- A certification such as SOC 2.
- An external penetration test. It comes before the first customer outside our pilot.
- A published data processing policy.
If your security team needs anything else to evaluate us, tell us in the demo.
Have your agent review it.
Before talking to us, your agent can read this page against your product and draft your security team's questions.
Read https://frailen.com/seguridad.md and https://frailen.com/llms.txt. Review Frailen's security model against our product: identity and tokens, what's stored and for how long, isolation between companies, and how the brake works. List the questions our security team should ask before a pilot, and what Frailen says it doesn't have yet.
Paste it into Claude Code, Cursor, Codex or any agent that can read a URL.
Ask us anything you need.
In the demo we answer your security team's questions, with the code at hand.