You built something useful. Your team needs it. The official path is: open an IT ticket, wait 3 to 8 weeks for procurement, provisioning, security review, and SSO configuration. By then, you've moved on to something else and the tool dies.
Here's how to ship your internal tool today — no ticket required.
Why IT tickets exist (and why they're the wrong tool here)
IT provisioning processes exist for good reasons: security review, vendor contracts, cost management, compliance. They're designed for production systems that handle customer data, require SLAs, or need enterprise-grade access control.
Your Claude Code app that the CX team uses to summarize support tickets is not that. But it goes through the same queue — because there's no alternative designed for internal tools built by individual contributors.
Until now.
What you actually need for an internal tool
- A URL your team can open
- Authentication that only lets @yourcompany.com in
- The app stays running when your laptop is closed
- No public exposure to the internet
That's it. You don't need vendor contracts, SLA agreements, or a Jira ticket.
Workshop: deploy without IT
npm install -g @getworkshop/cli
workshop login # authenticate once with your work email
cd your-project
workshop init # auto-detects framework
workshop deploy # done in ~30 secondsWhen asked about access mode, choose Company domain. The deployed URL only works for people who sign in with @yourcompany.com email. Your IT department doesn't need to do anything — the access control is handled at the infrastructure layer.
What this is and isn't
It is: A fast path for individual contributors to deploy internal tools with real email-domain access control. Appropriate for ops tools, reporting dashboards, AI utilities, and scripts your team uses day-to-day.
It isn't: A replacement for proper IT infrastructure for production customer-facing systems. If you're handling PII, financial data, or customer-facing systems, loop in IT.
The conversation with IT (if you need it)
If you do need to tell IT about it eventually: "I deployed an internal tool on Workshop. Access is restricted to @company.com email sign-in via Google/Microsoft OAuth. No data leaves company email domain. Here's the URL." That's usually the end of the conversation.
Pricing
Free for one app. $19/month for five apps. No contract, cancel anytime.