Skip to main content
Publishing takes an app’s latest successful build live. Every commit produces a versioned build and snapshot, so shipping is safe and reversible.

​
From commit to live

1

Commit

A commit type-checks, pushes to the workspace repo, and builds a snapshot in the background. Each commit is a version.
2

Publish

publish_app pins the latest successful build as the published version. If the build is still running or failed, publishing is blocked until it’s green.
3

Serve

External apps deploy to an edge worker at a public URL; internal apps become available to your organization.
You publish by asking an agent (publish_app) or from the editor.

​
Internal vs external

Internal apps

Served to members of your Zite organization only. No public URL.

External apps

Deployed to a public edge worker at https://<subdomain>.zite.so (or your custom domain), with the app’s sign-in for its users.
Changing an app’s access mode between internal and external is a confirmed action.

​
Versions & rollback

Every version is backed by a commit and its snapshot. From the app’s History you can:
  • Browse previous versions and preview them.
  • Restore an earlier version to roll back.
Because each build carries its commit, you always know exactly what’s live.

​
Custom domains

External apps can be served from:
  • A custom Zite subdomain, such as yourname.zite.so.
  • A custom domain you own. Connect it with a CNAME record; TLS is handled automatically.

​
Audit logs

Zite records an audit trail at the account level covering deploys, permission changes, and administrative actions, so you can see who changed what and when.