Create a Machine
Step-by-step guide to provision a GPU-powered cloud development environment on Outpost.
Launch a machine from the Outpost dashboard or the CLI. Both paths give you the same result: a cloud instance with your chosen GPU, ready for SSH.
Prerequisites
- An Outpost account
- The Outpost CLI installed (
brew install outpostkit) - An SSH key added to your account (see SSH Keys )
Available GPUs
| GPU | VRAM | Best for |
|---|---|---|
| A10G | 24 GB | Inference, fine-tuning small models |
| A100 | 40/80 GB | Large model training, multi-GPU experiments |
| H100 | 80 GB | Cutting-edge training, large batch sizes |
Create from the CLI
Available flags:
| Flag | Description |
|---|---|
--name / -n | Machine name (required) |
--cloud | Cloud provider (e.g. aws, azure) |
--region | Cloud region (e.g. us-east-1) |
--gpus | GPU type and count, e.g. A100 or V100:4 |
--cpus | Number of vCPUs (e.g. 8 or 8+ for minimum) |
--memory | Memory in GB (e.g. 64 or 64+ for minimum) |
--disk-size | Disk size in GB |
--image | Container image |
--config / -c | Config file |
-s, --namespace | Namespace (global flag) |
Tip
Use `outpost dev list` to see all your machines and their current state.
Create from the dashboard
- Navigate to + New > Machine from the dashboard.
- Select a GPU type, cloud provider, and region.
- Name the machine and configure idle timeout, ports, and setup script.
- Click Create Machine. The instance is typically ready in under 60 seconds.
Manage machine lifecycle
| Action | CLI command |
|---|---|
| Start a stopped machine | outpost dev start dev-box |
| Stop a running machine | outpost dev stop dev-box |
| View status | outpost dev status dev-box |
| View logs | outpost dev logs dev-box |
| Delete permanently | outpost dev delete dev-box |
Warning
Stopping a machine preserves its disk. Killing a machine permanently removes all data. Push your work before deleting.
Next steps
- Connect and Develop — SSH setup, IDE integration, and file sync
Previous → Overview
Next Connect & Develop →