Qwen3 Coder Next vs Ternary Bonsai 1.7B

At a Glance

Compare
Pricing and Limits
Input priceFrom · USD / 1M tokens$0.12Openrouter · Sep 22, 2026Not reported
Output priceFrom · USD / 1M tokens$0.80Openrouter · Sep 22, 2026Not reported
Context windowMaximum documented tokens262K33K
Model facts checkedAug 28, 2026View model evidence →Sep 18, 2026View model evidence →

Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →

Available Benchmarks

All benchmark results →
No Protocol-Matched Benchmark Yet.Results appear here only when both models share the same benchmark version, metric, evaluation protocol, and evidence class.

Side-by-Side Facts

FieldQwen3-Coder-NextTernary Bonsai 1.7B
DeveloperQwenPrismML
FamilyQwen3 Coder NextBonsai 1 7b
ModelQwen3-Coder-NextTernary Bonsai 1.7B
VersionQwen3-Coder-NextTernary Bonsai 1.7B
Lifecycleactiveactive
Released2026-02-022026-04-18
Knowledge cutoffUnknownUnknown
Input modalitiesTextText
Output modalitiesTextText
Context window262K33K
Total parameters79.7B1.7B
Active parameters3BUnknown
Licenseapache-2.0apache-2.0
Open weightsYesYes
API availableYesNo
Self-hostableYesYes
Provider accessHugging Face (Standard), Openrouter (Standard)Unknown
Capabilitieschat, generation, toolschat, generation
Effective bit widthUnknown1.58 bits per weight
Weight sizeUnknown0.46 GB
Weight formatUnknownTernary Q2_0

Qwen3 Coder Next Capabilities

chatgenerationtools
Serving providers2
Canonical IDQwen/Qwen3-Coder-Next

Ternary Bonsai 1.7B Capabilities

chatgeneration
Serving providers0
Canonical IDprism-ml/Ternary-Bonsai-1.7B

Primary Evidence

Sources and Freshness

Questions

Qwen3 Coder Next vs Ternary Bonsai 1.7B FAQs

Is Qwen3 Coder Next or Ternary Bonsai 1.7B better for coding?+

This comparison does not currently contain a protocol-matched coding benchmark for both Qwen3 Coder Next and Ternary Bonsai 1.7B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.

Which is cheaper, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

Only Qwen3 Coder Next has a directly sourced input price: $0.12 per million tokens. Only Qwen3 Coder Next has a directly sourced output price: $0.80 per million tokens.

Which has a larger context window, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

Qwen3 Coder Next has the larger sourced context window. Qwen3 Coder Next supports 262K and Ternary Bonsai 1.7B supports 33K.

Which performs better in benchmarks, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.

Can Qwen3 Coder Next or Ternary Bonsai 1.7B be self-hosted?+

Both models have the same recorded self-hosting status: supported. Qwen3 Coder Next is open weight; Ternary Bonsai 1.7B is open weight.

Can Qwen3 Coder Next and Ternary Bonsai 1.7B understand images?+

Qwen3 Coder Next is not documented with image input; Ternary Bonsai 1.7B is not documented with image input. This reflects supported input modalities, not vision quality.

Which can generate longer answers, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

Neither has a larger sourced maximum output. Qwen3 Coder Next is — and Ternary Bonsai 1.7B is —.

Do Qwen3 Coder Next and Ternary Bonsai 1.7B support reasoning and tool use?+

Qwen3 Coder Next: tool calling. Ternary Bonsai 1.7B: none of these features are definitively sourced. Feature support does not establish relative quality.

Which is available from more inference providers, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

Qwen3 Coder Next has 2 sourced provider routes; Ternary Bonsai 1.7B has 0, so Qwen3 Coder Next has broader tracked availability.

Which offers better value, Qwen3 Coder Next or Ternary Bonsai 1.7B?+

There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.

Send Feedback