When Thinking Machines Lab released Inkling 2 Mini (Apache 2.0) today, most of the headlines focused on the benchmark numbers: 20.1 on the Artificial Analysis Index and 48.2% on DeepSWE v1.1 in a 26.4B parameter package with a 1M-token context window.
From an inference FinOps perspective, though, the more interesting detail is how it gets there—and what a looped transformer does to your local vs. cloud unit economics. Standard transformers allocate one set of weights per layer and execute each layer once per token.
Inkling 2 Mini uses 26.4B total parameters (~3.4B–5.4B active per token) across 24 layers, but loops the middle 12 layers 3x with shared weights:
6 + 12×3 + 6).
That changes the classic LLM deployment bottleneck:
| Deployment Target | Bottleneck | Practical Result for Inkling 2 Mini |
|---|---|---|
| 32GB Mac / DGX Spark (Ollama) | Unified RAM capacity & memory bandwidth | Fits comfortably alongside dev tools at $0/token |
| 16GB Laptop (Unsloth Dynamic GGUF) | Quantized weight size ( llama.cpp ) |
Runs locally without cloud API bills for single-user coding loops |
| Cloud API (Tinker / Serverless) | Compute FLOPs per token & concurrency | 3x middle-layer looping means higher compute per token than a non-looped 26B MoE, so cloud endpoints shine mainly for burst concurrency & fine-tuning |
$0/Token vs. Cloud API Break-Even
In practice, teams running coding agents or 1M-context repo analysis hit two very different cost curves:
tok/s latency for zero API spend.
Looped architectures compress weight memory faster than they compress FLOPs. That makes them disproportionately strong for local/edge hardware (where RAM capacity is the hard wall) while keeping cloud vs. self-hosted break-even math very sensitive to concurrency.
If you want to model exact local hardware vs. cloud API break-even or compare 470+ models side by side, we published the full breakdown here:
👉 [Inkling 2 Mini (26.4B Looped Transformer) FinOps Breakdown on TokenMargin](https://tokenmargin.dev/guides/inkling-2-mini-26b-looped-transformer-local-16gb-gguf-vs-tinker-cloud-api-cost-2026.html)