For IT
Approve it once. Stay in control.
Your teams already build tools with AI. Langrove gives those tools one home in your company's AWS account. You decide who builds and who ships, and you can see exactly what we can reach.
What you control
Tools off personal laptops, into your account.
- One account for every tool. Every project runs in one AWS account you control, hosted in Europe, on your company's domain.
- You decide who builds. An admin approves each person and sets what they can do on each project: nothing, view or edit. The admin also chooses who can start projects.
- Remove someone and they're out at once, along with any AI editors they connected.
- The AI editor can't put anything live, and its data tools only see test rows. Going live takes a person with edit rights.
- Our access is one role, listed in full. AWS logs every session, and the security review lists every permission it has.
- Apps keep running without us. Delete our role and your teams' tools keep working.
Green dots are your users' requests, answered inside your account. The dashed line is our only way in.
Langrove is off, and the requests keep flowing. Agents, schedules and search carry on. So does sign-in, once each project sends its own email. Only the console, the AI editor and releases wait for us.
Stays in your AWS account
- Your tables and every row in them
- Files and the document search index
- Your users' sessions and passkeys
- Logs and metrics, in your CloudWatch
- Your users' requests, answered there
Reaches Langrove
- Your app's definitions: models, code, rules and flows
- Test rows your AI editor works with
- What you open in our console, read live through our role
- Your team's accounts and daily usage per project
What our role does: it publishes your releases, applies table changes and shows your data in the console, and AWS CloudTrail logs every session. The security review lists exactly what reaches us, and where.