"Open-Weight" Is a Licensing Decision, Not a Freedom Decision: Reading Meta's Muse Spark Open Like an Operator

For builders deciding what to build on. Check the license before the leaderboard.

---

What shipped

On October 15, Meta released the weights for Muse Spark Open — the open-weight version of its Muse Spark model, and, in Meta's own words, "the most capable US open-weight model to date." The numbers are specific: 816 billion total parameters with 42 billion active per token, a 1-million-token context window, and native multimodality — it takes text, images, audio, and video as input and returns text. It is built for coding and agentic work, and Meta optimized it to run locally on Apple's M5 Ultra Mac Studio.

Three days earlier, Meta had released Muse Wonder and Muse Wonder Full, its first frontier models — and those are closed. Muse Wonder is served on Meta's API at $4 input / $20 output per million tokens; Muse Wonder Full is subscription-only inside Muse Code. Independent benchmarks put them at 52 and 56 on Artificial Analysis's Intelligence Index, against 48 for Muse Spark 1.3 six weeks earlier.

So the pattern in one week: the strongest models stay behind a subscription, and the open one is roughly a generation behind. That is the standard playbook, not a scandal. The interesting part is the word "open."

The word doing all the work: "conditions"

Muse Spark Open is genuinely downloadable, free to fine-tune, and free to ship inside your own product. That is not marketing. But it ships under Meta's own Muse Model License, not a standard open-source license, and the grant is explicitly "subject to the following conditions." Three of them deserve a builder's full attention:

  • Attribution is mandatory.* You must "prominently display 'Built with Muse Spark Open'" in the UI, documentation, website, or settings of every product that uses the model or any derivative of it*. Fine-tuned and distilled models count.
  • There is a scale trigger. If you sell access to the model as a service — API-style, where your users receive its outputs — and you (plus affiliates) pass $20 million in gross revenue over any 12 months**, you must notify Meta and sign a separate agreement before continuing. Internal use, research, and using the model as a non-exposed component of your own product are carved out.
  • The Usage Policy rides along** and must be included in copies and derivatives.

Two more facts worth knowing before you commit: the weights are gated on Hugging Face behind a registration form (legal name, date of birth, organization), and Meta claims no ownership of the outputs you generate — the clause builders most want to see, and it is there.

The five-question license check

Before building a product on any model marketed as "open," answer these. They decide more than the benchmark table does.

  • Does the license let me ship a derivative** — fine-tuned, distilled, merged — or only use the base model?
  • Is there a revenue or scale trigger** that changes my obligations as I grow? (For Muse Spark Open: $20M, Model-as-a-Service.)
  • What must I display** to users? (An attribution requirement is a product requirement, not a footnote.)
  • What uses are barred**, if any? (Read the Usage Policy exhibit, not the summary.)
  • Where can it physically run**, and does that match where my data has to live? (An 816B/42B model with a 1M-token context optimizes toward two M5 Ultra Mac Studios and roughly a terabyte of unified memory — a real bar, but also a real answer to "can this run on hardware I control?")

If the answers to 1 and 2 are "no" and "yes," you have not chosen an open model. You have chosen a vendor with a shorter contract.

Why this matters more than the benchmark table

Every release post leads with scores, and Muse Spark Open's are good — Meta's own table puts it well ahead of the other US open-weight models on its agent benchmark, while the "most capable US open-weight model" framing remains Meta's own claim rather than an independently confirmed one. But the scoreboard is the least decision-relevant fact here. It changes monthly. The license is what either lets you ship next quarter or sends you to a lawyer.

"Open-weight" has quietly become two different things: open weights (downloadable, licensed, conditional) and open source. Meta shipped the first and named it correctly. The mistake is to hear "open" and assume the second.

The compressed ending

Read the license before the leaderboard. "Open-weight" tells you the file is available; the license tells you what you are permitted to do with it, and at what scale the rules change. The most capable US open-weight model to date is free to use — within conditions that a growing product will eventually meet, and that a careful builder reads first.

Sources