Open LLMs/amazon

Open-Weight LLM · Private & Custom AI

GDN-primed-HQwen3-8B-Instruct

Long-context hybrid inference engine for ops teams building private AI systems that need 2× throughput gains on document processing, knowledge retrieval, and agent workflows without sacrificing model quality.

GDN-primed-HQwen3-8B-Instruct is an 8B hybrid model (50% Transformer attention + 50% State-Space Model layers) fine-tuned from Qwen3-8B to handle 128K context natively while delivering ~2× faster decode throughput at long sequences. For ops teams running private deployments, this trades minimal accuracy loss (~3 points on short tasks) for substantial inference cost reduction—critical when batching many concurrent requests or operating on tight hardware budgets.

8.5B
Parameters
apache-2.0
License (OSI/permissive)
Unknown
Context
86.3k
Downloads

Model facts

Developeramazon
Parameters8.5B
Context windowUnknown
Licenseapache-2.0 — OSI/permissive
Tasktext-generation
GatedNo
Downloads86.3k
Likes2
Updated2026-04-03
Sourceamazon/GDN-primed-HQwen3-8B-Instruct

Private deployment

Run GDN-primed-HQwen3-8B-Instruct in your own environment

Self-hostable on a single high-end GPU (H100/H200, ~16–20 GB VRAM at bfloat16). The hybrid architecture's fixed-size recurrent state (vs. growing KV cache) means lower memory footprint and higher batch concurrency—advantages that compound in private, multi-tenant ops environments where you control the infrastructure. No external API calls; all inference and data stay in your environment.

Operational AI use cases

01

Long-Document Support Ticket Routing & Summarization

Ingest 128K-token customer emails, knowledge base excerpts, and ticket history. The model's linear-cost SSM layers process extended context efficiently, enabling real-time routing to the right department and auto-generating concise summaries—reducing triage time and cost-per-ticket in high-volume support ops.

02

Internal Knowledge & Compliance Document Search with Retrieval Augmentation

Build a private RAG pipeline over internal policies, SOPs, and regulatory docs. GDN's throughput allows you to batch many retrieval queries and re-rank results on live context without waiting for API responses. Deploy entirely on-prem; sensitive compliance docs never leave your data center.

03

Agentic Workflow Orchestration for Finance & Operations

Use the model as a backbone for multi-step workflows—parsing expense reports, cross-referencing GL accounts, flagging exceptions. The 128K context lets you hold full transaction batches + policy context in a single forward pass, reducing round-trips and latency in automated approval chains.

Custom AI

As a base for custom AI

Strong foundation for building proprietary ops AI products. The Apache 2.0 license and published Hybrid Model Factory approach allow you to retrain or adapt the architecture (e.g., adjust hybrid ratio, SSM layer placement) for domain-specific tasks. Use it as a base model for instruction-tuning on internal workflows, or integrate into a larger agent framework where you own the full stack.

In the operating system

Where it fits

Operates at the **knowledge/retrieval layer** and **agent reasoning layer** in an AI OS. It's the inference engine behind RAG systems, workflow agents, and real-time knowledge workers. Its throughput advantage makes it practical for high-concurrency scenarios (many parallel user requests); the 128K context supports rich multi-document reasoning and fact-grounding that smaller models cannot achieve.

Data control & security

Running GDN-primed-HQwen3-8B-Instruct privately means your prompts, documents, and generated outputs never touch external servers. For regulated industries (finance, healthcare, legal), this architecture choice eliminates API-level data exposure and allows you to implement granular access controls on the hardware layer. No model itself has built-in encryption or compliance guarantees—those are implemented via your deployment infrastructure (network isolation, audit logging, etc.).

Hardware footprint

**Estimate (bfloat16):** ~17 GB VRAM (weights + activation cache for typical batch size 1–4). At batch size 8–16 with 128K context, expect 20–24 GB. A single H100 (80GB) can run inference + moderate batching; two A100s (80GB each) provide comfortable headroom for production. Hybrid architecture's reduced KV cache significantly lowers memory vs. pure Transformer at long sequences.

Integration

Supports Hugging Face `transformers` library and `safetensors` format. Compatible with vLLM, Text Generation WebUI, and llama.cpp-style inference servers for easy API wrapping. No special kernels required (though GitHub references optional fused SSM+SWA kernels for added speed). Integrate via REST/gRPC endpoints or sync batching to your ops stack (Zapier, Make, internal microservices). Requires minimal tokenizer/model config changes.

When it's not the right fit

  • Your workload requires cutting-edge reasoning or complex multi-step math—short-context benchmarks show ~3-point gap vs. base Qwen3-8B (Long); for reasoning-heavy tasks, check Amazon's Primed Hybrid Reasoning models.
  • You need guaranteed chain-of-thought or explicit thinking tokens—this is instruct-tuned only, not a 'thinking model'; no native reasoning traces in generation.
  • Your use case is short-context only (<8K tokens)—the hybrid benefit (throughput, memory) vanishes; pure Transformer or smaller dense models are simpler.
  • You require real-time sub-50ms latency on single requests—hybrid's SSM layers add marginal latency per token; for ultra-low-latency APIs, profile carefully.

Alternatives to consider

Qwen3-8B (base)

Pure Transformer; marginally higher quality on short tasks, but 2× slower decode at 128K context and higher KV-cache memory. Better if you have GPU budget and don't prioritize throughput.

Llama 3.1 8B

Established, widely deployed, good community support. Shorter native context (8K, extendable via RoPE), no hybrid optimization. Safer if you want proven ops reliability over cutting-edge efficiency.

Mamba2-7B

Pure SSM (no Attention), fully linear-time inference. Lower quality than hybrids, but extreme memory/throughput gains. Choose if throughput is the only constraint and you accept quality trade-offs.

FAQ

Can we deploy this entirely on-premises for a document processing workflow?

Yes. Download the model from Hugging Face, load it into a private GPU cluster (single H100 or multi-A100 setup), and serve via vLLM or similar. No external calls; all documents stay in your data center. Ideal for regulated environments.

What license terms apply if we use this in a commercial product?

Apache 2.0 explicitly permits commercial use, modification, and distribution. You can ship it as part of a SaaS product, build a fine-tuned derivative, or embed it in proprietary tools. No royalties, no vendor lock-in. Review Apache 2.0 terms for attribution requirements.

How does the hybrid architecture affect latency for single-token requests?

Negligible difference; SSM state updates are constant-time. For batched or streaming scenarios, the throughput gain (2×) directly reduces wall-clock latency. For ultra-low-latency single-token APIs, benchmark on your hardware—SSM complexity is small but non-zero.

Can we fine-tune or instruction-tune this model on our internal data?

Yes. Apache 2.0 license + published Hybrid Model Factory repo means you can adapt the architecture, adjust hybrid ratio, or continue training on domain data. Start with the base or use existing instruction-tuned version as a checkpoint. Requires deep learning infrastructure but gives you full control.

Build Your Private AI Operations System with GDN-primed-HQwen3-8B

Deploy this hybrid model as the backbone of your ops AI stack—no external APIs, full data control, and 2× throughput efficiency. LLM.co helps you integrate it into custom workflows, RAG systems, and agent frameworks. Start building your private AI OS today.