UVdesk
Ticketing system for customer support with email, workflows and a knowledge base.
OSL-3.0Network copyleft (AGPL)
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.
The licence in brief
Open Software License 3.0 (OSL-3.0)
Copyleft that also applies when the software is offered over a network (like AGPL). Changes you offer as a service must be made available.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- OSL-3.0
- Licence type
- Network copyleft (AGPL)
- Open core
- No
- GitHub stars
- 19.6k
- Latest activity
- Deployment
- Server
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/uvdesk/community-skeleton
- 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