Your business teams already build their tools with AI.Say yes, without losing control.
That’s shadow AI: tools built with ChatGPT or Claude, in personal accounts, that no one sees. With while, they are in one place, in France, behind the company sign-in, with the history of every change.
Malik’s Claude
- Malik: I’m on the planning team. Share my tool with the team, using while.
- Malik’s Claude: I’m putting it on while, with its data and the morning import.
- Authorize your AIwhile · A new projectAuthorized
- Malik’s Claude: Done, it has its address.Schedule of visitsplanning.acme.com
- Malik: Give the planning team access.
- Malik’s Claude: Requested. The request is waiting for IT’s approval.Give the planning group accessrequested by Claude
- Malik: Connect the import to Pennylane.
- Malik’s Claude: I set up the connection to Pennylane, read only. The connection is waiting for IT’s approval, and I will never see the credential.PennylaneRead only · declared by Claude
- while: Known vulnerability in lodashCVE-2021-23337, high
- Malik’s Claude: I’m upgrading lodash to the fixed version, then updating the tool.Securitylodash 4.17.21
- Malik’s Claude: It’s fixed.
- Malik: What did you do this week?
- Malik’s Claude: It’s all in while’s history.
planning.acme.com
Schedule of visits
IFMBLDInès, Malik and Léa used it this morning
A business team’s AI shares its tool
You choose who uses it
The credential is entered in while, not with the AI
The AI fixes known vulnerabilities
You see everything the AIs do
hello@while.sh
The message is the same for every AI.
Hosted in Franceby Nextmap
What you would have to assemble is already there
Each tool serves the people you choose
Your colleagues with the company account, by group or by domain, or a client with a link and a password.
Business teams work on their own, and nothing important happens without you
You choose who approves what, two-person approval included.
You know who did what, and you can prove it
The history is signed and verifiable. With the Enterprise plan, it streams to your SIEM.
A business team’s tool doesn’t put the others at risk
Each tool runs isolated from the others, and the business team’s AI fixes the known vulnerabilities in its dependencies, checked at every new version, then every day.
The company’s credentials stay secret, even from the AIs
Tools and AIs use your software without ever seeing its credentials.
Your data stays in France, with a French company
Your tools and their backups are hosted in France, by Nextmap.
When its author leaves, the tool stays with the company
The code is in your repository or in the archive of each version, and the data on while.
What your security team will ask
- Identity
- Your colleagues use the tools with the company sign-in, over OpenID Connect, with Microsoft Entra, Google Workspace, Okta, Keycloak or any other provider.
- Approvals
- You set rules by role, by group and by tool, with two-person approval if you like. An AI never approves.
- History
- It is append-only, chained and signed. It can be exported and re-verified with a small script.
- Isolation
- Each tool runs in its own sandbox, with no access to the other tools. Its outbound traffic to the internet is blocked by default.
- Known vulnerabilities
- Each tool’s dependencies are checked against known vulnerabilities at every new version, then every day, and the business team’s AI updates them.
- Backups
- Every day, they go to storage outside the cluster where the tools run, dedicated to your organization and encrypted with AES-256. They are kept for 14 days.
- Cutting access
- You disconnect an AI, revoke a credential or a token, close a person’s sessions or remove someone’s access, at any time.
- Leaving
- The code of each version is archived. Data can be exported as CSV or as files.
Questions
Getting started
What is shadow AI?
The AI tools and uses that teams set up without IT. When they are banned, they move to personal accounts.
A CFO wants to share their tool: where do we start?
They ask their AI to share the tool with their team, and you approve the access.
Do we need a team to run while?
No, there is nothing to install or run on your side.
Your rules
How do we oversee the AIs of business teams and contractors?
Each AI acts with the permissions of the person using it, and your rules say what waits for an approval.
Can a business team make a tool public without IT?
No. By default, making a tool public waits for an admin’s approval.
Who maintains these tools?
The business team’s AI maintains them, within the rules you have set.
What if a business team’s AI breaks its tool?
It goes back to the previous version on its own.
Data
Can the tools use our software, like the ERP or the CRM?
Yes. Each piece of software connects as a data source, which you approve.
Can one tool read another tool’s data?
Only after your approval, and read only.
Can an AI delete the data of a tool in production?
Not on its own. On while, replacing or destroying a production database always waits for a person’s approval.
Can we bring over tools that are on AWS or Heroku?
Yes. The AI takes over the code, copies the data from a backup and carries over the settings, as in the guide Leaving Heroku.
Start with one business team’s tool
The while team’s address
hello@while.sh
Talk to the while teamTo try it, a business team gives this message to its AI:
Read while.sh/agents and help me get started with while. Copy the message