
Your guide on the ONLYOFFICE license and Trademark Policy
Hey everyone,
We know software licensing and trademark rules can get pretty confusing, especially if you're deploying the community edition, forking our code for a custom project or integrating ONLYOFFICE into another platform.
To help clear things up, we have prepared a straightforward guide explaining how our licensing works and how to handle branding without stepping on any legal toes.
If you're a tech enthusiast, developer or partner, here is what to keep in mind:
- We use dual licensing: We offer both open-source (AGPLv3) and commercial options depending on your project needs and whether you are offering it as a commercial service.
- AGPLv3 has specific rules: If you use the open-source version, you need to stick to the copyleft requirements, retain all legal notices and clearly label any modifications.
- Code permissions ≠ Trademark permissions: Just because you can modify the code under AGPLv3 doesn't mean you automatically have the right to use the ONLYOFFICE name, logos or brand identity.
- Forks need their own branding: If you modify the software, you have to give it a distinct name and look. You can't call your modified version "ONLYOFFICE" or use our logos.
- Attribution matters: Whenever you make permitted references to our brand (like stating your project is "based on" or "compatible with" ONLYOFFICE), you just need to include a proper trademark attribution notice.
The goal here is simply to make it as easy as possible for everyone to use and share the software while protecting the integrity of the brand.
You can read the full guide on our blog.