Nebius Token Factory fine-tuning vs Unsloth

Nebius Token Factory fine-tuning

Supervised fine-tuning on 49 open base models through OpenAI-style /v1/fine_tuning/jobs calls, with LoRA or full weights and every checkpoint file downloadable. No fine-tuning price was found outside the script-drawn console, and the docs say tuned models deploy only to dedicated endpoints, with custom weights in beta on request.

Unsloth

The Apache-2.0 core runs on customer hardware and keeps model weights there. Users supply and pay for the GPU.

Nebius Token Factory fine-tuning

1. Use the OpenAI client with base_url https://api.tokenfactory.nebius.com/v1/ and NEBIUS_API_KEY. Upload JSONL with purpose=fine-tune, then create the job.
2. Set hyperparameters.lora to true for an adapter. The default is false, which runs full fine-tuning.
3. Poll GET /v1/fine_tuning/jobs/{job_id} no faster than every 15 seconds. There is no idempotency key, so list jobs before recreating one after a timeout.
4. Download every ID in a checkpoint's result_files before relying on hosted copies. The terms allow deletion of tuned models at three days' notice.
5. The spec requires wandb.api_key although the guide omits it, and it also accepts mlflow and hf integrations. Check the price in the console before starting a job.

Unsloth

1. Install with uv pip install unsloth --torch-backend=auto on a CUDA machine; the desktop app is for people
2. Start from the notebook for the model family in unslothai/notebooks; it sets LoRA targets and the chat template
3. Save the LoRA adapter while iterating and merge to 16-bit or GGUF only when you ship
4. If Studio must be reachable by other agents, pass --disable-tools and keep it on 127.0.0.1 behind a tunnel
5. Pin the exact unsloth version; releases land several times a week and don't flag breaking changes