Documentation

Provisioning lifecycle

An order moves through a durable workflow. Each stage is visible on the instance page as a timeline: payment confirmed → reserving capacity → allocating public address → cloning system image → applying cloud-init → booting → installing control panel (optional) → verifying network, SSH and agent → delivering access details. Failed steps retry with backoff; an instance is only marked active once the guest answers on the agent, network and SSH checks.

Connecting to an instance

Add your public key under SSH keys before ordering; it is injected through cloud-init.

ssh -i ~/.ssh/id_ed25519 scodyx@<instance-ip>
sudo -i   # first login sets no root password; use sudo

API authentication

Create a key in the console under API keys. Keys are hashed on our side and shown once.

curl https://cloud.scodyx.com/api/public/v1/instances \
  -H "Authorization: Bearer sx_live_xxxxxxxxxxxxxxxx"

{
  "instances": [
    {
      "id": "0b1c…",
      "hostname": "vps-101",
      "status": "active",
      "vcpu": 2,
      "ram_mb": 4096,
      "disk_gb": 60,
      "region_id": "bhs",
      "panel": "xpanel",
      "created_at": "2026-08-31T10:12:44.000Z"
    }
  ]
}

Errors return 401 missing_api_key or 401 invalid_api_key. Revoked keys stop working immediately.

Snapshots and backups

Snapshots are node-local and instant; backups are written to an offsite target and survive node loss. Restores stop the instance, roll the disk back and boot it again — the timeline shows each stage.

Availability

ScodyX Cloud runs a single Beauharnois node today with a 99.5% best-effort target. A 99.9% SLA is published only after the high-availability cluster is live. Live component state is on the status page.