openimsdk / openimsdk/open-im-sdk-reactnative
[Other]: Clarification on React Native SDK licensing for a proprietary commercial app
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 58
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to share?
Hi OpenIM team,
We are evaluating OpenIM for a commercial chat product with the following architecture:
- Self-hosted OpenIM Server
- Our own existing user/account system
- A fully custom React Native UI
@openim/rn-client-sdkused only for messaging, local storage, synchronization, and connection management- Proprietary iOS and Android applications that will not be open-sourced
- Possible integration with a separate voice/video service in the future
We noticed that the licensing information appears inconsistent:
- The
open-im-sdk-reactnativerepository is marked as AGPL-3.0 on GitHub. - Its README states that it is licensed under Apache 2.0.
- The official OpenIM licensing documentation says that OpenIMClientSDK is licensed under AGPL-3.0 or a commercial license.
- The React Native demo is AGPL-3.0 with additional terms stating that commercial use is not permitted.
Could you please clarify the following?
- What is the authoritative license for
@openim/rn-client-sdkand theopen-im-sdk-reactnativerepository? - Can we use
@openim/rn-client-sdkin a proprietary commercial React Native app without open-sourcing our application code? - If a commercial license is required, how is it priced: per application, platform, MAU, deployment, company, or annually?
- Does one commercial license cover both iOS and Android?
- Does the license allow us to modify the React Native bridge or underlying client SDK while keeping those modifications proprietary?
- Is the React Native demo restricted from commercial use only as a complete demo application, or are individual UI components and code snippets also restricted?
- If we use only the Apache-2.0 OpenIM Server and implement our own client without OpenIMClientSDK, is any commercial license required?
- Could you update the repository LICENSE/README to remove the apparent Apache-2.0 versus AGPL-3.0 conflict?
A clear written answer would help us complete our technical and legal evaluation.
Thank you.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository LICENSE and README alongside the official OpenIM licensing documentation and the React Native demo’s stated terms. Done means providing an authoritative written answer to the licensing questions and resolving the apparent Apache-2.0 versus AGPL-3.0 conflict in the repository documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100