How Pricing and Billing Work on Vast.ai

Vast.ai prices GPU rentals by real-time supply and demand across its GPU pool, and bills by the second. You add credit (starting at as little as $5), get an API key, and launch instances without a contract or sales call. That model fits short, bursty, or experimental workloads where you want to start and stop cheaply — and it means the price you see is a live market rate, not a fixed list price.

Where the price comes from

Vast.ai states that prices are "set by supply and demand across 20,000+ GPUs" and are "transparent" and "programmatically queryable." In practice that means:

• No single fixed rate card. Different hosts offering the same GPU model can list different prices at the same moment.
• Prices move. Because they track supply and demand, the cheapest option for a given GPU type can change between sessions.
• You can query them. Pricing is exposed through the same API used to deploy, so you can filter and compare before committing.

The site's own framing is "Compare. Launch. Exit. Repeat." — the pricing design assumes you shop around rather than lock into one machine.

Billing is per-second

Vast.ai bills per second. Combined with the marketplace pricing above, this has a few practical consequences:

• You pay for the compute time you actually use, so a job that runs for minutes costs proportionally less than one that runs for hours.
• Stopping an instance stops the meter, which makes iterative or interruptible work cheaper than on hourly-billed platforms.
• Because rates vary by host, the same per-second billing can produce different totals depending on which instance you pick.

The site does not publish a per-second rate table in the material available; the rate is whatever the selected GPU is listed at when you deploy.

Getting started costs $5

The documented entry point is small:

1. Add credit and get your API key. Vast.ai says you can "start with as little as $5," with "no contracts, no sales calls." The API key comes from the console.
2. Search GPUs. Filter by model, VRAM, price, and availability — through the console or the API.
3. Deploy. Launch instances in seconds and scale up or down programmatically.

The advertised flow is "from sign-up to running GPU workloads in under five minutes."

What "no contract" means for cost control

There is no contract and no sales call in the documented sign-up path, and instances can be exited and relaunched. For budgeting, that means:

• Your spend is bounded by the credit you add, not by a committed term.
• You can exit an instance and pick a cheaper host later, which is the intended loop ("Compare. Launch. Exit. Repeat.").
• Cost predictability comes from your own usage discipline (stopping instances) rather than from a fixed monthly fee.

Choosing between the three deployment types on cost grounds

Vast.ai offers three ways to deploy, and the billing logic differs by type:

If your workload is intermittent or request-driven, Serverless's scale-to-zero is the model designed to avoid paying for idle time. If you need full control of the machine, GPU Cloud's per-second on-demand billing is the fit. Clusters target sustained large-scale training, where you're paying for dedicated multi-node capacity rather than opportunistic spot-style pricing.

Practical checks before you commit

• Query before deploying. Since pricing is programmatically queryable, pull current listings for your target GPU model and VRAM rather than assuming a rate.
• Confirm the host's rate at launch. The marketplace structure means the cheapest listing can change; the rate that applies is the one on the instance you actually start.
• Watch idle time. Per-second billing rewards stopping instances you aren't using — an idle instance still bills.
• Start small. The $5 minimum lets you test the deploy-and-exit loop before scaling up.

For current rates on specific GPU models, use the pricing page or query the API directly, since the numbers are live and change with supply and demand.