Show HN: RudderStack, open-source CDI (a.k.a. open-source Segment)

GitHub: https://github.com/rudderlabs/rudder-server/

===

Firstly, a big thanks to the HN community for showing us love and support in our previous HN post (https://news.ycombinator.com/item?id=21081756). At that point, we had just open-sourced the repo and were not fully prepared for a Show HN. We wanted to share updates since then and also do our official Show HN.

Updates since Sept 2019

1. Changed the name from Rudder to RudderStack :)

2. API compatibility with Segment

3. Open-source control plane so no dependency on the hosted control plane for open-source users. (https://github.com/rudderlabs/rudder-server/blob/config-gen/...)

4. Multiple hosting options: Docker, Kubernetes, Terraform, Native.

5. ~30 integrations (https://rudderstack.com/) including cloud mode and device mode

6. Support all the popular data-warehouses & lakes - RedShift, Snowflake, BigQuery, S3, Google Cloud Storage, Azure Blob Storage

7. Detailed documentation - https://docs.rudderstack.com/

8. Multiple production deployments including few really large ones (our largest deployment is sending a peak of ~40K events/sec, ~300M events/day)

9. Switched license from SSPL to AGPLv3 (after long discussions internally as well as on HN)

10. Built some interesting Analytics & ML use cases

11. Launched our “paid plans” (primarily around managed hosting)

Wishing everyone best wishes for staying safe from COVID-19

Here at @Grofers we have been using rudder for a while. A great solution for people who want to create their customer data platform. Plus an awesome team who is always happy to help out :)

In your pricing > faq - there is a mention of why you chose SSPL and NOT AGPLv3!

And then you are on AGPLv3 ?

Can you please share your thoughts on why you moved to AGPLv3 ?

Oops, that was old.

We had long discussions on and off HN about this topic. The biggest problem with SSPL is it is not an open-source license and we got a bunch of pushback (rightly so) for calling ourselves open-source.

We initially went with SSPL to help prevent cloud providers from offering this as a service. However, there was a viewpoint that AGPLv3 already provides this and there is no reason for SSPL. Also, neither has been held up in court.

In the end, we prioritized something which our community felt strongly about. The business risk was questionable anyway.

But the repo says SSPL... in the readme & in the LICENSE file isn't that the source of truth? Or what matters to an organization evaluating adoption?