# Overview

> Start from maintained environments, or save your own setup so you and your team deploy it the same way every time.

A template is a container image with its settings, ready to deploy as an instance or a Run Job. This page explains official templates, your own templates, and what happens when you deploy from one.

## Get started

<card-group>
<card icon="i-lucide-box" title="Manage templates" to="/templates/manage">

Create, share, deploy and edit templates.

</card>

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

Run your own image from any registry.

</card>
</card-group>

## Concepts

### Official templates

Official templates are maintained environments, such as PyTorch, vLLM and SGLang, with SSH and JupyterLab included. Each lists its versions, newest first; a new deploy uses the newest unless you choose another. Each official template runs on the GPU vendor its image is built for: ROCm images on AMD GPUs, CUDA images on NVIDIA GPUs.

### Your templates

A template you create saves an image and every launch setting: compute, container disk, network volumes, start command, environment variables, secrets, public ports and the tmux setting. It's **Private** to you, or shared with your **Organization** so every member can deploy it, secrets included.

### Deploying from a template

When you deploy from a template, anything you change on the deploy page overrides the template's value for that deploy. Environment variables and secrets merge by name. Instances and Run Jobs keep their settings when the template is later edited or deleted.

## Next steps

<card-group>
<card icon="i-lucide-rocket" title="Deploy an instance" to="/instances/deploy">

Deploy from a template.

</card>

<card icon="i-lucide-terminal" title="templates command" to="/cli/templates">

Manage templates from the CLI.

</card>
</card-group>
