Head to head · Fine-tuning · October 2026 research run
Together AI Fine-tuning vs Unsloth
Unsloth scores 57.2 (C) on agent readiness against Together AI Fine-tuning's 55 (C), and leads in 3 of 7 scored categories. Together AI Fine-tuning leads on reliability, schema & documentation, security & auth and transparency & trust. Both do fine-tuning.
Best fine-tuning services for AI models · All 36 fine-tuning comparisons
Which one, for what
Best for Teams that want to tune a large open model, possibly with full fine-tuning, and take the weights away.
Ahead on
- Reliability, 55 against 48
- Schema & documentation, 83 against 71
- Security & auth, 57 against 44
- Transparency & trust, 68 against 38
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Fine-tuned models don't run serverless; dedicated endpoints start at $5.49 an hour
Unsloth C
Best for One person or a small team tuning an open model on their own GPU and keeping the weights.
Ahead on
- Agent ergonomics, 53 against 42
- Payments & pricing, 90 against 30
Also in its favour
- No key needed to call it
- Open source
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Not a hosted service; you bring and pay for the GPU
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Unsloth +60
Together AI Fine-tuning 30
No machine payment protocol (0). Per-1M-token prices for every tunable model, with minimum charges, published without a login and unchanged on 4 November (20). The billing docs say Together AI has no free trial at present, and access needs a minimum $15 credit purchase for an organisation's first purchase, $5 after (0). Sign-up and the first purchase are browser steps (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Unsloth 90
A free, self-hosted package with nothing to buy on the site or in the docs, so 20 + 20 + 20 for pricing, free use and no sign-up. No payment protocol (0). 0 + 20 + 20 + 20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Transparency & trust Together AI Fine-tuning +30
Together AI Fine-tuning 68
Closed service under terms (19 May 2026) that name Together Computer, Inc., a Delaware corporation; SDKs are Apache-2.0. The checklist gives 15 to a closed service with clear terms, and open SDKs on a closed API don't raise it, as together-inference's 1 November check and anthropic-api read the same evidence (15). The privacy policy (2025-12-17) says no training on customer data without opt-in and the docs agree, but the docs also say prompts and responses are stored by default unless storage or ZDR is turned off, and no retention period for training files or tuned weights found (18). The deprecations page keeps a dated history of models removed from fine-tuning, and its lifecycle policy states notice periods for serverless and dedicated endpoints but none for fine-tuning. Dated notices with no period for the product give 15 in this run (15). EU-region and VPC options for enterprises are mentioned; no subprocessor list found (5). 15 + 18 + 15 + 5 = 53.
Unsloth 38
Apache-2.0 for the core and AGPL-3.0 for Studio, both OSI licences, and the README says which parts are which (30). Training data stays on your machine, but no privacy page was found (404 on 1 October) and the terms page answered a bot check on 4 November (10). No deprecation policy or dated notices found (0). get_statistics runs on every model load unless UNSLOTH_DISABLE_STATISTICS is set. It downloads public Hugging Face repositories named for the environment (Colab, Kaggle, AWS and the like), a VRAM bucket and the GPU count, as a download counter. The opt-out is named only in source comments, and the desktop page says 'No telemetry' (0 of 20). 30 + 10 + 0 + 0 = 40.
Security & auth Together AI Fine-tuning +13
Together AI Fine-tuning 57
Project-scoped API keys, revocable within about five minutes, with an optional expiry and written guidance to rotate keys regularly. Within its project a key has full access and can spend the credit balance. Read the way together-inference's 1 November check read the same key model (30). Projects isolate resources, but the project roles are Admin and Editor and there's no read-only role; no confirmation for job deletes (5). Returns job state and your own model's output, no third-party content (10). Per-job event lists over the API; no audit log found, the per-key cost attribution covers inference requests only, and the docs say per-key spend caps don't exist (5). security.txt (PGP-signed, Expires 2028-09-30) sends reports to HackerOne with no acknowledgement time stated, and no SOC 2 or ISO report, bounty terms or public advisories were found in the docs. A disclosure route with no stated acknowledgement time gives 7 in this run (7). 30 + 5 + 10 + 5 + 7 = 57.
Unsloth 44
Read as local software. No account; Studio asks for an admin password once it's exposed beyond loopback, generates a random first-run password that must be changed, limits failed logins and issues API keys for its server (20). The Security in Unsloth docs page describes ask, auto and full approval modes for tool calls, with Allow and Deny prompts and dangerous shell commands blocked, and operating-system sandboxes (bubblewrap, Seatbelt, MXC). Server-side tools stay on by default when Studio is exposed, and full mode turns the sandbox off (16 of 20). Hugging Face repositories are scanned before loading, trust_remote_code needs permission, flagged malware is blocked, and HTML and MCP artifacts render in sandboxed frames. No guidance on injection through training data or tool output was found (8 of 15). No audit log found (0). No security.txt, SECURITY.md or disclosure route found. The docs list CodeQL, Semgrep, dependency audits and pinned Actions, but no reporting channel, and the two published CVEs came from third-party assigners (0 of 20). 20 + 16 + 8 + 0 + 0 = 44.
Schema & documentation Together AI Fine-tuning +12
Together AI Fine-tuning 83
A public OpenAPI 3.1.0 file at docs.together.ai/openapi.yaml ('Together APIs' 2.0.0), read in full on 4 November, has 12 fine-tuning paths under /v1/fine-tunes and /v1/finetune/download with typed schemas (25). llms.txt with .md twins (10). Field descriptions say what a field does and sometimes the trade-off ('may improve results but increase cost and risk of overfitting'), rarely when to use it (12). Two required fields, enums for training_type, training_method and the scheduler, defaults and limits such as n_checkpoints up to 10 and suffix up to 64 characters (13). Python, TypeScript, JavaScript and curl examples on each call. The error code page covers inference only, and in the OpenAPI file job creation lists only 200 and 503 while preview, cancel, delete, download and metrics list some 4xx answers, so the partial value is kept (8). Versioned /v1 paths and a dated changelog with 44 entry days from 6 August to 3 November 2026 (15). 25 + 10 + 12 + 13 + 8 + 15 = 83.
Unsloth 71
Read as a framework. No API reference or typed contract published beyond the Python signatures; the docs teach through guides and notebooks (10). llms.txt and llms-full.txt at unsloth.ai/docs (10). The fine-tuning guide says when to pick LoRA, QLoRA or full fine-tuning and which hyperparameters to start from (15). Parameters such as max_seq_length, load_in_4bit and LoRA targets are explained in guides rather than a typed reference (8). Over 100 notebooks by model family, and a troubleshooting section (13). Calendar versions on PyPI, and a dated public changelog in the docs (Unsloth Updates) with seventeen entries between 10 August and 30 October 2026, each linking GitHub release notes (15). 10 + 10 + 15 + 8 + 13 + 15 = 71.
Agent ergonomics Unsloth +11
Together AI Fine-tuning 42
GET /v1/fine-tunes returns truncated job objects, with no limit or field selection (10). The OpenAPI file lists no query parameters on the list call, so no pagination or filters (0). An error page maps 11 status codes to a cause and a fix, scoped to inference; fine-tuning errors aren't listed (12). No idempotency keys or client-chosen job IDs; the docs advise trying 5xx again after a short wait (5). Only model and training_file are required, defaults are documented, and official SDKs exist for Python and TypeScript plus the tg CLI (15). We didn't score POST /v1/fine-tunes/estimate-price, a dry-run quote the checklist has no line for, though it saves an agent a failed or overpriced job.
Unsloth 53
Read as a framework an agent drives with code. A full SFT run is a notebook of a few dozen lines, and Studio adds an OpenAI-compatible endpoint (15). You choose what to save, an adapter of about 100 MB, merged 16-bit or GGUF, which controls output size (10). Error messages weren't tested in this run; the docs have a troubleshooting page (10). Training resumes from checkpoints through the Trainer, which is the nearest thing to a safe retry (10). Sensible defaults in every notebook, but Python only (8). 15 + 10 + 10 + 10 + 8 = 53.
Reliability Together AI Fine-tuning +7
Together AI Fine-tuning 55
Better Stack status page at status.together.ai with component history for the website, the playground and each serverless model, but no component for fine-tuning jobs. A vendor page with no component for the product takes 15 in this run (15). Read on 4 November, its feed posts no incident since January 2025 (the newest items are maintenance on 21 April and 2 July 2026), and the monitors record downtime on single serverless models only. Fine-tuning jobs don't run on those models, and a page that has posted no incident in 22 months while its monitors show downtime isn't shown to post incidents, so the window isn't credited as clean. The 1 October 20 is kept, the value for a page that doesn't post incidents (20). The rate-limit page gives no numbers, and the dynamic serverless limits the 1 October note leaned on were retired on 2 October 2026. No limits for fine-tuning calls found (0). The docs say to reduce the rate and use exponential backoff on 429 and to retry 503 with backoff, with no idempotency key or safe-retry guidance for job creation (10). No SLA found for fine-tuning (0). Fine-tuning carries no beta label (10). 15 + 20 + 0 + 10 + 0 + 10 = 55.
Unsloth 48
Scored on the local-package checklist. Installs from PyPI (unsloth) or a Docker image, with Python 3.12 and 3.13 and Windows, Linux, WSL and macOS stated in the README (20). 64 GitHub Actions workflows in the repository on 4 November, among them a consolidated test workflow that runs pytest on every push to main and on pull requests, plus CodeQL and lockfile audits. GitHub's pages refused our reader, so the result on main is unread (15 of 25). 792 open issues and 472 open pull requests on 1 October against several releases a week, not re-read on 4 November because GitHub's pages refused us (8). Calendar versions (2026.11.2 in the source on 4 November) with release notes that don't call out breaking changes (5). No 1.0 or stability declaration found, and the Studio's GitHub tags carry a -beta suffix (0). 20 + 15 + 8 + 5 + 0 = 48.
Score by category
| Category | Weight | Together AI Fine-tuning | Unsloth | Edge |
|---|---|---|---|---|
| Reliability | 16% | 55 | 48 | Together AI Fine-tuning +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 83 | 71 | Together AI Fine-tuning +12 |
| Agent ergonomics | 13% | 42 | 53 | Unsloth +11 |
| Security & auth | 14% | 57 | 44 | Together AI Fine-tuning +13 |
| Payments & pricing | 10% | 30 | 90 | Unsloth +60 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 80 | 82 | Unsloth +2 |
| Transparency & trust | 7% | 68 | 38 | Together AI Fine-tuning +30 |
| Negative events | ≤15 | -3 | -2 | |
| Total | C 55/100 | C 57.2/100 |
Facts side by side
| Fact | Together AI Fine-tuning | Unsloth |
|---|---|---|
| Kind | HTTP API | Agent framework |
| Vendor | Together AI | Unsloth |
| Hosted endpoint | https://api.together.ai/v1 | no (local only) |
| Transports | HTTP | |
| Auth | API key | None |
| Pricing | Pay per use | Free |
| Price for fine-tuning | $0.34 per 1M tokens | free |
| x402 | no | no |
| Licence | Apache-2.0 (SDKs) | Apache-2.0 (core), AGPL-3.0 (Studio UI) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-22 | 2026-10-30 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | no document linked |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 10 stars, 118k npm/wk, 369k PyPI/wk | 77k stars, 230k PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Together AI Fine-tuning | Unsloth |
|---|---|---|
| LedgerCost analyst | 3/5 A quote endpoint, then $5.49 an hour to serve | 5/5 $0 for the software, and the GPU is yours to price |
| KeelOperations and maintenance reviewer | 3/5 A changelog almost daily, two weeks of warning | 2/5 Fifteen releases with no breaking-change notes |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Together AI Fine-tuning
31 tunable base models, 11 or 12 of them with full fine-tuning as well as LoRA, and weights can be downloaded at any saved checkpoint. Fine-tuned models don't run serverless; dedicated endpoints start at $5.49 an hour. Over 100 base models were removed from fine-tuning on 29 July 2026 with notice posted only that day.
Unsloth
Unsloth fine-tunes open models with LoRA, QLoRA, full training or RL on the user's own GPU under an Apache-2.0 core, with approval modes and OS sandboxes for Studio's tools. A default download counter runs on every model load while the desktop docs say 'No telemetry', and no security disclosure route was found.
Before you call either
Together AI Fine-tuning
- Call POST /v1/fine-tunes/estimate-price with the same body before creating the job, and check the model's minimum charge
- Read
lora_training.max_rankfrom the model limits response before settinglora_r; most models went to 128 on 2026-09-29 - Don't retry a create call blindly after a timeout; there's no idempotency key, so list jobs and check first
- Download with checkpoint=adapter if you'll merge locally; merged weights for a 70B model are a large stream
- Tear down the dedicated endpoint once evaluation ends, since it bills while idle
Unsloth
- Install with
uv pip install unsloth --torch-backend=autoon a CUDA machine; the desktop app is for people - Set
UNSLOTH_DISABLE_STATISTICS=1before loading a model to stop the default statistics downloads - Stay on Unsloth 2026.8.20 or later, which carries the fix for CVE-2026-93348, and load only models you trust
- If Studio must be reachable by other agents, pass --disable-tools and keep it on 127.0.0.1 behind a tunnel
- Pin the exact unsloth version; releases land several times a week and don't flag breaking changes
Questions
Which is better for AI agents, Together AI Fine-tuning or Unsloth?
Unsloth scores 57.2 (C) on agent readiness against Together AI Fine-tuning's 55 (C), and leads in 3 of 7 scored categories. Together AI Fine-tuning leads on reliability, schema & documentation, security & auth and transparency & trust.
Which is cheaper for fine-tuning, Together AI Fine-tuning or Unsloth?
Unsloth, at free against $0.34 per 1M tokens for Together AI Fine-tuning. These are the vendors' published prices for the job.
Can an agent call Together AI Fine-tuning and Unsloth without installing anything?
Together AI Fine-tuning has a hosted endpoint at https://api.together.ai/v1. No hosted endpoint is listed for Unsloth.
Are Together AI Fine-tuning and Unsloth open source?
No open-source release is listed for Together AI Fine-tuning. Unsloth is open source (Apache-2.0 (core), AGPL-3.0 (Studio UI)).
Other comparisons with Together AI Fine-tuning or Unsloth
- Amazon Bedrock model customisation vs Together AI Fine-tuning
- Amazon Bedrock model customisation vs Unsloth
- Axolotl vs Together AI Fine-tuning
- Axolotl vs Unsloth
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Together AI Fine-tuning
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Unsloth
- Fireworks AI Fine-tuning vs Together AI Fine-tuning
- Fireworks AI Fine-tuning vs Unsloth
- Nebius Token Factory fine-tuning vs Together AI Fine-tuning
- Nebius Token Factory fine-tuning vs Unsloth
- Tinker vs Together AI Fine-tuning
- Tinker vs Unsloth
- Together AI Fine-tuning vs Vertex AI Gemini tuning
- Unsloth vs Vertex AI Gemini tuning
Machine-readable
- This page as Markdown
/compare/together-fine-tuning-vs-unsloth.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/together-fine-tuning.json·/api/v1/tools/unsloth.json - From a terminal
anchor compare together-fine-tuning unsloth(the CLI) - Over MCP
compare_tools {"a": "together-fine-tuning", "b": "unsloth"}at/mcp, no key