Guide · June 7, 2025

How to Share an Internal Tool with Your Team (Without IT)

Four approaches to sharing an internal tool with your team — ranked by how fast they actually work. No IT ticket required.


You built something. It's useful. You want your team to use it. Here are the realistic ways to make that happen — ranked by how fast they actually work in practice.

Option 1: Workshop (30 seconds)

Built for exactly this use case. Deploy your existing app (Next.js, Python, Node, static HTML) to a company-gated URL. Your team signs in with their work email.

npm install -g @getworkshop/cli
workshop login
workshop init    # in your project directory
workshop deploy  # 30 seconds to live URL

Cost: Free for one app. $19/month for five.
IT involvement: None.
Auth code required: None — Workshop handles it at the infrastructure layer.
Time to working URL: 30 seconds.

Option 2: Cloudflare Access (free, ~45 min setup)

Cloudflare Zero Trust lets you put any web app behind company email authentication for free (up to 50 users). You need to set up a Cloudflare Tunnel and configure an access policy. Takes about 45 minutes for the first time. More configuration than Workshop but free and very flexible.

Best for: Teams already using Cloudflare who want a free solution and don't mind the setup.
Limitation: More complex to set up; requires your app to be accessible to the Cloudflare tunnel.

Option 3: Deploy publicly + add auth to the app (~2–4 hours)

Deploy to Railway, Render, or Fly.io (all public by default), then add authentication directly to your app using Clerk, Auth0, or a custom Google OAuth integration. Restrict sign-ups to @yourcompany.com domain.

Best for: Developers who want full control over the auth layer and are comfortable implementing OAuth.
Limitation: 2–4 hours of work that doesn't exist in the Workshop path. And you have to maintain the auth code.

Option 4: Share your screen / Loom (not a real solution)

Record a demo. Works for one-off knowledge transfer. Doesn't scale, doesn't let your team actually use the tool.

Option 5: IT ticket (weeks)

The official path. Submit a ticket, wait for procurement, provisioning, security review, SSO configuration. Realistic timeline: 3–8 weeks. By then the need has passed or you've moved on.

Only use when: The tool handles regulated data (HIPAA, PCI), requires centralized IT administration, or is a production system serving customers.

The right choice for most teams

If you built something with Claude Code or Cursor and want your team to use it today: Workshop is the answer. Zero IT involvement, zero auth code, 30 seconds from terminal to working URL.

workshop deploy

Try Workshop

Deploy your internal app in 30 seconds.

Free for one app. No credit card required.

npm install -g @getworkshop/cli && workshop deploy

Get early access → getworkshop.io

Related

Deploy Your Claude Code App So Your Team Can Use It
Run workshop deploy and get a URL only your @company.com coworkers can open. No IT ticket, no Vercel enterprise plan. Free for one app.
How to Deploy a Vibe-Coded App Internally (Without Making It Public)
You built it with Claude Code or Cursor. Now your team needs to use it — without it being on the public internet. Here's the 30-second path.
Deploy a Flask App for Internal Company Use (Company Email Only)
How to deploy a Flask or FastAPI app so only @yourcompany.com employees can access it — without IT, without AWS, in 30 seconds.