One control planefor any compute.

• Web app

  A domain, its certificate, and the deployment it routes to.

  unisrv.hcl

  project = "unisrv-io"
  
  service "unisrv" {
    hosts = ["unisrv.io"]
  
    location "/" { deployment = "web-ssr" }
  }
  
  deployment "web-ssr" {
    port = 80
    container {
      image = "ghcr.io/unisrv/unisrv-io:latest"
    }
  }

  The whole file that deploys unisrv.io. Of course we self-host :)

• App + database

  Postgres keeps its volume through restarts and rollouts. The api reaches it by name.

  unisrv.hcl

  deployment "api" {
    port    = 8000
    network = "internal"
    container {
      image = "ghcr.io/acme/api:1.4"
      env   = { PGHOST = "postgres" }
    }
  }
  
  deployment "postgres" {
    network = "internal"
    container {
      image = "postgres:17"
      env   = { POSTGRES_PASSWORD = var.db_password }
    }
    volume {
      mount_path = "/var/lib/postgresql/data"
      size       = "10GB"
    }
  }
  
  network "internal" {}

• One-off task

  Runs to completion and exits with the container's code. On a node with KVM, each one is its own Firecracker microVM.

  terminal

  unisrv instance run --rm python:3.13 python3 -c "$AGENT_CODE"
  
  unisrv instance run --rm alpine echo hello
  [09:14:12] Image ready: library/alpine:latest -> sha256:d56c381f961d… 57.5 MB in 563ms
  [09:14:13] state: online
  [09:14:13] Instance v. 0.1.0
  [09:14:13] state: pulling_container_image
  [09:14:13] state: executing_container
  hello
  [09:14:13] Container exited with code: 0 after 8ms

• Preview per PR

  The same file under another environment name is an independent copy, at its own *.unisrv.dev address.

  terminal

  # in CI, for every pull request
  unisrv up -y --env pr-42 --var tag=$GIT_SHA
  
  # once it merges
  unisrv destroy -y --env pr-42

None of these name a machine: the control plane picks one.