# Marketplace

C3 aggregates GPU capacity from multiple data centers. When you submit a job, we find available compute at competitive rates—no need to manage cloud accounts or hunt for capacity yourself.

## Available GPUs[​](#available-gpus "Direct link to Available GPUs")

| GPU       | VRAM | Best for                                                                     |
| --------- | ---- | ---------------------------------------------------------------------------- |
| L40       | 48GB | Recommended for new jobs, training, inference, general-purpose GPU workloads |
| H100 80GB | 80GB | Temporarily unavailable for non-admin job submissions                        |
| A100 80GB | 80GB | Temporarily unavailable for non-admin job submissions                        |
| RTX A4000 | 16GB | Light training, testing, development                                         |

Set `gpu: l40` in your `.c3` config for new jobs. Run `c3 list` to see current pricing, availability, and provider/region offerings.

## Pricing[​](#pricing "Direct link to Pricing")

### Compute[​](#compute "Direct link to Compute")

You're billed per second of actual compute time—not for time spent queuing or provisioning. New accounts receive £10 in free credits. Check your balance:

```
c3 balance
```

### Plans[​](#plans "Direct link to Plans")

Plans are about **iteration speed**, not storage. The warm pool plus smart caching turns 5-45 minute cold starts into \~20-second job starts. Every new account starts with a **14-day Pro trial** — warm-pool access, smart caching, 100 GB of storage, and £10 in compute credits.

| Plan | Price     | Warm pool          | Smart caching | Concurrent jobs | Walltime  | Storage |
| ---- | --------- | ------------------ | ------------- | --------------- | --------- | ------- |
| Free | £0/month  | — (cold pool only) | —             | 1               | 6 h cap   | 10 GB   |
| Pro  | £25/month | L40 (\~20s start)  | yes           | 5               | 24 h      | 100 GB  |
| Max  | £45/month | L40 (\~20s start)  | yes           | 20              | unlimited | 1 TB    |

Manage your plan anytime:

```
c3 upgrade              # Interactive picker
c3 upgrade pro          # Subscribe to or switch to Pro
c3 upgrade max          # Subscribe to or switch to Max
c3 upgrade free         # Cancel subscription (takes effect at period end)
c3 upgrade free --yes   # Non-interactive cancel (for scripts)
c3 upgrade free -y      # Short form of --yes
```

Upgrades (e.g. Pro → Max) are immediate: you get the new features right away and your card is charged the prorated difference for the remainder of the current billing period. Downgrades (e.g. Max → Pro) and cancellations take effect at the **end of your current billing period** — you keep the features you paid for until then. To reverse a pending downgrade or cancellation before it takes effect, run `c3 upgrade <current-tier>`.

When your trial ends, you're moved to the Free plan. Existing data is preserved — you just can't upload more until you upgrade or free up space.

## How jobs run[​](#how-jobs-run "Direct link to How jobs run")

1. **PENDING** — Job submitted, waiting for a GPU
2. **SCHEDULING** — Assigning to a machine
3. **RUNNING** — Your script is executing
4. **COMPLETED** — Done. Download results with `c3 pull`
5. **SYNCED** — Results downloaded locally

Failed or cancelled jobs show as **FAILED**, **CANCELED**, or **TIMED\_OUT**.

## Warm pool[​](#warm-pool "Direct link to Warm pool")

C3 maintains a pool of pre-provisioned GPUs. Jobs hitting the warm pool start running in **\~20 seconds** instead of waiting 5-45 minutes for cold provisioning.

| Path           | Allocation   | Total Startup |
| -------------- | ------------ | ------------- |
| **Warm pool**  | seconds      | \~20 seconds  |
| Cold provision | 5-45 minutes | 5-45 minutes  |

This enables rapid iteration: edit locally, submit, see results quickly, repeat.

**[Learn more about the warm pool →](https://docs.cthree.cloud/warm-pool.md)**

## Providers[​](#providers "Direct link to Providers")

By default, `c3 deploy` asks the C3 marketplace to choose a route before job submission. The control plane then makes the authoritative selection from enabled provider/GPU offerings using stock, warm-pool capacity, cache affinity, price, and provider spend guard state.

Use `provider:` in `.c3`, `c3 deploy -p <provider>`, or `C3_PROVIDER` only when you need to pin a job to a specific provider such as `nextgen` or `nebius`. Provider availability is still gated by operator configuration, live inventory cleanup, spend controls, and stock, so a pinned provider can be rejected while auto-routing succeeds on another provider.

`c3 list` is the source of truth for provider ids exposed to users. It shows the profile-level view plus provider/region offerings so the CLI, `.c3`, and route-preview paths agree on what can be selected.

Operators can inspect provider readiness with:

```
c3 admin balance <provider>
c3 admin provider-status <provider>
```