Granite Embedding 107m Multilingual vs Bonsai 1.7B
At a Glance
| Compare | Bonsai 1.7BPrismML | |
|---|---|---|
| Pricing and Limits | ||
| Context windowMaximum documented tokens | 1K | 33K |
| Model facts checked | Aug 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
Side-by-Side Facts
| Field | granite-embedding-107m-multilingual | Bonsai 1.7B |
|---|---|---|
| Developer | IBM | PrismML |
| Family | Granite Embedding 107m Multilingual | Bonsai 1 7b |
| Model | granite-embedding-107m-multilingual | Bonsai 1.7B |
| Version | granite-embedding-107m-multilingual | Bonsai 1.7B |
| Lifecycle | active | active |
| Released | 2024-12-18 | 2026-03-29 |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Embedding | Text |
| Context window | 1K | 33K |
| Total parameters | 107M | 1.7B |
| Active parameters | Unknown | Unknown |
| License | apache-2.0 | apache-2.0 |
| Open weights | Yes | Yes |
| API available | Yes | No |
| Self-hostable | Yes | Yes |
| Provider access | Hugging Face (Standard) | Unknown |
| Capabilities | embeddings | chat, generation |
| Effective bit width | Unknown | 1 bit per weight |
| Weight size | Unknown | 0.25 GB |
| Weight format | Unknown | Binary Q1_0 |
Granite Embedding 107m Multilingual Capabilities
Bonsai 1.7B Capabilities
Primary Evidence
Sources and Freshness
Questions
Granite Embedding 107m Multilingual vs Bonsai 1.7B FAQs
Is Granite Embedding 107m Multilingual or Bonsai 1.7B better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both Granite Embedding 107m Multilingual and Bonsai 1.7B, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, Granite Embedding 107m Multilingual or Bonsai 1.7B?+
Neither model has a directly sourced input price in this comparison. Neither model has a directly sourced output price in this comparison.
Which has a larger context window, Granite Embedding 107m Multilingual or Bonsai 1.7B?+
Bonsai 1.7B has the larger sourced context window. Granite Embedding 107m Multilingual supports 1K and Bonsai 1.7B supports 33K.
Which performs better in benchmarks, Granite Embedding 107m Multilingual or Bonsai 1.7B?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can Granite Embedding 107m Multilingual or Bonsai 1.7B be self-hosted?+
Both models have the same recorded self-hosting status: supported. Granite Embedding 107m Multilingual is open weight; Bonsai 1.7B is open weight.
Can Granite Embedding 107m Multilingual and Bonsai 1.7B understand images?+
Granite Embedding 107m Multilingual is not documented with image input; Bonsai 1.7B is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, Granite Embedding 107m Multilingual or Bonsai 1.7B?+
Neither has a larger sourced maximum output. Granite Embedding 107m Multilingual is — and Bonsai 1.7B is —.
Do Granite Embedding 107m Multilingual and Bonsai 1.7B support reasoning and tool use?+
Granite Embedding 107m Multilingual: none of these features are definitively sourced. Bonsai 1.7B: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, Granite Embedding 107m Multilingual or Bonsai 1.7B?+
Granite Embedding 107m Multilingual has 1 sourced provider route; Bonsai 1.7B has 0, so Granite Embedding 107m Multilingual has broader tracked availability.
Which offers better value, Granite Embedding 107m Multilingual or 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.