Upstream said "not doing it," and the fork that caught the overflow got 800+ stars: how PolyStrata took in the people Strata turned away

This autumn's hottest local inference engine, Strata, only ran one model. Someone asked whether it could run DeepSeek or GLM, and the maintainer closed the request with one line: "not planned." Five days later, a developer who called themselves a CS student created PolyStrata: Strata left intact, with a separate engine written to run the rejected models. 863 stars in a month. Below: where its stars came from, why it holds up, and how to use the same playbook if you want a project that gets stars too.

An issue that got closed

On 2026 Sep 30, user uvhat opened issue #310 on the Strata repo with one line: "Maybe there's room to run DeepSeek Flash V4 0731 at iq2..iq3?" The next day someone replied: "Or GLM 5.3 Flash <3." The same day, maintainer Niko1221 replied: "Other MoE architectures (DeepSeek, GLM) are not on the roadmap: the kernels and packaging format are built around this one model. Closing."

Strata had only been listed for a week at that point, gaining over a thousand stars a day (by 11-06 it had 40,493 stars, 6 weeks after its listing, per GitHub). What it does is make large MoE models like Qwen3.8-Flash-Next run fast on a home PC with a 12 GB GPU. Many of the people who came in didn't have Qwen3.8 models, or only had a GPU with 8 GB.

In Oct 6, GitHub user VecSzn created PolyStrata. Its first FAQ entry is "Why not contribute to Strata directly?" The answer quotes the refusal from #310 and then says: "So other models get their own engine, sitting next to Strata."

What it is

A local inference program that runs large models on an ordinary computer, installs in one click on Windows and Linux, and exposes an OpenAI / Anthropic-compatible endpoint on the machine, so coding assistants like Claude Code and Cursor can connect directly.

It has two engines: Qwen3.8-Flash-Next runs on Strata's engine, unmodified. The other eleven models (GLM 5.3 Flash, DeepSeek V4 Flash, Qwen3.6-35B-A3B, Gemma 4, LFM2.5, and others) run on the engine the author wrote. That engine does one specific thing: MoE models keep most of their "experts" in system RAM, and the frequently used ones get cached in VRAM. The result is that a 8 GB GPU can run 35B models. The README cites an RTX 4070 laptop (8 GB) generating 3.6–94 tokens per second on Qwen100.

The first animated GIF in the README shows Claude Code running on that 8 GB laptop, adding a parameter to a small program, writing tests, and running them.

Where the stars came from

Daily stars (GitHub, as of 11-06):

It's getting 25 to 40 a day, peaking at +60 on 10-20. No single spike. It doesn't show up on HN, X has barely mentioned it in 30 days, and no media has covered it. What the curve says: nobody set this off. It sits next to a big traffic pool and picks up a little every day.

