Nova Micro vs ShieldGemma 9B
Nova Micro (2025) and ShieldGemma 9B (2024) are compact production models from Amazon Web Services (AWS) AI and Google DeepMind. Nova Micro ships a 128k-token context window, while ShieldGemma 9B ships a 8k-token context window. This comparison covers specs, pricing, API access, capabilities, benchmarks, input and output token costs, and production fit for coding and agent workloads. It focuses on practical selection signals rather than broad model-family marketing.
Nova Micro fits 16x more tokens; pick it for long-context work and ShieldGemma 9B for tighter calls.
Decision scorecard
Local evidence first| Signal | Nova Micro | ShieldGemma 9B |
|---|---|---|
| Best for | provider-routed production | general production evaluation |
| Decision fit | RAG, Long context, and Classification | Classification |
| Context window | 128k | 8k |
| Cheapest output | $0.14/1M tokens | - |
| Provider routes | 2 tracked | 1 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Nova Micro has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Nova Micro has broader tracked provider coverage for fallback and procurement flexibility.
- Nova Micro uniquely exposes Structured outputs in local model data.
- Local decision data tags Nova Micro for RAG, Long context, and Classification.
- Local decision data tags ShieldGemma 9B for Classification.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Nova Micro
$63.00
Cheapest tracked route/tier: OpenRouter
ShieldGemma 9B
Unavailable
No complete token price in local provider data
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- No overlapping tracked provider route is sourced for Nova Micro and ShieldGemma 9B; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Structured outputs before moving production traffic.
- No overlapping tracked provider route is sourced for ShieldGemma 9B and Nova Micro; plan for SDK, billing, or endpoint changes.
- Nova Micro adds Structured outputs in local capability data.
Specs
| Specification | ||
|---|---|---|
| Released | 2025-03-17 | 2024-07-01 |
| Context window | 128k | 8k |
| Parameters | — | 9B |
| Architecture | decoder only | decoder only |
| License | Proprietary | Gemma |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Nova Micro | ShieldGemma 9B |
|---|---|---|
| Input price | $0.04/1M tokens | - |
| Output price | $0.14/1M tokens | - |
| Providers |
Capabilities
| Capability | Nova Micro | ShieldGemma 9B |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | Yes | No |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on structured outputs: Nova Micro. Both models share the core language-model surface, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.
Pricing coverage is uneven: Nova Micro has $0.04/1M input tokens and ShieldGemma 9B has no token price sourced yet. Provider availability is 2 tracked routes versus 1. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose Nova Micro when long-context analysis, larger context windows, and broader provider choice are central to the workload. Choose ShieldGemma 9B when provider fit are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.
FAQ
Which has a larger context window, Nova Micro or ShieldGemma 9B?
Nova Micro supports 128k tokens, while ShieldGemma 9B supports 8k tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible.
Is Nova Micro or ShieldGemma 9B open source?
Nova Micro is listed under Proprietary. ShieldGemma 9B is listed under Gemma. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Which is better for structured outputs, Nova Micro or ShieldGemma 9B?
Nova Micro has the clearer documented structured outputs signal in this comparison. If structured outputs is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Where can I run Nova Micro and ShieldGemma 9B?
Nova Micro is available on OpenRouter and AWS Bedrock. ShieldGemma 9B is available on NVIDIA NIM. Provider coverage can affect latency, region availability, compliance posture, and fallback options. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.
When should I pick Nova Micro over ShieldGemma 9B?
Nova Micro fits 16x more tokens; pick it for long-context work and ShieldGemma 9B for tighter calls. If your workload also depends on long-context analysis, start with Nova Micro; if it depends on provider fit, run the same evaluation with ShieldGemma 9B.
Continue comparing
Last reviewed: 2026-05-19. Data sourced from public model cards and provider documentation.