What is Jitsu?
Jitsu collects event data from your websites, apps and servers, and delivers it to your data
warehouse and to whatever other tools you use. It covers the same ground as Segment, but it's
MIT-licensed and self-hostable, so the whole pipeline can run inside your own infrastructure —
or on Jitsu Cloud, same software, hosted.
Data lands in minutes, not hours: Segment loads warehouses once or twice a day (hourly at best),
while Jitsu delivers per destination in batches as frequent as a minute, or row-by-row where that
suits the destination. And where Segment bills by Monthly Tracked User, Jitsu Cloud bills by event
volume, so the bill tracks data rather than audience size — while self-hosting has no usage billing
at all.
A typical Jitsu setup gives you:
- Event collection from the browser, mobile, or the server, via
SDKs, an HTTP API, or a drop-in Segment proxy.
- Delivery to destinations — ClickHouse, BigQuery, Snowflake, Redshift, Postgres, S3, GCS, and
dozens of SaaS tools, streamed or micro-batched depending on what the destination prefers. See the
destination catalog.
- Functions — JavaScript that runs on every event to filter,
transform, and enrich it before delivery.
- Write them in the browser, or build and deploy them from your own repo with the
Jitsu CLI —
jitsu-cli init scaffolds a TypeScript project
with tests, and jitsu-cli deploy ships it to your workspace. Use whatever tooling you like:
TypeScript, npm libraries, your own test suite, and your normal CI.
- Connector syncs — pull data into your warehouse from third-party sources (Airbyte-compatible
connectors).
- A user identity graph and profile builder, built automatically from the event stream.
- Live Events — see every event, function log and
destination write as it happens, which makes debugging a pipeline a matter of seconds rather than
days.
- An MCP server, so an AI agent can configure and operate all of
the above.
Get started with Jitsu Cloud
The fastest way to run Jitsu is Jitsu Cloud — we host and scale it for
you.
- Free tier: 200k events/month, no credit card required.
- Unlimited destinations and unlimited captured events on every plan.
- A free ClickHouse instance is included, so you can go from zero to queryable event data
without provisioning a warehouse first.
- Custom domains, events debugger, and the Configuration API on the free tier too.
See pricing for the full breakdown, or jump straight into the
Quick Start guide.
Once you have a workspace:
- Create a site (a stream) and grab your write key.
- Add a destination — ClickHouse, BigQuery, Snowflake, Postgres, S3, or anything from the
catalog.
- Start sending events using one of the methods below.
Sending events
Everything the UI does is also available through the
Management API and the
Jitsu CLI.
Jitsu MCP Server
Jitsu ships a Model Context Protocol server, so coding agents and
AI assistants can build and operate your data pipelines directly — no clicking through the UI.
An agent connected to Jitsu can set up a destination, wire a connection, send a test event, read the
resulting Live Events, notice that a function threw, fix the function, and re-run it — the full
loop, without a human in the middle.
Endpoint: https://use.jitsu.com/mcp (or <your-console-url>/mcp when self-hosting).
Connect your client
Claude Code
claude mcp add --transport http jitsu https://use.jitsu.com/mcp
Other clients (Claude Desktop, Cursor, VS Code) take the same URL — see
jitsu.com/docs/mcp for their setup.
Authentication
Interactive clients use OAuth 2.1 — no API key to manage. The first tool call opens a browser
tab asking you to approve the connection; tokens are scoped, listed, and revocable from your account
settings page.
Headless environments (CI, cron, servers) use a personal API key instead — generate one on the user
settings page and pass it as Authorization: Bearer <keyId>:<keySecret>:
claude mcp add --transport http jitsu https://use.jitsu.com/mcp \
--header "Authorization: Bearer $JITSU_API_KEY"
This is the beginning of the README. Read the rest at the original. Read the full README ↗
