Rank #1 of 5 in Customer Data Platforms
Showcase


Try itExperimental
See what an agent can do with Jitsu before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -si -X POST https://use.jitsu.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'recorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai cdp — stories about ai cdp in this arenaAi cdpevidence →
Stories about ai cdp in this arena
Audiences activation — stories about audiences activation in this arenaAudiences activationevidence →
Stories about audiences activation in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrationsevidence →
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collectionevidence →
Stories about event collection in this arena
Identity resolution — stories about identity resolution in this arenaIdentity resolutionevidence →
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Pipeline observability — stories about pipeline observability in this arenaPipeline observabilityevidence →
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consentevidence →
Stories about privacy consent in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portabilityevidence →
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations qualityevidence →
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse nativeevidence →
Stories about warehouse native in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 4 free · 0 paid · 0 enterprise · 31 not stated in evidence
Follow the green: where the map greys out is where Jitsu stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Webhooks · Machine-readable spec · Versioning policy
Subscribe to events via webhooks
—0/10
Build against official SDKs
~6/10
Issue scoped/least-privilege API credentials for an agent
~4/10
Connect an agent via an official MCP server
✓9/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
~5/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓8/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—0/10
Operate the product with natural-language commands
✓8/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
~6/10
Ai cdp — stories about ai cdp in this arenaAi cdp
Stories about ai cdp in this arena
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
~4/10
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
✓8/10
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema
n/an/a
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift
n/an/a
Audiences activation — stories about audiences activation in this arenaAudiences activation
Stories about audiences activation in this arena
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time
—0/10
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
—0/10
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
~3/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Destinations integrations — stories about destinations integrations in this arenaDestinations integrations
Stories about destinations integrations in this arena
Event collection — stories about event collection in this arenaEvent collection
Stories about event collection in this arena
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
✓8/10
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
~6/10
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
~5/10
Identity resolution — stories about identity resolution in this arenaIdentity resolution
Stories about identity resolution in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Pipeline observability — stories about pipeline observability in this arenaPipeline observability
Stories about pipeline observability in this arena
Privacy consent — stories about privacy consent in this arenaPrivacy consent
Stories about privacy consent in this arena
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
—–
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations
—0/10
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
~4/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Replay portability — stories about replay portability in this arenaReplay portability
Stories about replay portability in this arena
Transformations quality — stories about transformations quality in this arenaTransformations quality
Stories about transformations quality in this arena
Warehouse native — stories about warehouse native in this arenaWarehouse native
Stories about warehouse native in this arena
Sorted by importance (agentic first) (high → low) · 51/51 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 9/10 | Tprobed⚿ | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Tprobed⚿ | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ⚿ | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ⚿ | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed⚿ | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed⚿ | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed⚿ | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed⚿ | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ⚿ | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 5/10 | Cclaimed | |
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control C Warehouse sync | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 3 | full | 9/10 | Cclaimed | |
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server C Agent pipeline | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | full | 8/10 | Tprobed⚿ | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Tprobed | |
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page) C Sdks | data engineer | Event collection — stories about event collection in this arenaEvent collection | 3 | partial | 6/10 | Cclaimed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 6/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialfree | 6/10 | Tprobed | |
Route events to a large catalog of documented destination integrations with per-destination mapping and filtering C Destinations | data engineer | Destinations integrations — stories about destinations integrations in this arenaDestinations integrations | 3 | partial | 6/10 | Xcommunity | |
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules C Stitching | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 3 | partial | 5/10 | Cclaimed | |
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop C Agent audiences | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 3 | partial | 4/10 | Tprobed⚿ | |
Build audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating C Audiences | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | 0/10 | ||
User consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically C Consent | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 3 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | fullfree | 8/10 | Tprobed | |
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees C Ingest | data engineer | Event collection — stories about event collection in this arenaEvent collection | 2 | full | 8/10 | Tprobed | |
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations C Transformations | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | full | 8/10 | Cclaimed | |
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting C Observability | data engineer | Pipeline observability — stories about pipeline observability in this arenaPipeline observability | 2 | partial | 7/10 | Cclaimed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed⚿ | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 5/10 | Tprobed | |
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store C Profiles | data engineer | Identity resolution — stories about identity resolution in this arenaIdentity resolution | 2 | partial | 5/10 | Tprobed | |
A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data C Data quality | data engineer | Transformations quality — stories about transformations quality in this arenaTransformations quality | 2 | partial | 4/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Cclaimed | |
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes C Pii controls | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | partial | 4/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Cclaimed | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 4/10 | Cclaimed | |
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting C Traits | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | partial | 3/10 | Cclaimed | |
Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks C Replay | data engineer | Replay portability — stories about replay portability in this arenaReplay portability | 2 | partial | 3/10 | Cclaimed | |
Audiences sync to ad platforms and engagement tools continuously, with membership entering and exiting in near-real-time C Activation | marketer | Audiences activation — stories about audiences activation in this arenaAudiences activation | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Process user deletion and suppression requests (GDPR/CCPA) and have them forwarded to connected destinations C Deletion | privacy lead | Privacy consent — stories about privacy consent in this arenaPrivacy consent | 2 | none | 0/10 | ||
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL) C Composable | data engineer | Warehouse native — stories about warehouse native in this arenaWarehouse native | 2 | none | 0/10 | ||
AI decisioning agents pick messages, timing, and channels per customer autonomously within guardrails I set, with measurable lift C Ai decisioning | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | n/a | untested | none yet | |
Describe an audience in natural language and AI builds the segment definition for review, grounded in my actual schema C Ai assist | ai-native user | Ai cdp — stories about ai cdp in this arenaAi cdp | 2 | n/a | untested | none yet | |
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps C Sources | data engineer | Event collection — stories about event collection in this arenaEvent collection | 1 | partial | 5/10 | Xcommunity | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | partial | 4/10 | Cclaimed |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 38 stories with headroom
What would move Jitsu’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
Jitsu documents an MCP server that lets external AI agents control the pipeline (create destinations, edit functions, etc.), but this is the reverse of the story — it makes Jitsu controllable BY agents, not a built-in assistant users delegate tasks to within Jitsu's own UI.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Evidence shows Jitsu operates as an MCP *server* — 'Jitsu runs an MCP server, so AI agents can manage your pipeline directly' (jitsu-docs-19, jitsu-probe-rt-1) — which is the opposite role from what this story asks (Jitsu acting as an MCP *client* that plugs in and uses external MCP servers' tools).
Privacy consent — stories about privacy consent in this arenaUser consent is captured and enforced across destinations — opt-outs and consent categories are honored downstream automatically
nonemoves PA Scoreimpact 30
No evidence anywhere in the pack describes consent capture, consent-category mapping, opt-out enforcement, or CMP/consent-signal propagation to destinations.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Jitsu's security page covers encryption, SOC2 compliance, and DPA/SCC agreements, but nothing in the evidence pack addresses whether customer event data is used to train AI models or how a user could opt out of such use.
Audiences activation — stories about audiences activation in this arenaBuild audiences from traits and behavior in a visual builder — no SQL required — and see estimated size before activating
nonemoves PA Scoreimpact 30
Jitsu's evidence shows a 'Profile Builder' that generates customer profiles from traits/events, but this is developer-driven (JS functions) and warehouse/SQL-oriented, not a marketer-facing visual audience builder with no-SQL segment creation or size-before-activation preview.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
Jitsu's AI-related evidence is limited to an MCP server that lets external AI agents configure the pipeline (create destinations, streams, edit functions) — this is agentic control of infrastructure, not the product generating insights or suggestions from the data itself.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Evidence shows Jitsu can *receive* data via webhook (e.g., a Segment webhook destination sending data into Jitsu) and can deliver events to various destinations, but there is no evidence of an outbound webhook subscription mechanism that lets an AI-native consumer subscribe to Jitsu's own event stream.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
No evidence of an interactive API reference with runnable examples; only static HTTP API docs mentioning sending data via HTTP, and probes for OpenAPI/Swagger specs at Jitsu's docs domain all returned 404s.
Showing the top 8 of 38 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map12 surfaces · 35 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs32 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Set up automations that run autonomously in the background
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the loop
- An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP server
- Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targeting
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Self-host the core product
- Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- Choose where my data is stored (region/residency)
- Control data retention and deletion
- A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
GitHub README17 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Build against official SDKs
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Schedule recurring jobs or workflows
- Version, review, and roll back my automations
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
Changelog docs9 stories
- Issue scoped/least-privilege API credentials for an agent
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Version, review, and roll back my automations
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Self-host the core product
- Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alerting
- Replay archived events into a new destination or backfill history when a tool is added or a pipeline breaks
- A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
docs.jitsu.com9 stories
- Set up automations that run autonomously in the background
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Export all of my data in open formats and leave
- Self-host the core product
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- Choose where my data is stored (region/residency)
- Control data retention and deletion
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
jitsu.com9 stories
- Set up automations that run autonomously in the background
- Define rules that trigger actions automatically on events
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Export all of my data in open formats and leave
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
Hacker News6 stories
- Build against official SDKs
- Define rules that trigger actions automatically on events
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Pull customer data in from third-party cloud apps and feeds — not just my own instrumented apps
- Read the product's source under an open license
- Self-host the core product
Features docs6 stories
- Build against official SDKs
- Perform bulk operations across many items at once
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)
- Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rules
- Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I control
OpenAPI spec5 stories
- Drive the product through a documented public API
- Build against official SDKs
- Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guarantees
- Query unified customer profiles — traits, identifiers, event history — through a documented profile API or store
- Do everything through the API that I can do in the UI
Pricing docs4 stories
- Route events to a large catalog of documented destination integrations with per-destination mapping and filtering
- Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributes
- A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream data
- Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinations
llms.txt3 stories
Security docs3 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -si -X POST https://use.jitsu.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'reproduced$ curl -si -X POST https://use.jitsu.com/mcp -H 'Content-Type: application/json' -d '<jsonrpc initialize>'
HTTP/2 401
date: Tue, 08 Sep 2026 22:00:14 GMT
content-type: application/json; charset=utf-8
content-length: 96
x-frame-options: DENY
x-content-type-options: nosniff
referrer-policy: strict-origin-when-cross-origin
permissions-policy: camera=(), microphone=(), geolocation=(), browsing-topics=()
www-authenticate: Bearer realm="jitsu-mcp", error="missing_[redacted]", error_description="Authorization header either missing or malformed", resource_metadata="https://use.jitsu.com/.well-known/oauth-protected-resource"
etag: "va5atzba9y2o"
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
{"error":"missing_[redacted]","error_description":"Authorization header either missing or malformed"}
$mktemp -d && npm install @jitsu/js && node -e "import('@jitsu/js').then(m=>console.log('PA_PROBE_OK jitsu jitsuAnalytics:', typeof m.jitsuAnalytics))"reproduced$ mktemp -d && npm install @jitsu/js && node -e "import('@jitsu/js').then(m=>console.log('PA_PROBE_OK jitsu jitsuAnalytics:', typeof m.jitsuAnalytics))"
added 13 packages in 157ms
PA_PROBE_OK jitsu jitsuAnalytics: function
$git clone --depth 1 https://github.com/jitsucom/jitsu.git # then list root files, LICENSE head, docker-compose.ymlreproduced$ git clone --depth 1 https://github.com/jitsucom/jitsu.git # then list root files, LICENSE head, docker-compose.yml Cloning into '/tmp/pa-jitsu'... --- root files --- AGENTS.md CHANGES.md CLAUDE.md CONTRIBUTING.md JITSU_FUNCTIONS_DEPLOYMENT.md JITSU_FUNCTIONS_PIPELINE.md LICENSE README.md THIRD-PARTY-LICENSES.md all.Dockerfile build-fs.sh build-rotor.sh builder.Dockerfile bulker --- license --- MIT License Copyright (c) 2021 Jitsu Labs, Inc --- compose --- ls: /tmp/pa-jitsu/docker-compose.yml: No such file or directory
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
10 of 19 testable claims verified · 1 contradicted → integrity 42/100
34 distinct capability claims found in Jitsu’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
10
Verified
8
Unverified
1
Contradicted
17
Undersold
Verified (13)
“Server-to-server event ingestion via a documented HTTP API”
Send events server-to-server through a documented HTTP ingestion API with authentication and delivery guaranteesfullproof ↗
“Profile Builder generates customer profiles from identify-event traits”
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or storepartialproof ↗
“jitsu-cli manages workspace config (destinations, streams, connections) and the Functions dev workflow”
“CLI can scaffold a TypeScript function project and deploy it to the workspace”
“Can be self-hosted on Kubernetes via an official Helm chart”
“A zero-config development Helm chart deploys the full architecture to Minikube”
“SOC2-oriented audit log with activity alerts, plus named API tokens that support expiration”
Issue scoped/least-privilege API credentials for an agentpartialproof ↗
“Runs an MCP server so AI agents can create destinations, wire streams, inspect Live Events, and edit Functions directly”
“Runs an MCP server so AI agents can create destinations, wire streams, inspect Live Events, and edit Functions directly”
An agent can manage the pipeline itself — create sources and destinations, wire streams, inspect deliveries — through a documented API or MCP serverfullproof ↗
“Supports personal API key auth for headless/CI environments where browser login isn't possible”
Run the product headlessly / in CI for automationfullproof ↗
“Ships dozens of documented destination integrations with streamed or micro-batched delivery per destination”
Route events to a large catalog of documented destination integrations with per-destination mapping and filteringpartialproof ↗
“Connector syncs pull data from third-party sources into the warehouse via Airbyte-compatible connectors”
Pull customer data in from third-party cloud apps and feeds — not just my own instrumented appspartialproof ↗
“Stored event data can be queried directly with SQL for analysis”
Query unified customer profiles — traits, identifiers, event history — through a documented profile API or storepartialproof ↗
Unverified (12)
“Functions let you filter, transform, and enrich events before they reach the destination”
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinationsfullproof ↗
“Anonymous and identified user activity is automatically merged into one profile once identity is known”
Anonymous and known activity stitches into one customer profile across devices, with documented and configurable identity-resolution rulespartialproof ↗
“JavaScript/React SDK is Segment-API compatible for web event collection”
Collect events from web, mobile, and server apps through official SDKs that implement a documented tracking spec (track, identify, page)partialproof ↗
“Delivers data to the warehouse in sub-second time, with optional batching”
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I controlfullproof ↗
“Automatically creates tables and columns in the warehouse based on incoming data”
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I controlfullproof ↗
“Custom JavaScript logic can generate profiles using up to a year of historical event data”
Computed traits and predictive scores (LTV, churn or purchase propensity) are calculated on profiles and usable in targetingpartialproof ↗
“Failed events go to a dead-letter queue and can be replayed via a reprocessing worker”
Replay archived events into a new destination or backfill history when a tool is added or a pipeline breakspartialproof ↗
“Delivery logs/records are emitted as OpenTelemetry OTLP so they can feed Datadog, Grafana, New Relic, Elastic, etc.”
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alertingpartialproof ↗
“Positions the data warehouse as the single source of truth, optimized for fast delivery into it”
Raw events and profiles land in my own warehouse or lake (Snowflake, BigQuery, ClickHouse, S3) on a schedule I controlfullproof ↗
“Live Events data can be exported near real-time to your own monitoring stack”
Watch events flow live and diagnose delivery failures per destination — debugger views, delivery metrics, and alertingpartialproof ↗
“Full-featured deployment runs functions/profile builders as dedicated servers and connector syncs as Kubernetes CronJobs”
“Event routing can be controlled by not connecting a source to a destination or by using a Function to filter events”
Transform, filter, and enrich events in-pipeline with custom code or functions before they reach destinationsfullproof ↗
Contradicted (1)
“Functions can expose a warehouse API (ctx.getWarehouse) to query your data warehouse directly from function code”
Run warehouse-native: define models and audiences on tables already in my warehouse and activate them without re-collecting the data (reverse ETL)noneproof ↗
Undersold (17)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Drive the product through a documented public APIpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Operate the product with natural-language commandsfullproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
An agent can query customer data and create or activate audiences end to end through documented APIs or MCP — no dashboard in the looppartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Control PII flow per destination — hashing, masking, and field-level filtering of sensitive attributespartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
A tracking plan or schema is enforced — violating events get flagged, blocked, or quarantined instead of silently corrupting downstream datapartialproof ↗
Claims outside our story set (9)
Real capability claims found in Jitsu’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Setup requires only adding a single tracking tag/snippet”
source ↗“Can receive a webhook feed from Segment and deliver it to your DB in real time”
source ↗“Buffers events in Kafka during warehouse downtime and delivers once it's back”
source ↗“Automatically deduplicates repeated event sends”
source ↗“Customer data is encrypted at rest (AES-256) and in transit (TLS)”
source ↗“Jitsu is SOC 2 compliant”
source ↗“Can add a plugin to send a copy of existing tracked data to Jitsu without changing frontend code, for gradual migration”
source ↗“Includes a built-in functions debugger/editor to test functions against sample data”
source ↗“DPA and SCC documents are available for data-processing/compliance needs”
source ↗
Business model
MIT-licensed and self-hostable; Jitsu Cloud is free up to 200K active events/month, Business is $99/month for 2M events then $40 per additional 1M, and Enterprise (private cloud/on-prem) is custom.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime MCP up · llms.txt up (tracking since Sep 10 '26)
