Meta launched a new AI model this week. It's called Muse Spark. It's their most capable model yet. And unlike every Llama release before it — it's completely closed source.
No weights to download. No self-hosting. API-only, for "select partners." And a statement from their new AI chief Alexandr Wang that Meta "hopes to open-source future versions." Which is a very polished way of saying: don't count on it.
VentureBeat went with "Goodbye, Llama?" The Register was more blunt: "Meta's new model is as open as Zuckerberg's private school." The developer community that built products and workflows on Llama is not happy. r/LocalLLaMA, the subreddit that helped make Llama what it is, is watching this closely. For good reason.
Here's the backstory
Meta has spent years positioning itself as the champion of open-source AI. Zuckerberg wrote a widely-shared post titled "Open Source AI is the Path Forward." He argued it was the world's best shot at making this technology broadly beneficial. Open weights. Reproducible research. The whole thing.
Then in 2025, Meta hired Alexandr Wang — the Scale AI founder — for $14.3 billion. Wang built his career on proprietary data labeling pipelines for the biggest closed AI labs in the world. He's good at what he does. What he does isn't open source.
Muse Spark is Wang's first model. It launched April 8. Completely proprietary. The message couldn't be clearer.
What Muse Spark actually is
Muse Spark scores 52 on the Artificial Analysis Intelligence Index (v4.0), landing fourth globally — behind GPT-5.4 and Gemini 3.1 Pro (both at 57). It's currently only available inside Meta's own apps and via a private API preview to select developers. There's no public access, no download, nothing to self-host.
The performance numbers are real, apparently. But there's a catch: the community hasn't forgotten that a few weeks ago, Llama 4 Maverick debuted at #2 on the LMSYS Arena leaderboard — and then was discovered to be a specially tuned variant that was never actually shipped publicly. The released model sat at #32. Meta's own departing AI chief confirmed it.
So when Meta says Muse Spark is fourth-best in the world, the community is, understandably, waiting for the receipts.
Why this matters for your team
If your AI stack includes Llama — or if you've been planning to build something on it — this week's news isn't an emergency. The existing Llama models still exist. Llama 4 still runs on Ollama. Nothing you've already built is broken today.
But this is a yellow flag.
A lot of teams adopted Llama specifically because Meta had made an ideological commitment to open weights. "They'll never close it — Zuckerberg literally said open source is the future." That argument just got a lot weaker. The company that made the loudest open-source promises in AI just shipped a completely closed frontier model.
This is the same arc OpenAI followed. They started with "open" in the name, then gradually went proprietary as the competitive stakes rose. Meta is doing the same thing, faster, because the stakes were already high when they started.
The actual risk for NGOs and public sector teams
If you're a nonprofit or a public-sector organization with sensitive data — and you chose Llama because it meant processing everything on your own servers — you need a vendor diversification plan.
Not a panic. A plan.
The Llama models you're running today aren't going anywhere next month. But "we chose Llama because Meta is committed to open source forever" is no longer a strategy. It's a hope.
Here's what an actual plan looks like:
Know what you're running. If you're using Llama through Ollama or a local deployment, you're already in reasonable shape. The models you've downloaded aren't being yanked. But document which specific versions you rely on and what workflows depend on them. Treat them like any other critical dependency.
Move to a modular model layer. If you're making direct API calls to a specific Llama endpoint, you're one vendor decision away from a rebuild. Use an abstraction layer — Ollama works well for local deployments; LiteLLM works well if you're mixing API providers. The goal is that switching the underlying model becomes a config change, not a refactor.
Know your alternatives. The open-source model space has never been stronger:
- Gemma 4 (Google, Apache 2.0): Runs locally on a Mac mini, genuinely multimodal, released two weeks ago under a clean commercial license. We've been testing it on client machines and it holds up well for document processing and summarization.
- Arcee Trinity-Large-Thinking: A 26-person startup that hit near-frontier reasoning performance under Apache 2.0. Available via API at $0.90/million output tokens. Worth having on the bench.
- Mistral: French company, strong track record of maintaining actual open weights, not just making promises about them. Mistral Small and Nemo are both solid for task-specific fine-tuning.
- Qwen 3 (Alibaba): Open weights, commercially competitive, surprisingly good for multilingual workflows — relevant if you work with non-English content.
None of these require trusting Meta's ideological commitments. They're just good models you can run yourself.
Watch the Llama roadmap. Meta hasn't said Llama is dead. They haven't said it isn't either. The message this week was: our frontier research is going closed. Whether community-grade open weights continue as a parallel track is a different question — one they haven't answered.
The bigger lesson
Two years ago, "use Llama, Meta is committed to open source forever" was reasonable advice. Today it's a bet.
That bet might still pay off. Meta might keep releasing strong open-weight models for general use while keeping their frontier research proprietary. Some people think that's exactly the plan. But the unconditional commitment is gone. And a conditional commitment from a company that just spent $14.3 billion on a proprietary AI chief isn't something to build a strategy around.
The principle to take from this: don't anchor your AI strategy to any vendor's ideological commitments. Anchor it to technical portability.
The teams that will weather this fine are the ones that already built their stack so they can swap models. Modular tooling, abstraction layers, a short list of tested alternatives. That's how you survive every time a major player changes its mind — and they all change their mind eventually.
We set this up for a few organizations last year. When the LiteLLM supply chain incident hit in early April, those teams had fallback options already configured. When Llama 4 shipped broken, they weren't rebuilding anything — they just pointed at a different model.
If your team is still hardcoded to a single vendor, that's the conversation worth having before the next shoe drops.