Jitsu

1. 1

   You collect events. Jitsu accepts data from an HTML snippet, an npm package, a tracking pixel, the HTTP API, server-to-server calls, and SDKs for React, React Native, iOS, and Android. There is also a Segment Proxy, which lets an existing Segment implementation point at Jitsu without the application being re-instrumented, which is by some distance the cheapest migration path in this category.

2. 2

   Events pass through functions written in TypeScript. These run in the pipeline and can filter, transform, or enrich an event before delivery, so a personal data field can be dropped for one destination while the warehouse keeps it, or an event can be reshaped for a tool that expects a different schema.

3. 3

   Destinations receive the result. Warehouses and block storage are the primary targets, alongside analytics tools including Amplitude, Mixpanel, and PostHog, advertising platforms such as Google Ads, email services including SendGrid and Resend, CRMs including HubSpot and Salesforce, plus generic webhooks and custom tags for anything without a native connector. Destinations are unlimited on every plan including the free one.

4. 4

   Connectors run in the other direction, pulling data from third-party sources on a schedule. Sync frequency is the paid differentiator: manual runs with one daily active sync on the free plan, hourly syncs with five monthly active syncs on Business, and one-minute syncs with unlimited active syncs on Enterprise.

5. 5

   The events debugger shows data arriving in real time, which is the feature that makes instrumentation work tolerable, and a configuration API means the whole pipeline can be managed programmatically rather than clicked together. Deployment is your choice throughout: Jitsu Cloud, a private cloud, on-premises, or the MIT-licensed self-hosted build via Docker Compose or Helm.

Freemium cloud subscription metered on active events per month with unlimited destinations on every plan and connector sync frequency as the tier differentiator, alongside a free MIT-licensed self-hosted build with no usage limits.

Value assessment: On price per event, Jitsu is the cheapest credible option in this category, and the MIT-licensed self-hosted build is free at any volume for teams able to run it. Modelling the bill takes one multiplication. A product with 10,000 monthly users generating around twenty events each produces roughly 200,000 events a month, which lands exactly on the free tier boundary. The same product at 100,000 monthly users produces around 2 million events, which is precisely the $99 Business allowance. The equivalent RudderStack figures are the free tier at 250,000 and $265 a month for one million, so at the 100,000 user mark Jitsu is roughly a fifth of the cost. What that money does not buy is governance. There are no tracking plans, no data catalog, no consent management at the pipeline level, and no warehouse-native identity resolution, and the destination catalogue is dozens rather than hundreds. Jitsu is excellent value if your requirement is delivery, and false economy if your requirement is data quality control across a growing organisation.

Setup time

An hour on the cloud: create a source, add the tag or SDK, connect a warehouse destination, and confirm in the events debugger. Self-hosting is a longer exercise, from an afternoon with Docker Compose to a proper Helm deployment with its own datastore and monitoring.

Learning curve

Low for basic delivery and moderate once TypeScript functions are involved, since transformation logic is real code that needs testing and maintenance. The absence of tracking plans means schema discipline is entirely a matter of your own process rather than something the tool enforces, which is the main thing to plan for.

Onboarding

Fully self-serve on Free and Business, with cloud, private cloud, and on-premises deployment options offered on every plan. Enterprise adds direct support. Documentation covers ingestion methods, functions, connectors, and self-hosted deployment.

Migration notes

The Segment Proxy is the standout: an existing Segment implementation can point at Jitsu without touching application code, so migration is configuration rather than re-instrumentation. Historical events already delivered elsewhere do not move, but with a warehouse destination configured from the start your history accumulates somewhere you own. Leaving Jitsu costs you the pipeline configuration and any TypeScript functions you wrote, and because the software is MIT licensed the ultimate fallback is simply to keep running the version you have.

Platforms

JavaScript HTML snippet and npm packageReact and React NativeiOS and AndroidHTTP API and server to serverTracking pixelSegment ProxyDocker Compose and Helm self-hosting

API

HTTP ingestion API plus a configuration API for managing sources, destinations, and functions programmatically, included even on the free plan. Transformations are written as TypeScript functions that run inside the pipeline.

Compliance

GDPR considerations addressed primarily through self-hosting and per-destination transformation rather than a packaged consent featureConfirm current certification status with the vendor during procurement

Data residency

Self-hosting via Docker Compose or Helm on your own infrastructure gives complete residency control, and private cloud and on-premises deployment are offered on every commercial plan including the free tier, which is unusual. This is the strongest residency answer among the pipeline options here.

Security notes

TypeScript functions can drop or hash personal fields per destination before delivery, so sensitive data need not reach a marketing tool that does not require it. Custom domains improve collection reliability and keep the tracking endpoint under your own name. There is no packaged pipeline-level consent management of the kind RudderStack provides, so consent enforcement is your own design problem.

Channels

Community support on the open source and free tiersStandard support on BusinessDirect support on Enterprise

Documentation

Documentation at jitsu.com/docs covering ingestion methods, TypeScript functions, connectors, destinations, and self-hosted deployment via Docker Compose and Helm.

Community

Public development on GitHub with an active repository, plus a community around the open source Segment alternative positioning that dates back to the project's 2021 Hacker News launch.

Founded

2020

Headquarters

San Francisco, California, United States

Ownership

Venture-backed, privately held, Y Combinator S20

Founders

Peter Wysinski, Vladimir Klimontovich

Employees

Approximately 9 (2026)

Funding

$2M seed raised in December 2020, led by Costanoa Ventures with participation from Y Combinator, The House Fund, and SignalFire. No subsequent rounds reported.

Jitsu is the cheapest honest way to get event data into your own warehouse, and the MIT licence is the reason to take it seriously rather than treat it as a budget option. Two million events for $99 a month, unlimited destinations on every plan including free, custom domains and a configuration API without paying, and a Segment Proxy that turns a migration into a configuration change: for a technically capable small team, that is a strong offer. It is also an unambiguous one, because the gaps are easy to see. There is no governance layer, no identity resolution, no consent management, a destination catalogue measured in dozens, and nine people behind it. Buy Jitsu when the requirement is delivery, when your team can write a TypeScript function without ceremony, and when owning the software matters. Buy RudderStack instead when data quality across a growing organisation is the actual problem, and buy neither if you have one analytics tool, no warehouse, and no third destination in sight.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.