- Unlimited events
- Segment API Compatibility
- Unlimited sources
- Unlimited destinations
- Docker/Kubernetes Install
- Community support
- Everything in Open-Source
- Event Replay
- Managed Hosting
- Chat support
- Everything in Team
- Multi-node & High-Availability
- Multiple Hosting Options
- Performance Dashboard
- Customer Success Manager
Weren’t you guys on HackerNews?
How is Rudder different from Segment.com?
Open-source and being able to run inside your VPC is how we differentiate with Segment. On feature parity, we have data routing, warehous dumps, replay while personas is coming in Q1.
Is it evil to collect user-data?
Collecting user data is always a tricky subject. On one hand you want to improve the product experience which requires you to collect data on how the users are using the app but on the other hand, you want to respect their privacy.
A good middle ground is to avoid collecting PII or user-identifiable data as much as possible and keeping checks and controls on how has to access that data. From the fact that they are using your app, your users probably expect that you are keeping some data about them and would even prefer to have the personalized experience they can get.
However, what should absolutely be avoided is sharing that data with 3rd party vendors (likes of Google, Facebook and tens of other vendors) unless absolutely required. Your users put their trust in you, not them. The increasing array of privacy regulations like CCPA, GDPR are increasingly making it illegal to do so.
Under what license is the open-source project released?
The open-source project is released under SSPL (MongoDB’s license).
Why did you choose SSPL? It isn't an OSI approved license.
Licensing is something we have thought a lot about. We want to build an open-source product but also build a commercial entity around it – which means we want to stop the cloud providers from offering this as a service. SSPL was the easiest choice but we do understand that it’s not an OSI approved license.
AGPL (an OSI compliant license) does provide a similar level of protection against cloud providers – any app talking to RudderStack over an API to send events would be forced to open-source the app and hence it is almost impossible to build a SaaS service on top. But for this exact same reason, our users don’t like AGPL. AGPL is considered an absolute NO in lot of enterprises. To get around this, we have also thought of releasing our binary (and AMI images, docker images) under MIT license so that people can still run it but then it also lets Amazon offer it as a service. Another thing people do is Apache with Common Clause but even that too is, not an OSI approved license. Other companies like CockroachDB have implemented their own (non-OSI approved) license.
We are hoping that one of the big OSS guys (with the budget to pay the attorneys) will figure this shit out once for all and we can just follow. Till then, we are just focused on building RudderStack in a license model that maybe is not ideal but works for a vast majority of our users.
Who are the people associated with this project?
We are a team of engineers with years of background in data. The company has been funded by S28 Capital (investors behind other popular open-source projects like Mattermost and Gravitational)
Is your open-source code maintained and stable?
How do we contact you?
You can email me, Soumyadeb, the founder of Rudder, at email@example.com.
What support is available with the Community plan and Enterprise plan?
If you are on the Enterprise plan, you will have a dedicated account manager (initially a senior member of the management team).