Deploy your first server

The deploy wizard lives at Servers → Deploy. Every server boots with a public IPv4 address.

Region

Pick where the server runs. Each region lists the features it supports — block storage, floating IPs, backups. Latency to your users usually decides this.

Some regions are listed but can't be picked yet. Coming soon means we haven't opened that location; Fully booked means it's open but every machine there is taken. Either way you can join the waitlist — one tap, one vote per account — and we'll know to build there next. Joining needs an account, you can leave again whenever you like, and it costs nothing. See Region waitlist.

Operating system

Choose a base image. Linux distributions log in over SSH; Windows images log in over RDP. Only images marked deployable can be selected. The image you pick changes which login options appear in step 4.

Size

Pick a plan. Each shows vCPUs, memory, SSD, and monthly transfer. Prices are monthly; the hourly rate is derived from them and capped at the monthly price. Which one you actually pay depends on your account's billing mode — monthly by default. See Billing.

Authentication

Decide how you'll log in — this is set at first boot:

SSH key (Linux) — select a saved key, or add one inline.
Set a password — always works for the console/VNC. On Linux, it also works for SSH only when the platform's guest-agent bootstrap is enabled; otherwise SSH stays key-only. On Windows this is required, since RDP needs an Administrator password.
Email me a generated password — we generate one and send it as a 3-day link. You'll be required to change it on first login.

Hostname

The field arrives already filled in with a readable two-word name — quiet-harbor, copper-birch, that sort of thing — so you can deploy without stopping to invent one. Type over it if you'd rather, or press the dice for a different suggestion. Letters, numbers and hyphens, up to 63 characters; the Deploy button stays disabled while the field is empty or invalid. Optionally add tags to organise and filter your fleet later.

The name is only your label, and you can change it any time. The identifier that never changes is the server's handle — see Names and handles.

You need a way in

If you set neither an SSH key nor a password, the server will still deploy — but you won't be able to log in. For Windows, an Administrator password is mandatory.

Check the cost before you confirm

The wizard shows the effective rate for your choices and checks your wallet balance. If the balance is too low, the Deploy button stays disabled until you top up — head to Billing and add funds, then come back.

Deploy from code

Every deploy is a single authenticated POST /instances. The wizard shows the Equivalent API request as a ready-to-run curl snippet, so you can lift it straight into CI or a script:

curl -X POST https://console.ekire.net/api/v1/instances \
  -H "Authorization: Bearer $EKIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "planId": "nano",
    "regionId": "<region-id>",
    "osImageId": "<image-id>",
    "name": "quiet-harbor"
  }'

name is required. Deploying from code, you pick it yourself — the console's suggestion is a convenience of the form, not a server-side default.

See the API reference for every field and the full set of endpoints.

After it boots

Open the server's detail page to find its IP address, open the web console, watch live CPU/network graphs, manage snapshots and backups, resize, or reinstall the OS. If you chose the emailed-password option, open the secure link from your inbox to reveal the generated root password, then log in — your first console login forces you to change it.