Skip to main content
World Monitor source code is licensed under the GNU Affero General Public License v3.0 (AGPL-3.0-only). This page is a plain-language summary for contributors and users. It is not legal advice and does not replace the license text in LICENSE. Exception — official client packages are MIT. The thin API clients — the worldmonitor npm CLI (cli/), and the Python (sdk/python/), Ruby (sdk/ruby/), and Go (sdk/go/) SDKs — are licensed under MIT (see the LICENSE file in each directory) so they can be embedded in any application without copyleft obligations. This exception covers only those client packages: the World Monitor platform, server, and dashboard remain AGPL-3.0-only.

​
AGPL-3.0-only code license

AGPL-3.0-only is a strong copyleft license for network software. It permits commercial use, private use, modification, copying, and redistribution when you follow the AGPL terms. Commercial use is permitted under the AGPL. A paid deployment, consulting use case, or commercial SaaS is not automatically a license violation. The key question is whether you comply with the AGPL obligations that apply to your use.

​
What AGPL permits

Under AGPL-3.0-only, you may:
  • use World Monitor for personal, educational, research, nonprofit, or commercial purposes
  • self-host the unmodified project
  • modify the code
  • distribute copies and modified versions
  • charge money for services, hosting, support, or distribution
These permissions come from the AGPL itself; they apply to personal, nonprofit, and business use alike.

​
What AGPL requires

When AGPL obligations apply, you must follow the license terms. In practice, this includes:
  • keeping copyright and license notices intact
  • licensing covered modified versions under AGPL-3.0-only
  • providing corresponding source when you distribute covered binaries
  • prominently offering corresponding source to users who interact with a modified public network deployment
  • documenting relevant changes you made
The AGPL does not grant permission to remove license notices or make covered modified versions proprietary.

​
Optional commercial licensing

Commercial licensing is an alternative option, not a restriction on the AGPL license. A separate commercial license may be useful if you want to:
  • keep modified source code private
  • combine World Monitor code into proprietary products in ways the AGPL would not permit
  • receive custom contractual terms, warranties, support, or indemnity
  • obtain separate permissions for official branding, white-labeling, or trademark use
Contact the maintainer through the GitHub repository to discuss commercial licensing.

​
Trademark and branding

The AGPL covers copyright permissions for the code. It does not grant rights to use the World Monitor name, logo, visual identity, or official project branding. See the Trademark Policy for branding, attribution, rebranding, white-labeling, and affiliation rules.

​
Common scenarios

Personal use or research: Permitted under AGPL-3.0-only. Internal company use: Commercial use is permitted under AGPL-3.0-only, subject to the license terms. Running a modified public instance: You must prominently offer corresponding source to users who interact with that modified network deployment. Shipping a proprietary fork: Request separate private-source terms for proprietary forks. Using World Monitor’s public API in your own tool: API terms of service may apply separately from the source-code license. Contributing a pull request: By submitting a PR, you agree that your contribution is licensed under AGPL-3.0-only, consistent with the rest of the project.