Chaskiq
Live chat, customer support and marketing messages in one platform.
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 Usually, for internal use. Check the terms.
- B2 Build your own product or service on top and offer it to customers as SaaS No Usually no for a service that competes with the vendor, without an agreement.
- B3 Make a closed-source derivative and sell or distribute it No No, not without an agreement with the vendor.
- 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
Commons Clause (on top of an OSS licence) (LicenseRef-Commons-Clause)
An OSS licence with an added clause: you may not sell the software or services whose value derives mainly from it.
What does LicenseRef-Commons-Clause mean?
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- LicenseRef-Commons-Clause
- Licence type
- Source-available (not OSI)
- Open core
- No
- GitHub stars
- 3.6k
- Latest activity
- Deployment
- Docker
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/chaskiq/chaskiq
- 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