Managing a service | Seenode Docs
seenode™
Deploy
Managing a service

Managing a service

Environment variables, deploys and rollbacks, logs, metrics, and private networking for a seenode service.

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

Environment variables

Open the Envs tab and click Add env to add a KEY and value. Environment variables are available to your build and start commands. Adding or changing a variable takes effect on the next deploy.

Deploying, redeploying, and rolling back

Use the Deploy button on the service:

  • Deploy latest commit: build and deploy the newest commit on the connected branch.
  • Deploy specific commit: pick an earlier commit to deploy, for example to roll back.
  • Restart service: restart the running service without rebuilding.

To deploy automatically whenever you push, enable Auto-deploy in Settings (it is off by default).

Logs

The Logs tab streams your service’s output. Filter by source (Runtime, Build, or Request), switch between a live tail and a fixed time range (up to 14 days), and search the output.

Metrics

The Usage tab shows CPU and memory usage over time (1 hour to 7 days).

Private networking

Every service has an internal address of the form http://web-<id>-service, shown on the Domains tab. Other services in the same workspace can reach it over seenode’s private network, useful for calling an internal API or a worker without exposing it publicly.

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.