> For the complete documentation index, see [llms.txt](https://docs.gofigr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gofigr.io/managed-compute/tiers.md).

# Choosing a Machine Type

When you launch an instance you pick a **tier**—the machine type that sets how much CPU and memory it has. Start small; you can change the tier later if a workload needs more headroom.

## Available tiers

| Tier                     | vCPU | RAM   | Best for                                                  |
| ------------------------ | ---- | ----- | --------------------------------------------------------- |
| **Micro**                | 2    | 2 GB  | Quick experiments and light, short-lived notebooks.       |
| **Standard** *(default)* | 2    | 4 GB  | General-purpose notebooks and light analysis.             |
| **Pro**                  | 4    | 16 GB | Larger datasets and memory-hungry workloads.              |
| **Performance**          | 8    | 32 GB | Heavier compute and mid-size datasets on dedicated cores. |
| **Performance XL**       | 16   | 64 GB | Large, parallel, memory-hungry workloads.                 |

**Standard** is selected by default and handles most notebook work. Reach for a bigger tier when you hit memory limits or want more cores for parallel jobs. The tiers available to you depend on your plan.

## Changing the tier

To move an instance to a different machine type, **Stop** it, then choose **Change type…** from its menu and pick a new tier. Your data volume and files are unaffected—only the CPU and memory change.

## What it costs

Larger tiers cost more per minute of runtime. Rather than memorize numbers, check the live figures in the app:

* The **Estimated cost** table in the launch dialog shows the hourly rate plus typical monthly estimates (24/7 and 8 h/day) for the tier you've selected.
* The [**Compute Usage**](/billing-and-plans/compute-usage.md) card shows what you've actually used this period.

Compute bills per minute **only while an instance is Running**, so a bigger machine you stop when idle can still be economical. See [Compute & storage charges](/billing-and-plans/compute-usage.md) for the full model.