Why developers leave Segment: per-MTU pricing punishes large user bases, Twilio acquisition has slowed product velocity, and self-hosted alternatives like Rudderstack are now genuinely competitive. Teams at >1M MTU routinely evaluate alternatives for cost optimization.
Twilio (which owns Segment) is included as the parent product for teams that ended up consolidating customer-data + messaging in one vendor. Different shape than Segment alone.
Hasura is included as an alternative for teams whose Segment use was primarily routing data to internal data warehouses. Hasura GraphQL over a warehouse can replace some Segment routing patterns.
Yes — open-source, self-hostable, per-MTU pricing more competitive than Segment. Reviewer cohorts growing. We rank it in our customer-data infrastructure category. For teams at >1M MTU the cost savings can fund a quarter of ops investment.
For data-warehouse-only routing: increasingly yes. Tools like dbt + warehouse-native modeling reduce the need for Segment's many-to-many routing. For sending events to product tools (Mixpanel, Customer.io) Segment's catalog is still the cleanest path.
Segment can export historical events. The harder work is rewriting destination integrations. Most reviewers reported a 1-2 quarter migration window to validate parity before turning off Segment. Plan for overlap costs during validation.
