Skip to main content
Workshop Cloud includes built-in publishing. Click Publish, and your app is deployed to serverless infrastructure with a unique URL that anyone can access.

How Publishing Works

1

Click Publish

Click the Publish button in the top-right corner of the Workshop Cloud 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 everything to serverless infrastructure.Deployment typically takes 30 seconds to 2 minutes depending on project size and dependencies. The maximum timeout is 5 minutes.
4

Share the URL

Once deployed, copy the shareable URL and send it to anyone. They can start using your app immediately.

Custom Project URLs

Every published app gets a unique URL based on your project’s slug — an auto-generated identifier like gentle-elephant-alice. The resulting URL follows the pattern:
https://{your-project-slug}.memex.build
On a paid plan (Build or Scale), you can rename the slug to something more meaningful. Renaming is only available when the app is stopped — stop the app first, rename, then republish.
Slug names must be 3-50 characters, lowercase letters, numbers, and hyphens only. No leading, trailing, or consecutive hyphens. Each slug must be globally unique.

Public vs Private Apps

Public Apps

  • Select “Anyone on the internet” in the Visibility dropdown
  • No sign-in required for visitors
  • Available on all plans including the free Discover tier

Private Apps

  • Select “Only people invited” in the Visibility dropdown
  • Invite specific people by email in the “Who can access” section
  • Visitors who aren’t invited see an “Access Restricted” page
How private app authentication works:
  1. A visitor opens your private app URL
  2. If they’re not signed in, they’re redirected to a sign-in page showing your app name and your identity as the owner
  3. They sign in with Google or request an email magic link
  4. After signing in, they’re redirected back to your app automatically
Private apps require a paid plan. On the Build plan, you can invite up to 5 viewers and publish 1 private app. The Scale plan offers unlimited viewers and private apps.

What Happens During Deployment

When you click Publish, Workshop performs these steps:
  1. File packaging — Your project files are collected and uploaded to the deployment infrastructure
  2. Secret injection — Any secrets you’ve configured (API keys, database credentials) are securely injected into the deployment environment
  3. Connector credentials — If your project uses managed connectors (Workshop-provided AI connectors), fresh API keys are auto-generated for the deployment
  4. App startup — Your app’s start command is auto-detected and executed (Streamlit run command or FastAPI server)
  5. URL routing — Traffic is routed to your app through the project slug URL

Updating a Published App

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

Stopping a Published App

To take your app offline:
  1. Open the Publish popover
  2. Click Stop
  3. Confirm the action
Stopped apps show a friendly “App Temporarily Unavailable” page to visitors instead of a technical error. You can republish at any time.

Viewing Published Apps

On the Projects page, published apps display a green Live indicator with the deployment URL. You can filter your projects by the Live tag to see only published apps. Clicking the URL opens the app in a new tab.

Hide Workshop Branding

On paid plans, you can remove the Workshop badge from your published apps. Toggle the Hide branding option in the Publish popover’s advanced settings. Private apps can always hide branding regardless of plan.

Plan Limits

FeatureDiscover (Free)BuildScale
Public appsUnlimitedUnlimitedUnlimited
Private appsNot available1Unlimited
Invited viewers (per private app)N/A5Unlimited
Custom slug renameNoYesYes
Hide brandingNoYesYes

Troubleshooting

Deployments have a 5-minute timeout. If your app has many large dependencies, it may take longer to install them. Try simplifying your requirements or breaking the project into smaller pieces.
This means the deployment has stopped. Open your project in Workshop Cloud and click Publish again to redeploy. If the app keeps stopping, check your app’s startup logic for errors.
Private visibility requires a paid plan. On the Build plan, you’re limited to 1 private app — if you already have one, you’ll need to upgrade to Scale or make the existing private app public first.
You can only rename a slug when the app is stopped. Stop the app first, rename the slug, then republish.