Segment vs RudderStack: tracked users or events, hosted or self-hosted
By Julian Pryor · Updated 7 Oct 2026
RudderStack publishes a price ladder by event volume: free up to 250K events a month, then $265 at 1 million events and $1,675 at 10 million. Segment's pricing is on request (quote-based) and is built on monthly tracked users. Which one is cheaper depends on how many events each of your users produces, so the useful exercise is converting your own tracking into both units. This page shows how, and covers what else differs: warehouse sync, reverse ETL, governance add-ons, self-hosting and the cost of moving.
Two different units
Segment defines a monthly tracked user (MTU) as "the number of anonymous and logged-in visitors that you track". Both of its plans are priced on MTUs with custom volume, invoiced, and unlimited seats. RudderStack defines an event as a data point generated by a website, app, server or cloud application, and prices on monthly events, not users. The two units reward opposite behavior:
- Many visitors, few events each (a marketing site with heavy anonymous traffic): an MTU-priced tool counts every visitor, while an event-priced tool counts a handful of page views per visitor. Event pricing tends to cost less.
- Few users, heavy tracking (a B2B product that logs hundreds of in-product actions per user): MTU pricing is blind to the volume of events per user, while event pricing grows with every click. MTU pricing tends to cost less.
Neither vendor's page lets you compute the other side, so ask Segment for a quote on your MTU count and price your event volume on RudderStack's ladder.
RudderStack's published ladder
Readouts from RudderStack's pricing page on 7 October 2026. Growth includes unlimited team members, unlimited tracking plans, 30-minute warehouse sync, two workspaces and 25 Reverse ETL connections.
| Events per month | Billed monthly | Billed annually, per month |
|---|---|---|
| Up to 250K | Free | Free |
| 1 million | $265 | $225 |
| 3 million | $735 | $625 |
| 5 million | $995 | $845 |
| 7 million | $1,195 | $1,015 |
| 10 million | $1,675 | $1,420 |
| 25 million | $2,750 | $2,335 |
| Above 25 million | Talk to sales; Enterprise is custom | |
Turning your tracking into a RudderStack bill
Multiply monthly active users by events per user, then read the ladder. These are illustrations of the method, not benchmarks; use your own counts.
| Monthly users | Events per user | Total events | Ladder price (billed monthly) |
|---|---|---|---|
| 5,000 | 20 | 100,000 | Free |
| 20,000 | 50 | 1 million | $265 |
| 60,000 | 50 | 3 million | $735 |
| 100,000 | 100 | 10 million | $1,675 |
Because the ladder steps up at 1, 3, 5, 7, 10 and 25 million, the cost between steps is the next step's price. An event total that creeps just past a tier should send you back to your instrumentation: dropping noisy events such as scroll or heartbeat pings is the cheapest saving available on an event-priced tool.
What else differs
- Warehouse and Reverse ETL. RudderStack ships warehouse destinations on every plan and syncs every 3 hours on Free, 30 minutes on Growth and 5 minutes on Enterprise, with 10, 25 and unlimited Reverse ETL connections. Segment lists Reverse ETL as a Connections feature that activates warehouse data into 750+ tools and says a warehouse is optional.
- Governance. Segment's Protocols data governance is an add-on on its Customer Data Pipeline plan. RudderStack's Free plan has one tracking plan with 5 events; Growth has unlimited tracking plans.
- Destinations. Segment advertises 550+ destinations for Connections. RudderStack's Free plan lists 16 SDK sources and 200+ cloud destinations.
- Team size. Segment lists unlimited seats on both plans; RudderStack allows 10 team members on Free and unlimited on Growth.
- Hosting. RudderStack has a self-hosted project under Elastic License 2.0; Segment is hosted with regional infrastructure in Europe and the United States.
Which to choose
- Choose RudderStack if you want a published price, a free start up to 250K events, warehouse-first routing or self-hosting, and your events per user are modest.
- Choose Segment if you need its destination catalog and governance tooling, or you plan to run its identity-resolved profiles and journey orchestration on top of the pipeline, and a quoted, invoiced contract suits your procurement.
- Get both numbers before deciding. A quote for your MTU count and a ladder lookup for your event count take an afternoon, and the gap is often large enough to decide the matter on its own.
Migrating from Segment to RudderStack
RudderStack's pricing page invites Segment customers to talk with its migration specialists, which is worth a call before you start. The work itself follows a pattern:
- Inventory every source, destination, tracking plan, transformation and warehouse schema in Segment. The inventory is the project.
- Recreate sources and destinations in RudderStack, noting that its Free plan limits you to 5 transformations and one tracking plan.
- Send events to both pipelines for a period and compare warehouse table and column names, since destination tools key off those names.
- Move destinations one at a time, starting with the least critical, and retire the Segment write key only after a full reporting cycle matches.
Related reading: Segment alternatives, PostHog vs Amplitude, Mixpanel vs Amplitude, customer analytics tools and an analytics stack for SaaS.
Segment vs RudderStack: common questions
How much does Segment cost?
Segment pricing is on request (quote-based). Its pricing page says both plans, Customer Data Pipeline and Customer Data Platform, are priced on monthly tracked users with custom volume, billed by invoice, and it publishes no dollar figure. It also does not publish overage rates or data retention periods on that page. A free trial is offered for Connections.
How is RudderStack priced?
By monthly event volume rather than by tracked user. The Free plan covers 250K events a month. Growth is $265 a month at 1 million events, $735 at 3 million, $995 at 5 million, $1,195 at 7 million, $1,675 at 10 million and $2,750 at 25 million; billing annually lowers each by roughly 15%. Above 25 million events it is a sales conversation.
What happens if I exceed the RudderStack free plan?
Its page states that data processing will stop after your second consecutive overage. That is a real constraint for a production pipeline: set an alert at 80% of 250K events and plan the move to Growth before you reach it, since stopped processing means missing data in your warehouse and downstream tools.
Can I self-host either one?
RudderStack lists a self-hosted project released under the Elastic License 2.0, a source-available license. Segment is offered as a hosted service, with regional infrastructure in Europe and the United States. If keeping event data inside your own network is a requirement, that single difference may settle the choice.