inclusionAI's Ling-3.1-flash (Ant Group), released in October under MIT: a 560B mixture-of-experts reasoning model with 25B parameters active per token. It is aimed at agents, coding and long office tasks. Only 9 of its 72 layers keep a growing cache, and those store MLA's compressed vectors, so even its full 256K window adds only about 3 GB: the weights decide where it runs. At Q4_K_M it needs about 371 GB at 4K context, more than any single GPU in this index. The 512 GB Mac Studio gives its GPU about 384 GB, which holds it only tightly on this site's rule; on servers the vendor's reference setup is eight H200s or four GB300s running FP8. Q8_0 needs about 628 GB. The vendor quotes a 1M-token window, but the released config sets 262,144 positions with no scaling, so that is the limit used here. llama.cpp runs it as bailingmoe3 from build b11571. Sizes come from a published GGUF file, whose maker reports KL divergence rather than perplexity, so no quality-loss figure is shown.
Model: Ling-3.1-flash
InclusionAI, Ant Group's research arm, released Ling-3.1-flash in October under the MIT license: a 560B-parameter mixture-of-experts reasoning model with 25B parameters active per token, aimed at agents, coding and long office tasks. Only 9 of its 72 layers keep a growing cache storing MLA's compressed vectors, so the full 256K window adds about 3 GB, but at Q4_K_M the weights need about 371 GB at 4K context — more than any single GPU in the index — with the 512 GB Mac Studio's roughly 384 GB of GPU memory holding it only tightly, while the vendor's reference server setup is eight H200s or four GB300s running FP8. The released config sets 262,144 positions with no scaling despite the vendor's 1M-token claim, and llama.cpp runs the model as `bailingmoe3` from build b11571.
Run your AI side-project on zahid.host
EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.