> 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/compute.md).

# Overview

Managed Compute gives you your own cloud machine for data science—running JupyterLab, code-server, and R Server in your browser, with the GoFigr client **already installed and signed in**. Launch one in a couple of clicks, work exactly as you would locally, and every figure you publish is captured with its code, data, and environment automatically.

No setup, no credentials to copy, nothing to install. Open a notebook and start working.

## Why use it

* **Zero setup.** The machine is pre-authenticated to your GoFigr account and comes with common Python and R packages already installed.
* **Reproducible by default.** Because the GoFigr client is built in, figures publish with full provenance from the moment you start.
* **Right-sized to the job.** Pick a small machine for light notebooks or a large one for memory-hungry workloads, and change it later.
* **Your work persists.** Files, notebooks, and packages you install live on a data volume that survives stop/start.
* **Costs stay in check.** Instances auto-stop when idle, and you only pay for compute while a machine is running.

## What you get

Every instance runs three editors against the same files—use whichever you prefer:

| Editor          | Best for                                           |
| --------------- | -------------------------------------------------- |
| **JupyterLab**  | Interactive Python notebooks                       |
| **code-server** | Scripts, multi-file projects, the GoFigr extension |
| **R Server**    | R notebooks, R Markdown, and Quarto                |

## Key concepts

* **Instance** — one cloud machine. You can have more than one.
* **Machine type (tier)** — how much CPU and memory the instance has. See [Choosing a machine type](/managed-compute/tiers.md).
* **Data volume** — your persistent home directory (`/home/gofigr/notebooks`). Files, installed packages, and data here survive stop/start; they're removed only when you delete the instance.
* **Lifecycle** — an instance is **Running** (you can connect and it bills for compute), **Stopped** (parked—no compute charges, files preserved), or somewhere in between. See [Lifecycle & persistence](/managed-compute/lifecycle.md).
* **Idle auto-stop** — instances stop themselves after a period of inactivity so you don't pay for a machine you forgot about.

## Start here

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Launch your first instance</strong></td><td>From launch to your first published figure in a few minutes</td><td><a href="/pages/Udm1YQfq3n9wSLEe6mJy">/pages/Udm1YQfq3n9wSLEe6mJy</a></td></tr><tr><td><strong>Lifecycle &#x26; persistence</strong></td><td>Running vs. stopped, what persists, and idle auto-stop</td><td><a href="/pages/I7y2OYGzCKnvGdDoYL10">/pages/I7y2OYGzCKnvGdDoYL10</a></td></tr><tr><td><strong>Compute &#x26; storage charges</strong></td><td>How compute and storage are billed</td><td><a href="/pages/3SUuNQhRYMt39Q5VwM2F">/pages/3SUuNQhRYMt39Q5VwM2F</a></td></tr></tbody></table>