Kovara Run launches GPU clusters, managed batch jobs and autoscaled service endpoints from the Kovara console, on your own SkyPilot API server. Your server holds your cloud, Kubernetes and Slurm credentials and does the provisioning; Kovara chooses where to try first from its market data, sends the request, and shows what is running. Kovara never receives your cloud keys and bills nothing for compute.
Open it at Deployments → Kovara Run (/deployments/run, signed in).
What you can run
| Mode | What SkyPilot does | Good for |
|---|---|---|
| GPU cluster | sky launch: one or more nodes you can SSH into. Autostop (default 30 idle minutes) tears the cluster down so nothing runs by accident. | Development, notebooks, interactive debugging |
| Managed job | sky jobs launch: runs the task to completion on a fresh cluster, recovers from spot preemption and failures, then cleans up. | Training, fine-tuning, batch inference, sweeps |
| Service endpoint | sky serve up: replicas behind one load-balanced address, with readiness checks and request-rate autoscaling. | Inference APIs (vLLM, SGLang, TGI), any HTTP service |
Every launch can mount buckets at a path (/data = s3://bucket/prefix MOUNT), with MOUNT (streamed), COPY (copied at start) or MOUNT_CACHED (streamed with a local cache, good for checkpoints). Supported stores are the ones SkyPilot supports: s3://, gs://, r2://, az:// (Azure Blob), oci://, cos:// (IBM) and nebius://.
Because the work runs on your API server, Kovara Run reaches whatever that server can reach: Lambda, Verda and the other clouds SkyPilot supports, your own Kubernetes clusters (managed Kubernetes or on-premises), and Slurm clusters SkyPilot is configured for.
How the order is decided
Kovara writes the same task the SkyPilot task builder writes: an ordered list of exact instance types. Places whose provider reported capacity in the last 15 minutes come first, then the rest by Kovara's listed price per GPU-hour. SkyPilot tries them top-down and stops at the first that launches. Spot launches are ordered by price only, because Kovara does not read spot capacity. See SkyPilot tasks for the full rules.
Connect your server
- Run a SkyPilot API server. The quickest production setup is SkyPilot's Helm chart on any Kubernetes cluster; see SkyPilot's deployment guide, which also covers running it on a single VM. Give it a public HTTPS address: Kovara calls only
https://addresses on the public internet and never follows redirects. - Add your clouds to it, as SkyPilot's docs describe, and check with
sky checkagainst that server. - Create a service account in the SkyPilot dashboard (Users → Service accounts). Copy the token; it starts with
sky_. Give the account only the workspace and role it needs. - In Kovara, open Deployments → Kovara Run, enter the server address and the token, and choose Connect and check.
Each person can connect up to five servers.
Security
- The token is encrypted. It is stored in Supabase Vault (encrypted at rest, with the key held outside the database). The database row keeps only the Vault reference and the last four characters. Only a server-side function, callable by Kovara's backend and only for the connection's owner, can read it, and only while you act on the page.
- It never reaches the browser. No page or API returns it. Error messages have tokens removed.
- Calls go only to public HTTPS addresses. Every request resolves the host name and refuses private, loopback, link-local and cloud-metadata addresses, the same guard Kovara uses for webhooks. Redirects are not followed.
- No secrets in task files. The launch form has no secret fields. Keep API keys and tokens on your server (SkyPilot
secretsor your image). Environment variables you type are written into the task file and kept in your activity log. - Removing a server deletes the token from Vault immediately. Revoke the service account on your server as well.
- Nothing is shared. Connections and the activity log belong to the person who created them; row-level security allows no direct reads, and every function checks the signed-in user.
Activity
Every request Kovara sends is logged with SkyPilot's request id, the status your server reports (queued, in progress, done, failed, cancelled) and, for launches, the exact task file that was sent. Status is refreshed each time you open the page; a failed request shows your server's error message.
Controls
From Running on… you can stop and restart clusters, tear them down, cancel managed jobs and tear down services. Destructive controls ask for a second click. Kovara never stops or deletes anything on its own.
Limits
- Kovara Run does not upload a working directory. Put code in a git repository and clone it in Setup, bake it into an image, or mount it from a bucket.
- The GPU list is the one the SkyPilot task builder offers: configurations whose exact instance type Kovara recorded from a provider's own API and SkyPilot's catalog lists. For anything else, write the task yourself and launch it with the
skyCLI against the same server. - Status comes from your server when you open the page. Kovara does not poll your server in the background.