jitsu.com
Independent Directory - Important Information
This llms.txt file was publicly accessible and retrieved from jitsu.com. LLMS Central does not claim ownership of this content and hosts it for informational purposes only to help AI systems discover and respect website policies.
This listing is not an endorsement by jitsu.com and they have not sponsored this page. We are an independent directory service with no affiliation to the listed domain.
Copyright & Terms: Users should respect the original terms of service of jitsu.com. If you believe there is a copyright or terms of service violation, please contact us at support@llmscentral.com for prompt removal. Domain owners can also claim their listing.
Current llms.txt Content
# Jitsu > Jitsu is an open-source data integration platform and a self-hostable alternative to Segment. It collects event data from web, app, and server sources and streams it in real time into your data warehouse, with identity stitching, serverless functions, and Segment-compatible ingestion APIs. ## Site - [Home](https://jitsu.com/) - [Pricing](https://jitsu.com/pricing) - [Customers](https://jitsu.com/customers) - [Blog](https://jitsu.com/blog) - [Changelog](https://jitsu.com/changelog) - [Connectors (sources) catalog](https://jitsu.com/integrations/connectors) - [Destinations catalog](https://jitsu.com/integrations/destinations) - [Real-time Event Streaming](https://jitsu.com/features/event-streaming) - [Identity Stitching](https://jitsu.com/features/identity-stitching) - [Functions](https://jitsu.com/docs/functions) - [Segment API Compatibility](https://jitsu.com/features/segment-compatibility) - [Security & Compliance](https://jitsu.com/security) - [Privacy Policy](https://jitsu.com/privacy) - [Terms of Service](https://jitsu.com/tos) - [On-premise CDP](https://jitsu.com/on-premise): Jitsu as an on-premise CDP on the Enterprise plan: On Prem on your own infrastructure, or Private Cloud (single-tenant, managed by Jitsu on a dedicated GCP or AWS sub-account); the services and dependencies an install runs, which warehouses it loads, and what Enterprise adds (SSO via OIDC, priority support and an uptime SLA, a security and compliance review). - [MCP server](https://jitsu.com/features/mcp): The Jitsu MCP server at https://use.jitsu.com/mcp (or /mcp on an on-premise console): 26 tools for configuration, Live Events and testing, connectors and syncs, statistics and the audit log; OAuth 2.1 for Claude Code, Claude Desktop, Cursor and VS Code, a personal API key for CI; every change recorded in the audit log with an MCP origin. - [Access control and audit log](https://jitsu.com/features/access-control): Access control in Jitsu: workspace roles (owner, editor, read-only analyst), Enterprise SSO via OIDC, personal API keys with names and optional expiration dates, revocable agent connections, and an audit log that records configuration changes with a field-level diff and masked secrets, membership changes and logins, with the origin of each: UI, API, CLI or MCP. ## Comparisons Each page below is also available as markdown by appending `.md` to its URL. - [Compare Jitsu](https://jitsu.com/compare): Head-to-head comparisons of Jitsu against Segment, RudderStack, Snowplow, PostHog and Hightouch. Published prices, named concessions, no ticks and crosses. - [Jitsu vs Segment](https://jitsu.com/compare/jitsu-vs-segment): Per active event against per tracked user. At 50,000 tracked users and 5M events, $219 against $575, both published rates. - [Segment alternatives](https://jitsu.com/compare/segment-alternatives): Five Segment alternatives compared. At 50,000 tracked users and 5M events a month, on published list prices: Segment $575, RudderStack $995, Jitsu $219. - [Jitsu vs RudderStack](https://jitsu.com/compare/jitsu-vs-rudderstack): Same billing model. MIT against Elastic License 2.0, and at 5 million events $219 against $995, both published. - [Jitsu vs Snowplow](https://jitsu.com/compare/jitsu-vs-snowplow): Snowplow needs a schema for each custom event, prices by quote after a 14-day trial and loads into your own warehouse. Jitsu creates columns from the data, includes ClickHouse and publishes its price. - [Jitsu vs PostHog](https://jitsu.com/compare/jitsu-vs-posthog): PostHog is a destination, Jitsu is the pipe that feeds it and every other tool. Events are sent once and billed once as active events, $219 a month at 5 million. - [Jitsu vs Hightouch](https://jitsu.com/compare/jitsu-vs-hightouch): Hightouch sells event collection as one module of a marketing platform, priced after a demo. Jitsu is the collection layer on its own, MIT licensed, from a published $99. - [Self-hosted vs managed CDP](https://jitsu.com/compare/self-hosted-vs-managed-cdp): What running the pipeline yourself actually costs against paying somebody to run it. ## Industries Each page below is also available as markdown by appending `.md` to its URL. - [Event tracking by industry](https://jitsu.com/industries): Jitsu guides for fintech, mobile apps and games, and media and publishing. Each starts from that industry's problem (funded-account ad conversions, noisy game telemetry and retention, subscriber attribution) and gives the events, Jitsu functions, warehouse SQL and a tracking plan CSV. - [Fintech & financial services](https://jitsu.com/industries/fintech): Jitsu for fintech: funded-account conversions sent from the backend to Meta Ads and Google Ads, the signup to KYC to first deposit funnel in the warehouse, a guardrail function that drops events carrying card numbers, Jitsu Cloud, Private Cloud, On Prem or MIT-licensed self-hosting, a 35-event tracking plan (CSV), and billing on active events (Free 200,000 a month; Business $99 a month for 2M, then $40 per additional 1M). - [Onboarding and KYC funnel](https://jitsu.com/industries/fintech/onboarding-kyc-funnel): Seven events from Account Created to Account Funded, five of them sent from the backend over the HTTP API with a server-to-server write key, a tracking-plan contract function, and ClickHouse funnel SQL using FINAL; identity stitching is Enterprise on Jitsu Cloud, warehouses only, up to 30 days back. - [Funded-account ad conversions](https://jitsu.com/industries/fintech/funded-account-ad-conversions): Account Funded sent from the backend to the Meta Ads and Google Ads destinations, so ad platforms optimize on funded accounts instead of signups: a guardrail function drops events carrying card numbers, an allowlist function keeps two conversions with value and currency and sends only a SHA-256 of userId, and Google Ads SHA-256 hashes email, phone and names. - [Self-hosted data residency](https://jitsu.com/industries/fintech/self-hosted-data-residency): Data residency for fintech: Jitsu Private Cloud (single-tenant, managed by Jitsu on a dedicated GCP or AWS sub-account) and On Prem on the Enterprise plan, with a security and compliance review, SSO via OIDC and an uptime SLA, or MIT-licensed self-hosting on Kubernetes with the Jitsu operator; a function writes a raw and a masked copy of every event; Jitsu Cloud is hosted in the United States. - [Mobile apps & games](https://jitsu.com/industries/mobile-apps-and-games): iOS, Android and React Native apps send through Segment's open-source libraries pointed at Jitsu; Unity, Unreal and Godot clients and backends post JSON to the HTTP API. Functions enforce the tracking plan and drop noise before billing; every Jitsu Cloud workspace includes ClickHouse. - [Event tracking plan](https://jitsu.com/industries/mobile-apps-and-games/event-tracking-plan): A 33-event plan as a CSV, Segment's mobile setup, purchases sent from the backend with the store's transaction ID as order_id and store:order_id as messageId, and functions that keep purchases server-side and quarantine events outside the plan. - [Filtering noisy events](https://jitsu.com/industries/mobile-apps-and-games/filter-noisy-events): A function drops heartbeats, frame ticks and QA accounts and samples performance data per player. Dropped events are not billed unless the function called fetch before dropping them. - [Retention and revenue in ClickHouse](https://jitsu.com/industries/mobile-apps-and-games/clickhouse-retention-analytics): Tested ClickHouse SQL for retention by install day, sessions from a 30-minute gap and first-week revenue per cohort, against Jitsu's default events table with FINAL. - [Media & publishing](https://jitsu.com/industries/media): What publishers track (11 core events, a 34-event CSV), how reader events reach BigQuery or ClickHouse through Jitsu functions, subscription conversions sent from billing to Google Ads and Meta with consent, measuring blocker loss on your own site, running next to Segment, and Investing.com's 5 billion events a month. - [Server-side and first-party tracking](https://jitsu.com/industries/media/first-party-tracking-ad-blockers): Custom domains (Business and Enterprise), the ID endpoint for Safari's 7-day cap on script-set cookies, and BigQuery SQL that measures what browser analytics still misses on your own site from sampled server-side page renders. - [Subscription analytics](https://jitsu.com/industries/media/subscriber-conversions): Subscription conversions from the billing backend sent to Google Ads and Meta only with recorded advertising consent and three properties, SQL for what new subscribers read in the 30 days before signing up, and the reader-to-subscriber funnel events. - [Reader events in your own warehouse](https://jitsu.com/industries/media/reader-data-warehouse): One events table in BigQuery or ClickHouse, a function that adds CMS article metadata with fetch and a cached store lookup, a function that strips internal traffic and personal URL parameters, engaged-reading SQL, and a query that estimates your monthly active events and events per reader. ## Blog Each post below is also available as markdown by appending `.md` to its URL, except "Introducing Jitsu Connectors", "What is warehouse-first architecture?" and "Introducing Jitsu Next", which are built as pages rather than markdown documents. - [Claude Code MCP for Event Pipelines: 5 Prompts That Work](https://jitsu.com/blog/claude-code-mcp-event-pipeline): Connect Claude Code to the Jitsu MCP server and run an event pipeline with five prompts: set up a destination, debug a failing function, audit agent changes. - [PII Masking for Event Data, Before the Warehouse](https://jitsu.com/blog/pii-masking-event-data): A tested Jitsu function that removes, hashes and redacts PII in event data before storage: emails, phone numbers, card numbers in free text and IP addresses. - [On-Premise CDP: 9 Questions to Settle Before You Buy](https://jitsu.com/blog/on-premise-cdp-questions): The questions regulated teams ask before running a CDP on-premise, in order: what leaves the network, who patches it, which warehouse it loads, what it costs. - [Segment pricing: how MTUs work and when they get expensive](https://jitsu.com/blog/segment-pricing-mtus): Segment charges by monthly tracked user, not by event. Here is how MTUs are counted, what that costs as you grow, and when per-event pricing is cheaper. - [Jitsu 2.14 is now public: Kubernetes-native for production self-hosting](https://jitsu.com/blog/jitsu-2-14): Jitsu 2.14 is public: a Kubernetes-native release that runs functions, profile builders, and connector syncs as managed workloads, with major self-hosting upgrades. - [Jitsu now speaks MCP: let your agent build and debug the pipeline](https://jitsu.com/blog/jitsu-mcp): Connect Claude, Cursor, or VS Code to the Jitsu MCP server to configure destinations and streams, watch Live Events, and edit Functions β an agent that builds and debugs your pipeline. - [Best Open-Source CDPs & Self-Hosted Segment Alternatives (2026)](https://jitsu.com/blog/open-source-cdp): An honest guide to open-source and self-hosted CDPs in 2026 β real pros, cons, and licenses for Jitsu, RudderStack, PostHog, Snowplow, and more. - [Jitsu, now programmable: Management API, CLI, and ready for AI agents](https://jitsu.com/blog/openapi-and-cli): Use the Jitsu Management API, OpenAPI spec, and jitsu-cli to automate pipelines, manage resources in CI, and give AI agents a real API surface. - [Introducing Jitsu Notifications: Proactive Monitoring Made Simple](https://jitsu.com/blog/introducing-notifications): Get proactive monitoring for Jitsu pipelines with notifications that alert your team by email or Slack when syncs, streams, or destinations fail. - [Server side tracking 101](https://jitsu.com/blog/server-side-tracking): Learn server-side tracking basics, how it differs from browser pixels, where it improves reliability, and how to implement it with Jitsu today. - [Introducing Jitsu Connectors](https://jitsu.com/blog/jitsu-connectors): Jitsu Connectors are out of beta. Pull data from SaaS apps, databases, and custom sources into warehouse destinations with managed syncs today. - [What is warehouse-first architecture?](https://jitsu.com/blog/data-warehouse-first): Learn what warehouse-first architecture means, why modern data teams use the warehouse as their source of truth, and how Jitsu fits the pattern. - [Introducing Jitsu Next](https://jitsu.com/blog/jitsu-next): Meet Jitsu Next: a faster way to capture event data into your stack, with a new UI, rebuilt core, free tier, and unlimited incoming events for teams. ## Documentation The documentation pages below are also available as markdown by appending `.md` to any URL. ## Get Started - [Introduction](https://jitsu.com/docs) - [Quickstart](https://jitsu.com/docs/quick-start.md) - [Core concepts](https://jitsu.com/docs/core-concepts.md) - [Management API](https://jitsu.com/docs/api.md) - [MCP Server](https://jitsu.com/docs/mcp.md) ## Sending Data - [Overview](https://jitsu.com/docs/sending-data.md) - [JavaScript Reference](https://jitsu.com/docs/sending-data/js-reference.md) - [ITP Mitigation](https://jitsu.com/docs/sending-data/js-reference/itp.md) - [HTML snippet](https://jitsu.com/docs/sending-data/html.md) - [HTTP API](https://jitsu.com/docs/sending-data/http.md) - [Pixel API](https://jitsu.com/docs/sending-data/pixel.md) - [NPM Package](https://jitsu.com/docs/sending-data/npm.md) - [React](https://jitsu.com/docs/sending-data/react.md) - [React Native](https://jitsu.com/docs/sending-data/react-native.md) - [iOS](https://jitsu.com/docs/sending-data/ios.md) - [Android](https://jitsu.com/docs/sending-data/android.md) - [Segment Proxy](https://jitsu.com/docs/sending-data/segment-proxy.md) - [Consent Management](https://jitsu.com/docs/sending-data/consent-management.md) - [Server to Server](https://jitsu.com/docs/sending-data/server-to-server.md) ## Functions - [Overview](https://jitsu.com/docs/functions.md) - [Functions Runtime](https://jitsu.com/docs/functions/runtime.md) - [Pipeline](https://jitsu.com/docs/functions/pipeline.md) - [Advanced](https://jitsu.com/docs/functions/advanced.md) - [Command-line SDK](https://jitsu.com/docs/functions/sdk.md) ## Destinations - [All Destinations](https://jitsu.com/docs/destinations/catalog.md): Every destination Jitsu can send your event data to, grouped by type. - [BigQuery](https://jitsu.com/docs/destinations/warehouse/bigquery.md) - [ClickHouseοΈ](https://jitsu.com/docs/destinations/warehouse/clickhouse.md) - [MongoDB](https://jitsu.com/docs/destinations/warehouse/mongodb.md) - [MotherDuck (DuckDB)](https://jitsu.com/docs/destinations/warehouse/duckdb.md) - [MySQL](https://jitsu.com/docs/destinations/warehouse/mysql.md) - [PostgreSQL](https://jitsu.com/docs/destinations/warehouse/postgres.md) - [Redshift](https://jitsu.com/docs/destinations/warehouse/redshift.md) - [Snowflake](https://jitsu.com/docs/destinations/warehouse/snowflake.md) - [Google Cloud Storage](https://jitsu.com/docs/destinations/block-storage/gcs.md) - [S3](https://jitsu.com/docs/destinations/block-storage/s3.md) - [Amplitude](https://jitsu.com/docs/destinations/amplitude.md) - [Google Ads](https://jitsu.com/docs/destinations/google-ads.md) - [Google Analytics 4 (Cloud)](https://jitsu.com/docs/destinations/ga4.md) - [Google Analytics 4 (Device)](https://jitsu.com/docs/destinations/ga4-tag.md) - [Hotjar](https://jitsu.com/docs/destinations/hotjar.md) - [Hubspot](https://jitsu.com/docs/destinations/hubspot.md) - [Microsoft Clarity](https://jitsu.com/docs/destinations/clarity.md) - [Mixpanel](https://jitsu.com/docs/destinations/mixpanel.md) - [Posthog](https://jitsu.com/docs/destinations/posthog.md) - [Resend](https://jitsu.com/docs/destinations/resend.md) - [Salesforce](https://jitsu.com/docs/destinations/salesforce.md) - [SendGrid](https://jitsu.com/docs/destinations/sendgrid.md) - [Tag](https://jitsu.com/docs/destinations/tag.md) - [Webhook](https://jitsu.com/docs/destinations/webhook.md) ## Features - [Custom Domains](https://jitsu.com/docs/features/custom-domains.md) - [Deduplication](https://jitsu.com/docs/features/deduplication.md) - [Event Backups & Data Retention](https://jitsu.com/docs/features/event-backups.md) - [Identity Stitching](https://jitsu.com/docs/features/identity-stitching.md) - [Live Events](https://jitsu.com/docs/features/live-events.md) - [Observability Exports](https://jitsu.com/docs/features/observability-exports.md) - [Profiles](https://jitsu.com/docs/features/profiles.md) - [Provisioned ClickHouse](https://jitsu.com/docs/features/provisioned-warehouse.md) - [Schema Management](https://jitsu.com/docs/features/schema.md) - [Sessions](https://jitsu.com/docs/features/sessions.md) ## Jitsu CLI - [Overview](https://jitsu.com/docs/jitsu-cli.md) - [Authentication](https://jitsu.com/docs/jitsu-cli/auth.md) - [Manage configuration](https://jitsu.com/docs/jitsu-cli/config.md) ## Self-hosting - [Overview](https://jitsu.com/docs/self-hosting.md) - [Quick Start](https://jitsu.com/docs/self-hosting/quick-start.md) - [Connector Syncs](https://jitsu.com/docs/self-hosting/quick-start/syncs.md) - [Production Deployment Guide](https://jitsu.com/docs/self-hosting/production-deployment.md) - [Configuration Reference](https://jitsu.com/docs/self-hosting/configuration.md) ## Jitsu Cloud - [IP addresses](https://jitsu.com/docs/cloud/ip-addresses.md) ## Jitsu Classic - [Overview](https://jitsu.com/docs/migration-from-classic.md) - [Migration guide](https://jitsu.com/docs/migration-from-classic/step-by-step.md) - [What has changed in Jitsu 2.0](https://jitsu.com/docs/migration-from-classic/what-changed.md)
Version History
Categories
Visit Website
Explore the original website and see their AI training policy in action.
Visit jitsu.comContent Types
Recent Access
No recent access
