Third Party Software
The DTaaS platform uses a range of third-party software components. Each component remains subject to its upstream licence terms.
Deployment and Runtime Software
The core deployment stack currently references the following software:
| Software Package | Usage | Licence |
|---|---|---|
| Docker CE | mandatory | Apache 2.0 |
| Traefik | mandatory | MIT |
| Traefik Forward Auth | optional | MIT |
| GitLab CE | optional | MIT |
| GitLab Runner | optional | MIT |
| Dex | optional | Apache 2.0 |
| Keycloak | optional | Apache 2.0 |
| RabbitMQ | optional | MPL 2.0 |
| MongoDB | optional | SSPL v1 |
| Grafana | optional | AGPL v3 |
| InfluxDB | optional | Apache 2.0 / MIT |
| PostgreSQL | optional | PostgreSQL Licence |
| ThingsBoard | optional | Apache 2.0 |
Development Environments
In addition to runtime software, the development and documentation workflows use the following tools.
| Software Package | Usage | Licence |
|---|---|---|
| Node.js | mandatory | Node.js licence |
| npm | mandatory | Artistic Licence 2.0 |
| Yarn | optional | BSD 2-Clause |
| Material for MkDocs | mandatory | MIT |
| JupyterLab | optional | BSD 3-Clause |
| MicroK8s | optional | Apache 2.0 |
Package Dependencies
Additional third-party dependencies for client, servers, CLI, and tooling are declared in:
client/package.jsonservers/**/package.jsoncli/pyproject.tomldeploy/services/cli/pyproject.tomlscript/docs/mkdocs-requirements.txt
Upstream dependency licences should be consulted in those manifests when detailed licence auditing is required.