The best hosting options for an internal tool in 2026
An internal tool has to run somewhere, and above all stay among colleagues. Hosts and protection tools each offer their own way to keep it for your colleagues, more or less long to set up. We compared five ways to do it in November 2026.
By Grégoire Mougeolle, co-founder of Nextmap. Facts checked on November 18, 2026.
An internal tool raises two questions at once: where it runs, and how it stays among colleagues. The second matters more, because an internal tool open to anyone with its link is no longer really internal. Hosts and protection tools each answer in their own way, and the difference lies mostly in what you have to set up before the team can use it.
The short version. For a tool built by your AI, while: your colleagues use it with nothing to set up, a client with a password, and the tool is in France. Elsewhere, only if the tool already runs there: Google IAP on Google Cloud, or Vercel’s deployment protection for a site on Vercel. Replit has its workspace-only access, and Cloudflare Access protects a tool whose domain is on Cloudflare.
The 5 ways at a glance
| Who it is for | What to set up | Sign-in | |
|---|---|---|---|
| while | A tool built by your AI | Nothing beyond the tool | Email accounts on the Pro plan, a password for a client |
| Cloudflare Access | A tool hosted anywhere | The domain on Cloudflare, a tunnel | The identity providers you choose, free for up to 50 users |
| Google IAP | A tool on Google Cloud | A load balancer | The accounts your rules accept |
| Vercel | A site hosted on Vercel | The project’s protection settings | Vercel Authentication, password or IP addresses, depending on the plan |
| Replit | A tool built in Replit | The publishing setting | The workspace, chosen people or a password |
Try while on your tool, no sign-up. Copy the message
How we chose
On November 18, 2026, we reread the pages of Cloudflare, Google Cloud, Vercel and Replit, cited as sources, and we used while ourselves. We looked at each way with three questions: what you have to set up before the team uses it, who can use it, colleagues and clients, and what the team costs.
For a tool built by your AI: while
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 time-off tracker on while, for company accounts only.

- Your colleagues sign in with a while account for up to 3 people, or, on the Pro plan, with their email account, Google or Microsoft, whatever their number. 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.
- The data is backed up every day, the credentials of your software stay in while, and your tools are hosted in France by Nextmap.
Strengths: nothing to set up around the tool, no per-person price on the Pro plan, and hosting in France.
Limits: while serves the tools your AI puts there, and does not protect a tool hosted elsewhere.
For a tool hosted anywhere: Cloudflare Access
Cloudflare Access protects a tool wherever it runs. It is part of Cloudflare Zero Trust, free for up to 50 users, then $7 per user per month1. The tool’s domain must be active on Cloudflare, and the tool is published through a Cloudflare Tunnel installed next to it2.
Strengths: free for a small team, and independent of the host.
Limits: a domain on Cloudflare and a tunnel to set up and maintain.
For a tool on Google Cloud: Google IAP
Identity-Aware Proxy protects tools hosted on Google Cloud. Its features come at no charge, but the load balancer it requires is billed3.
Strengths: nothing to add for a tool already on Google Cloud.
Limits: you have to be on Google Cloud, and pay for the load balancer.
For a site on Vercel: deployment protection
Vercel protects a project with Vercel Authentication, a password or a list of IP addresses, depending on the plan and each person’s permissions4. It is simple for a team that already has its sites on Vercel.
Strengths: set in the project, with no extra tool.
Limits: the options depend on the Vercel plan, and everyone goes through Vercel’s sign-in.
For a tool built in Replit: restricted access
Replit publishes a tool kept for the workspace, for chosen people, or behind a password visitors use without a Replit account5.
Strengths: access is set when publishing, and a password is enough for a client.
Limits: for a restricted tool, your colleagues must be part of the Replit workspace.
Which one to choose
| Your situation | Our pick |
|---|---|
| Your AI builds the tool, and you want company sign-in with nothing to set up | while |
| The tool runs elsewhere, and your domain is on Cloudflare | Cloudflare Access |
| The tool runs on Google Cloud | Google IAP |
| The tool is a site on Vercel | Vercel |
| The tool is built in Replit | Replit |
The full head-to-head is in Cloudflare Access, Google IAP or while. 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
- Vercel, MCP project tools (deployment protection), accessed November 18, 2026
- Replit, Private deployments, accessed November 18, 2026