Compute model

Capacity

Amics ranks current compatible Spot GPU capacity against the requested GPU family, count, minimum VRAM, location, preference, runtime, and optional maximum hourly price.

Capacity results are observations, not reservations of a particular machine. When a run is accepted, Amics records the exact GPU family, count, minimum VRAM, location, host class, and price ceiling as an immutable acquisition policy. Each initial launch and Spot recovery resolves fresh physical capacity against that policy. A recovery may use a different machine or backing provider, but it never substitutes another GPU family or widens the approved bounds.

Without --location, selection can use capacity anywhere and keeps alternatives available during bounded acquisition retries. Explicit locations are hard constraints and are never widened.

Host class is also a hard constraint. any is the default and includes both datacenter and verified community-operated hosts. --host datacenter restricts selection to datacenter capacity; retries never widen that request to community capacity.

Spot capacity is interruptible. Amics records the run as durable state but does not replay a command whose completion cannot be proved. Managed infrastructure recovery stays within the same run; reconnect to that run instead of submitting a replacement.

Project identity and warm cache

A stable --project value lets compatible commands reuse a machine during an approved warm lease. The remote project directory backs:

• $HOME/.cache
• $UV_CACHE_DIR
• $AMICS_CACHE_DIR
• $AMICS_WORKSPACE

These paths survive while that compute remains warm. They disappear when the machine stops or is preempted.

Compute lifecycle

Data lifecycle

Default runs do not create persistent storage. Put large or reusable datasets in external storage.