# Servers (VMs) with `aral`

    aral server plans                 # id, name, vcpu, ram_mb, disk_gb, price_monthly_cents (UZS tiyin)
    aral server regions               # slug (e.g. hel1), node_count
    aral server images                # os image slugs, e.g. ubuntu-24.04

## Create

    aral server create --name my-vm \
      --plan-id <plan-uuid> --region hel1 --os-image ubuntu-24.04 \
      --ssh-key "ssh-ed25519 AAAA... me@host"

Returns `{id, status: "pending"}`. Poll `aral server get <id>` until
`status == "active"` (~2 min). `--ssh-key` is repeatable; at least one key is
required for access.

## Connect

    aral server ssh <id>    # prints: ssh -p <port> ubuntu@<node-ip>

The login user is **ubuntu** on every image. `server get` fields that matter:
`node_ip` + `ssh_port` (the address that actually answers from the internet),
`ipv6` (direct, port 22), `ipv4` (node-internal — NOT reachable from outside).
First boot takes ~2.5 min before sshd answers; retry for up to 5.

## Lifecycle

    aral server stop|start|reboot <id>
    aral server delete <id>

Delete first parks the server in `deleting` while a final disk copy is taken,
then `destroyed`. The copy is a custom image named "<name> (deleted copy)",
kept 7 days (billed at a reduced storage rate) — restore by creating a server
from it, or free it early by deleting the image.

## Domains

    aral server domain list <id>      # HTTP(S)-only: the edge routes by hostname
Raw TCP/UDP never rides a domain — use port forwards / the node address.