Capture Event Data into Your with Jitsu (YC S20) 🔥 Open-source, compatible with Segment

Joined November 2019
Every paid tool in the data stack has an open-source replacement now. Segment → @jitsucom @Snowflake → @ClickHouseDB Looker → @metabase dbt Cloud → dbt Core @datadoghq → @grafana @tableau → @superset_sh All are self-hostable. What's missing from the list?
12
7
4
22
8,097
Hey X, I'm doing my first ever LinkedIN Live today in less than 12 hours 🙂 The news is what every founder building a company dreams of. Getting Acquired... @heliumventureco announced last week that it acquired @jitsucom , and i'm hosting @vl_klmn (jitsu's co-founder) and @rohitdotmittal (helium's ceo) on how the deal came together and what's next come hang out with us and say Hi It's gonna be a bangerr session with a lot of insights from 2 YC founders who've raised Millions of $$, built and sold to enterprises and F500s 10am PT / 10:30pm IST, register here: linkedin.com/events/75179372…
6
3
6
347
When a company gets acquired, its roadmap stops being its own. Our biggest competitor is now the memory layer for someone else’s AI agents. These are the receips, all from @Twilio: Oct 2020: Twilio buys Segment for $3.2B in stock. Dec 2023: Twilio’s CEO tells the company “Segment is core to CustomerAI.” Q2 2025: Segment revenue is “nearly flat” year over year. Net expansion 95%, from “churn and contraction affecting our existing customers.” Q3 2025: Twilio stops reporting Segment as its own segment. It’s folded into the rest of Twilio. 5 Oct 2026: Segment’s new GA release syncs customer profiles into Twilio Conversation Memory, so Twilio’s AI agents can read them mid-conversation. An acquired product serves the acquirer’s strategy. Twilio’s strategy is communications and agents. But 95% net expansion means existing customers, as a group, spent less on Segment than they did a year earlier. Put that next to the timeline. Customers are spending less, Twilio stopped reporting Segment on its own, and this month’s Segment GA release was built for Twilio’s AI agents. If your events run through Segment, you’re paying for a product whose next move gets decided by what Twilio needs. @jitsucom takes the same tracking calls as Segment, so switching is not a rewrite. It’s MIT licensed and self-hostable, so the code you run is yours, permanently. If you’re renewing Segment this year and want to see what moving over looks like, DM me. I’ll personally get on a call and answer your questions.
1
2
7
410
A normal event pipeline only knows the event that just arrived. The history of that user lives somewhere else, so a first-time buyer and a repeat buyer are treated like the exact same thing when data flows to destinations. Which is exactly why we have Jitsu functions. A Jitsu function is javascript code that runs on every event before it reaches any destination. So you and your team can rewrite the event, add fields, or drop it entirely. One of the helpers you receive is getWarehouse, which runs a SQL query against the warehouse from inside the function. An Order Completed event can therefore arrive, the function can ask ClickHouse how many orders that user has already placed, write the number onto the event as lifetime_orders, and let the enriched event continue to its destinations - @Meta Conversions API included. The ad platform receives an event that already knows whether this is the first purchase or seventh. Functions also receive a key-value store with a 31-day default TTL, fetch for calling external APIs, geo derived from the IP, and a parsed user agent that includes a bot flag. If you're a CTO/VP of data eng and are fed up of managing complex data pipelines or tired of your $250k Segment bill, DM @sohmehta jitsu.com/docs/functions
1
1
4
444
Thanks for reading my post. I may not be able to personally get back to each one of you today because of the sheer volume of requests but I'll try my best to so by Sunday Eve. Incase anybody wants to try jitsu.com for their data pipelines, please feel free to DM me - I'll help you get started. We're an open source segment alternative and are paving the next generation of customer data platforms. The number one reason why enterprises trust @jitsucom is because of jitsu transformation functions and data transformation capabilities. We not only have a profile builder that can track anonymised users (this is big for marketing use cases) but also we don't charge you for MTUs like segment. Enterprises and mid market customers are saving hundreds of thousands of $$ on their segment bill with jitsu. If you're a VP of data engineering/CTO you can directly book a meet with me from my profile - completely free. Hope you Have a great weekend!
1
3
1
9
3,033
early days at @jitsucom were not all about launches.. people were already pissed about their Segment bill. we dm’d them, got on a call, and fixed their pipeline. We're the leading open-source Segment alternative. mid-market teams are cutting hundreds of thousands of $$ on their annual bill with Jitsu. We are revolutionising what it means to be a Customer Data Platform. jitsu.com
i got to $120k revenue without doing half of this. no product hunt. no 50 chatgpt blog posts. no facebook ads. what actually got me my first 100 users (no bs): 1) dm'ing people who had already complained about the exact problem i was trying to solve on LinkedIn and X. keep it short and simple. 2) replying under every post in the niche for 30 days. not “check out my tool.” actual answers with insights. 3) obsessing over the first 20 users. be it calls, loom videos, or fixing their setup myself. 4) posting the $$ numbers. $0. then $10k. people trust authenticity. ads and blogs only start working after some users are already paying you. before that 90% of the job is just talking to people who already have the problem. are you stuck at getting users for your product? comment the product link and i’ll tell you how i'll go about acquiring your first 100 users. first 10 comments get a loom video. Disclaimer - I lead growth at a YC startup
3
248
i got to $120k revenue without doing half of this. no product hunt. no 50 chatgpt blog posts. no facebook ads. what actually got me my first 100 users (no bs): 1) dm'ing people who had already complained about the exact problem i was trying to solve on LinkedIn and X. keep it short and simple. 2) replying under every post in the niche for 30 days. not “check out my tool.” actual answers with insights. 3) obsessing over the first 20 users. be it calls, loom videos, or fixing their setup myself. 4) posting the $$ numbers. $0. then $10k. people trust authenticity. ads and blogs only start working after some users are already paying you. before that 90% of the job is just talking to people who already have the problem. are you stuck at getting users for your product? comment the product link and i’ll tell you how i'll go about acquiring your first 100 users. first 10 comments get a loom video. Disclaimer - I lead growth at a YC startup
148
100
11
1,932
137,259
A typical YC homepage loads 1 tracker. The ones with OpenAI's ChatGPT ads pixel load 7. Of the 36 homepages that load 10 or more, 20 have the pixel. @Jitsucom collects each event once and delivers it to each destination. jitsu.com
1
5
214
@jitsucom MCP launched on September 8. The post got 281,853 views on X, 640 likes and 16 reposts. đź’ś Thank you to everyone who showed their support. @salesforce 's Data 360 MCP server and @RudderStack 's both came before ours, and you guys made us the most viral MCP launch of the month for event pipelines! Docs - jitsu.com/docs/mcp
2
116
it still amazes me how our @jitsucom MCP launch on X went viral beating companies like @salesforce and @RudderStack ( mind blowing, right? ) jitsu mcp is one of the biggest things i've posted, with over 280k views and hundreds of DMs from you guys salesforce's data 360 mcp server went live 20 days before us and rudderstack posted theirs 28 days before we were third and still outperformed them. If you're a CTO/VP of data eng and are fed up of managing complex data pipelines or tired of your $250k Segment bill, DM me. Link to the post in comments 👇
5
2
7
386
Segment began in 2012 as analytics.js, one API instead of a snippet per analytics tool. On YC homepages from the 2025-26 batches it appears on 1 of 1,303, while 3 in 4 PostHog homepages load another tracker beside it. @jitsucom runs the same analytics.js API, open source. set up your event pipeline today for free: jitsucom
1
6
339
Most analytics tools make you send your user data to them first. Then they drip it into your database later. And they charge you based on how many people visit your site. Jitsu works the other way. You collect events from your website or app and send them straight into a database you control. Usually in minutes. You don’t have to rip out your existing tracking to try it. If you already use Segment, those same snippets still work. Free to start: 200,000 events a month on Jitsu Cloud a real database included or run it yourself for free (it’s open source) If you use Claude or Cursor, you can also hook Jitsu up and let the AI set up the pipeline for you. One command: claude mcp add --transport http jitsu use.jitsu.com/mcp Site: jitsu.com
1
4
331
Another reason why you should use Jitsu
Today we're launching Observability Exports in Jitsu. Everything you see in Live Events can now stream into @datadoghq, @grafana Cloud, @newrelic, @elastic, or your own @OpenTelemetry Collector. Here's how it works: 1. Go to your Jitsu account's Settings → Observability exports. Set your OTLP endpoint: otlp.datadoghq.com/v1/logs 2. Add your auth header. Datadog wants dd-api-key. 3. Send test log, toggle Enabled, then go find it: service:jitsu-live-events Four record types land: function, bulker_batch, bulker_stream, dead-letter. Your raw event traffic is never exported. These are operational logs about your pipelines. Datadog takes OTLP directly, so there's no agent or collector sitting in between. @Jitsucom is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Observability Exports is on Jitsu Enterprise plan. DM me to enable it for your org. More in comments!
1
3
472
đź’śđź’ś
Today we're launching Observability Exports in Jitsu. Everything you see in Live Events can now stream into @datadoghq, @grafana Cloud, @newrelic, @elastic, or your own @OpenTelemetry Collector. Here's how it works: 1. Go to your Jitsu account's Settings → Observability exports. Set your OTLP endpoint: otlp.datadoghq.com/v1/logs 2. Add your auth header. Datadog wants dd-api-key. 3. Send test log, toggle Enabled, then go find it: service:jitsu-live-events Four record types land: function, bulker_batch, bulker_stream, dead-letter. Your raw event traffic is never exported. These are operational logs about your pipelines. Datadog takes OTLP directly, so there's no agent or collector sitting in between. @Jitsucom is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Observability Exports is on Jitsu Enterprise plan. DM me to enable it for your org. More in comments!
3
176
Today we're launching Observability Exports in Jitsu. Everything you see in Live Events can now stream into @datadoghq, @grafana Cloud, @newrelic, @elastic, or your own @OpenTelemetry Collector. Here's how it works: 1. Go to your Jitsu account's Settings → Observability exports. Set your OTLP endpoint: otlp.datadoghq.com/v1/logs 2. Add your auth header. Datadog wants dd-api-key. 3. Send test log, toggle Enabled, then go find it: service:jitsu-live-events Four record types land: function, bulker_batch, bulker_stream, dead-letter. Your raw event traffic is never exported. These are operational logs about your pipelines. Datadog takes OTLP directly, so there's no agent or collector sitting in between. @Jitsucom is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Observability Exports is on Jitsu Enterprise plan. DM me to enable it for your org. More in comments!
52
95
24
1,035
211,152
Your data pipeline broke overnight. And Now you're digging through logs trying to figure out whether the event reached @Snowflake , @HubSpot , or your email tool. Jitsu MCP lets you ask your agent instead. “Did yesterday's signups reach HubSpot?” It checks the logs and tells you where the sync stopped, so you can actually focus on fixing the problem instead of finding it.
2
2
5
405
Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu use.jitsu.com/mcp Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.
2
39
try our MCP now in Claude Code: claude mcp add --transport http jitsu use.jitsu.com/mcp
2
99
Jitsu MCP covers more than 26 tools across configuration, Live Events, connector syncs, testing and the audit log. Which means an agent can create a destination, watch what lands, and rewrite the function in the path without leaving the conversation. You can read more about it: jitsucom/docs/mcp
Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu use.jitsu.com/mcp Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.
1
1
4
212
Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu use.jitsu.com/mcp Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.
55
16
35
611
283,010
Someone in the comments moved off Segment to Jitsu and says their costs dropped ~75%. The reason is simple: We only bill you for events delivered to a destination, not events collected. Capturing events is unlimited. Turns out what most teams capture never needed to be billable in the first place. This is especially true if you are running an E-commerce or a D2C brand - where anonymised users and bots make up for a decent amount of your traffic. With Jitsu, You're converting your $500k Segment bill to almost $100 - 150k.
Introducing Jitsu, the open source event data pipeline. Every signup, click and payment in your product is an event. Most companies ship those off to a vendor and pay by the event to read them back. We run the same job on your own infrastructure. One script tag to collect, one workspace to route, and a provisioned ClickHouse on the other side. Or send everything to Snowflake, BigQuery, Redshift, Postgres, MySQL. Capturing events is unlimited and free. We only charge for events we deliver to a destination. Need to change an event on its way through? Write a function in the workspace and we run it on everything in flight. MIT licensed, so the whole thing is yours to read, change and run. 200k delivered events a month, free. jitsu.com
3
2
9
548