ToolJet
Low-code platform for internal apps and workflows.
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes, with conditions Yes, but if staff or others reach it over a network they must be able to get your modified source.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes, with conditions Yes, but you must share your changes with the users (AGPL).
- B3 Make a closed-source derivative and sell or distribute it No No. The derivative must carry the same licence and the source must be offered.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
This is guidance, not legal advice. Check with a lawyer before deciding.
Verify with a lawyer. Not verified: check the following in the product's own documentation before deciding: sso.
The licence in brief
GNU AGPL 3.0 (AGPL-3.0)
Network copyleft. Free to run. If you modify it and users reach it over a network, you must offer them your modified source.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- AGPL-3.0
- Licence type
- Network copyleft (AGPL)
- Open core
- No
- GitHub stars
- 41.0k
- Latest activity
- Unknown
- Deployment
- Docker, Helm
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- No
- Source code
- github.com/ToolJet/ToolJet
- Source
- GitHub API, fetched 2026-10-03
Licence analysis per use case
Sign in to see what the licence means for eight use cases – from internal self-hosting to offering the tool as a service.
Sign in