As of 2025-2026, what closed API fine-tuning options exist (OpenAI, Anthropic, etc.), and what are the trade offs vs open weight LoRA style FT on Llama / Mistral / Qwen?
Closed APIs (OpenAI, Claude on Bedrock, Gemini on Vertex) offer hosted fine-tuning with no weight access. Open weights give portability and lower cost at scale, but you carry the infra.
Imagine you want a custom chef. The closed-API path is hiring a chef through an agency: they train someone for your tastes, but the chef stays employed by the agency, you pay per meal forever, and you never get to take the chef home. The open-weight path is adopting a trainee cook you own outright: you teach them yourself, you feed and house them (the GPUs), but once trained they cook in your kitchen for the price of groceries, and you can move them anywhere. For a tiny cafe, the agency is easier. For a busy restaurant serving thousands of meals, owning your own cook pays off fast. The big chains often start with the agency, then bring cooking in-house once volume justifies it.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Concept explanation~2 min read
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
By 2026 the fine-tuning decision is no longer just LoRA versus full fine-tune. It is a fork between renting a vendor-hosted tuning service and owning the whole stack on open weights. The two paths produce different artifacts, different cost curves, and different compliance footprints, and a strong answer names all three.
The confusion that trips candidates is the word 'fine-tuning' itself. On a closed API it means you hand the vendor a dataset, they adapt their proprietary model, and they hand you back a model ID, never a weight file. On open weights it means you run the gradient updates yourself and walk away with an adapter you can serve anywhere. Same word, completely different ownership.
The interview value is in the trade-off reasoning, not the provider list. Anyone can recite that OpenAI, Anthropic, and Google offer tuning. The senior signal is knowing why a regulated bank cannot use the closed path, why a high-volume consumer app eventually migrates off it, and roughly where the break-even volume sits. This deep dive walks the provider landscape, the structural trade-offs, the cost math, and the decision framework that ties them together.
The closed-API fine-tuning landscape in 2026
Every major frontier vendor now exposes hosted fine-tuning, and the shape is nearly identical across them. You upload a dataset in the vendor's required format, you launch a training job through the API, and you serve the result through the same API by referencing a new model ID.
The concrete options. OpenAI fine-tunes gpt-4o-mini and gpt-4o, supporting supervised fine-tuning and DPO-style preference tuning, so you can shape both task behavior and ranked preferences. Anthropic offers Claude fine-tuning through AWS Bedrock, rolled out in 2025 for select Claude models, where the dataset lives in Bedrock and the tuned model is callable through the standard Anthropic-on-Bedrock API. Google offers Gemini tuning through Vertex AI for Flash and Pro variants, using an adapter-style approach under the hood. Cohere, Mistral La Plateforme, and AI21 round out the field with hosted tuning of their own proprietary models.
The method menu is narrower than on open weights. You typically choose between supervised fine-tuning and a preference method, and the vendor fixes most hyperparameters. You may get an epoch count or a learning-rate multiplier, but not rank, target modules, or optimizer internals. The vendor also gates dataset size, format, and content through its own safety filters, so some training data is silently rejected.
The defining property is in the negative space. In none of these cases do you receive the weights. You receive an endpoint. That single fact drives every downside that follows: lock-in, residency, capped control, and a marginal cost that never decays.
Situations where this technique stops working.
2–4 min · Everything important, quickly.
| Concern | Closed-API FT | Open-weight FT |
|---|---|---|
| Weight access | None, hosted-only inference | Full, download and serve anywhere |
| Infra burden | Zero, vendor runs everything | You run training and serving |
| Marginal cost at scale | Per-token API price forever | Your own GPU amortization, much lower |
| Data residency | Data goes to vendor stack | Stays in your perimeter, on-prem possible |
| Safety guardrails | Built in by vendor | You implement them |
| Hyperparameter control | Limited presets | Full: rank, learning rate, target modules |
Real products, models, and research that use this idea.
- OpenAI's fine-tuning API tunes GPT-5.5 with SFT plus preference tuning, hosted-only, served through the same Chat Completions endpoint.
- Anthropic offers Claude fine-tuning through AWS Bedrock, where you stage the dataset in Bedrock and call the tuned model via the standard Anthropic-on-Bedrock API.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you estimate the break-even volume between OpenAI hosted tuning and self-hosted Llama 4?
Compare hosted per-token price times monthly tokens against amortized GPU rental plus engineer time for training and serving. Find the monthly volume where the lines cross, then add a margin for operational risk.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Red flags & common mistakes
The phrases that signal junior thinking. Click to expand.
Assuming closed-API fine-tuning gives you a model you own. You never receive weights, you rent inference forever, and portability is zero. That changes the cost and compliance story completely.
60 second bullets to scan on the way to the call.
Which providers offer hosted fine-tuning and on which models
Why closed-API tuning never gives you the weights
Primary sources. Browse if you want the original framing.
Same topic, related formats. Practice these next.