Cloudflare Access, Google IAP or while to protect an internal tool in 2026
Your internal tool must stay among colleagues, behind company sign-in. Cloudflare Access and Google IAP do this, as long as you set up what they require: a domain, a tunnel or a load balancer. while does it with nothing to set up. We compared the three on what you need to prepare, the price and what a client sees.
By Grégoire Mougeolle, co-founder of Nextmap. Facts checked on November 18, 2026.
An internal tool must stay among colleagues. The sure way is company sign-in: everyone signs in with their Microsoft or Google account, and nobody else uses it. Cloudflare Access and Google IAP are the two classic answers. They work, on one condition: setting up what they require. One needs a domain on Cloudflare and a tunnel, the other Google Cloud and a load balancer.
Our verdict. To put company sign-in in front of a tool built with your AI, while: no domain or tunnel to set up. A client uses it with a link and a password, and the tool is in France. Google IAP only if the tool already runs on Google Cloud. Cloudflare Access only if your domain is already on Cloudflare, with someone who can set up a tunnel.
The three at a glance
| Cloudflare Access | Google IAP | while | |
|---|---|---|---|
| What you need first | The domain active on Cloudflare, a tunnel to the tool | The tool on Google Cloud, a load balancer | The tool on while, put there by your AI |
| Sign-in | The identity providers you choose | The accounts your rules accept in Google Cloud | The company account: Microsoft Entra, Google Workspace, Okta, any OIDC |
| The price | Free up to 50 users, then $7 per user per month | No charge for IAP, the load balancer is billed | Free for up to 3 people, Pro for the whole team |
| A client | An identity your rules accept | An identity your rules accept | An access link and a password |
| History | 24 hours on Free, 30 days pay-as-you-go | Depends on Google Cloud | Who did what, kept for 13 months |
Try while on your tool, no sign-up. Copy the message
Cloudflare Access: a domain on Cloudflare and a tunnel
Cloudflare Access is part of Cloudflare Zero Trust, free for up to 50 users. Beyond that, the pay-as-you-go plan costs $7 per user per month, with no limit on numbers, and keeps logs for 30 days instead of 24 hours1.
To protect an internal tool, its domain must be active in your Cloudflare account, with a full or partial setup. You then choose identity providers, write access rules, and publish the tool through a Cloudflare Tunnel installed next to it. Cloudflare also advises that the tool check the token of each request itself, or let the tunnel do it2.
Google IAP: for a tool already on Google Cloud
Identity-Aware Proxy protects resources and tools hosted on Google Cloud, and its features come at no charge. The networking and compute of the load balancer it requires, however, are billed3. For a team already on Google Cloud, it is a direct path. For a tool hosted elsewhere, you first have to move it there.

while: company sign-in with nothing to set up
The tools your AI builds often have no server, no domain and no tunnel. We built while for them: your AI, Claude, ChatGPT or Cursor, puts the tool on while, and you keep it for your colleagues in one sentence.
You, to your AI: Put this dashboard on while, and keep it for company accounts.
- Company sign-in. On the Pro plan, everyone signs in with the company account: Microsoft Entra, Google Workspace, Okta or any OIDC provider. Access is set by group, by address or by domain. See keep a tool for your colleagues.
- A client uses the tool with an access link and a password, valid for 1, 7 or 30 days, with no identity to create.
- The history shows who did what, kept for 13 months, and opening to everyone waits for a person’s approval.
- The data is backed up every day, the credentials of your software stay in while, and your tools are hosted in France by Nextmap.
What while changes for IT is detailed on the IT page, and the case of tools everyone builds on their own in shadow AI: govern the tools your employees build.
On this point, while wins: company sign-in in front of a tool built with AI, with no domain or tunnel to set up.
Which one to choose
Choose while if:
- Your tools are built with AI, and you do not want to set anything up around them.
- A client must use them with a link and a password.
- You want your data in France, backed up every day.
Pick Google IAP only if your tools already run on Google Cloud. Pick Cloudflare Access only if your domain is already on Cloudflare and someone knows how to set up a tunnel.
To try while, give this message to your AI. The trial is free, with no sign-up, and your tool has its address in 3 minutes.
Read while.sh/agents and help me get started with while.
Sources
- Cloudflare, SASE and Zero Trust pricing, accessed November 18, 2026
- Cloudflare, Publish a self-hosted application behind Access, accessed November 18, 2026
- Google Cloud, Identity-Aware Proxy pricing, accessed November 18, 2026