New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Somewhat unclear licensing model #76
Comments
@moqmar Thanks for bringing up this issue. Slash is an open-source, self-hosted link shortener and sharing platform designed to help users save and share links easily. It offers a seamless experience for managing and sharing links, whether for personal or professional use.
As you correctly pointed out, Slash has a Pro version that unlocks additional features, including unlimited members for teams. Our Free version is designed to be sufficient for personal use, allowing users to create an unlimited number of shortcuts with the main restriction being the number of members. However, for commercial use cases such as teams or businesses, we recommend using the Pro version. Open source doesn't mean free.
Features in Custom plan are currently under development. They are mainly using for enterprise version with a larger number of people. Once again, we appreciate your feedback and welcome any further questions or suggestions. Our goal is to provide a comprehensive and user-friendly experience for all our users, whether they choose the free version for personal use or the Pro version for commercial purposes. |
Describe the bug
It's not specifically a software bug, but rather the fact that license management and a pricing page is included in the app, but mentioned nowhere in the README or docs, and it's unclear whether that facilitates an Open Core model (seemingly with the "more" features being completely proprietary, and "pro" completely FOSS?), or - if not - whether the features mentioned in the "more" license actually exist yet (e.g. I couldn't find any reference to SSO in the publicly available code).
I'd love to get some clarification here and ideally also in the README and docs.
Steps to reproduce
Expected behavior
Getting all the information I need about this project's licensing model, to decide whether and how I want to pay for it and/or contribute.
Screenshots or additional context
The text was updated successfully, but these errors were encountered: