Trading server use case

SkyVM Medium is a dedicated KVM VPS in Dallas (TX - USA) with a public IPv4, not an exchange colo. It is a good fit for broker APIs, paper/live workers, and isolated strategy processes. It is not NY4, not same-AZ AWS, and not a cross-connect to an exchange.

What “low latency” means here

• Dedicated public IPv4 (not shared NAT).
• Guest clock via chrony against pool.ntp.org — typical offset is milliseconds, not exchange PTP.
• Host clone usually finishes within about three minutes.

Provision without a human

Use PUT /api/v1/vms/{name} so a worker named worker-1 is created once and reused. Subscribe to vm.ready. Optional healthCheck waits for FastAPI :8090/health inside the guest (qemu guest agent), not just qemu start.

curl -X PUT https://www.skyvm.cloud/api/v1/vms/worker-1 \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"plan":"medium","password":"...","healthCheck":{"port":8090,"path":"/health"}}'

Not in this API yet

• Outbound HTTPS allowlist (broker-only egress).
• No public SSH by default / Cloudflare private ingress.
• Ubuntu + Docker Compose or partner cloud-init images.
• Keys scoped to a single named VM.

Those are follow-ups. The $10 Medium is enough for a trading worker once list / ensure / status are pinned — see the cookbook and OpenAPI.