Skip to main content
An instance (or “pod” — we use the terms interchangeably) is a single rental: a machine with one or more GPUs, running the template image you picked, with your SSH key injected at first boot.

Multi-GPU: a whole machine, pooled

Many machines carry more than one GPU. When you rent more than one, you get the whole box — the GPUs are pooled in a single node with their fast interconnect, ready for multi-GPU training. You aren’t handed GPUs spread across separate hosts. A marketplace (seller) listing is always rented whole: every GPU in that machine is yours for the session. How many GPUs a machine offers is shown on its listing.

Service tiers

When a machine offers them, you choose how you rent — a trade-off between price and how long you’re guaranteed to keep the GPU: If your Spot instance is reclaimed, you’re only charged for the time you actually ran, and the unused hold is released. Save your work often on Spot. Which tiers a machine sells is up to its seller, and it is not simply “whatever is priced”. Some machines sell both. Some sell on-demand only. Some are Spot only — the seller has withdrawn on-demand from sale, so the machine is cheap because it can be taken back, and there is no full-price option on it at all. The listing shows what you can actually pick; if a tier is not there, it is not on offer, whatever prices you may see elsewhere.

Lifecycle

Templates

A template is a starting OS image plus pre-installed software. Seven are wired in today:

PyTorch + Jupyter

CUDA + PyTorch 2.x with Jupyter Lab. The default pick.

Ubuntu + CUDA

Bare Ubuntu with CUDA drivers — bring your own stack.

Ollama

Ollama daemon ready to ollama pull.

vLLM

OpenAI-compatible inference server. Pass a model to serve.

Text Generation WebUI

Oobabooga’s text-generation WebUI.

ComfyUI

Node-based Stable Diffusion workflow UI.

Stable Diffusion (A1111)

AUTOMATIC1111 WebUI.
Custom images are on the roadmap.

Per-second metering

Every running instance sends a heartbeat every second. The metering worker:
  1. Reads the instance’s hourly rate
  2. Converts to per-second: rate_per_hour / 3600
  3. Atomically debits that amount from the rental’s wallet ledger entry
  4. If the wallet reaches $0, sends a terminate signal to the machine
The dashboard shows the live accrued charge for each running instance, updated every second.

Stopping

Click Stop in the dashboard. The instance is unreachable within ~5 seconds. We settle the final partial second, so you pay exactly for what you used — not a rounded-up minute.
Stopping is permanent. The instance’s local disk is wiped. Save your work to external storage (S3, your machine via scp, a HuggingFace repo) BEFORE hitting Stop.

Failure & refund

If an instance fails to provision or crashes within 60 seconds of going Running, the wallet is refunded in full automatically. You’ll see the error in the rental detail view.