Model comparison
Composer 2.5 vs Laguna S 2.1
Head-to-head evidence from 3 shared benchmark results across 2 categories. Overall scores shown here use the public BenchAlign v5 ranking lane.
Evidence parity. Composer 2.5 and Laguna S 2.1 share 3 comparable benchmark results. 1 of 8 categories are comparable. 2 results are unique to Composer 2.5; 3 to Laguna S 2.1.
Updated July 21, 2026- Shared results
- 3
- Composer 2.5 only
- 2
- Laguna S 2.1 only
- 3
- Comparable categories
- 1 / 8
Treat this as a split decision. Composer 2.5 makes more sense if its workflow fits your team better; Laguna S 2.1 is the better fit if agentic is the priority or you want the cheaper token bill.
Confidence note. This is a partial-evidence comparison with 3 shared benchmark results across 2 evidence categories; 1 of 8 categories currently have scoreable aggregates for both models. Treat the verdict as directional until coverage is more balanced.
Why this result
Composer 2.5 and Laguna S 2.1 finish on the same BenchAlign overall score, so this is less about a single winner and more about where the edge shows up. The BenchAlign headline says tie; the benchmark table is where the real choice happens.
Composer 2.5 is also the more expensive model on tokens at $0.50 input / $2.50 output per 1M tokens, versus $0.10 input / $0.20 output per 1M tokens for Laguna S 2.1. That is roughly 12.5x on output cost alone. Laguna S 2.1 gives you the larger context window at 1M, compared with 200K for Composer 2.5.
Category breakdown
Exact category averages are shown below. Not measured means BenchLM does not have enough sourced public coverage for that model and category.
| Category | Composer 2.5 | Δ | Laguna S 2.1 |
|---|---|---|---|
| Agentic | Composer 2.569.3 | Margin→ 0.9 | Laguna S 2.170.2 |
| Coding | Composer 2.5Not measured | MarginNo overlap | Laguna S 2.159.4 |
Decisive benchmark drivers
The largest measured benchmark gaps in this matchup, with exact reported values.
More
- Source ↗
Terminal-Bench 2.0
AgenticA 69.3%B 70.2%Winner: Laguna S 2.1Δ 0.9Terminal-Bench 2.0: Composer 2.5 scored 69.3%; Laguna S 2.1 scored 70.2%. Laguna S 2.1 wins this benchmark.
Operational comparison
Runtime and commercial metrics are compared only when both models have a complete sourced value.
| Metric | Composer 2.5 | Laguna S 2.1 | Comparison |
|---|---|---|---|
| Input / output priceUSD per 1M tokens | Composer 2.5$0.5 input / $2.5 output | Laguna S 2.1$0.1 input / $0.2 output | Laguna S 2.1 has the lower combined listed price. |
| Generation speedtokens per second | Composer 2.5Not available | Laguna S 2.1Not available | A complete speed comparison is not available. |
| First-answer latencyseconds to first token | Composer 2.5Not available | Laguna S 2.1Not available | A complete latency comparison is not available. |
| Context windowmaximum listed tokens | Composer 2.5200K | Laguna S 2.11M | Laguna S 2.1 lists the larger context window. |
Benchmark Deep Dive
AgenticLaguna S 2.1 wins2 benchmarks
Coding6 benchmarks
Frequently Asked Questions (2)
Which is better, Composer 2.5 or Laguna S 2.1?
Composer 2.5 and Laguna S 2.1 are tied on the BenchAlign overall score, so the right pick depends on which category matters most for your use case.
Which is better for agentic tasks, Composer 2.5 or Laguna S 2.1?
Laguna S 2.1 has the edge for agentic tasks in this comparison, averaging 70.2 versus 69.3. Inside this category, Terminal-Bench 2.0 is the benchmark that creates the most daylight between them.
Related Comparisons
Explore More
Choose a model with this week’s evidence
Join 2,000+ readers for ranking moves, pricing changes, and the claims that still need proof.
One email each week. Unsubscribe anytime.