Free to start

Google: Gemma 3 27B vs Qwen: Qwen3 32B

Try both on us. Starter credit covers your first requests, then one key routes Gemma 3 27B and Qwen3 32B. Switch by changing the model name.

Compare routesProviders, price, context, and policy posture in one view.

Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.

Same API shapeUse the OpenAI client and set the model you want.

Practical read

Monthly evidence

Google: Gemma 3 27B has the lower published input-plus-output rate and more Credits provider routes. Their context windows are the same size. There is not enough recent probe data to compare speed.

$0.2532/1MGoogle: Gemma 3 27B cheapest route

$0.34815/1MQwen: Qwen3 32B cheapest route

not enough dataGoogle: Gemma 3 27B fastest measured p50 TTFT

not enough dataQwen: Qwen3 32B fastest measured p50 TTFT

The price comparison adds each route's rate for one million input tokens and one million output tokens; your cost depends on your input/output mix. Prices and live route measurements can change. Use the monthly reports when you need a stable evidence window, then run a small task-specific eval before choosing a production default.

Google: Gemma 3 27BQwen: Qwen3 32B

Model idgoogle/gemma-3-27b-itqwen/qwen3-32b

Publisher Google AI Studio Alibaba Cloud Model Studio

AI IQ — —

Context131,072 tokens131,072 tokens

Credits provider routes53

Cheapest route$0.2532/1M$0.34815/1M

Cached input$0.0422/1M$0.010972/1M to $0.050113/1M

Privacy posturehas ZDR routehas Confidential route (E2EE + ZDR)

Fastest measured p50 TTFTnot enough datanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough datanot enough data

Modes chat chat

Google: Gemma 3 27B routes

Overview5 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Qwen: Qwen3 32B routes

Overview3 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Related comparisons

Browse every comparison

Google: Gemma 3 27B vs Z.ai: GLM 5.338 combined provider routes
Google: Gemma 3 27B vs Z.ai: GLM 5.237 combined provider routes
Google: Gemma 3 27B vs Z.ai: GLM 5.3 Flash37 combined provider routes
Qwen: Qwen3 32B vs Z.ai: GLM 5.336 combined provider routes
Qwen: Qwen3 32B vs Z.ai: GLM 5.235 combined provider routes
Qwen: Qwen3 32B vs Z.ai: GLM 5.3 Flash35 combined provider routes
Google: Gemma 3 27B vs MoonshotAI: Kimi K333 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Google: Gemma 3 27B31 combined provider routes

Production choice

Pick a default model. Keep fallback enabled.

TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.

OpenAI clientPython

client = OpenAI(
    base_url="https://api-azure.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="google/gemma-3-27b-it",
    messages=messages,
)

Questions

Which should I use, Google: Gemma 3 27B or Qwen: Qwen3 32B?

Google: Gemma 3 27B has the lower published input-plus-output rate and more Credits provider routes. Their context windows are the same size. There is not enough recent probe data to compare speed.

Is Google: Gemma 3 27B or Qwen: Qwen3 32B cheaper?

The current cheapest TrustedRouter route is $0.2532/1M for Google: Gemma 3 27B and $0.34815/1M for Qwen: Qwen3 32B. The comparison uses current catalog prices and updates as provider pricing changes.

Is Google: Gemma 3 27B or Qwen: Qwen3 32B faster?

Current measured p50 time to first token is not enough data for Google: Gemma 3 27B and not enough data for Qwen: Qwen3 32B. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Google: Gemma 3 27B and Qwen: Qwen3 32B with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between google/gemma-3-27b-it and qwen/qwen3-32b. This makes side-by-side evals possible without maintaining two provider integrations.