Jitsu has been very helpful for us because its transformation functions let us strip PII in the pipeline, before anything ever lands in ClickHouse.

With our previous vendor, doing the same thing turned into a two-week engineering effort plus a compliance review.

The connectors also covered the sources and destinations we already had, so standing up the first pipeline was mostly configuration rather than a build, and the UI makes it easy to see the state of each connection without digging through logs. Throughput has kept up with our event volume without us having to tune anything. Onboarding and support have been a real part of the value as well. Their team helped us plan and run the migration instead of just pointing us to docs, and they still answer questions quickly. The automated side has quietly done a lot of work for us. Jitsu auto-generates the tables and columns in ClickHouse as new event properties show up, so we aren't writing a migration every time we instrument something new, and the identity stitching builds the user graph in real time instead of leaving us to reconcile anonymous and known sessions in SQL after the fact. Deduplication on the sync side has held up well enough that we never built our own guardrails around it. Review collected by and hosted on G2.com.

Adjusting to the lack of native schema enforcement took some time. We ended up writing a transformation function to handle it, and it works, but this really should be available as a toggle rather than something you have to piece together from a recipe.

The editing experience around those functions is also pretty bare-bones. There's no easy way to test a transformation against real events before it goes live. Review collected by and hosted on G2.com.