By role
For IT and security, homemade AI tools are a familiar problem in a new form: useful software, built outside IT, holding someone's login. Blocking it rarely works — people find a way around. Approving it is easier when you can see who uses it, limit what it can do, and switch it off per person.
People sign in through your existing company login (like Okta or Microsoft Entra). Each person connects their own apps; the tool never stores a password or key.
Apps it uses: Your company login, The apps the tool uses
Why it's hard to share today: Today the usual choice is a shared account or an outright ban.
New users can read and prepare drafts but not send or change anything. You or a manager allow more, per person and per tool.
Apps it uses: Any connected app
Why it's hard to share today: Most tools either can do everything or nothing.
Every action is written down once, naming the person and the tool version, linked to the record before it and checkable offline.
Apps it uses: Your logging or security tools
Why it's hard to share today: Homemade tools usually leave no trail at all.
Cresec is designed so tools fall back to read-only rather than break: people can keep reading and drafting, and nothing is sent or changed without a record.
Leaving is designed to be simple: it's a small configuration change in the tool, and you keep your records and can still check them.
Your existing identity provider, such as Okta or Microsoft Entra. People sign in the way they already do.
The tools keep running wherever their builders put them. Cresec sits between them and your apps, so you control access without hosting anyone's code.
Yes. Every tool, version, person and action shows up in one place, so shadow tools become visible — and approvable.