Side-by-side comparison
Reka Edge vs Gemma 3 27B
Google
Gemma 3 27B
👁 Vision
🔧 Tools
{} JSON
Input / 1M
$0.0800
Output / 1M
$0.1600
| Reka Edge | Gemma 3 27B | |
|---|---|---|
| Provider | Rekaai | |
| Context window Maximum tokens (input + output) the model can process in a single request. Glossary → | 16,384 | 131,072 |
| Capabilities Optional capabilities the model advertises: vision (images), tools (function calling), json_mode (structured output). | vision, tools | vision, tools, json_mode |
| Input $ / 1M tokens Cost for tokens you send (prompt + context). Cheaper side highlighted. Glossary → | 0.1000 | 0.0800 |
| Output $ / 1M tokens Cost for tokens the model generates. Output is normally 3–5× pricier than input. Glossary → | 0.1000 | 0.1600 |
Frequently asked questions
Which is cheaper, Reka Edge or Gemma 3 27B?
Reka Edge is cheaper than Gemma 3 27B on a 50/50 input/output blend by about $0.02 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, Reka Edge or Gemma 3 27B?
Gemma 3 27B has the larger context window at 131k tokens versus 16k tokens for Reka Edge. That means Gemma 3 27B can ingest about 8.0x as much text per request.
What is the difference between Reka Edge and Gemma 3 27B?
Reka Edge comes from Rekaai; Gemma 3 27B comes from Google. They differ in pricing, context window, and supported capabilities — see the side-by-side table on this page for the exact figures, refreshed nightly.