seenode™
Deploy
Managing a service

Managing a service

Deploys and rollbacks, logs, metrics, and day-to-day management for a seenode service.

Last updated September 18, 2026

Once a service is running, you manage it from its tabs in the dashboard.

Environment variables

Open the Envs tab to add keys, mark secrets, or import a .env file. Saving on a web, worker, or private app restarts it with the current image (not a Git rebuild). Static sites use env vars at build time only. Full detail: Environment variables.

Deploying, redeploying, and rolling back

Full detail: Redeploy, rollback, and restart. Short version: use Deploy for latest or a prior commit, Restart to bounce the current image, and enable Auto-deploy in Settings if you want every push to deploy (off by default).

Logs

The Logs tab streams output. Filter by source (Runtime, Build, or Request), switch between a live tail and a fixed time range (up to 14 days), and search. Static sites have build (and request) logs; there is no runtime process.

Metrics

The Usage tab shows CPU and memory over time (1 hour to 7 days). Static sites have no container metrics tab.

Private networking

Web and private services expose an internal http://{name}-service address on the workspace network. Full detail: Private networking.

Duplicating and deleting

  • Duplicate: from the service’s ⋯ menu, create a copy with the same configuration.
  • Delete: from Settings → Danger Zone. Deleting a service is permanent.