Discussions about Jitsu

Events evolve over time. How are you managing schema changes in [Jitsu](https://saaskart.co/software/jitsu) without breaking warehouse tables?

Cloud pricing scales with events. How predictable has [Jitsu](https://saaskart.co/software/jitsu) Cloud cost been as your traffic grew?

Good instrumentation matters. How is the developer experience of the [Jitsu](https://saaskart.co/software/jitsu) SDKs across web and server?

Pairing [Jitsu](https://saaskart.co/software/jitsu) with a warehouse and reverse-ETL builds a composable CDP. How complete does that stack feel versus a package

A data pipeline must not drop events. How reliable has self-hosted [Jitsu](https://saaskart.co/software/jitsu) been under load, and how do you monitor it?

Streaming events into ClickHouse enables fast analytics. How is the [Jitsu](https://saaskart.co/software/jitsu) plus ClickHouse combination working for you?

Shaping events before they land is useful. How are you using [Jitsu](https://saaskart.co/software/jitsu) functions to clean and enrich events?

Segment gets expensive at scale. For teams that moved to [Jitsu](https://saaskart.co/software/jitsu), how smooth was the migration and how much did it save?

Running [Jitsu](https://saaskart.co/software/jitsu) yourself saves money but adds ops. At what volume did teams decide Jitsu Cloud was worth it?

Both are open-source event pipelines. How does [Jitsu](https://saaskart.co/software/jitsu) compare to RudderStack on connectors, transformations, and operationa