-
Notifications
You must be signed in to change notification settings - Fork 5
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
Create license.md #82
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
--- | ||
title: "FalkorDB License" | ||
nav_order: 1100 | ||
description: "Understanding the FalkorDB License" | ||
--- | ||
|
||
# FalkorDB License | ||
|
||
FalkorDB is licensed under the the [Server Side Public License v1 (SSPLv1)](https://github.com/FalkorDB/FalkorDB/blob/master/LICENSE.txt). | ||
|
||
## FalkorDB Licensing FAQ: Understanding the SSPLv1 License | ||
|
||
1. What does it mean that FalkorDB is licensed under SSPLv1? | ||
|
||
The Server Side Public License (SSPLv1) is designed to ensure that if you use FalkorDB as part of a service you make available to others (e.g., in the cloud or as an API), you are required to make the source code of your complete service available under the SSPLv1 license. This is similar to GPL but extends to server use. | ||
|
||
2. Can I use FalkorDB in my internal projects without open-sourcing my code? | ||
|
||
Yes! If you're using FalkorDB for internal purposes only—within your organization without providing it as a service to external users—you are not required to open-source your code. | ||
|
||
3. Can I use FalkorDB in my closed-source project without open-sourcing the entire project? | ||
|
||
If your closed-source project does not make FalkorDB available to external users as part of a service, you can use it without open-sourcing the rest of your code. However, if you provide FalkorDB as part of a service, the SSPLv1 requires you to open-source your codebase associated with the service. | ||
|
||
4. How does the SSPLv1 license affect my commercial application that uses FalkorDB? | ||
|
||
You can use FalkorDB commercially, but if your application provides FalkorDB as a service to users, then under SSPLv1, you must open-source the code that enables this service. For companies needing a commercial license to avoid this requirement, please contact us to discuss options. | ||
|
||
5. What if I want to use FalkorDB in my product but don’t want to release my source code? | ||
|
||
If you’re providing a service with FalkorDB and prefer not to release your source code, reach out to our team. We offer commercial licensing options that can accommodate these needs without the open-source requirement. | ||
|
||
6. Does the SSPLv1 license affect FalkorDB’s SDKs and other libraries? | ||
|
||
The SSPLv1 applies to the core FalkorDB software and any libraries distributed under the same license. We may distribute certain FalkorDB libraries or SDKs under more permissive licenses, so please check each repository for the specific license details. | ||
|
||
7. Can I modify FalkorDB under the SSPLv1 license? | ||
|
||
Yes! You’re welcome to modify FalkorDB under SSPLv1. If you distribute a modified version as part of a service, however, the SSPLv1 requires that you open-source your modifications. | ||
|
||
8. Can I redistribute FalkorDB in my applications without following SSPLv1? | ||
|
||
If you redistribute FalkorDB as part of an application that does not make it available as a service, you do not need to open-source your code. But if you’re using FalkorDB as part of a public service, SSPLv1 obligations apply. | ||
|
||
9. What should I do if I’m unsure whether SSPLv1 affects my use of FalkorDB? | ||
|
||
We’re here to help! If you have questions about specific use cases or licensing terms, feel free to reach out to our team for guidance. | ||
|
||
10. Is FalkorDB free to use for evaluation and prototyping? | ||
|
||
Yes, you are free to use FalkorDB under SSPLv1 for evaluation, prototyping, and internal testing without needing to release your source code, as long as it's not provided as a public service. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Clarify the scope of "service" and code release requirements
The current wording about what constitutes a "service" and which parts of the code need to be open-sourced could be clearer. Consider adding specific examples or scenarios to help users better understand their obligations.
Suggested addition after line 32:
Also applies to: 27-28, 31-32