The homepage for OpenRadioss now carries a single sentence about its future: “The future of Radioss is Simcenter.” The rest of the page explains that after four years of community-driven research, Siemens is “entering a new chapter for the Radioss solver” and consolidating its efforts into the commercial Simcenter portfolio, where users are told they can continue, with an application link for its research and development program. The quiet part is what happened to everything else.
What the record shows
The project started in September 2022, when Altair introduced OpenRadioss as open source: the same input format and source code base as the commercial solver, plus a community of researchers and industry users it promised to bring together. That community ran for four years, on top of a solver lineage that goes back more than three decades in heavy industry. Today the GitHub organization has no public repositories left, and the address where the solver lived, github.com/OpenRadioss/OpenRadioss, returns a 404. Not an archived repository with a read-only sign on the door. Not a redirect. A deletion. There is no archive and no deprecation notice, which are the polite endings; the organization page holds nothing at all.
Why the details matter more than the outcome
That a company folded an open project into its commercial portfolio is not shocking; it is what portfolios are for, and Siemens says the goal is faster innovation for production users. The handling is the part worth studying. An archived repository costs nothing, keeps the history, and tells users the truth about support. A deletion tells them their builds, their bookmarks, and their years of issue reports are simply gone, and that the community was a marketing channel with a lifecycle. Every vendor-led open-source project is one strategy meeting away from this outcome, which is not an argument against using them, just against assuming the repository will outlive the strategy. Clone what you depend on, keep your own builds, and read the license before a workflow depends on someone else’s roadmap.
My read
The openness was the whole pitch at launch, and the closing deserves the same clarity: the solver was real, the community was real, and they were retired without an archive or a farewell. If you ran OpenRadioss in any pipeline, the practical checklist is short: preserve your copy now, and treat the R&D program application as the migration path the company has left you. The transferable lesson for every self-hoster is older than software: the mirror you control is the only copy that cannot be 404ed, and open source without an exit plan is still a dependency on one company’s mood.
Source: the notice at openradioss.org, and the repository’s current status.