Drupal
Flexible CMS in PHP for larger websites, with fine-grained permissions and many modules.
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 Yes, as long as you don't distribute it.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes Yes. Running it as a service is not distribution.
- B3 Make a closed-source derivative and sell or distribute it No No. If you distribute it, the whole work must carry the same licence, with source.
- 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
GNU GPL 2.0 or later (GPL-2.0-or-later)
Strong copyleft. Free to run internally and as a service. If you distribute it (modified or not), the whole work must be GPL with source.
What does GPL-2.0-or-later mean?
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- GPL-2.0-or-later
- Licence type
- Strong copyleft
- Open core
- No
- GitHub stars
- 4.3k
- Latest activity
- Deployment
- Server
- Login/SSO
- SAML, OIDC, LDAP
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/drupal/drupal
- 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