The first slice, and the biggest, is Strata itself. Hundreds to thousands of people a day come to Strata wanting to run LLMs locally. Some of them, asking other models or searching "Strata GLM" or "Strata 8GB", end up hitting PolyStrata. PolyStrata's daily new stars run about 4% to 6% of Strata's (my estimate, from comparing the two repos' daily star counts). On Oct 12 the author opened issue #2186 on Strata, politely asking whether a line pointing to them could go in the README or FAQ: "#310 You said you're not doing other architectures, which makes sense..." Maintainer 10-19 closed it with a blanket "resetting the tracker, more than 1,300 issues is too many to go through," and no link was added. But the issue sat there for a week, and anyone browsing Strata's issues could see it.

The second source is Reddit's r/LocalLLM and r/LocalLLaMA. The launch post was titled "PolyStrata: Strata with four more MoE models." Later, users posted their own demos running it with Cline, plus threads like "Which model for 16 GB?" and "How to switch models in PolyStrata." In the local-LLM community it's already mentioned alongside Strata. Post upvote counts weren't retrieved (unverified).

The third source is long-tail tutorial and aggregator sites. In 10-22 an English step-by-step tutorial appeared (about 365 stars at the time), followed by a Korean guide, several open-source directory sites listing it, and a YouTube video titled "PolyStrata GitHub Explained." Each brought in only a few people, but together they make the steady curve.

The fourth source is contributors. A port to AMD GPUs, a port to Intel Arc, and a community benchmark page were all built by outside people. One contributor posted on LinkedIn about a cache optimization they ported in, which made things about 20% faster. Each contributor shares it with their own circle once.

There was also a hiccup: around Oct 13, the GitHub repo disappeared. The author put the source on Hugging Face as an emergency backup, someone asked on Reddit "Where did PolyStrata go?", and someone posted the mirror link under Strata's #310. The cause wasn't found (unverified), and it was later restored. In Nov 4 the repo moved from the author's personal account to the simplexai-labs organization, and daily stars didn't change before or after the transfer.

Why picky people are willing to star it

The people who run models locally are among the hardest audiences in open source: they own the hardware, read benchmarks, and re-run them themselves. PolyStrata got several things right:

• Every number can be verified. Each speed in the README states which machine, which file, and which prompt. The benchmark scripts are in the repo, so anyone can re-run them with one command. Outputs were checked token-for-token against llama.cpp. It claims "on the same GGUF, prompt processing is 2.7–3.5× faster and generation 1.5–1.8× faster," with the logs from both runs attached.
• It's gracious toward upstream. It keeps Strata's git history, merges in every Strata release, leaves Strata's engine untouched, and says in the FAQ: "If Strata starts accepting other architectures, I'd like this work to go upstream, and I'm happy to help." That makes the community see it as a legitimate fork, not someone riding the name.
• The bar is lower. Strata needs a 12 GB GPU. PolyStrata's small models run on 8 GB, which opens it up to a much bigger group of people.
• Installation is handed to your AI. The first install method in the README is to paste a block of text into Claude Code, Cursor, or Codex and have it follow the install doc in the repo. The README is in seven languages, Chinese included.

Its weak spots

The moat is shallow. Its reason to exist is "upstream won't do it," and upstream is doing it: Strata's README now lists Qwen3.6-35B-A3B and DeepSeek V4.1 Flash, and PolyStrata's own FAQ mentions that GLM and DeepSeek PRs were raised on the Strata side. Once upstream fully supports multiple models, most of PolyStrata's reason for existing is gone. Last week's additions were already lower than the week before (220 vs 258, per GitHub).

The spot is crowded too. Since October, Strata has spawned a string of forks: Xolotl (462 stars), focused on DeepSeek V4.1 Flash; strata-nvfp4 (4 stars), which only does NVFP221 quantization; and UnbiasedStrata (219 stars), a fork of PolyStrata that swaps the Python shell for C++, whose author live-streams coding on YouTube. Beyond those are the veterans: llama.cpp (130k stars), ollama (180k stars), and ktransformers (nearly 20k stars).

If it were you

Verdict: B. The playbook is very clear and can be copied: find an open-source project that's exploding, do the thing its maintainer publicly refused, quote the refusal as the first line of your FAQ, and stay gracious toward upstream. But Strata's slot is already taken by PolyStrata and a string of forks, upstream is catching up, and this kind of project demands real skill. PolyStrata wrote CUDA inference kernels, not a thin wrapper.

Who it suits: people who can work at that depth. For a project like PolyStrata, that means someone who knows CUDA and inference optimization and has the hardware to re-run benchmarks over and over. On a different parent project, it means a developer who can reach parent-level quality in that domain within a week or two.

Who it doesn't suit: anyone wanting to build yet another Strata fork, since you'd be the fifth or sixth one in; anyone who can only wrap existing code and can't produce verifiable numbers, because this community will call it out immediately; and anyone hoping to earn money from it, since the stars here are reputation and a track record, not revenue.

How to do it, ranked by how worthwhile:

1. Swap the parent project, do the same thing. Look at the open-source projects that have grown fastest in the last month or two (GitHub Trending, Reddit subs for each domain), read their closed issues, and find the requests where several people upvoted and the maintainer explicitly said no: support for other models, other platforms, other languages, lower hardware. The hotter the parent and the more explicit the refusal, the more people you catch.
2. Build the piece nobody in the Strata ecosystem has built. For example, multi-model support on Mac (Apple Silicon): PolyStrata only runs Qwen3.8 on Mac. Or small-VRAM cards at 6 GB and 4 GB: its FAQ says it was only tested above 8 GB, with 6 GB untested. This bet only works if upstream doesn't fill the gap soon.
3. Build accessories for the parent. Benchmark aggregation pages, a GUI for switching models with one click, and config for plugging into coding assistants. The star ceiling is low, but the bet is almost risk-free.

How to get users. Follow the order. First, politely comment on the parent's issue saying what you built and that you'll merge back. Then post in the community where the parent's users cluster (for this one, r/LocalLLaMA), with a title that states "parent + what you added" plainly. In the README, include a real-device demo GIF and a benchmark table with machine models, plus a reproducible script. Write an install doc that an AI coding assistant can follow. Tutorial sites and directory sites will index you on their own.

When is the window. The sooner the better. This play works while the parent is still exploding and hasn't filled the gap yet, which usually means one to two months after the parent's repo goes up. For the Strata slot, that window is mostly closing.

What would mean you read it wrong. (1) PolyStrata keeps gaining dozens of stars a day after Strata fills in multi-model support. That would mean it runs on its own engine speed and community, not just spillover from upstream, so a head-on faster MoE engine is a wider path than estimated here. (2) The reverse: if it drops to single-digit stars a day by late November, spillover traffic has a shorter life than assumed, so when you switch parents, pick needs that upstream clearly won't fill. (3) The rejected need you found gets no replies after two weeks of posting. That would mean the people who upvoted were just clicking in passing, and the need is smaller than it looks.

Data and sources

GitHub: the simplexai-labs/PolyStrata repo page, README, docs/FAQ.md, and daily stars (10-17 to 11-06); Niko1221/Strata issue #310 (2026-09-30 open, 10-01 closed) and #2186 (10-12 open, 10-19 closed) and their star counts; star counts for Xolotl, strata-nvfp4, UnbiasedStrata, llama.cpp, ollama, and ktransformers. Reddit r/LocalLLM and r/LocalLLaMA post titles (search snippets). The aifrontierpost tutorial (10-22), the localai.co.kr Korean guide, the aibynick.com record on the takedown and Hugging Face mirror, and a contributor's LinkedIn post. Where the text says "inferred" or "unverified", it is inferred or unverified.