Deploy and monitor

Deploy provider-neutral static or Node output and inspect protected production metrics.

Build the deployment output

tavo build creates static assets and prerendered HTML under .tavo/build/client plus a generated Node production server at .tavo/build/server/start.mjs.

BASH

bashnpx tavo build
PORT=4174 node .tavo/build/server/start.mjs

Choose static hosting or Node

Publish .tavo/build/client when every required route can run as CSR or prerendered HTML. Use the generated Node server when SSR, server loaders, actions, sessions, server routes, or monitoring require request-time execution. Browser-safe loaders can run in CSR; the deciding factor is whether the feature needs a server at request time.

Configure trusted hosts and canonical origin where the platform synthesizes request URLs.
Set CSP, secrets, body limits, and image allowlists for the deployment.
Rebuild before deploying; generated output is not application source.

Follow the deployment guide for static-host fallback rules and a production checklist. The command above uses POSIX shell syntax; in PowerShell, set the variable with $env:PORT = "4174" before running the Node command.

Protect runtime monitoring

The generated server exposes monitor data only when TAVO_MONITOR_TOKEN is configured. The CLI sends the same token in an Authorization: Bearer header and can print one JSON snapshot or refresh continuously.

BASH

bash# Server process: provide TAVO_MONITOR_TOKEN through deployment secrets.
node .tavo/build/server/start.mjs

# Separate terminal: set the same TAVO_MONITOR_TOKEN, then request a snapshot.
npx tavo monitor --url https://app.example.com --once
npx tavo monitor --url https://app.example.com --json --once