docs/en/platform/integrations/on-premise.md
On Premise lets your Enterprise workspace use datasets and compute on a Linux, macOS, or Windows computer. Source images and videos remain on your computer. Training behaves like any other remote training location: metrics stream to Platform and completed model weights upload for download, prediction, export, and deployment.
Setup takes one command. Platform detects your operating system, fills in sensible folder locations, installs Docker if needed, and shows live connection progress.
flowchart LR
A[Your browser] <-->|Interface, labels, and progress| B[Ultralytics Platform]
A <-->|Dataset previews| C[Your On Premise computer]
B <-->|Jobs, metrics, and model weights| C
C --- D[(Dataset folder)]
C --- E[(Models folder)]
| Data | Your On Premise computer | Platform and cloud services |
|---|---|---|
| Source and derived dataset pixels | Stay local for ingest, preview, and training | Never stored, logged, or processed |
| Classes, labels, and annotations | Source labels are read during ingest | Stored as the canonical dataset metadata so you can annotate in Platform |
| Training models | The run, best checkpoint, and other training artifacts are written to your models folder | The best checkpoint uploads for download, prediction, export, and deployment; other artifacts stay on your computer |
Model weights, labels, annotations, and metrics can encode information learned from your images. Only the dataset pixels have the strict local-only boundary. Cloud prediction processes only images you separately submit to that cloud workflow; the worker never forwards an image from your mounted dataset.
Choose a computer that can access your datasets and remain powered on while Platform is using them.
| Minimum | Recommended | |
|---|---|---|
| Operating system | 64-bit Linux, Mac with an M-series chip, or 64-bit Windows with WSL 2 | Current OS and Docker releases |
| CPU | 4 cores | 8 or more cores for training |
| Memory | 8 GB RAM | 16 GB or more |
| Storage | 20 GB plus space for datasets and models | SSD with twice your working dataset size free |
| Network | Outbound HTTPS | Stable broadband for the first Docker download |
A GPU is optional. Every computer can ingest datasets and train models on its CPU. A compatible NVIDIA GPU can accelerate larger training jobs.
!!! note "Corporate networks"
If your company restricts outbound traffic, allow HTTPS access to Ultralytics Platform, Docker registries, and Python package downloads before setup.
Settings > Integrations and select Connect on the On Premise card.Platform fills in the folders and one-time connection token before you copy the command. The generated command follows the format below:
=== "Linux"
Open **Terminal** and paste:
```bash
curl -fsSL 'https://platform.ultralytics.com/api/workers/install?os=linux' \
| sudo sh -s -- \
"/datasets" \
"/models" \
"YOUR_CONNECTION_TOKEN"
```
=== "macOS"
Open **Terminal** and paste:
```bash
curl -fsSL 'https://platform.ultralytics.com/api/workers/install?os=macos' \
| sh -s -- \
"$HOME/Ultralytics/datasets" \
"$HOME/Ultralytics/models" \
"YOUR_CONNECTION_TOKEN"
```
=== "Windows"
Open **PowerShell** and paste:
```powershell
$installer = Invoke-RestMethod `
'https://platform.ultralytics.com/api/workers/install?os=windows'
& ([scriptblock]::Create($installer)) `
-DataPath "$HOME\Ultralytics\datasets" `
-ModelsPath "$HOME\Ultralytics\models" `
-ConnectionToken "YOUR_CONNECTION_TOKEN"
```
!!! warning "Copy your command from Platform"
Platform includes the connection token automatically. It proves this computer is allowed to connect to your workspace, expires after 10 minutes, and works once. You never enter it separately. Do not share the generated command while it is valid.
The defaults work without editing:
| Linux | macOS and Windows | |
|---|---|---|
| Dataset folder | /datasets | ~/Ultralytics/datasets |
| Models folder | /models | ~/Ultralytics/models |
The setup command creates these folders, installs and starts Docker when needed, and configures the connection to restart with your computer. Your operating system may ask you to approve installation or restart before setup can finish.
The installer runs one container and selects the official Ultralytics base image for the host:
| Host | Base image |
|---|---|
| Apple Silicon or ARM64 Linux | ultralytics/ultralytics:8.4.100-arm64 |
| x86-64 CPU | ultralytics/ultralytics:8.4.100-cpu |
| x86-64 with a supported NVIDIA runtime | ultralytics/ultralytics:8.4.100 |
The installer pins the image matching Platform's Ultralytics version. The worker adds its connectivity dependencies without reinstalling Ultralytics. It detects CUDA at runtime, so an NVIDIA host still runs one container rather than separate CPU and GPU workers. These lightweight images support local ingest and training; Platform's existing cloud services handle model prediction and export after the best checkpoint uploads.
!!! info "Optional GPU acceleration"
CPU setup requires nothing beyond the guided installation. For NVIDIA GPU acceleration, install current NVIDIA drivers and enable Docker GPU support. Platform detects the GPU automatically.
Platform indexes the dataset locally and opens it in the same gallery used for uploaded and cloud-storage datasets. You can preview images, inspect labels, filter the dataset, and annotate without uploading the pixels.
On Premise supports the same ingest formats and computer-vision tasks as uploaded data:
Platform automatically recognizes common dataset layouts, classes, labels, and train/validation/test splits. Platform treats source files as read-only and never resizes, re-encodes, edits, or deletes them.
When you open an image, your browser loads it directly from the connected computer. There is no certificate, hostname, VPN, or preview configuration.
Annotations and dataset organization are saved in your Platform workspace, but edits in Platform never change your source image or label files.
Start training through the normal Platform training dialog:
Platform runs the job on the connected computer. It uses an available NVIDIA GPU or falls back to CPU automatically, so a Mac can train a small model such as YOLO26n on COCO8 without dedicated GPU hardware.
Training files are written to the configured models folder while the run is active. The Ultralytics package uses the same remote-training callbacks as any customer-managed machine: progress and metrics stream to Platform, the best checkpoint uploads to Platform storage, and the completed model works with the existing download, prediction, export, and deployment paths. Other training artifacts remain in your models folder. On Premise training does not use Platform compute credits, and Platform never sends the training job to cloud compute.
Open Settings > Integrations to see whether the computer and its CPU or GPU are available. You can reconnect to refresh its access or disconnect it when it is no longer needed.
Disconnecting prevents new jobs and previews but does not delete datasets or source files from the computer. Uploaded models remain available in Platform.
Settings > Integrations, and create a new install command.Also see Datasets, Annotation, and Training.