Announcing Rosetta's Transition to a Public Repository (including Licensing Changes)

Dear Rosetta Community and users of Rosetta,

We're excited to announce that we have moved the Rosetta code repository to a public repository! We have made this move to honor our longstanding philosophy of sharing our work publicly and making it broadly accessible to scientists. This change marks a new chapter for Rosetta, where future developments will be more collaborative and accessible. 

This move required crucial changes to our workflow and licensing terms that are designed to streamline contributions to our platform. The new repository is accessible at

Licensing adjustments:

The repository's public status means that non-commercial users no longer need to explicitly sign up for a license to access Rosetta. However, despite being publicly accessible, Rosetta is not open source; redistribution restrictions and other licensing restrictions remain in place for all users. For our commercial users, the existing license will continue as before, with no immediate changes. New commercial users will also be required to purchase a separate commercial license.

Code contributions:

With the repository now open, we welcome code contributions from both academic and commercial users outside of the Rosetta Commons. To contribute, non-Rosetta Commons contributors will first need to sign a Contributor License Agreement, ensuring a smooth integration of contributions into the Rosetta codebase. Scientists in Rosetta Commons labs remain able to contribute under the terms of their Institutional Participation Agreement and individual Developers Participation Agreement.

Workflow changes:

As previously announced, the old Rosetta/main repository is now closed for merges but will remain available to Rosetta Commons members. To align better with now-standard practices, we will now use the fork model workflow with the new RosettaCommons/rosetta repository. 

  • If you just want to use Rosetta, you can clone the new repository using standard Git/Github tools. 

  • If you want to develop Rosetta, you should fork the repository before cloning it to your local machine. You can then use the traditional branch model workflow that we've been using for many years, on your private fork. Contributions back to the main RosettaCommons/rosetta repository will be managed through pull requests. We are currently addressing some minor technical issues related to forks and automated testing and will update affected developers directly.

Should you have any questions or require further assistance, please feel free to reach out via Slack or email Rocco ( or @rmoretti) or Sergey ( or @sergey) for support.

The Rosetta Commons open repository team

(Rocco Moretti, David Nannemann, Sergey Lyskov, James Vasile)


Popular posts from this blog

Future of Rosetta Task Force Update

De novo proteins and where to find them - RosettaCon 2022

Proposal for the Future of Rosetta