Jitsu

Teams that outgrow a hosted analytics pipe tend to hit the same two walls, delivery latency and billing tied to tracked users. Jitsu collects event data from websites, apps and servers and delivers it to your warehouse and whatever else you use, covering the same ground as Segment while staying self-hostable.

Data lands in minutes rather than hours, because each destination is fed in batches as frequent as a minute, or row by row where that suits it better. Events reach Jitsu through SDKs, an HTTP API, or a drop-in Segment proxy that needs no client code changes at all.

A working setup usually leans on a handful of pieces.

• Destinations: ClickHouse, BigQuery, Snowflake, Redshift, Postgres, S3, GCS and dozens of SaaS tools, streamed or micro-batched.
• Functions: JavaScript that runs on every event to filter, transform and enrich it before delivery.
• Connector syncs: Airbyte-compatible connectors pull third party data into your warehouse.
• Live Events: every event, function log and destination write is visible as it happens.
• MCP server: twenty five tools let an AI agent configure and operate the whole pipeline.

The services are backed by Postgres for configuration, Kafka or Redpanda as the event bus, ClickHouse for live events and metrics, and MongoDB for profiles. Self-hosting under the MIT license carries no usage limits and no feature gating. A development Helm chart brings the full stack up on Minikube for a first look, while the production guide covers scaling each service and sizing Kafka.