On May 5, 2026, a Miami startup called Subquadratic walked out of stealth with a $29 million seed round and a model named SubQ that, on paper, sounds like the most aggressive long-context claim of the year:
- A 12 million token context window, about 9 million words, or roughly 120 books.
- 52× faster than FlashAttention at 1 million tokens.
- Less than 5% of the cost of Claude Opus 4.6 at the same context length.
- ~1,000× compute reduction at the full 12M-token window.
- 95% on RULER 128K, edging Claude Opus, at $8 per run vs. ~$2,600 for Opus.
- 81.8% on SWE-Bench Verified, a hair above Opus 4.6's 80.8%.
If even half of that survives independent testing, SubQ is the most consequential architectural launch since DeepSeek V3. And within hours of the announcement, the AI community split almost neatly into two camps: people who think this is the real deal, and people who think we just watched another Magic.dev rerun in real time.
A widely shared reaction summed it up bluntly: SubQ is either the biggest breakthrough since the Transformer, or it is AI Theranos. There is no in-between.
Let's walk through what was actually announced, what is being challenged, and what builders should do about it.
What SubQ actually is
Subquadratic was founded by Justin Dangel (CEO, five-time founder) and Alexander Whedon (CTO, previously a software engineer at Meta and Head of Generative AI at TribeAI, where he led more than 40 enterprise AI implementations). The team includes 11 PhD researchers and engineers with backgrounds at Meta, Google, ByteDance, Adobe, Microsoft, Oxford, and Cambridge. The investor list reads like a startup highlight reel: Tinder co-founder Justin Mateen, ex-SoftBank Vision Fund partner Javier Villamizar, plus early backers of Anthropic, OpenAI, Stripe, and Brex.
The technical claim sits on one acronym: SSA, Subquadratic Sparse Attention.
In a standard transformer, attention compares every token in a sequence with every other token. That is what makes it powerful, and it is also what makes long context expensive. Double the input, quadruple the work. This is the wall every frontier lab keeps slamming into.
SSA replaces the dense attention matrix with a content-dependent selection mechanism. For each query token, the model picks a small subset of positions in the sequence that actually matter, then runs exact attention on just those. The company reports this drops the complexity to roughly O(n), linear, not quadratic.
The pitch is straightforward: dense attention is wastefully quadratic. In trained models, most attention weights are near zero anyway. Why compute all the comparisons that don't matter? Subquadratic's answer: don't.
The product surface, all currently in private beta:
- SubQ API: OpenAI-compatible, 1M context in production preview, 12M in research mode.
- SubQ Code: a CLI coding agent that loads entire repos into context.
- SubQ Search: a long-context research tool, free during the beta.
Architecturally interesting. Strategically aggressive. And, depending on who you ask, possibly oversold.
Then the CTO confirmed something awkward
The first crack in the marketing wall opened within hours of launch. AI engineer Will Depue posted that SubQ was almost surely a sparse-attention fine-tune of Kimi or DeepSeek, meaning the impressive base capabilities were inherited from existing open-source weights, and the SSA contribution was the sparse-attention layer added on top.
Depue could have been wrong. He was not.
CTO Alex Whedon confirmed it on X: the company is using weights from open-source models as a starting point, framed as a function of their funding stage and company maturity.
That admission matters. There is nothing wrong, technically or ethically, with starting from an open-weight base. Kimi K2.5 is licensed for exactly this kind of work. But there is a meaningful gap between "we built a fully sub-quadratic frontier model from scratch" and "we fine-tuned someone else's pretrained model with our sparse-attention layer." The first is a redesign of how attention works at frontier scale. The second is a research contribution riding on someone else's pretraining bill.
The launch coverage leaned heavily on the first framing. The reality, by the CTO's own account, is closer to the second.
Depue escalated from there, arguing the O(n) scaling claims and the reported speedups don't line up cleanly, and calling the communication either incredibly poorly explained or simply not real.
The benchmarks: strong, narrow, and conveniently chosen
Subquadratic published results on three benchmarks. Read them carefully.
Three things stand out.
First, RULER at 128K is essentially saturated. Every frontier model is at 94 to 95%. Matching Opus there is more about not regressing than winning. Subquadratic positioned this as a headline number, but it is the easiest of the three benchmarks to clear.
Second, SubQ trails on the harder long-context test. MRCR v2 is the more honest proxy for real-world work, finding multiple pieces of evidence scattered across a million tokens and combining them into one answer. SubQ scores 65.9%. GPT-5.5 scores 74.0%. The production model is meaningfully behind the current frontier on the benchmark that most resembles the use case the company is selling.
Third, the comparison set is one version behind. Subquadratic benchmarks against Claude Opus 4.6 (80.8% on SWE-Bench Verified). The current frontier is Opus 4.7, which reportedly scores around 87.6% on the same benchmark. SubQ's 81.8% looks competitive when staged against last quarter's Opus and meaningfully behind when staged against this quarter's. Picking the older comparison isn't dishonest, but it's not accidental either.
Developer Stepan Goncharov's reaction was that the benchmarks looked very interesting and very cherry-picked. Other commenters described them as suspiciously perfect. According to coverage in The New Stack, each benchmark was run only on the configuration where it would look best. There is no MMLU. There is no HELM. There is no broad capability suite. There is no full needle-in-a-haystack chart at every position across the 12M window.
There is also no technical report. There are no public weights. There is no peer review. The model card is, per Subquadratic's own site, "coming soon."
The Magic.dev problem nobody wants to talk about
Here is the comparison that should be on every reader's mind, because the parallels are uncomfortably exact.
In August 2024, a startup called Magic.dev announced LTM-2-mini: a 100-million-token context window with claimed 1,000× efficiency gains over Llama 3.1 405B at that context length. Magic raised roughly $465 million on the strength of those numbers, a $117M Series B in February 2024 followed by a $320M round in August led by Eric Schmidt with Sequoia, Atlassian, and others.
Nearly two years later, there is no public evidence anyone outside Magic.dev is using LTM-2-mini or its 100-million-token context for real work. The weights are not public. The independent benchmarks never came. The model never shipped to a meaningful user base.
Now read the SubQ launch with that history in your head:
- Frontier-scale long-context claim.
- ~1,000× compute reduction claim.
- No open weights.
- No full technical report at launch.
- Reported $500M valuation on a seed round.
- Three private-beta products gating access.
This is not a guarantee SubQ is vaporware. Whedon is a credible engineer, the team is real, and the architectural direction, content-dependent sparse attention, is exactly the line of research the field has been pushing on. But the structural similarity to a launch that did not deliver is too clean to ignore. VentureBeat drew the parallel directly. The Reddit r/LocalLLaMA thread hammered it for hundreds of comments. It is the elephant in the press release.
One developer's argument is the sharpest version of this critique: if SubQ truly costs less than 5% of Opus and reduces compute by 1,000×, the company should have no problem serving it to anyone who shows up. Why gate the API behind early-access forms?
There is no comfortable answer to that question.
The defenders have a point too
To be fair to Subquadratic, the dismissive read is also incomplete.
AI researcher John Rysana pushed back on the Theranos framing, arguing that the work looks like sub-quadratic attention done well, that this is genuinely meaningful for long-context workloads, and that the odds of it being fraudulent are extremely low. Tech commentator Linus Ekenstam said he was intrigued enough to wait for real-world implications, particularly in complex AI-powered software workflows.
CEO Justin Dangel's response to the noise was disarmingly reasonable: extraordinary claims will be greeted with skepticism, and they should be. He said more technical papers and product releases are coming in the months ahead, and that the team hopes the community will be satisfied.
That is the right tone. Whether the substance arrives on time is a different question.
There is also a version of this story where SubQ is partly right and partly oversold, and the partly-right part still matters. If SSA is a real and useful sparse-attention layer that integrates cleanly with strong open-source base models, it could end up as a standard component of hybrid architectures the way mixture-of-experts went from suspicious to standard practice in about eighteen months. The 1,000× headline gets walked back. The 50× number probably survives in narrower domains. The architecture quietly becomes part of the toolkit.
Why this matters even if you never use SubQ
Long context is the real frontier right now. Every major lab advertises a million-token window, but almost none of them are actually good at using all of it. On MRCR v2, GPT-5.5 leads at 74%. Claude Opus 4.7 sits at 32.2%. The gap between advertised context and useful context is the unsolved problem in production AI.
Whoever cracks sub-quadratic scaling at frontier quality unlocks a different category of product:
- Coding agents that hold an entire repo, every PR, and months of agent state in one prompt.
- Legal and financial work that ingests full case histories or filings without RAG plumbing.
- Research tools that reason across an entire literature instead of retrieved chunks.
- Long-running agents that don't lose their memory every twenty minutes.
These use cases are technically possible today. They are not economically possible. SubQ's actual contribution, if it holds up, is moving the line from technically-possible to economically-default.
That is why the response has been so loud. The prize is enormous. The marketing is ahead of the evidence. The pattern looks familiar. All three of those things can be true at once.
What to do about it as a builder
If you ship long-context AI workloads, here is the honest playbook for the next quarter:
- Request early access if 1M+ token workloads are a real part of your stack. The cost claim, even discounted heavily, is worth a calibration test.
- Run your own benchmarks. Don't rely on RULER 128K, it's saturated. Run MRCR-style multi-evidence retrieval on a corpus you understand. Test at 500K, 1M, and as far past that as the API will let you.
- Wait for the technical report and the model card before designing anything important around SubQ. Subquadratic has promised both.
- Watch for independent benchmarks from labs that aren't paid by Subquadratic. That is the line that separates Magic.dev from DeepSeek V3.
- Treat the 1,000× number as marketing until proven otherwise. Treat the 50× number as plausible. Treat the SSA mechanism itself as worth reading about regardless of how the company performs.
The bottom line
SubQ is the most architecturally interesting LLM launch since DeepSeek V3, and it is also the most marketing-forward one. The team is credible. The architectural direction is real. The CTO has already publicly walked back the "fully built from scratch" framing in favor of "fine-tune of an open-source base." The benchmarks are narrow. The weights are closed. The technical report is not out. The product is gated. The valuation is rich. The Magic.dev parallel is too tight to dismiss.
The honest read is that the marketing is ahead of the evidence, and the gap will close one of two ways in the next quarter.
Either the technical report, the weights, and the independent benchmarks land, and SubQ permanently changes how long-context AI gets built. In which case every frontier lab quietly accelerates its own sparse-attention research and we look back on May 2026 as a turning point.
Or the gap becomes the story, and SubQ joins a long list of architectures that worked beautifully in a press release and disappointingly in production.
For now: cautious watch, early-access form filled out, and a healthy refusal to bet the roadmap on a paper that hasn't been published yet.
The race to sub-quadratic AI is officially on. Whether SubQ is the model that wins it, or just the one that fired the starting gun, is the question the next ninety days will answer.