It is the pipeline: collect, transform, send. Audiences and journeys are a different product. Most teams only needed the pipeline.

Stacks / Analytics

Medium

Jitsu

Open-source Segment: capture events, script the pipeline, warehouse the rest.

The problem

Segment bills monthly tracked users and then sells Unify. Jitsu is the catalog OSS Segment alternative — ingest, transform, warehouse, no MTU invoice.

Replaces

Segment

Replace Segment

Estimated SaaS saved

$2,400

per year, small team, before lock-in

Deploy on Railway

Sponsor this stack

Placeholder: Jitsu + Postgres (or ClickHouse). Replace the Segment snippet with Jitsu's. Warehouse later.

The stack

Jitsu
Open-source Segment alternative
Catalog entry →

Cost table

You stop paying	Typical / year	Self-host instead
Twilio Segment Connections	$2,400	Jitsu self-host

Agent setup prompt

Replace Segment with Jitsu.

- Deploy Jitsu. Point the existing analytics snippet at it. Keep one destination (warehouse or webhook) working.
- Do not rebuild every Segment destination on day one. Write AGENT_PROMPT.md and a note on MTU vs hosting.

Also as markdown: /stacks/jitsu-cdp.md

FAQ

Is this a full CDP?: It is the pipeline: collect, transform, send. Audiences and journeys are a different product. Most teams only needed the pipeline.