{
 "categories": [
  "data-exchange",
  "marketing"
 ],
 "deployment": "hybrid",
 "evidence": [
  {
   "date": "2026-10-12",
   "fact": "homepage",
   "note": "The homepage og:title is Jitsu \u2014 Open-source data collection platform. The visible heading is Capture Event Data into Your Stack.",
   "source": "https://jitsu.com/",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "license",
   "note": "The pricing page says Open source, Free. Forever, MIT License, and lists cloud, private cloud, and on-prem. The free cloud plan includes 200k events per month.",
   "source": "https://jitsu.com/pricing",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "deployment",
   "note": "Pricing lists Jitsu Cloud, Jitsu Private Cloud, and On Prem.",
   "source": "https://jitsu.com/pricing",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.exists",
   "note": "Jitsu documents a management API that requires a personal API key.",
   "source": "https://jitsu.com/docs/api",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.kinds[0]",
   "note": "The management API is documented as HTTP requests with an Authorization header.",
   "source": "https://jitsu.com/docs/api",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.auth[0]",
   "note": "Management API calls send Authorization: Bearer and a personal API key. Keys have the form keyId:keySecret.",
   "source": "https://jitsu.com/docs/api",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.auth[1]",
   "note": "The ingestion HTTP API authenticates with the X-Write-Key header set to the site write key.",
   "source": "https://jitsu.com/docs/sending-data/http",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.coverage",
   "note": "Management and ingestion are separate APIs with different credentials. This pass did not open every management resource, so coverage stays partial.",
   "source": "https://jitsu.com/docs/sending-data/http",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.api.docs",
   "note": "Public management API documentation.",
   "source": "https://jitsu.com/docs/api",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.mcp.first_party",
   "note": "Jitsu documents its MCP server. The cloud endpoint is https://use.jitsu.com/mcp. A self-hosted console serves /mcp on that host.",
   "source": "https://jitsu.com/docs/mcp",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.mcp.verdict",
   "note": "The same vendor page says interactive clients use OAuth 2.1 and headless clients send a personal API key as Authorization: Bearer.",
   "source": "https://jitsu.com/docs/mcp",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.cli.exists",
   "note": "Jitsu documents jitsu-cli as the command-line interface that calls the management API.",
   "source": "https://jitsu.com/docs/jitsu-cli",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "modalities.agent_docs.llms_txt",
   "note": "https://jitsu.com/llms.txt opened as a Jitsu text index and describes Jitsu as open source and self-hostable.",
   "source": "https://jitsu.com/llms.txt",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "freshness.watch[0].url",
   "note": "Opened the Jitsu MCP document on 2026-10-12.",
   "source": "https://jitsu.com/docs/mcp",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "freshness.watch[1].url",
   "note": "Opened the Jitsu management API document on 2026-10-12.",
   "source": "https://jitsu.com/docs/api",
   "tier": "declared"
  },
  {
   "date": "2026-10-12",
   "fact": "freshness.watch[2].url",
   "note": "Opened Jitsu pricing on 2026-10-12.",
   "source": "https://jitsu.com/pricing",
   "tier": "declared"
  }
 ],
 "freshness": {
  "last_verified": "2026-10-12",
  "volatility": "medium",
  "watch": [
   {
    "type": "docs",
    "url": "https://jitsu.com/docs/mcp"
   },
   {
    "type": "docs",
    "url": "https://jitsu.com/docs/api"
   },
   {
    "type": "docs",
    "url": "https://jitsu.com/pricing"
   }
  ]
 },
 "homepage": "https://jitsu.com/",
 "id": "jitsu",
 "license": "open-source",
 "modalities": {
  "agent_docs": {
   "llms_txt": true
  },
  "api": {
   "auth": [
    "bearer",
    "write-key"
   ],
   "coverage": "partial",
   "docs": "https://jitsu.com/docs/api",
   "exists": true,
   "kinds": [
    "rest"
   ]
  },
  "cli": {
   "exists": true
  },
  "computer_use": {
   "issues": [],
   "viability": "unknown"
  },
  "data_access": {
   "export": [],
   "import": []
  },
  "extensibility": {
   "scripting": [],
   "webhooks": "unknown"
  },
  "integrations": {
   "make": "unknown",
   "n8n": "unknown",
   "power_automate": "unknown",
   "zapier": "unknown"
  },
  "mcp": {
   "first_party": true,
   "third_party": [],
   "verdict": "official"
  },
  "rpa": {
   "drivability": "unknown",
   "notes": "No repeatable UI probe was run. Pipeline changes are documented as the management API, the CLI, and the MCP server, and computer-use viability was not measured.\n",
   "ui_stack": [],
   "vendor_support": []
  },
  "sdk": {
   "exists": "unknown",
   "languages": [],
   "official": "unknown"
  }
 },
 "name": "Jitsu",
 "platforms": [
  "web",
  "linux"
 ],
 "related": {
  "alternatives": [
   "rudderstack",
   "hightouch"
  ],
  "our_products": []
 },
 "schema_version": 1,
 "score_version": 1,
 "status": "active",
 "vendor": "Jitsu",
 "verdict": {
  "best_path": "mcp",
  "scores": {
   "api": 7,
   "cli": 6,
   "computer_use": null,
   "integrations": null,
   "mcp": 8,
   "overall": 8,
   "rpa": null
  },
  "summary": "Jitsu is automatable today through its official MCP server. This record is the Jitsu customer data platform, cloud and self-hosted. RudderStack and Hightouch are separate products. The pricing page says the open-source edition is MIT and free to self-host, and it lists Jitsu Cloud, Jitsu Private Cloud, and on-prem. The free cloud plan on that page includes 200k events per month. The management API requires Authorization: Bearer and a personal API key in the form keyId:keySecret. The ingestion HTTP API authenticates with an X-Write-Key header. The MCP document says there is a single cloud endpoint, https://use.jitsu.com/mcp, and that a self-hosted console serves /mcp on its own host. Interactive auth is OAuth 2.1. Headless clients send the same personal API key as Bearer. jitsu-cli calls the management API. Client SDK manuals were not opened. Connector catalogs were not opened. https://jitsu.com/llms.txt describes Jitsu as an open-source, self-hostable data integration platform. Computer-use viability is unassessed. MCP scores 8 and is the best path because it is the documented agent interface for pipeline changes. The management and ingestion APIs score 7. The CLI scores 6.\n"
 }
}