Launching a VM requires three things: a hardware profile, a number of GPUs, and an SSH public key. The platform provisions the VM, configures it to accept your key, and returns the IP once it’s ready.Documentation Index
Fetch the complete documentation index at: https://docs.lyceum.technology/llms.txt
Use this file to discover all available pages before exploring further.
SSH keys
Every VM is bootstrapped with one or more SSH public keys you provide. The corresponding private key stays on your machine and never touches Lyceum Cloud — that’s the whole point of the asymmetric scheme. If you don’t have a key, generate one:~/.ssh/id_ed25519.pub (the public half) when launching.
On-demand vs reserved capacity
The platform supports launching VMs on demand (billed hourly, terminate any time) or under a reserved-capacity contract (1, 3, 6, or 12 months) at a discounted rate. For reserved capacity, contact the team via the dashboard’s quote flow or info@lyceum.technology — there’s no self-service contract path.Checking availability
Hardware availability varies by region and demand. Before launching, check whether the profile you want is available:Launching
- CLI
- REST API
| Flag | Default | Description |
|---|---|---|
-h, --hardware-profile | a100 | Hardware profile (cpu, a100, h100, …) |
-k, --key | required | SSH public key (the contents, not a path) |
-g, --gpu-count | 1 | Number of GPUs |
-a, --async | off | Return immediately without waiting for the VM to be ready |
ready and prints the IP. Use --async to fire-and-forget; you can poll status afterwards with lyceum vm status.After launching
Once the VM isready:
scp, run jobs, and lyceum vm terminate <vm_id> when you’re done.
