Hi,
First of all, thank you for creating such a solid production-ready Tauri template.
It’s really impressive how much is already set up out of the box - UI, state management, auto-updates, CI/CD, security checks… it’s a great starting point for building real-world desktop apps.
That’s why I’m a bit curious about the licensing choice.
Currently, the template is under AGPL-3.0-or-later, which is one of the strongest copyleft licenses. This has a few implications:
- Any project based on this template must also be released under the same license.
- Even private, server-side code must be shared if the app is made available to users over a network.
- This effectively prevents using the template for any closed-source or commercial projects, which seems to contradict the “production-ready” positioning for a broader audience.
Because of this, I’m wondering:
- Was AGPL chosen intentionally to limit usage to open-source projects?
- Would you consider switching to a more permissive license (e.g. MIT, Apache 2.0, BSD) so both open-source and commercial projects could benefit from this work?
Permissive licenses allow for a wide range of uses - including proprietary and commercial - while only requiring that the original copyright notice be kept.
Conversely, AGPL’s strong copyleft can be a blocker for adoption - especially for corporate or SaaS users who prefer not to expose their source code.
By switching to a permissive license, this template could attract more usage, contributions, and visibility - possibly becoming the go-to starting point for the Tauri community.
I understand the desire to protect your work, and AGPL ensures modifications stay open. However, a more permissive license might broaden your reach and benefit everyone.
Thanks again for your hard work, and I’m looking forward to hearing your thoughts!
- Cheers