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

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

@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

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

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.

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?

40,583,074,337 events through Jitsu in the last 90 days. 451 million a day. 5,217 every second. We open sourced Jitsu under MIT, so you can Clone it and run it on your own hardware with 0 volume cap. Jitsu's free tier gives you 200,000 active events a month and provisions a real @ClickHouseDB with credentials you can point your terminal at. Try it now: jitsucom

Jitsu just passed 5,000 stars on @GitHub.💜 We’re an open-source event pipeline that’s Segment-API compatible and MIT-licensed. Your existing analytics.js works unchanged. Our free tier provisions a live @ClickHouseDB instance with real credentials—not a query box. You can query your events directly from your terminal: clickhouse-client --host --port 9440 --secure --database --user You can also point a Segment webhook destination at a Jitsu endpoint and run both pipelines on the same traffic while you evaluate—no migration required. Free for upto 200,000 events per month. Self-hosted is free forever. Grateful to everyone who starred, filed issues, and contributed PRs.

🚀 Exciting news! Jitsu 2.6 has landed! Check out the latest enhancements in our release notes on GitHub: git.new/jitsu-2-6 And of course, all those amazing features are already live on Jitsu Cloud too! 👉go.jitsu.com/cloud