# Concepts

> The building blocks of Featherless GPU Cloud and how they fit together.

This page defines the terms you'll meet in the console, the CLI and these docs, and helps you choose between an instance and a Run Job.

## Terms

<card-group>
<card icon="i-lucide-server" title="Instance" to="/instances">

A container on dedicated GPU or CPU compute. Use it for development, notebooks and services.

</card>

<card icon="i-lucide-square-terminal" title="Run Job" to="/run-jobs">

A command that runs on temporary compute and ends when the command exits. You pay only while it runs. Use it for training, batch processing and evaluations.

</card>

<card icon="i-lucide-box" title="Template" to="/templates">

A container image with its settings, ready to deploy. Use an official template such as PyTorch or vLLM, or save your own and share it with your organization.

</card>

<card icon="i-lucide-database" title="Network volume" to="/storage/network-volumes">

Persistent storage you mount at a path you choose. It keeps its data until you delete it, and several instances and Run Jobs can mount it at once.

</card>

<card icon="i-lucide-hard-drive" title="Container disk" to="/storage">

Temporary storage for the container's files. It's erased when the instance stops or restarts.

</card>

<card icon="i-lucide-container" title="Custom image" to="/templates/custom-images">

Any Linux container image you can pull, used instead of a template. Private images need registry credentials.

</card>

<card icon="i-lucide-globe" title="Public port" to="/instances/ports">

A port in your container served at its own HTTPS address, so you can reach a web app or API without SSH.

</card>

<card icon="i-lucide-key-round" title="API key" to="/get-started/credentials#create-an-api-key">

A secret that lets the CLI or your scripts act as you. Its scopes limit what it can do.

</card>

<card icon="i-lucide-users" title="Organization" to="/account/organizations">

The account that owns your instances, Run Jobs, volumes, templates and credit. Every member works with the same resources.

</card>
</card-group>

## Instance or Run Job?

<table>
<thead>
  <tr>
    <th>
      You want to
    </th>
    
    <th>
      Use
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Work interactively in a terminal, notebook or IDE
    </td>
    
    <td>
      An instance
    </td>
  </tr>
  
  <tr>
    <td>
      Serve a model or web app continuously
    </td>
    
    <td>
      An instance with a public port
    </td>
  </tr>
  
  <tr>
    <td>
      Run a script once and collect its output
    </td>
    
    <td>
      A Run Job
    </td>
  </tr>
  
  <tr>
    <td>
      Run many independent tasks
    </td>
    
    <td>
      Run Jobs, one per task
    </td>
  </tr>
  
  <tr>
    <td>
      Pay only while your command runs
    </td>
    
    <td>
      A Run Job
    </td>
  </tr>
</tbody>
</table>

## Next steps

<card-group>
<card icon="i-lucide-rocket" title="Quickstart" to="/get-started/quickstart">

Deploy your first instance.

</card>

<card icon="i-lucide-square-terminal" title="Submit a Run Job" to="/run-jobs/submit">

Run a command on temporary compute.

</card>
</card-group>
