Side-by-side comparison
Gemma 2 27B vs Weaver (alpha)
| Gemma 2 27B | Weaver (alpha) | |
|---|---|---|
| Provider | Mancer | |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 8,192 | 8,000 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | json_mode | json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 0.6500 | 0.7500 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 0.6500 | 1.0000 |
Frequently asked questions
Which is cheaper, Gemma 2 27B or Weaver (alpha)?
Gemma 2 27B is cheaper than Weaver (alpha) on a 50/50 input/output blend by about $0.225 per 1M tokens. Exact savings depend on your input-vs-output ratio — use the cost calculator on this page for a workload-specific estimate.
Which has a larger context window, Gemma 2 27B or Weaver (alpha)?
Gemma 2 27B has the larger context window at 8k tokens versus 8k tokens for Weaver (alpha). That means Gemma 2 27B can ingest about 1.0x as much text per request.
What is the difference between Gemma 2 27B and Weaver (alpha)?
Gemma 2 27B comes from Google; Weaver (alpha) comes from Mancer. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.