When should you choose open-weight serving over a hosted API?
This page compares the older editions named in its title. For current GPT-6, Claude 5.5 and Gemini 3.8 comparisons, open the current comparison library. The historical model identities are preserved for migration and reproducibility.
A dense text model with thinking and non-thinking modes.
A dense deployment has different memory and serving requirements from an MoE model. Check the actual quantization and context configuration.
Official source ↗A hosted model family introduced for coding and instruction following.
Use a dated model snapshot for reproducible API comparisons. Responses and Chat Completions have different request shapes.
Official source ↗Exact checkpoint fields from pinned publisher files. The configured position limit does not establish the context enabled by a serving endpoint.
| Configuration field | Qwen3 32B | GPT-4.1 |
|---|---|---|
| Published architecture | Qwen3ForCausalLM | Not established |
| Transformer layers | 64 | Not established |
| Configured position limit | 40,960 | Not established |
| Pinned configuration revision | 9216db5781bf | Not established |
| Configuration checked | 2026-10-10 | Not established |
| Original configuration | Read pinned file ↗ | Read publisher source ↗ |
Self-hosting brings responsibility for capacity, updates and monitoring. An API endpoint can reduce that work, but its processing and service terms still matter. Compare accepted outputs before comparing token rates.
Use the same representative inputs and a written answer rubric. Pin the model version and record the endpoint, thinking configuration, quantization when known, context length, output allowance and concurrency. Preserve native request differences in an adapter rather than silently dropping fields.
Measure full request time, error rate and reported usage. For tools, validate arguments and score the result after execution. For images, preserve resolution and preprocessing. A valid response format alone does not establish a correct answer.
Calculate input cost plus all billed output, including reasoning where the provider counts it. Add retries and discarded answers. Divide the total by the number of results that pass your quality criteria. Keep API usage cost separate from deployment and engineering cost.
Estimate token costs with the API calculator →Enter results from your own evaluation. A task should count once it meets your written quality criteria. Include failed attempts and retries in total spend. These inputs stay in this browser and are not a Flonno benchmark.
Enter all four values. Attempted tasks must be at least one; accepted tasks cannot exceed attempted tasks.
Enter all four values. Attempted tasks must be at least one; accepted tasks cannot exceed attempted tasks.
A source benchmark can inform your shortlist, while your evaluation shows whether a model finishes the work at an acceptable cost. Keep the chosen endpoint, processing terms and output limits in the decision record. Inclusion in the Radar does not mean the model is served by Flonno.
For the API currently offered here, explore Qwen3.8 Flash 27B and the production evaluation guide.
When is a larger dense Qwen model worth the extra serving cost?
How should you compare a dense model with a mixture-of-experts deployment?
Which reasoning configuration fits your latency and output budget?
Do you need text reasoning, image inputs, or both?
