3 ms·
I’m building an Open Source multi-tenant email newsletter tool [1] and the project is entirely AGPLv3 licensed. I have automatic builds from the `main` branch t
by pentacent_hq 2y ago
I’m building an Open Source multi-tenant email newsletter tool [1] and the project is entirely AGPLv3 licensed. I have automatic builds from the `main` branch that I deploy to the SaaS version while public Docker images are available only for tagged releases.
There is currently no difference between the self-hosted and the SaaS version, but I am planning two things:
1) An env variable `IS_SELF_HOSTED` which, when set to `false`, toggles certain features like billing (currently enabled via a separate env variable and theoretically available to self-hosters) and includes hard-coded stuff like a footer with links to the official project website and our ToS.
2) Add a registration feature for self-hosters who make a donation. I haven’t fully planned out this feature, but if a self-hosted instance is registered by a paid supporter, it will most likely remove a call for becoming a supporter (that is yet to be added) or give them a supporter badge.
Choosing the AGPLv3 has been partially inspired by Plausible’s very successful model [2]. They’re also using a `SELFHOST` env variable to differentiate between their "Enterprise Edition" and the "Community Edition" [3].
[1] https://www.keila.io https://www.keila.io
[2] https://plausible.io/blog/open-source-licenses https://plausible.io/blog/open-source-licenses
[3] https://github.com/plausible/analytics/blob/baa99652f612f50bbb63282b42737ced93b6d483/config/runtime.exs#L243 https://github.com/plausible/analytics/blob/baa99652f612f50b...
- anonu 2y agoAfero, i feel, is a hindrance to adoption, especially in for profit companies where IP matters.
- MoOmer 2y agoThat’s by design; those corporations can purchase an enterprise license - and this is commonly the route desired!
- pentacent_hq 2y agoI see the AGPL as a way to ensure user freedom and as a way to make sure those who profit from our work give back to the community. If someone is so concerned about their so-called "software patents" to the extent that they don't want to deploy their own instance of the AGPL code, they are more than welcome to use our SaaS offer.