Overview

Never synced
My projects—Sign in to load
My trainings—Sign in to load
Running now—
Failed · need attention—

My trainings

All my jobs
Loading…

My projects

All projects
  • Projects will appear after connecting.

Needs attention

  1. Failed runs and their cause will appear here.
DUses Docker on this machine
Advanced
1Choose the model

Pick the size template first. The advisor, batch shape, and generated YAML all follow from this choice.

2Choose the training machine

Pick the exact registered server or temporary cloud GPU first. Advice and capacity then use that machine—not a hidden default.

Choose a registered training server.
Choose the machine before tuning the recipeThe selected hardware will drive capacity and throughput advice.

3 Configure and review training

Model publication branch: projects automatically reserve a new v1, v2, … branch in one shared repository. Existing versions are preserved. Without a project, the target model is published to main. Dataset branches below are selected independently.

Configure a checkpoint bucket in Settings. Only the final FP32 artifact is published to the target model.
0 selected
Synchronize datasets in Settings before creating a training job.

Dataset branches

Select a branch for each dataset. Only repository metadata is consulted here; no examples or dataset files are downloaded. The job keeps the exact selected commit even if the branch changes later.

Weights & Biases tracking is always enabled using the cluster settings.
Advanced settings
Show generated YAML
Deployment policy
Choose a provider first.
0 GPUsAvailability reflects the selected tier, GPU count, and pricing mode.
Load a provider catalog to browse GPUs.
Checkpoint and history are preserved. Saving immediately retries with the updated contract.