Fireworks AI Fine-tuning vs Nebius Token Factory fine-tuning

Fireworks AI Fine-tuning

SFT, DPO, ORPO and RFT as managed jobs, plus a serverless Training API that is generally available. Tuned LoRAs only deploy to on-demand GPUs at $8 an hour and up, never to serverless.

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.

Fireworks AI Fine-tuning

1. Add a payment method before the first job; without one the account has 0 training GPUs and 10 requests a minute
2. Check firectl model get -a fireworks <MODEL-ID> for Tunable: true before uploading a dataset
3. Pass your own supervisedFineTuningJobId on create, so after a timeout you can GET the job by that name instead of guessing whether it started
4. Deploy the LoRA to an on-demand deployment with a BF16 shape if several adapters will share it, and delete the deployment when evaluation ends
5. Download with firectl model download and keep the exact base model; the adapter alone won't run

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.