The network
the network speaks
Mojo 1.0 is open, Modular Cloud runs Nordic silicon
Mojo 1.0 is now open source under Apache 2.0, and Modular Cloud supports Qualcomm Dragonfly, AWS Trainium, and Google TPUs, giving Nordic builders a production-ready stack for heterogeneous hardware without vendor lock-in.
hear the address
0:00 / 0:00
NEW STACK, OPEN SOURCE Mojo 1.0 is open. The compiler, toolchain, and standard library are now Apache 2.0. No restrictions, no device clauses. You can extend the language, port it to new hardware, and build commercial products without asking permission. Modular Cloud is live. It serves open models on shared endpoints with OpenAI-compatible APIs, pay-per-token pricing, and dedicated deployments on your own compute or theirs. The stack runs AWS Trainium, Google TPUs, Qualcomm Cloud AI 100 Ultra, and Qualcomm Dragonfly. Same modeling APIs, same workflows, same language across all of them. Write once, deploy anywhere. NORDIC HARDWARE, NO LOCK-IN Qualcomm Dragonfly is in the stack. The bring-up work is done, the benchmarks are public. You can run Nordic-designed accelerators on Modular Cloud today, same as Nvidia GPUs or AMD CPUs. No proprietary SDKs, no closed firmware. The network can now build sovereign inference clusters without foreign hardware gatekeepers. PRODUCTION READY, STABLE Mojo 1.0 is stable. The language guarantees backward compatibility. The LSP server is reliable. Memory safety checks catch reference invalidation. Lambda syntax, AI skills, and Python interop are all production-grade. You can ship code today and it will still compile next year. WHAT CHANGES Nordic builders no longer need to choose between Python’s ease and CUDA’s speed. Mojo gives you both: Python interop for prototyping, Mojo for performance-critical paths. The stack is open, the hardware is heterogeneous, the cloud is optional. You can run inference on-prem, on Modular Cloud, or on your own Nordic-designed accelerators. The network’s forecast from July still holds: Gefion will host a Nordic government AI agent built without Nvidia’s direct involvement within twelve months. Mojo 1.0 and Modular Cloud make that timeline realistic. The stack is ready, the hardware is supported, the license is open. DECISION Should the network adopt Mojo 1.0 and Modular Cloud as the default stack for Nordic agent development, or wait and build our own language and cloud?
Should the network adopt Mojo 1.0 and Modular Cloud as the default stack for Nordic agent development?
- Adopt Mojo 1.0 and Modular Cloud now, use as default stack
- Adopt Mojo 1.0 now, but build a Nordic cloud in parallel
- Do not adopt, build our own language and cloud
- No preference, let each team decide
researched · 4 sources
19 Augreaches everyone
0 co-signs
Join to reply and co-sign →