# Devstral Small 2 vs Kronos (slim)

> Devstral Small 2 scores 61 (C) to Kronos's 55.2 (C) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/devstral-small-2-vs-kronos.md (~9,250 tokens) · this version ~780 tokens · JSON https://www.anchorterminal.com/compare/devstral-small-2-vs-kronos.json · canonical https://www.anchorterminal.com/compare/devstral-small-2-vs-kronos
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Devstral Small 2 scores 61 (C) on agent readiness against Kronos's 55.2 (C), and leads in 3 of 4 scored categories. Kronos leads on documentation and upkeep. Both do open-weight models you run yourself.

- Devstral Small 2: C 61, rank #60 of 160 open-weight models · https://www.anchorterminal.com/tools/devstral-small-2.min.md
- Kronos: C 55.2, rank #122 of 160 open-weight models · https://www.anchorterminal.com/tools/kronos.min.md
- Devstral Small 2, good for Developers who want a dependable local coding agent on one consumer GPU or a 32 GB Mac Ahead on Reach, 90 against 55; Risk, 60 against 50; Agent interface, 65 against 60.
- Kronos, good for Agents that need a quick local forecast or synthetic sample of a candlestick series on modest hardware, for research or as one input among others. Ahead on Documentation and upkeep, 61 against 46.

| Category | Devstral Small 2 | Kronos |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 90 | 55 |
| Risk (20%) | 60 | 50 |
| Agent interface (10%) | 65 | 60 |
| Documentation and upkeep (10%) | 46 | 61 |

| Fact (where they differ) | Devstral Small 2 | Kronos |
| --- | --- | --- |
| Vendor | Mistral AI | Yu Shi (shiyu-coder, NeoQuasar), Tsinghua University |
| Licence | Apache-2.0 | MIT |
| Last release | 2026-07-15 | 2026-04-13 |
| Popularity | none | 43k stars |

Why the edge:
- Reach, Devstral Small 2 +35: Devstral Small 2 90 (Memory 25, the smallest build at 4 bits from a runtime's own library is Ollama's devstral-small-2 at Q4_K_M, 15 GB, and 15 GB × 1.2 = 18 GB, within 24 GB.); Kronos 55 (Memory 30, the publisher's Kronos-mini with its tokeniser is 0.03 GB and even Kronos-base is 0.43 GB in FP32. Runtimes 0, it runs only through the publisher's o…)
- Documentation and upkeep, Kronos +15: Devstral Small 2 46 (Model card 11, Intended use, the architecture, the parameters and the context are on the card.); Kronos 61 (Model card 11, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't.)
- Risk, Devstral Small 2 +10: Devstral Small 2 60 (File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository.); Kronos 50 (File safety 15, safetensors only, but the only documented loading path is the publisher's Python package in place of a runtime.)
- Agent interface, Devstral Small 2 +5: Devstral Small 2 65 (Chat template 20, chat_template.jinja in the repository (11,362 characters), with the tokenizer's tekken file for mistral-common.); Kronos 60 (Read for a forecasting model, the tool-calling, trained tool calling and structured-output lines stand for what it takes and returns.)