Deployments

Preview and live

A deployment is a saved configuration snapshot. An environment is a name pointing to a deployment. preview is the default development target; live is the customer-facing target.

vatio push
vatio status
vatio diff --env live
vatio publish
vatio rollback

push validates and updates a preview; it cannot target live. publish promotes a preview. rollback restores the previous live configuration. diff --env live compares your local directory with live, so push local edits before publishing them.

Agents, tools, auth configuration, chats, and contacts are scoped by environment. Secrets, knowledge content, channel connections, business fields, and widget settings are workspace-wide. Applying a manifest can update business and widget settings during a preview push. A preview tool can also call the same external backend as live. Use a separate workspace when these resources must be isolated.

Rollback restores deployment configuration, not knowledge content, secret values, or actions already performed by a tool.

Named previews

Create an independent preview for a branch or pull request:

vatio push --env pr-42
vatio chat "What does Acme do?" --env pr-42
vatio tokens create --env pr-42
vatio publish --env pr-42

Names use lowercase letters and digits separated by hyphens or underscores, up to 40 characters. Shared WhatsApp and Instagram previews always use the literal preview environment.

The preview share URL printed by push opens without a login. Anyone with that URL can talk to the preview, so share it with its intended testers.

Deploying from GitHub

Install the Vatio GitHub App and bind a repository to your workspace in the console. The workspace owner chooses this binding; a repository's workspace value must match it. Set the workspace directory if the repository contains more than one vatio.yml.

Event	Result
Pull request opened, updated, or reopened	A pr-N preview and a comment with its URL when the workspace directory changes
Pull request closed	Its preview is removed
Push to the default branch	Deployment and publication to live

The CLI remains available for manual deployment and troubleshooting.

Secrets

vatio secrets set ACME_API https://api.acme.com
vatio secrets set ACME_API_KEY YOUR_BACKEND_KEY
vatio secrets list
vatio secrets rm ACME_API_KEY

Keys use uppercase letters, digits, and underscores, starting with a letter. Tools read values with $env.KEY. Listing returns names, never values. Changes take effect on subsequent calls without deploying and apply to every environment. Rollback does not restore old values.

Keep credentials out of manifests, tool source, knowledge, and tool results. The workspace upload includes ordinary files, so keep private signing keys outside that directory.