Licence change
Tesserae is now licensed under AGPL-3.0-or-later, up from MIT.
This release does not change any code. The licence governs new versions; existing copies you've already downloaded under MIT keep their freedoms.
What changes for users
- Self-hosting Tesserae on your own hardware: no change. Run it, modify it, share modifications with friends — same freedoms as under MIT.
- Distributing a modified version: must ship the source. Includes network-hosted modifications ("someone modifies Tesserae and runs it as SaaS"), which the AGPL closes — that's the distinguishing feature vs plain GPL.
- Combining Tesserae with proprietary software you ship: AGPL obligations apply to the combined work. Widgets that just plug in via the documented plugin API can keep permissive licences (MIT / Apache-2.0) as long as they don't ship Tesserae itself.
Why AGPL specifically
To keep the project ecosystem open. A closed-source SaaS fork of Tesserae wouldn't be a contribution back to the community, and AGPL is the established licence for ruling that path out cleanly while leaving everything else — self-hosting, study, modification, contribution — wide open.
Aligned repos
The full Tesserae ecosystem moved together:
- `dmellok/tesserae` (this repo)
- `dmellok/tesserae-widgets` (community catalog)
- `dmellok/tesserae-pi-bin-client` + `tesserae-pi-png-client` (Pi panel clients)
- All 20 bundled widget repos (`tesserae-ai-brief`, `tesserae-spotify`, `tesserae-calendar-schedule`, etc.)
The one exception is `dmellok/tesserae-fal-image`, which is archived and remains under its original MIT licence.
No code change
LICENSE text swapped, SPDX identifier in `pyproject.toml` updated, docs and README references retargeted at AGPL-3.0. Suite still green (981 passing, ruff + mypy strict clean).