Closed-API fine-tuning in 2025-2026: options and trade-offs vs open-weight FT

There are two broad ways to fine-tune a model in 2026, and the split is about who holds the weights. **Closed-API fine-tuning** means a vendor trains and hosts the model for you. OpenAI lets you fine-tune gpt-4o-mini and gpt-4o through its API. Anthropic offers Claude fine-tuning through AWS Bedrock. Google offers Gemini tuning through Vertex AI. You upload data, the vendor trains, and you call the result through the same API. You never download the weights. Open-weight fine-tuning means you take a model whose weights are public (Llama, Mistral, Qwen) and train it yourself, usually with LoRA or QLoRA. The trained model is yours to serve anywhere, including on your own servers. The trade-off is ownership versus convenience. Closed APIs are simple: no GPUs, no training code, strong base quality, safety built in. But you rent inference forever and your data leaves your walls. Open weights give you portability and cheap inference at scale, but you run the training and serving infrastructure yourself. A useful rule: low volume and quick prototypes favor the closed API; high volume, on-prem needs, or strict data control favor open weights.

The landscape splits by who controls the weights. **Closed-API fine-tuning** is vendor-hosted. OpenAI tunes gpt-4o-mini and gpt-4o, with SFT and preference (DPO-style) tuning. Anthropic tunes Claude through AWS Bedrock. Google tunes Gemini through Vertex AI. Cohere, Mistral, and AI21 offer hosted tuning for their own models. In every case you upload data, train via the API, and serve via the same API. You never receive weights. Open-weight fine-tuning means LoRA or QLoRA on public models like Llama, Mistral, or Qwen. The artifact is yours to serve anywhere. The trade-offs are structural. Closed APIs give zero infrastructure burden, frontier baseline quality, and built-in safety. The costs are no portability, data residency limits, capped hyperparameter control, and per-token inference that never ends. Open weights give full ownership, cheap inference at scale, total control, and on-prem options. The price is that you carry training and serving infrastructure and implement safety yourself. The decision turns on three axes. Pick closed APIs at low volume, for fast prototyping, or when you already trust the vendor's compliance. Pick open weights at high volume, when you need on-prem or adapter swapping, or when research-grade control matters.