Segment

Segment's core idea — instrument your app once, fan those events out to any tool you need — solved a real problem when it launched in 2011. Before Segment, every analytics vendor, advertising pixel, and A/B testing SDK required its own integration. Segment reduced that to a single analytics.js call and a connections dashboard. Its destination catalog grew to cover 400+ integrations, and the Segment event schema became an informal industry standard for how to name and structure user events.

Twilio's 2020 acquisition brought more resources but also a shift in pricing philosophy. Segment's event-volume billing means the cost correlates directly with how much your users engage with your product — which is an awkward incentive structure. B2C consumer apps with millions of sessions per month can find themselves paying tens of thousands of dollars annually to route data that ultimately lands in their own warehouse anyway. The warehouse-first CDP movement grew partly in reaction to this: if your source of truth is BigQuery or Snowflake, why pay Segment to be the middleman when you can ingest directly?

Segment also offers no self-hosting. All event traffic crosses Twilio infrastructure, which creates a data residency constraint for regulated industries and a dependency that complicates GDPR deletion workflows at scale. Teams that need the full 400-destination breadth and are comfortable with the pricing model will find Segment genuinely difficult to replace. Everyone else should evaluate whether a warehouse-first open-source alternative changes the economics significantly.