workshop deployone command, any folderLive in 30 secondsno config, no Dockerfile@company.com gatedautomatic, from day oneAPI keys stay privateproxied through our edgeFree to startno credit cardshouldn't be a Jira ticket.
workshop deploySign in with your work Google account. Your CLI key is stored locally — never committed to git.
npm i -g @getworkshop/cli workshop login
Workshop detects your runtime, bundles your app, and ships it to the edge. No Dockerfile, no config file.
cd my-project workshop deploy
Anyone with @yourcompany.com can open it immediately. No invite list, no passwords, no IT ticket.
acme-tool.getworkshop.io → Secured to @acme.com
Every Workshop app is gated to your company email domain from the moment it deploys. No configuration, no invite list, no SSO contract. You run workshop deploy and we handle the rest.
Workshop reads your work email on deploy and locks the app to that domain. Anyone with @yourcompany.com gets in. Nobody else does. Ever.
Add your API key once. We proxy calls through our edge — your key never touches your app's frontend code. Teammates get full functionality without seeing it.
We don't publish a list of what you've deployed. Your subdomain is yours. Only the people you let in know it exists.
Unlike public-hosting platforms, Workshop deploys private by default. We've seen what happens when internal tools accidentally ship to public URLs — Workshop makes that impossible from day one.
Not enterprises.
I'm personally onboarding the first 50 users.