Skip to main content
Publishing deploys the current main commit. There is no separate production branch - the most recently published commit on main is what’s live. For how building and iterating works before this point, see How building works.

​
What publishing does

  • Remote apps deploy to Kazzle’s cloud and get a public URL. See Deploying for how the deploy runs and what the URL looks like.
  • Local apps install on your computer. The UI loads directly, and the process part runs a dev server.
When you publish to the marketplace for others to install, your app receives a user identity token on launch, an install key for its backend, and install/uninstall webhooks. See Marketplace.

​
Caching, updates, and offline

Desktop and mobile only open your app URL in a normal browser view. They do not clear browser caches, force network-only loads, or pick a different cache policy for public vs private apps. Your web app owns caching:
  • HTTP Cache-Control headers for documents and assets
  • Optional service worker / PWA setup (templates ship vite-plugin-pwa with auto-update)
  • Whether a new build activates immediately, reloads once, or waits for the next open
  • Offline fallback for the latest activated build
When Kazzle sees a new published version for an open app tab, it asks the registered service worker to check for an update (registration.update()). Apps without a service worker ignore that check and keep using their own HTTP cache headers. Published apps can therefore open instantly from cache, pick up a new build without a hard refresh, and keep the latest build available offline.

​
Realtime apps

For apps that need instant local reads and offline support, the AI:
  1. Creates a database
  2. Turns on realtime sync
  3. Builds a two-part app: UI (React + sync client) and Process (token endpoint + sync upload)
  4. Wires credentials through the vault
See Realtime sync for how it works.

​
Custom domains

To use a custom domain, point your domain or subdomain at the deployed app URL.

​
Next steps

  • Deploying - deploy mechanics, production URLs, and runtime commands
  • Marketplace - let other Kazzle spaces discover and install your app