Brian Clemens Launched OpenCourant After Siemens Shutdown
The community has forked the discontinued OpenRadioss project to ensure continued open-source availability.
Updated on Oct. 4, 2026 in Openings & Closings

Live Poll
Should open-source software projects be protected by law from being discontinued by corporate owners?
Brian Clemens has introduced OpenCourant as a community-led fork following the surprise closure of the OpenRadioss project by Siemens. The new initiative preserves the codebase by utilizing the final publicly available snapshot of the software.
Why it matters
The transition ensures that developers can maintain access to the technology after Siemens discontinued its original project and removed the corresponding GitHub repository.
The new OpenCourant project operates under the GNU AGPLv3 license after replacing the 4-year-old OpenRadioss software. The repository is now managed under the Rocky Enterprise Software Foundation.
The players
Brian Clemens
He is the developer who launched OpenCourant as a community fork to preserve access to the codebase.
Siemens
This multinational technology company originally maintained the OpenRadioss project before deciding to discontinue it.
Rocky Enterprise Software Foundation
This foundation serves as the managing body for the newly established OpenCourant project.
The details
Developers created the fork using the last known snapshot of OpenRadioss to maintain continuity for users. The project is now officially hosted and managed under the Rocky Enterprise Software Foundation.
Timeline
Siemens shut down the OpenRadioss project in October 2026.
Market Landscape
The launch of OpenCourant follows the established pattern of open-source communities reclaiming software assets after corporate project terminations. This move highlights the risks associated with industry-backed open-source projects when corporate priorities shift.
Users of the previous software can continue their work by migrating to the new OpenCourant repository. This transition maintains project availability while shifting governance to the Rocky Enterprise Software Foundation.
The takeaway
Developers relying on corporate-led open-source tools should prepare for potential repository closures by tracking community-led alternatives. Maintaining a local snapshot of project code is a vital practice for ensuring long-term operational continuity.
Further reading
For more information on similar industry shifts, visit our Openings & Closings section.
More information
Access the latest technical updates and documentation on the OpenCourant project page.
Live Poll
Should open-source software projects be protected by law from being discontinued by corporate owners?







