Spin up a KVM VM with one REST call, run code via /exec, tear it
down when done. No SSH setup, no polling.
Per-minute billing — destroy to stop charges. Full GUI for humans too.
# 1. Obtain a token (once) POST https://api.litevps.dev/api/auth/login { "email": "agent@example.com", "password": "..." } ← { "token": "eyJ..." } # 2. Spin up a VM — returns in ~8 seconds POST https://api.litevps.dev/api/vps Authorization: Bearer eyJ... { "name": "task-runner", "plan_id": "plan_1vcpu_512mb" } ← { "id": "d4e1f2a3-...", "state": "running", "customer_ip": "10.0.4.7" } # 3. Run a command inside it — no SSH setup needed POST https://api.litevps.dev/api/vps/d4e1f2a3-.../exec { "command": "python3 solve.py --input data.json" } ← { "stdout": "result: 42\n", "stderr": "", "exit_code": 0, "duration_ms": 1823 } # 4. Destroy it — billing stops, resources released DELETE https://api.litevps.dev/api/vps/d4e1f2a3-... ← 204 No Content
Batch jobs, agent sandboxes, internal APIs, background workers — most workloads don't need a dedicated public IPv4. Outbound internet, proxied inbound access, and private networking cover almost every real use case. We pass the savings directly to you. See pricing →
Billed per minute — running or stopped, a VM accrues charges as long as it exists. Destroy it the moment you're done and billing stops immediately. No hourly rounding, no minimum commitment. Your agent's cost matches its actual lifetime exactly.
One REST call creates a VM, runs your code via /exec, and tears it down. No SSH keys to manage, no polling loops — just a synchronous response with stdout, stderr, and exit_code.
Every VM gets its own private network address and a dedicated KVM hypervisor slice. No shared kernel, no noisy neighbours, no surprises. Outbound internet included.
Predictable JSON in, JSON out. Every endpoint is documented at /docs with request/response schemas and a full general guide. Designed to be consumed by both humans and language models.
Checkpoint a VM mid-task and restore it later. Useful for agents that need to branch execution or retry from a known-good state without re-provisioning from scratch.