Segment → Jitsu
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Segment bills per monthly tracked user and mid-market plans reach four figures. Jitsu self-hosted is infrastructure — typically $50–150/month for the same event volume.
Moves cleanly
Your tracking calls. Jitsu accepts the Segment API shape, so analytics.track() calls keep working against a changed endpoint.
You rebuild
Destination configuration. Each downstream tool needs reconnecting, and Jitsu's catalogue is smaller than Segment's.
What Segment costs you today
Billed on monthly tracked users, with a free tier of about 1,000. Team starts around $120/month and scales with volume; Business is quoted and commonly reaches five figures a year. The mechanic that catches people is that a single user counts once no matter how many destinations receive their events, so the bill tracks audience size rather than the number of tools — which is the opposite of the intuition most buyers arrive with. Checked 2026-08-03.
What actually holds you in
Lower than most of this catalogue, and worth knowing. The tracking calls in your application follow a specification that RudderStack and Jitsu both deliberately implement, so the client-side code frequently works unchanged — that is the whole point of their SDK compatibility. What does not move is historical data already routed, the destination configurations built up over years, and any downstream tool keyed to Segment's user identifiers. Replaying history is the expensive part; new events are close to a drop-in.
What you are moving to
Jitsu is the option with nothing to explain: MIT, self-hostable, real-time event collection into ClickHouse, BigQuery, Snowflake, Postgres and the rest. Around 4.8k stars. It is smaller than RudderStack and has fewer destinations, and that is the entire trade — you give up catalogue breadth and get a licence you can read in five minutes and never think about again. For a team whose legal review killed the last two candidates, that is often the deciding feature.
Free and open source. Jitsu Cloud is a paid hosted option.
Jitsu strengths
- Genuinely MIT — no carve-outs, no source-available asterisk
- Real-time streaming into the major warehouses
- Lightweight enough to self-host without a platform team
- Simple, readable architecture
What you give up
- Far fewer destinations than RudderStack or Segment
- Smaller community and fewer worked examples
- No identity resolution to speak of
- Less mature governance tooling
The migration, step by step
- 1Inventory your active destinations — most estates have several nobody reads
- 2Deploy Jitsu with its Docker setup and ClickHouse or Postgres
- 3Repoint the JavaScript source to Jitsu while leaving Segment running
- 4Reconnect destinations one at a time, verifying events land in each
- 5Compare a week of event counts between the two before cancelling
The gotcha
Segment's value is often the destination catalogue rather than the pipeline. If you depend on a niche destination Jitsu does not support, you inherit building and maintaining that integration yourself.
When to stay on Segment
You use Segment Protocols for schema enforcement, or depend on destinations Jitsu lacks.
More Layer 3 migrations
Figures verified 2026-08-03 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.