openmoonray: a submodule wrapper around DreamWorks' path tracer
MoonRay is an open-source, award-winning, state-of-the-art production path tracing renderer, initially developed at DreamWorks and an active member project of the Academy Software Foundation.
At a glance
- What is it?
- The openmoonray repository looks small because it is mostly pointers: the README says the actual source code lives in other repositories referenced as git submodules, so a clone without --recurse-submodules gives you the top-level tree without the source code. What the project is underneath is a production path tracer open sourced by DreamWorks, built with CMake presets per platform and still in use on feature film animation.
- Who is it for?
- Adopt MoonRay if you render for animation or visual effects and want a path tracer with production tested materials, a USD Hydra delegate and multi-machine or cloud rendering rather than a preview renderer. Do not start from this repository alone: it holds submodule pointers, CMake wiring and documentation, so budget for a recursive clone and a full source build.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly CMake, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- OpenMoonRay/openmoonray4,755 ★ · +29
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| OpenMoonRay/openmoonray | 4.7k | 4.8k |
29 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
A plain clone gives you an empty tree
The repository states its own role plainly: this is the top-level repository for the MoonRay project, and the actual source code is contained in a number of other repositories referenced here as git submodules. That is why the clone command is not optional:
git clone --recurse-submodules https://github.com/OpenMoonRay/openmoonray.gitA reader who copies the URL and forgets the flag ends up with the top level tree and no renderer, which is the first thing to know before anything else about this project. The `.gitmodules` file at the root is the map. Everything else in the root is build machinery, documentation and policy, which is what a top level repository for a multi-repository project looks like when the code lives elsewhere.
The build is CMake presets, one file per platform
Four preset files sit at the root next to `CMakeLists.txt`: `CMakePresets.json` with `CMakeLinuxPresets.json`, `CMakeMacOSPresets.json` and `CMakeDWAPresets.json` beside it. Preset driven configuration rather than a long command line of defines is the pattern here, and the per platform split means the supported targets are readable from the file names rather than inferred from documentation. Supporting directories follow the same logic, with `cmake_modules/` for the CMake logic itself, `building/` for build related files, and `package.py` as the packaging entry point. The build instructions are not in the repository: the README points to the Building MoonRay document, which covers Linux, MacOS, or a container. Nothing in the repository describes a Windows build.
CPU and hybrid GPU hardware are the two named paths
MoonRay runs on CPU and hybrid GPU (XPU) hardware, and the README pairs that with the rendering modes: local, multi-machine and cloud rendering for interactive and batch rendering. Those two sentences together define what the renderer is for. Interactive rendering means a frame has to come back while an artist is still looking at the viewport, batch rendering means it does not, and a path tracer is expensive enough that the difference decides which hardware you need. Hybrid GPU means the CPU and the accelerator both do work rather than the GPU replacing the CPU, which is why the hardware statement is a list of two and not a single requirement.
The USD Hydra delegate is the studio integration point
Two integrations are named specifically. The first is a library of production tested, physically based materials, which is the part of a renderer that takes the longest to accumulate and the part studios are least willing to replace. The second is a USD Hydra render delegate, which is how a renderer plugs into an existing pipeline rather than asking the pipeline to learn it. The README also says MoonRay supports industry standards and libraries, which is the general statement, and the delegate is the specific one. For anyone evaluating a renderer, that is the part to test against your existing scene description, because a physically plausible render in isolation tells you nothing about whether the delegate handles the scenes you already have.
DreamWorks uses it, and that is stated plainly
MoonRay was open sourced by DreamWorks, where it is in active use for their feature film animation pipeline. The repository description adds that it is an active member project of the Academy Software Foundation, and the README links the foundation's Slack alongside the project website, the discussion forum, the documentation and the releases page. Two consequences follow. The tools a studio needs already exist: regression testing and performance monitoring are named as first-class parts of the project, with regression testing in its own `rats` repository and a render profile viewer for performance. And the surrounding policy files are the ones you would expect from an ASF member project, with `GOVERNANCE.md`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md` and a `THIRD-PARTY.md` for the licence accounting.
Regression tests and profiling are separate tools with their own data
Rather than describing features, the README points at two tools and their documentation, and both have a place in the tree. Regression testing points to the separate rats repository, and `rats` and `testdata/` also appear at the top level. Performance monitoring is a render profile viewer documented under the user reference tools, and `scripts/` is where repository automation lives. `tsc/` and `flowpipeline.yaml` are also at the top level.
The release list carries two version schemes
Three releases appear in the recent list, and they do not share a format. `openmoonray-3.6.0.1` was published on 2026-04-24, then `v2026.29.0` and `v2026.29.1` were both published on 2026-07-17, seconds apart. The later pair uses a calendar style version where 2026 and 29 read as year and sequence, and the two being seconds apart is what a tag and its immediate follow-up look like. A repository carrying both conventions is a small thing that matters if you script a build against a tag, because there is no single place where the version tells you which tree you have. The last recorded push is dated 2026-10-30, later than the newest release, and the licence is the Apache License, Version 2.0.
Editorial conclusion
Adopt MoonRay if you render for animation or visual effects and want a path tracer with production tested materials, a USD Hydra delegate and multi-machine or cloud rendering rather than a preview renderer. Do not start from this repository alone: it holds submodule pointers, CMake wiring and documentation, so budget for a recursive clone and a full source build. Verify first that your platform appears in the CMake preset files, because the build documentation covers Linux, MacOS and a container, and that your hardware path is one of the two the README names, CPU or hybrid GPU.
Frequently asked questions
What is MoonRay used for?
It is an open source production path tracing renderer that efficiently renders images for animation, visual effects and other uses, with an extensive library of production tested physically based materials, a USD Hydra render delegate, and local, multi-machine and cloud rendering for interactive and batch work.
What software does DreamWorks use to animate?
MoonRay is open sourced by DreamWorks, where it is in active use for their feature film animation pipeline. It was initially developed at DreamWorks and the project is an active member of the Academy Software Foundation.
How do I clone openmoonray?
With submodules, because the actual source code lives in other repositories referenced from the top level: git clone --recurse-submodules https://github.com/OpenMoonRay/openmoonray.git. A clone without the flag gives you the top level tree only.
Which platforms can MoonRay be built on?
The build documentation covers Linux and MacOS, or a container. The repository ships CMake preset files for those platforms, and the README does not describe a Windows build.
What hardware does MoonRay run on?
CPU and hybrid GPU (XPU) hardware, with local, multi-machine and cloud rendering available for both interactive and batch rendering.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/openmoonray-openmoonray)Star history chart for your README
[](https://hysenlabs.com/projects/openmoonray-openmoonray)Was this useful?