Head to head · Fine-tuning · October 2026 research run

Tinker vs Unsloth

Unsloth scores 57.2 (C) on agent readiness against Tinker's 53.7 (D), and leads in 3 of 7 scored categories. Tinker leads on security & auth, maintenance & community and transparency & trust. Both do fine-tuning.

Best fine-tuning services for AI models · All 36 fine-tuning comparisons

Which one, for what

Tinker D

Best for Researchers and teams writing custom post-training loops, especially RL, who want per-token billing and the weights at the end.

Ahead on

  • Security & auth, 57 against 44
  • Maintenance & community, 87 against 82
  • Transparency & trust, 62 against 38

Watch for

LoRA only; no full-parameter training

Unsloth C

Best for One person or a small team tuning an open model on their own GPU and keeping the weights.

Ahead on

  • Reliability, 48 against 35
  • Payments & pricing, 90 against 30

Also in its favour

  • No key needed to call it

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

Tinker 30

No machine payment protocol (0). Per-1M-token prices for prefill, cached prefill, sampling and training published without a login, and as JSON (20). No free tier; the quickstart says to add payment details before training, and the console's credit grant redemption (1 September) isn't a public offer (0). Sign-up is a browser flow (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 Tinker +24

Tinker 62

The SDK and the cookbook are Apache-2.0, and the hosted service has Service Terms of Use, last updated 10 January 2026, at thinkingmachines.ai/legal/terms/, which the 1 October check didn't find. Closed service with clear terms (15, up from 5). The terms commit not to use Customer Content for model training or fine-tuning, keep it only as needed for the service, and carry a DPA with deletion on request. Checkpoints carry user-set TTLs. The privacy notice moved to /legal/privacy/ and wasn't re-read (15, up from 8). A model deprecations page lists dated retirements and promises to 'aim to give advance notice' by email, per the 1 October check. Dated notices with no stated notice period, up from 12 (15). The DPA's Annex 2 names Google Cloud, Cloudflare, WorkOS and OpenAI with their service and location, mostly 'Global' (15, up from 5). 15 + 15 + 15 + 15 = 60.

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.

Reliability Unsloth +13

Tinker 35

The listing's kind is sdk, but the SDK is a thin client for a hosted training service, so the hosted checklist is kept as on 1 October; that's a judgement call. No status page found, on the vendor's pages read on 1 October or by search on 4 November (0), and so no readable incident history (5). The only published limit is the in-flight sample cap of 2,000, per the 1 October check, not re-read on 4 November (10). The SDK's retry handler retries sampling with stable request IDs, confirmed in the SDK repository, and the docs' guide on client-side retries is per the 1 October check (15). No SLA found (0). Sign-up is open and paid, but the cookbook README still says 'after our private beta is over' on 4 November, and no GA statement was found (5).

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.

Security & auth Tinker +13

Tinker 57

API keys from the console, revocable, with key verification since 0.26.2; no per-key scopes found (20). An org, team and project permissions model, with no read-only role found (5). Returns your own model's samples and losses, no third-party content (10). get_audit_log() in the SDK for admins (15). security.txt at thinkingmachines.ai lists security-reports@thinkingmachines.ai and expires 2029-07-13, per the 2 November reading this run made, and the site now links a disclosure policy that wasn't read. A reporting route with no stated acknowledgement time, up from 5 (7). No bug bounty, certifications or advisories found, and osv.dev lists none for tinker or tinker-cookbook.

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.

Maintenance & community Tinker +5

Tinker 87

tinker-cookbook v0.5.9 tagged on 27 October 2026, 8 days before this check. The SDK repository's newest version bump is 0.37.0 on 2 November, untagged, so it isn't counted (30). Cookbook tags v0.5.4 (11 August), v0.5.5 (19 August), v0.5.6 (1 September), v0.5.7 (3 September), v0.5.8 (21 October) and v0.5.9 (27 October) in the 90 days from 6 August (20). The cookbook had 22 open issues and 55 open pull requests on 1 October and its README defers outside PRs until the private beta ends; GitHub's pages refuse us, so not re-read (12). The SDK is current (15). The cookbook runs pytest on push and pull request, plus pyright, recipe smoke tests and a security workflow (10).

Unsloth 82

The docs changelog's latest entry is 30 October 2026 (v0.1.913-beta, whose commit carries unsloth 2026.10.11), and the source reads 2026.11.2 on 4 November (30). Seventeen dated changelog entries since 6 August, the latest on 30 October (20). 792 open issues and 472 open pull requests on 1 October; reply times not sampled, and GitHub's pages refused us on 4 November (12). The PyPI package and Docker images are current, per the 1 October check; PyPI couldn't be read on 4 November (15). Test, CodeQL and audit workflows exist but the result on main is unread (5). 30 + 20 + 12 + 15 + 5 = 82.

Score by category

CategoryWeightTinkerUnslothEdge
Reliability16%3548Unsloth +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7071Unsloth +1
Agent ergonomics13%5353even
Security & auth14%5744Tinker +13
Payments & pricing10%3090Unsloth +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8782Tinker +5
Transparency & trust7%6238Tinker +24
Negative events≤150-2
TotalD 53.7/100C 57.2/100

Facts side by side

FactTinkerUnsloth
KindSDK + MCPAgent framework
VendorThinking Machines LabUnsloth
Hosted endpointno (local only)no (local only)
TransportsHTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicenceApache-2.0 (cookbook)Apache-2.0 (core), AGPL-3.0 (Studio UI)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-272026-10-30
Terms last updatednot read yetcouldn't be read
Privacy policy last updatednot read yetno document linked
Customer content may train modelsnot read yetcouldn't be read
Terms restrict automated accessnot read yetcouldn't be read
Terms restrict benchmarkingnot read yetcouldn't be read
Terms or service can change without noticenot read yetcouldn't be read
Arbitration or class-action waivernot read yetcouldn't be read
Popularity4k stars, 331k PyPI/wk77k stars, 230k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

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

Tinker

Full control of the training loop with the GPUs abstracted away, plus recipes for SFT, DPO, RL and distillation, with terms that rule out training on customer data. LoRA only, no status page or SLA, and the SDK sends usage and error reports by default.

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

Tinker

  1. Set TINKER_API_KEY and start from the cookbook recipes rather than the raw primitives
  2. Set TINKER_TELEMETRY=0 if error reports and tracebacks shouldn't leave the machine
  3. Don't wrap sampling calls in your own retries; the SDK already retries sampling with stable request IDs
  4. Save intermediate checkpoints with a TTL between 1 hour and 10 years; storage bills at $0.10 a GB-month until they expire
  5. Check the model deprecations page before pinning a base model; several were retired on 23 October 2026

Unsloth

  1. Install with uv pip install unsloth --torch-backend=auto on a CUDA machine; the desktop app is for people
  2. Set UNSLOTH_DISABLE_STATISTICS=1 before loading a model to stop the default statistics downloads
  3. Stay on Unsloth 2026.8.20 or later, which carries the fix for CVE-2026-93348, and load only models you trust
  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

Questions

Which is better for AI agents, Tinker or Unsloth?

Unsloth scores 57.2 (C) on agent readiness against Tinker's 53.7 (D), and leads in 3 of 7 scored categories. Tinker leads on security & auth, maintenance & community and transparency & trust.

Are Tinker and Unsloth open source?

Yes. Tinker is open source (Apache-2.0 (cookbook)). Unsloth is open source (Apache-2.0 (core), AGPL-3.0 (Studio UI)).

Other comparisons with Tinker or Unsloth

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.