Pi-hole
Network-wide DNS server that blocks ads and trackers.
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.
Keep in mind
- There is a licence note for this product (e.g. parts under another licence or version-specific terms): read it and check the licence of the exact version you use.
This is guidance, not legal advice. Check with a lawyer before deciding.
The licence in brief
European Union Public Licence 1.2 (EUPL-1.2)
Copyleft from the European Commission, available in all EU languages. Also applies when the software is made available over a network.
Pi-hole Core is EUPL-1.2 from version 3.0. Commits before v3.0 keep their earlier licences.
This is guidance, not legal advice (inte juridisk rådgivning). Check with a lawyer before deciding.
Facts
- Licence
- EUPL-1.2
- Licence type
- Strong copyleft
- Open core
- No
- GitHub stars
- 61.1k
- Latest activity
- Deployment
- Docker
- Login/SSO
- Unknown
- API
- Unknown
- Multi-tenant
- Unknown
- EU vendor
- Unknown
- Source code
- github.com/pi-hole/pi-hole
- 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