Modular MAX 26.7 open on October 22 2026

On October 22, 2026 Modular shipped MAX 26.7 and opened up the last big pieces of its inference stack. Social posts summarizing the release, attributed to Chris Lattner, Modular's co-founder, described Mojo and MAX as "fully open - for development, extension, and commercial use" (we could not open the original post). The company's own blog says something narrower: "MAX is now source available and open to everyone." Developers "can now explore, modify, and extend the entire MAX stack," including the graph compiler, runtime and hardware backends for CPUs and GPUs.

The gap between "fully open" and "source available" matters if you plan to build a product on it. This post sets the claim against the license text in Modular's public repository, so you know what is confirmed, what you can do, and what to read before committing.

Copy

QuestionWhat is claimedWhat we could verifyWhat opened?"The full Mojo language, the MAX graph compiler, MLRT runtime internals, hardware abstraction" (social summary, not verified directly)The repo README lists the graph compiler (/GraphCompiler), runtime (/MLRT), driver, framework and pipelines as source availableIs it "open source"?"Fully open" (Lattner on X)Modular's blog says "source available"; the LICENSE file says portions of MAX use the MAX License, the rest Apache 2.0 with LLVM ExceptionsCommercial use?"Yes"Yes, with conditions: derivative works in object code, redistribution inside applications with "material additional functionality"Is Mojo itself open?YesYes. The compiler has been open since August 2026 (Apache 2.0 + LLVM Exceptions); the standard library since March 2024Any catches?Not mentionedTelemetry rights, a no-reimplementation-via-AI clause, trademark rules for hosted servicesReleaseMAX 26.7The MAX docs list v26.7 as the latest stable release, dated October 22, 2026

What opened, according to Modular

Modular's blog post of October 22 says the release builds on earlier open kernels, models and serving infrastructure, and opens the "remaining core components that power MAX's heterogeneous capabilities: the graph compiler, runtime, and hardware backends." A companion post titled "Modular 26.7: Opening up MAX" accompanies it. The Modular blog is the primary source here; we could read its index summaries and the public repository but not the full posts, so read them yourself. The 26.7 summary calls the new MAX License "intentionally permissive" and says you can use, modify, extend and build commercial products with MAX without licensing fees or royalties, and that source for MAX plugins for other chips, including Qualcomm Dragonfly and Google TPU, is planned "in the coming months."

The modular/modular repository README gives a clear map of what is available and since when:

The README also says "we're actively open-sourcing more of the Modular Platform over time," which tells you the staged approach continues. Our earlier post on the Mojo compiler going open source covers the first half of this story, and the AI chip architectures guide explains why a portable compiler and runtime matter across GPUs, TPUs and accelerators.

This is the part the short posts skip. The repository's LICENSE states that Mojo and its contributions are under Apache 2.0 with LLVM Exceptions, while "portions of the MAX source code and its binary distribution are licensed under the MAX License," and the rest under Apache 2.0. The MAX License file is marked as last modified October 21, 2026, a day before the release, and names the licensor as "Modular Inc, a Qualcomm Company."

Key points from the license text, which we read directly:

None of this makes MAX unusable. It does make "fully open" imprecise: by common definitions such as the Open Source Definition, a license that restricts what you may do with the code (here, the reimplementation and branding clauses) is source available rather than open source. Both statements are true in different senses, and the license file is what a lawyer will read.

If you run inference in-house. You can inspect and modify the compiler and runtime, and ship your own derivatives in compiled form. Read the telemetry section with your security team, because it applies to your use of MAX.

If you sell a hosted inference service. The trademark clause is the one to check. It does not forbid hosting, but it requires prominent Modular branding and approval workflows, which many providers would treat as a business term.

If you ship an app. Embedding runtime pieces is allowed when your app has substantial functionality of its own, in object code with the license copy included.

If you work on a competing runtime. Do not feed MAX source to a model to produce a lookalike. The clause is explicit, and the exception for interoperability is narrow.

If you work on kernels in Mojo. The compiler and standard library remain Apache 2.0, a much simpler position. The README notes that a single Bazel command builds the Mojo compiler and standard library from source.

Compare how other projects frame openness: Kimi K3.1 Pro's promised open weights and Reflection's Beam release under Apache show how model licenses differ from runtime licenses. The same questions apply on the local side, for example llama.cpp-based Windows apps, which sit on a very permissive stack. On hardware diversity, see Cerebras CS-4 for the kind of non-GPU target a portable compiler tries to reach.

Does "source available" change anything for contributors? Yes, in a practical way. Because the license lets you publish modified source in a fork of Modular's official repository to contribute upstream, pull requests are welcome, but a private fork you distribute as a competing product is not. The repo also ships contribution guidelines and an AI tool policy file, which suggests Modular expects agent-assisted contributions and wants them disclosed.

Is it a timeline of steady opening or a sudden flip? Steady. The README dates show the standard library in March 2024, kernels and GPU abstractions in May 2025, the Python framework in November 2025, the Mojo compiler in August 2026, and now the compiler and runtime for MAX in October 2026. Each step moved the line of what stays closed, and the license wording changed one day before this release.

Will Mojo and MAX diverge on licensing? Possibly. Mojo sits on a plain Apache 2.0 with LLVM Exceptions footing, while MAX mixes two licenses. If you only need the language, the simpler license applies.

Details are accurate as of October 23, 2026, based on Modular's blog index, docs and public repository. Licenses change; read the current file before shipping.