# Bear Shifts From MIT to Source-Available in a Bid to Block Hosted Forks
By IO Digest Desk
The creator of Bear said the platform’s license would move away from MIT to a source-available model based on the Elastic License, marking a familiar but still consequential turn in how independent software projects try to protect commercial sustainability.[16839]
The reasoning is personal and economic rather than technical. The author says Bear’s code was originally published under MIT so people could learn from it and audit the platform’s privacy and security claims.[16839] That reflected a classic open-source instinct: visibility builds trust, and permissive licensing lowers the barrier to understanding how a service works.
Over time, however, the author says others forked the project in attempts to launch competing services.[16839] The post describes that experience not as an abstract market outcome but as a direct threat to the creator’s livelihood. After repeated incidents, the author says, continuing with a fully permissive license no longer felt tenable.[16839]
The replacement is described as a version of copyleft based on the Elastic License. According to the post, the new terms remain almost identical to MIT except for one major restriction: the software cannot be provided as a hosted or managed service.[16839] Everything else, the author says, is still permitted.[16839]
That distinction is central to the source-available movement. Developers and users can still inspect the code, study it, and in many cases modify it, but the license blocks what some founders call “free-ride competition” by preventing third parties from turning the same code into a rival cloud offering.[16839]
The Bear post explicitly situates itself within that trend. The author says many other open-source projects have updated their licenses in recent years to prevent this kind of competition.[16839] The pressure, in the author’s view, is becoming stronger in an era of AI-assisted coding, where spinning up a renamed fork and deploying it can be easier and faster than before.[16839]
That AI reference is revealing because it reframes the licensing debate. Historically, source-available shifts were often discussed in the context of large cloud providers monetizing open-source infrastructure. Here, the fear is broader: software replication itself is getting cheaper, and the gap between code access and market entry is shrinking.[16839]
The author also draws a line between code and community. Bear’s code may be one asset, but the post argues that what makes the platform special is its user base and the long-term commitment to maintaining the service.[16839] In that sense, the license change is presented less as an abandonment of transparency than as a way to preserve the conditions under which the original service can keep operating.
For users, the practical outcome is mixed but clear. The code remains available to read and audit, which matters for trust and for anyone evaluating the platform’s privacy or security claims.[16839] At the same time, Bear is no longer open source in the permissive MIT sense if downstream operators cannot legally use the code to run their own hosted alternative.
The supplied evidence supports a precise conclusion: Bear’s creator chose to trade permissive commercial reuse for source visibility and anti-hosting protection.[16839] That tradeoff is increasingly common among software founders who want the credibility of inspectable code without giving rivals an easy path to turn that same code into a competing service. Bear is the latest project to put that tension in writing.
