I'm happy to share that Mojo and MAX are now fully open - for development, extension, and commercial use! This includes the full Mojo programming language, but also the MAX graph compiler, MLRT runtime internals, and hardware abstraction logic.
Get your agents going!👇
Get your agents going!👇
Oct 23, 2026 · 2:32 PM UTC
43
185
1,431
69,822
MAX includes a full suite of modern tech, including automatic kernel fusion and generation, advanced abstractions for tile-based programming, and portability across NVIDIA, AMD, Apple, Qualcomm, TPUs and Trainium.
Support for the first 3 are already public and more is coming.
Support for the first 3 are already public and more is coming.
1
4
93
5,027
Modular and Qualcomm are releasing this to help catalyze an open + unified future for heterogenous compute. We believe the datacenter is going to be filled with chips from multiple vendors, and with a unified standard we can make sure that silicon is the best and multi-vendor.
2
2
62
4,248
We also know that AI isn't limited to the datacenter - it touches everything in our personal lives, in all shapes and sizes. We want everyone to participate in this market, and for innovation to propel new products and experiences for everyone.
1
0
43
2,918
If you'd like to learn more, please take a look at our release blog: modular.com/blog/max-licen…
We also have an all-day tutorial track at the LLVM Developer Meeting on Monday, and we will continue to publish more content and more code as we have time to catch up everything.
We also have an all-day tutorial track at the LLVM Developer Meeting on Monday, and we will continue to publish more content and more code as we have time to catch up everything.
1
4
48
2,842
AI is still in its infancy; we know that AI must be open and community driven. I'd love to work together with you to support new accelerators, new models, and new use-cases.
We are launching a new Alliance (soon) to organize and bring people together:
modular.com/alliance
We are launching a new Alliance (soon) to organize and bring people together:
modular.com/alliance
1
1
39
3,435
If you'd like to learn more, please join us on our forum.modular.com, and check out the open source tab of Modular.com to learn much more. 🚀
0
0
36
2,923
@clattner_llvmternals being open is the sleeper here — agents writing kernels get a lot better when they can read the compiler they're targeting. The big question is whether the community shows up to build backends for the long tail of hardware, or if it stays a first-party story.
1
0
3
387
@ReignSwords We have a bunch of partnership announcements coming as part of the alliance launch: it is incredibly exciting, but will share at the right time!
0
0
5
349
@clattner_llvm Reading the two licences next to each other, Mojo is Apache 2 and MAX is its own thing. You can fork MAX to contribute back but not publish modified source. Is MAX meant to land on Apache too once the alliance governance exists?
1
0
1
713
@AIQuanting Yes, we are trying to reduce fragmentation and encourage people to work together to build a /unified/ platform for the world. That is our mission.
2
0
1
271
@clattner_llvm What is your current ETA on Mojo becoming a full system language?
1
0
0
992
@ChrisPa04674128 Within 6 months. Look at the mojo 1.2 changelog and the roadmap here: mojolang.org/docs/roadmap/
1
0
8
316
@clattner_llvm Open MLRT internals and hardware abstraction logic is the part I'd watch. Users can now see and patch how kernels map to new accelerators instead of waiting on Modular.
1
0
1
583
@iamRushabhSheth We have always known that Modular cannot scale to the complexity of the world’s heterogeneous chips. We need to work together as a community to make this happen together
0
0
2
267
@clattner_llvm Is your recent talk at Oakland available on the YouTube?
I'm interested to see how this stack works with embedded systems
I'm interested to see how this stack works with embedded systems
0
0
0
38
@muthutalks OOPSLA is working on it, but I'm not sure about the timeline on that unfortunately.
0
0
0
23
@the_dismal_tide Hah, ask on the forums and you shall receive! :-)
0
0
4
311
@clattner_llvm Useful distinction: Mojo's compiler is open source; the newly exposed MAX internals are source available. Modified-source distribution is limited to contribution forks. License: modular.com/legal/max-lice…
0
0
2
684
@clattner_llvm "Fully open" with the small exception that it's not open source. This is a "don't compete" freeware licence, not far off from what happened to TF or Redis.
You could have said "open-core" and kept the goodwill.
You could have said "open-core" and kept the goodwill.
0
0
0
29
@clattner_llvm The runtime internals are the interesting bit here. Will contributors be able to reproduce the performance results on ordinary hardware?
0
0
0
15
@clattner_llvm Agents are running to support for custom target hardware...
0
0
0
283
@clattner_llvm the runtime internals too? did not expect that part opened
0
0
0
301
@clattner_llvm @jeremyphoward mojo/MAX as the backend for BPL wen? :D
1
0
1
367
@clattner_llvm Open sourcing the whole compiler stack is a big deal. I've been curious about Mojo for a while, so now there's no excuse not to actually poke around in it.
0
0
1
71
@clattner_llvm open source mojo is likewhen the textbook finallydrops the answer key-everyoneraces to copy the methodsbut still cant explain whythey work. or so they say
0
0
1
86