[soumyadeb]

We have been thinking about this a lot for our open-source Segment project (https://github.com/rudderlabs/rudder-server/). We launched things under mongo-SSPL (which is not a OSS approved license) but we now think AGPL is probably good enough for a product like ours. AGPL should kick in for anything (e.g. mobile app) that sends events to the our AGPL-backend so needs to be open-sourced too - that should be a strong enough deterrent for anyone to offer this as a service. Is this statement true? If yes, why did Mongo with with SSPL instead of AGPL?

At the same time, we still want businesses who don't care about OSS to use Rudder without having to open-source their code. To address that we are thinking of releasing our binary (and AMI images etc) under MIT license. Sure, someone can spin up a SaaS service on the binary but that's hard.

Any feedback on this would be highly appreciated.

[matchy]

AGPL hasn’t really been tested in court so it’s not clear whether it would be enough to stop someone from running your software as a service.

[soumyadeb]

Isn't that true for most OSS licenses (not being tested in court)?