Software licensing
What Simplewala installs on your server, under what terms, and where the line falls between software we choose and software you choose.
How software reaches your server
Simplewala never ships you a copy of third-party software. When you install a database, a CMS or a mail server, the install runs on your server and pulls the official upstream image from its own registry. We do not rebuild, re-tag, fork, mirror or republish anyone else's software, and no Simplewala artifact or registry contains it.
Configuration and plugins are written into the running container at install time rather than baked into an image we publish. That is a deliberate design choice, not an implementation detail — it is what keeps the software you run exactly the upstream release, byte for byte, and verifiable as such.
What we install, and under what licence
Every image the platform installs is pinned to an exact version and recorded with its licence and upstream source. The full inventory is generated from that manifest on every build, so it cannot drift from what actually ships:
- Permissive — nginx, HAProxy, Apache Kafka, RabbitMQ, Memcached, Valkey, PostgreSQL, Gitea, Woodpecker CI, File Browser, Distribution (container registry), VictoriaMetrics, docker-mailserver.
- GPL family — WordPress, Ghost, Joomla, Drupal, Jellyfin, Roundcube, MySQL, MariaDB. The GPL attaches its obligations to copying, distribution and modification. Running software and serving it over a network are none of those, which is why hosting these creates no obligation for you or for us.
What we will not install
Simplewala does not template software whose licence forbids offering its functionality as a service, or which attaches obligations to operating it over a network. In practice that means no AGPL, SSPL, RSAL, Business Source Licence, Confluent Community Licence, Elastic Licence or Commons Clause software — in any capacity, and with no exception process.
This is a deliberately stricter line than the law requires. The cheapest position to be in is one where the obligation never arises, so where a restricted project is the best technical option we use the next best one instead.
Software removed under this rule, and what replaced it:
- Redis (RSALv2 from 7.4) → Valkey, which speaks the
same wire protocol. Existing clients and
REDIS_URLwork unchanged. - MongoDB (SSPL) → no replacement is offered. PostgreSQL handles document workloads through JSONB, or you can bring your own image.
- Grafana, Loki, Metabase, Immich, Nextcloud, PhotoPrism (AGPL) → withdrawn. Server and app analytics are built into the dashboard; Apache Superset remains available for business intelligence.
Software you choose is yours to license
You can deploy any container image, repository or package you like. When you do, you have chosen it — Simplewala does not select, endorse or vet it, and complying with its licence is your responsibility.
We do not scan, block or warn on what you deploy. That is not an oversight: your application's licensing is not ours to police, it cannot be done reliably, and a check that looked authoritative while missing cases would be worse than no check at all.
The practical consequence is that nothing above restricts what you can run. If you need MongoDB or Grafana for your own application, deploy the image yourself — the platform will run it. What changed is only that we no longer offer it as a one-click product.
Trademarks
Third-party names in the dashboard and in these docs identify the software a resource runs — nothing more. They are the trademarks of their respective owners. Simplewala does not use any third-party mark in a product, plan or hostname, does not display third-party logos, and claims no affiliation with or endorsement by any of these projects.
Questions
Licensing questions about the platform go to our contact form. Questions about the licence of software you have chosen to deploy are best answered by that project upstream.