Skip to main content
Deploying takes the app you’ve been building in the preview sandbox and publishes it to the internet on Cloudflare’s global network. Until you publish, your app only runs in the preview panel — deploying gives it a real, shareable URL.
Your live app is separate from the preview. The preview reflects your latest changes as you build; the deployed app only updates when you publish or redeploy.

​
The Publish Wizard

When your app is ready to share, open the Publish wizard from the editor. It walks you through everything in a few steps.
1

Open the Publish wizard

Click Publish in the editor.
2

Add a title and description

Give your app a title and, optionally, a short description. Fabricate assigns your app’s address on fabricate.chat automatically when you publish, so there’s no address to pick.
3

Choose visibility

Set your app public or private. Public apps can be opened by anyone with the link and are eligible for the Discover gallery; private apps can be opened only by you and are available on paid plans. See App Visibility for the full breakdown.
4

Publish

Review your choices and confirm. Before your app goes live, Fabricate opens it in a real browser: if it crashes, never mounts, or renders a blank page, publishing is blocked so you can fix it in the preview first. Otherwise, Fabricate deploys your app onto Cloudflare’s global edge network.

​
Your App’s URL

Every published app gets an address on fabricate.chat, which Fabricate assigns automatically. It works immediately — no DNS setup, no SSL configuration. It’s ready to share the moment publishing finishes. If you’d rather use your own domain, you can connect one after publishing on a paid plan. See Custom Domains.

​
Redeploying After Changes

Publishing is not a one-time action. As you keep iterating in the chat, your live app stays on the last version you published until you redeploy. When you’ve made changes you want to ship, open the Publish wizard again and redeploy. Your app’s address, visibility setting, and any custom domain stay the same, and so does its data — only the app’s code is updated. This lets you test changes safely in the preview before they reach your users.
Treat the preview as your staging environment. Get a change feeling right in the preview, then redeploy to push it live.

​
Plans and Published Apps

How many apps you can have live at once depends on your plan:
  • Free — a limited number of published apps
  • Pro — unlimited published apps
  • Scale — unlimited published apps
See pricing for the current limits. Publishing an update to an app that’s already live doesn’t count again. On the Free plan, once you reach the limit, publishing another app means deleting one you’ve published or upgrading to Pro or Scale.

​
Frequently Asked Questions

Fabricate builds and checks the new version before it replaces the live one, so if an update is blocked or fails, your current version keeps running.
No. Your app’s fabricate.chat address is assigned automatically and stays the same across redeploys. To serve your app from an address you choose, connect a custom domain on a paid plan.
Environment variables and secrets you’ve set in your project’s settings are applied to the published app when you publish. If you change one later, it takes effect the next time you publish. See Environment Variables & Secrets.
Not for apps built today. A published app stores its data in the published app itself, so unpublishing would delete that data. To remove public access while keeping everything, make the app private (paid plans), or delete the app if you no longer need it.

​
Next Steps

Custom Domains

Connect your own domain with automatic SSL.

App Visibility

Understand public vs private apps and the Discover gallery.