A quick two-line bugfix doesn't need a frontier reasoning model costing 10x more and taking 20 seconds. Conversely, a complex architecture decision for your game's economy system probably deserves more deliberate reasoning than a fast, lightweight model can provide.
Most competitors pick one model and call it a day — either because it simplifies their stack or because model pricing is complex. We chose to do the harder work and support multiple tiers because we think developers deserve that control.
Qualitative illustration. Exact costs to be determined based on usage during final pricing.
When you need an answer in under two seconds — syntax checks, quick bugfixes, one-liner helpers, rapid iteration on small changes. Speed gets out of your way.
The right choice for most everyday tasks. Feature additions, UI work, multi-file refactors, DataStore setups — you get thoughtful output on a reasonable timeline at a moderate cost.
When depth matters more than speed. Architecture decisions, complex multi-system coordination, performance optimization, and security review — tasks that benefit from deliberate, thorough reasoning.
| Capability | Speed | Balanced | Quality |
|---|---|---|---|
| Latency (approx) | Under 2s | 4–10s | 10–30s |
| Output quality | Good | Very Good | Excellent |
| Cost intensity | Low | Medium | High |
| Context window | Standard | Large | Very Large |
| Reasoning depth | Surface-level | Good | Deep |
| Multi-file coordination | Limited | ✔ Good | ✔ Excellent |
| Architecture & design | Not ideal | Capable | ✔ Best |
| Bugfixes & quick edits | ✔ Best | ✔ Good | Overkill |
| UI / feature work | Adequate | ✔ Best | ✔ Good |
Qualitative comparison. Specific model versions subject to change as we finalise the product.
Answer three quick questions and I'll suggest the right tier for your task.