Why we open-sourced CarphaCom — and what we kept proprietary

Introduction to CarphaCom's Licensing Strategy

At QubitPage SRL, we have adopted a licensing model for CarphaCom that balances the benefits of open-source development with the need to protect our intellectual property and generate revenue. This model, which we refer to as a 'mixed' or 'hybrid' approach, involves making certain components of the CarphaCom platform open-source, while maintaining others as proprietary. In this article, we will explain the reasoning behind this decision and provide an overview of the specific components that are open-source versus those that remain proprietary.

The Open-Source Components: Platform and SDK

The core CarphaCom platform and its associated software development kit (SDK) are made available under an open-source license. This allows developers to access, modify, and distribute the source code, which can lead to a number of benefits, including community-driven development, improved security through transparency, and the ability to customize the platform to meet specific needs. By open-sourcing these components, we aim to foster a community of developers who can contribute to the platform, provide feedback, and help drive its evolution.

The open-source license used for the CarphaCom platform and SDK is designed to be permissive, allowing for free use, modification, and distribution of the software. This approach is intended to encourage adoption and collaboration, while also ensuring that any modifications or enhancements made by the community can be incorporated back into the main codebase.

The Proprietary Components: Federation Hub and Enterprise Plugins

In contrast to the open-source platform and SDK, certain components of CarphaCom are maintained as proprietary. These include the federation hub, which enables the integration of multiple CarphaCom instances, and a range of enterprise plugins that provide advanced functionality for large-scale deployments. The decision to keep these components proprietary is driven by a need to protect our intellectual property and maintain a revenue stream.

The federation hub and enterprise plugins represent significant investments in research and development, and are critical to the overall value proposition of the CarphaCom platform. By maintaining control over these components, we can ensure that they continue to meet the evolving needs of our customers, while also generating revenue through licensing and support agreements.

A Model for Success: GitLab and Sentry

Our approach to licensing is not unique, and is inspired by the models adopted by other successful open-source companies, such as GitLab and Sentry. These companies have demonstrated that it is possible to balance the benefits of open-source development with the need to generate revenue and protect intellectual property. By open-sourcing certain components of their platforms, they have been able to build large and active communities of developers, while also maintaining control over key aspects of their products.

GitLab, for example, open-sources its core platform, but maintains a range of proprietary features and tools that are designed to meet the needs of large enterprises. Similarly, Sentry open-sources its error tracking and monitoring platform, but offers a range of proprietary plugins and integrations that are designed to support advanced use cases.

Conclusion and Future Directions

In conclusion, our decision to adopt a mixed licensing model for CarphaCom is driven by a desire to balance the benefits of open-source development with the need to protect our intellectual property and generate revenue. By open-sourcing the core platform and SDK, we aim to foster a community of developers and drive adoption, while maintaining control over key components such as the federation hub and enterprise plugins. This approach is inspired by the models adopted by other successful open-source companies, and is designed to support the long-term success and sustainability of the CarphaCom platform.

Bottom line

The licensing model adopted for CarphaCom is designed to support the needs of both developers and enterprises, while also generating revenue and protecting our intellectual property. By adopting a mixed approach to licensing, we believe that we can build a large and active community of developers, while also maintaining control over key aspects of the platform.