Skip to main content
Workshop Desktop supports the same one-click publishing as Workshop Cloud. When you’re ready to share your app, Workshop handles hosting and compute — nothing to provision, no server to manage.

​
One-Click Publish to Workshop

Click Publish in the top-right corner of the interface. Workshop packages your project, injects secrets and connector credentials, and deploys to Workshop’s hosting infrastructure. Your app gets a public URL you can share immediately.
1

Click Publish

Click the Publish button in the Workshop Desktop interface. A popover opens showing your deployment settings and the URL your app will be available at.
2

Configure visibility

Choose who can access your published app:
  • Public — Anyone with the URL can use your app. No sign-in required.
  • Private — Only people you explicitly invite by email can access it. Requires a paid plan.
3

Deploy

Click Publish in the popover. Workshop packages your project files, injects any required secrets and connector credentials, and deploys to hosting infrastructure.
4

Share the URL

Once deployed, copy the shareable URL and send it to anyone. They can use your app immediately — no install, no setup on their end.

​
App URLs

Every published app gets a unique URL based on your project’s slug: 
https://{your-project-slug}.workshop.build
On a paid plan (Build or Scale), you can rename the slug to something more meaningful. Rename while the app is stopped — stop it first, rename, then republish.

​
Public vs Private Apps

​
Public Apps

Anyone with the URL can access the app. No sign-in required. Available on all plans.

​
Private Apps

Only people you invite by email can access it. Visitors who aren’t invited see an “Access Restricted” page. Private apps require a paid plan.
FeatureDiscover (Free)BuildScale
Public appsUnlimitedUnlimitedUnlimited
Private appsNot available1Unlimited
Invited viewers (per private app)N/A5Unlimited
Custom slug renameNoYesYes
Hide brandingNoYesYes

​
Updating a Published App

After making changes to your project, click Update in the Publish popover to push the latest version. The URL stays the same — visitors see the new version once the update completes.

​
Stopping a Published App

Open the Publish popover and click Stop. Stopped apps show a friendly “App Temporarily Unavailable” page instead of a technical error. You can republish at any time.

​
Deploying to External Platforms

Because Workshop Desktop projects are standard files on your local machine, you can also deploy to any external platform — Vercel, AWS, Railway, Fly.io, your own server, or anywhere else. This is entirely optional. If Workshop’s built-in hosting meets your needs, there’s no reason to set up external infrastructure. External deployment makes sense when you need:
  • Custom domains on your own infrastructure
  • Integration with an existing CI/CD pipeline
  • Compliance requirements around where your app runs
  • A platform you’re already using for other services
For external deployment, ask Workshop directly — describe your target platform and it will configure the deployment for you. 
Deploy this app to Vercel and set up a custom domain.

Set up a GitHub Actions pipeline that deploys to AWS on push to main.

Dockerize this app and write a docker-compose file for self-hosting.

​
Sharing and Access Control

Published apps support granular access control — share publicly or limit to specific people. For team-level sharing and managing access across your organization, see Sharing and Teams.