Why Business Source License 1.1?
TrustRosie.io is developed under the Business Source License 1.1 (BUSL-1.1), a source-available license that balances three goals: transparency, community participation, and sustainable development.
What BSL 1.1 Means
- Source code is publicly viewable and auditable. Anyone can review the implementation, verify security practices, and understand how the platform works. There is no black box.
- Community contributions are welcome. Developers can study, fork, and improve the codebase.
- Competing hosted services require a commercial license. This prevents well-funded corporations from offering a competing Rosie-as-a-Service without contributing back.
- Code automatically converts to Apache 2.0 after a set period (typically 4 years from each release). Every line of code has a guaranteed open-source future.
Who Can Use TrustRosie.io Under BSL 1.1
- Organizations for internal use
- Service providers using Rosie to serve their clients
- Researchers and educators
- Contributors improving the platform
- Non-profit and open-source projects
The only restriction: you cannot offer TrustRosie.io as a competing hosted service without a commercial license.
Why Not Pure Open Source?
The history of open-source infrastructure software shows a recurring pattern: a project builds community and adoption under a permissive license, then a well-funded cloud provider launches a competing managed service that captures the commercial value without contributing back. The original creators struggle to fund development, and the project stagnates.
BSL 1.1 is a proactive response to this pattern. It provides the transparency and community benefits of open source while ensuring that the investment in development is protected long enough to build a self-sustaining ecosystem.
Companies like MariaDB, CockroachDB, Sentry, and HashiCorp have adopted BSL 1.1 successfully, demonstrating that source transparency and sustainable business models are not mutually exclusive.
Alignment with Cooperative Values
The Contributory Ecosystem Model rewards participants based on the value they create. BSL 1.1 protects that value from extraction by external corporations:
- Members benefit, not external corporations. Revenue from the platform flows back to contributors and the organizations that operate nodes.
- Democratic control is maintained. The ecosystem's Governing Body -- elected members who set governance policies -- ensures the canonical platform cannot be co-opted by forking and out-investing the community.
- Eventual full openness is guaranteed. The automatic conversion to Apache 2.0 means the code becomes fully open source after the protection period.
Intellectual Property for Contributors
Contributors to the TrustRosie.io knowledge base retain full ownership of their intellectual property. The platform tracks attribution and ensures fair compensation:
- Copyright remains with the creator. Contributing content to the network does not transfer ownership.
- Licensing terms are set by the creator. IPR owners define their own rates and terms for how their content can be used.
- Attribution is transparent. When content is used in a response, the system tracks and reports which sources contributed.
Source Transparency Builds Trust
For organizations evaluating TrustRosie.io, source availability means:
- Security is verifiable. Review the access control implementation, data isolation, and encryption practices directly in the code.
- No vendor lock-in. If you need to self-host, the code is available. Your content is always portable.
- Privacy claims are auditable. Verify that tenant isolation and data protection work as documented.