Keep state. Write the difference.
- 48 value heads; 128 × 128 recurrent matrices per head.
- Short convolution state is retained alongside the matrix.
previous state → decay → delta write → query readA hybrid language and vision model that combines Gated DeltaNet, Qwen Sparse Attention and routed experts. Explore how the architecture balances compact recurrent state with selective access to a long context.
Recurrent state carries continuity. Sparse attention brings selected history back into focus.
Gated DeltaNet updates a bounded recurrent matrix rather than appending every token to a KV list. It decays the previous state, estimates an existing association and writes a gated correction.
previous state → decay → delta write → query readEach slab is a complete decoder block, including its own MoE FFN. The 3× GDN → 1× QSA pattern repeats 12 times. The side drawing is an FFN detail inset. The animation is explanatory; no model inference is executed.
Attention schedule shown. Every attention mixer is followed by an MoE; four residual branches run through the backbone.
Configuration, memory and computation—each with a specific role in the model.
previous state → decay → delta write → query readindex keys → pool 4 → top 512 blocks → sparse GQA4 branches → gated read → top-10 + shared → gated writetoken IDs → 2/3-gram hashes → table → context gateDeveloper papers, released configurations and reference implementations. Reviewed 10 September 2026.
§§2.1–2.3 · GDN, QSA, residual gates and n-grams
Model overview; linked config.json
QSAIndexer, Attention, GatedDeltaNet and GatedResidual
N-gram embedding, branch collapse and expert routing
125B describes the language backbone; additional n-gram and MTP allocations are listed separately.
262,144 tokens is the native context. Extended-context serving needs a validated configuration.
Bring product knowledge and conversational assistance closer to your customers.
Connect reasoning to approved tools, with application-level control and human oversight.
Connect retrieval to managed inference with agreed API access and data processing terms.
Perchy provides managed AI inference through authenticated APIs. Customers do not receive SSH, root, operating-system or bare-metal access. The service does not provide model-training or fine-tuning functionality. Server administration remains with Perchy.
API availability, model licensing, context length and serving configuration are confirmed for your workload. Parameter counts and context specifications describe the developer’s model, not a promise of Perchy service capacity. Extended context requires a separately validated configuration.
Read the model developer’s documentationOne conversation.
A whole new trajectory.