Decision guide
Should you switch volume work from GPT-6 Luna to Gemini 3.7 Flash?
Historical comparison: use current model profiles for current rates, IDs and availability. 3.7 Flash is Google's efficiency-first Flash row (3.8 Flash is newer). Compare current list rates and workload results against GPT-6 Luna; do not reuse GPT-5.6 Luna benchmark rows as if they described its successor.
Switch if
- Your pipelines send image, video, audio, or PDF input (catalogued 3.7 Flash modalities) that Luna's text+image row does not cover.
- You want Google's efficiency-first Flash row: an August 2026 Google evaluation reported 65.3% DeepSWE 1.1 at $2.18/task for Gemini 3.7 Flash. The older GPT-5.6 Luna comparison used a separate vendor snapshot; evaluate against GPT-6 Luna on your own task set.
- You are already on Google Cloud or Workspace and the introductory $0.75/$3.75 list (through 2026-12-31) fits a controlled batch test.
Stay if
- GPT-6 Luna already meets your pass rate. Its current list rate is $0.10/$0.50 versus 3.7 Flash at $0.75/$3.75 through 2026-12-31 (then $1.50/$7.50 from 2027-01-01).
- Your OpenAI integrations, tool schemas, and billing are not worth revisiting for a result that must be confirmed on your own workload.
- You need 128K max output (Luna) rather than 3.7 Flash's 65,536-token cap.
Check before production traffic moves
- 01Run the same high-volume batch on both models with identical validators.
- 02Include multimodal inputs only where your production workload actually sends them.
- 03Compare p95 latency, rate limits, and retry behaviour — quote catalog list rates, not a guessed blend.
This guide was first written for GPT-5.6 Luna and is now a pilot template for GPT-6 Luna. Current catalog list rates are $0.75/$3.75 for Gemini 3.7 Flash through 2026-12-31 (then $1.50/$7.50) and $0.10/$0.50 for GPT-6 Luna. The 65.3%/$2.18 Gemini DeepSWE figure is Google's August 2026 vendor evaluation; older Luna benchmark figures belong to GPT-5.6 Luna and are not current evidence about GPT-6 Luna. Do not treat separate benchmark snapshots as a ranking.
Run a controlled trial first
A second option in a labelled pilot is cheaper than a production cutover. Score the trial, then migrate or roll back on evidence.
Pilot plan
- Select a high-volume slice with repeatable inputs and a known error budget.
- Run GPT-6 Luna and 3.7 Flash on the same batch, including structured outputs and tool calls.
- Track cost per accepted task, latency p95, and reviewer minutes on a human sample.
Score the trial
- Modality fit
- Pass rate on the inputs your pipeline actually sends.
- Cost per success
- Tokens, retries, and review divided by accepted tasks.
- Throughput
- Rate limits, queue time, and p95 latency under load.
- Integration cost
- Adapter changes, auth, logging, and support path.
Migration sequence
- Add 3.7 Flash behind a feature flag with Luna as the default fallback.
- Route only the pilot cohort first; cap spend and monitor validator failures.
- Expand only when cost per success and latency stay within tolerance.
Rollback plan
- Keep Luna routing and prompt templates provider-specific for instant switch-back.
- Stop 3.7 Flash traffic if validation or latency breaches thresholds; replay safe failures.
- Archive batch logs so a later re-test can separate release changes from integration bugs.
Hidden costs to price
- Introductory Flash rates double on 2027-01-01 — forecast both the $0.75/$3.75 and $1.50/$7.50 catalog bands.
- A second cloud provider adds billing, policy review, and on-call complexity.
- Search grounding and tools on Gemini can add separate line items.
Evidence to check