[vklmn]

We're very similar indeed. But we attack the same problem from different angles:

- We truly believe that our product should be accessible for small teams too. That's why se made Jitsu very easy to deploy. I'm not sure you can deploy Rudder on Heroku, or on any service with a single Docker file.

- Our ETL component is open-source (and based on other great OSS projects - Airbyte & Singer). RudderStack haven't published the Cloud Extract (their ETL) to my knowledge.

- RudderStack aims to replace Segment, we go beyond that. We didn't copy Segment API one-to-one, we just added a Segment compatibility layer. Jitsu can be used for any kind of data. An example: a few companies (including our-selves) using Jitsu to collect open-source telemetry (anonymous usage). I'm not sure Rudder can be used for that use-case

[dmolot]

Fellow YC company (hotglue) here - we love the Singer spec so it is cool to see your modeling after that. It is worth giving a shout out to Meltano who is helping grow it (an Airbyte competitor). Love what you all are doing Vladimir! Congrats on the launch :D

[zimmerx]

Rudderstack user here (and ex Segment). Thanks for sharing this stuff, very cool project.

Just to answer some of this:

- rudderstack has deploy ready helm charts, which I'd argue are significantly better than docker compose or docker setups because they set up all the other niggly parts. Would be cool to see that here :)

- rudderstack has gone quite far away from replacing segment. It's true that their core API is compatible and I think your transformation layer is really cool. However it can be used for those use cases because rudderstack doesn't really care about users or user IDs and can be used for any sort of data generally.

There's a piece in the docs talking about the fact that you don't get caught by adblock - whilst this may be true when someone launches it, that's not true of your platform. That's just the fact that a lot of smaller businesses will not get their URLs added to the ad block lists. I think it's a bit misleading to mention that in such a way because technically we're all tracking users and ad block is a way for users to choose not to be tracked, not be tricked into being tracked because someone has masked the tracking script ;) if a huge client (a la Adidas or something) decided to use your scripts I'm sure someone would eventually add it to the ad block lists that get propagated.

One of the things that would be cool would be some sort of opt in configuration. Segment has some awful consent SDK that is really bad, would be cool to see what you do there. GDPR is a big deal and browser fingerprinting is data processing. It's worth looking at your comments on being GDPR compliant btw https://www.eff.org/deeplinks/2018/06/gdpr-and-browser-finge...