Repository navigation
Ory Open Source release cadence from 2027 #4140
Replies: 2 comments 2 replies
|
I find it difficult to reconcile "doubling down on open source" with a policy that potentially leaves OSS users exposed to known security vulnerabilities for months. Hydra is security-critical infrastructure. In a world where new vulnerabilities are discovered constantly, expecting anyone to run an OAuth2/OIDC server in production without timely security fixes is simply unrealistic. I fully understand the need for a sustainable business model. Take Bitnami, for example. They restricted access to their prebuilt container images, but the source code remains publicly available and up to date. The community can still build the images themselves. That's a commercial decision I can understand. But withholding security fixes at the source-code level is fundamentally different. If a vulnerability has already been fixed internally, but the fix won't be publicly available for months, OSS users cannot even build a patched version themselves. And that raises a genuine question: Would you feel comfortable running such a product in production, knowing that critical security fixes might already exist but remain unavailable to you for months? That's what makes this particularly disappointing. It doesn't feel like a stronger commitment to open source. It feels like the community is being asked to accept security risks that would be unacceptable for any production-grade identity infrastructure. I wish this trade-off were acknowledged for what it is, rather than presented as doubling down on open source. |
|
One question absent from the original discussion was around how this affects open source contributors. In this new world, where the source is not revealed until a new release is cut, how are community PRs addressed? How can the community build against a source it cannot see? |
Uh oh!
There was an error while loading. Please reload this page.
We published a post on how Ory Open Source releases work going forward: Doubling down on open source
tl;dr: starting in 2027 Ory releases twice a year, once in each half, and the first one lands in the first half of 2027. The public repositories get the full source with each release instead of commit by commit, and every release ships under Apache 2.0 with its security advisories.
If you need CVE fixes between releases, the Continuous Security License gives you patched builds on the same timelines as the Ory Enterprise License.
Questions or feedback: reply here or ask in the community Slack (https://slack.ory.com/).
All reactions