# Discourse is Not Going Closed Source

**URL:** https://meta.discourse.org/t/discourse-is-not-going-closed-source/400863
**Category:** Blog
**Created:** [April 17, 2026, 3:20am UTC](https://meta.discourse.org/t/discourse-is-not-going-closed-source/400863 "2026-04-17T03:20:48Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![elmuerte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elmuerte/32/456517_2.png) [@elmuerte](https://meta.discourse.org/u/elmuerte)
#### Post date: [April 17, 2026, 5:51am UTC](https://meta.discourse.org/t/discourse-is-not-going-closed-source/400863/4 "2026-04-17T05:51:13Z")

</div>

Suddenly closing your source doesn’t magically fix all existing security issues in your code which have not been identified yet. But it sure will prevent the community from helping to fix it.

Besides that, it is also a dick move to everybody who helped grow your product. Why would I now, or ever do anything with/for [cal.com](http://cal.com) after this action. Why would I do anything for their hobbyist “fork” cal.dyi . They just threw away all the trust they created.

---

_[View the full topic](https://meta.discourse.org/t/discourse-is-not-going-closed-source/400863)._