{ "data": { "a": { "slug": "gauge-cli", "name": "Gauge CLI", "vendor": "Gauge", "vendorUrl": "https://www.withgauge.com/agents/", "kind": "cli", "category": "agent-observability", "summary": "Gauge CLI runs real coding agents (Claude Code, Codex, Pi, OpenCode) against your skills, CLIs, SDKs, MCP servers and docs in Docker, records where they get stuck, and lets your agent test fixes before release.", "url": "https://www.anchorterminal.com/tools/gauge-cli", "markdownUrl": "https://www.anchorterminal.com/tools/gauge-cli.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/gauge-cli.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/gauge-cli.json", "dns": "gauge-cli.grade.anchorterminal.com", "repo": "https://github.com/gauge-sh/gauge-cli", "license": "MIT", "transports": [], "packages": [ { "registry": "npm", "name": "@withgauge/cli" } ], "auth": "none", "authNotes": "Local mode needs no Gauge account, only credentials for the agent under test (native Claude or Codex logins, or API keys). Hosted Gauge uses `gauge auth login`, with a device flow for remote terminals.", "pricing": "freemium", "pricingNotes": "The CLI and local mode are free and MIT-licensed; agent usage is billed by your provider or subscription. Hosted Gauge runs on workspace credits, whose prices weren't read (checked 2026-11-06).", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No payment protocol in the CLI or its README; hosted runs use workspace credits (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.withgauge.com/agents", "capabilities": [ "obs.evals" ], "tags": [ "open-source", "mit", "cli", "node", "docker", "telemetry", "new" ], "lastRelease": "2026-11-04", "graded": true, "anchor": { "graded": true, "score": 60.4, "grade": "C", "agentReady": false, "rank": 590, "ranked": true, "rankOf": 1354, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 82, "payments": 40, "reliability": 60, "schema": 60, "security": 55, "transparency": 53 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "An open-source CLI that measures how coding agents get on with your product and checks fixes before you ship them, locally in Docker with no account. It's young and pre-1.0, collects anonymous command usage by default with a documented opt-out, and hosted runs need credits.", "bestFor": "Teams that build skills, CLIs, SDKs or MCP servers and want to see where coding agents get stuck with them, and to test fixes before release.", "strengths": [ "Runs Claude Code, Codex, Pi and OpenCode in fresh Docker sessions against working-tree or pre-release versions", "Local mode needs no Gauge account, only your existing agent credentials", "Dated changelog with six releases in about two weeks", "Instructions bundled in the CLI for coding agents, and -o json on read commands", "CI runs checks on every push and pull request" ], "weaknesses": [ "Collects anonymous command usage by default, with an opt-out", "Pre-1.0 and about two weeks old in this repository", "Docs, authenticated MCP servers and authenticated APIs need hosted Gauge and credits", "Hosted credit prices weren't found on the pages read" ], "agentNotes": [ "npm install -g @withgauge/cli, then gauge local runtime pull and gauge init --local in the project", "Run gauge install-skill so your coding agent finds the CLI's own instructions", "Set GAUGE_TELEMETRY_DISABLED=1 in CI if you don't want command usage collected", "Rebuild and pack an npm CLI or SDK before rerunning, so test sessions get the new tarball", "Keep .gauge/ private; it holds measurements and analyses" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60.4 } ], "editorialScores": { "ergonomics": 75, "maintenance": 82, "payments": 40, "reliability": 60, "schema": 60, "security": 55, "transparency": 78 }, "provenanceScore": 27, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @withgauge/cli\ngauge local runtime pull\ngauge init --local\ngauge install-skill" }, "letme": { "capability": "https://letme.dev/obs.evals", "tool": "https://letme.dev/gauge-cli" }, "area": "developer", "provenance": { "legalEntity": "", "domain": "withgauge.com", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/gauge-sh/gauge-cli/blob/main/cli/CHANGELOG.md", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The npm package's author is Gauge \u003csupport@withgauge.com\u003e, its homepage agents.withgauge.com, and its repository field points at gauge-sh/gauge-cli. The licence names Gauge.", "Hosted Gauge's terms and privacy weren't read, and security.txt wasn't checked." ], "score": 27 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/gauge-cli.json" }, "answer": "Langfuse API + MCP scores 71.8 (BB) on agent readiness against Gauge CLI's 60.4 (C), and leads in 5 of 7 scored categories.", "b": { "slug": "langfuse", "name": "Langfuse API + MCP", "vendor": "Langfuse (ClickHouse)", "vendorUrl": "https://langfuse.com", "kind": "http-api", "category": "agent-observability", "summary": "Open-source tracing, evaluation, prompt management and datasets for LLM apps and agents, built on OpenTelemetry.", "url": "https://www.anchorterminal.com/tools/langfuse", "markdownUrl": "https://www.anchorterminal.com/tools/langfuse.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/langfuse.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/langfuse.json", "dns": "langfuse.grade.anchorterminal.com", "repo": "https://github.com/langfuse/langfuse", "license": "MIT (core), commercial licence for the ee directories", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://cloud.langfuse.com/api/public", "packages": [ { "registry": "pypi", "name": "langfuse" }, { "registry": "npm", "name": "@langfuse/tracing" }, { "registry": "npm", "name": "@langfuse/client" } ], "auth": "api-key", "authNotes": "Project-scoped key pair (public `pk-lf-...`, secret `sk-lf-...`) sent as HTTP Basic auth, for both the REST API and the MCP server at `/api/public/mcp`. Since 16 October 2026 a new key takes one permission set, Full access, Viewer (read-only), Ingestion or Scores ingestion, which can't be changed later. Organisation-level keys exist for SCIM and admin APIs on Enterprise.", "pricing": "freemium", "pricingNotes": "Cloud Hobby is free with 50,000 units a month, 30 days of data and 2 users, no card. Core $29 a month with 100,000 units and 90 days, Pro $199 a month with 3 years of data, Enterprise $2,499 a month. Extra units cost $8 per 100,000 on paid plans, lower with volume. A unit is one trace, observation or score. Teams add-on $300 a month for SSO and fine-grained RBAC. Self-hosted open source is free with unlimited usage, you pay for your own Postgres, ClickHouse, Redis and blob storage. Self-hosted Enterprise is custom and sold on top of a ClickHouse plan (https://langfuse.com/pricing).", "priceSummary": "$29 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402 support in docs or pricing (checked 2026-09-30).", "endpoints": [] }, "toolCount": 98, "popularity": { "githubStars": 35235, "npmWeekly": 3039593, "pypiWeekly": 5865664, "asOf": "2026-09-30" }, "docsUrl": "https://langfuse.com/docs", "llmsTxt": "https://langfuse.com/llms.txt", "openapi": "https://cloud.langfuse.com/generated/api/openapi.yml", "capabilities": [ "obs.traces", "obs.evals", "obs.prompts", "obs.datasets" ], "tags": [ "hosted", "freemium", "no-card", "open-source", "self-hosted", "mcp", "llms-txt", "openapi", "python", "typescript", "webhooks" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 71.8, "grade": "BB", "agentReady": true, "rank": 132, "ranked": true, "rankOf": 1354, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 88, "payments": 40, "reliability": 80, "schema": 93, "security": 77, "transparency": 86 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -5, "negativeNotes": [ "2025-11-09 to 2026-01-21. Three moderate advisories, cross-organisation enumeration of member and invitation lists (GHSA-94hf-6gqq-pj69), SSO account takeover through CSRF or phishing (GHSA-w9pw-c549-5m6w) and an unauthenticated Slack OAuth install that could link Slack to any project (GHSA-pvq7-vvfj-p98x). All fixed and published, eight to eleven months old, so -2 (https://github.com/langfuse/langfuse/security/advisories)", "2026-10-27, -3. v4.71.0, a minor release, stops self-hosted deployments with an Enterprise licence key and `LANGFUSE_REQUIRE_FIPS=true` from starting, and FIPS mode now needs a Government licence key (`lf_gov_`). The commit marks it BREAKING CHANGE. The 23 October changelog entry first said FIPS mode needed an Enterprise licence and was available from v4.57.0. It was changed to name the Government licence and v4.71.0 on 28 October, the day after the release, so no notice was given beforehand (https://github.com/langfuse/langfuse/commit/165b621fdf8fc7d34232df8d5a74a5ab36d3fc83, https://github.com/langfuse/langfuse-docs/commit/0e087c325947b3fded371150fc374b492cb7be93)" ], "verdict": "MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets.", "bestFor": "Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.", "strengths": [ "MIT core with no usage limits when self-hosted, and self-hosted telemetry documented with an off switch", "Project API keys can be created read-only (Viewer), ingestion-only or scores-only on every plan, since 16 October 2026", "Per-unit cloud pricing at $8 per 100,000 units, and a free Hobby plan with 50,000 units and no card", "Bug bounty, SOC 2 Type II, ISO 27001 and GitHub advisories handled in public", "Deprecated v1 read APIs have a dated sunset of 16 November 2026 and a migration guide" ], "weaknesses": [ "98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist", "17 incidents on the status history in the 90 days to 1 November, mostly ingestion delays, one of them over six hours", "Python SDK v5 and JS/TS SDK v6 drop `api.scores_v3`, `api.legacy.*` and `api.ingestion`, and need Langfuse v4.59.0 or later", "No uptime SLA found, only support response targets", "Self-hosting means running ClickHouse, Postgres, Redis and S3-compatible storage" ], "agentNotes": [ "Use a Viewer key for an agent that only reads traces. Keys created before 16 October keep full access and can't be narrowed", "Allowlist only the MCP tools the agent needs. All 98 load by default, writes included, and they share the General API bucket, so wait for `Retry-After` on 429", "Ask `listObservations` for specific `fields`. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days", "Move off `GET /api/public/traces`, `/observations`, `/sessions` and the other v1 reads before 16 November 2026, and replace `api.scores_v3` when moving to Python SDK v5 or JS/TS SDK v6", "Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 4, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.8 } ], "editorialScores": { "ergonomics": 74, "maintenance": 88, "payments": 40, "reliability": 80, "schema": 93, "security": 77, "transparency": 91 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -u \"$LANGFUSE_PUBLIC_KEY:$LANGFUSE_SECRET_KEY\" https://cloud.langfuse.com/api/public/projects", "claudeCode": "claude mcp add --transport http langfuse https://cloud.langfuse.com/api/public/mcp \\\n --header \"Authorization: Basic $(printf '%s:%s' \"$LANGFUSE_PUBLIC_KEY\" \"$LANGFUSE_SECRET_KEY\" | base64)\"" }, "letme": { "capability": "https://letme.dev/obs.traces", "tool": "https://letme.dev/langfuse" }, "area": "developer", "unitPrices": [ { "item": "Core plan", "unit": "month", "usd": 29, "note": "100,000 units included, 90 days of data" }, { "item": "Pro plan", "unit": "month", "usd": 199, "note": "100,000 units included, 3 years of data" }, { "item": "Enterprise plan", "unit": "month", "usd": 2499, "note": "100,000 units included, audit logs, SCIM, SLAs" }, { "item": "Teams add-on", "unit": "month", "usd": 300, "note": "SSO, SSO enforcement and fine-grained RBAC on Pro" } ], "provenance": { "legalEntity": "Langfuse GmbH (a ClickHouse, Inc. company)", "domain": "langfuse.com", "domainRegistered": "2023-04-20", "endpointOnVendorDomain": true, "terms": "https://clickhouse.com/legal/clickhouse-general-terms-and-conditions", "privacy": "https://langfuse.com/privacy", "statusPage": "https://status.langfuse.com", "changelog": "https://langfuse.com/changelog", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The imprint names Langfuse GmbH in Berlin. The privacy notice is issued by ClickHouse, Inc. and langfuse.com/terms redirects to the ClickHouse general terms" ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/langfuse.json", "live": { "slug": "langfuse", "probe": { "target": "https://cloud.langfuse.com/api/public", "method": "get", "lastAt": "2026-11-06T09:47:35.08402759Z", "lastOk": true, "lastStatus": 404, "lastMs": 59, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 53, "p95ms24h": 125, "samples24h": 221, "samples30d": 7856, "days": [ { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 102, "ok": 102 } ] }, "vendorStatus": { "page": "https://status.langfuse.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-06T09:43:14.239720131Z" }, "versions": [ { "registry": "github", "name": "langfuse/langfuse", "version": "v4.76.0", "released": "2026-11-05", "seenAt": "2026-11-05T21:41:58.581444925Z" }, { "registry": "npm", "name": "@langfuse/client", "version": "6.1.1", "seenAt": "2026-11-05T21:41:57.338486231Z" }, { "registry": "npm", "name": "@langfuse/tracing", "version": "6.1.1", "seenAt": "2026-11-05T21:41:56.31612923Z" }, { "registry": "pypi", "name": "langfuse", "version": "5.2.0", "released": "2026-11-05", "seenAt": "2026-11-05T21:41:56.156109407Z" } ], "githubStars": 37064, "npmWeekly": 4407650, "pypiWeekly": 7163057, "securityTxt": { "url": "https://langfuse.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-05T15:55:39.071190751Z" }, "llmsTxt": { "url": "https://langfuse.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-05T15:26:21.552730566Z" }, "domain": { "domain": "langfuse.com", "registered": "2023-04-20", "source": "https://rdap.verisign.com/com/v1/domain/langfuse.com", "checkedAt": "2026-11-01T14:25:22.869729216Z" }, "pages": [ { "url": "https://langfuse.com/changelog", "kind": "changelog", "status": 404, "checkedAt": "2026-11-05T12:57:46.370695567Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://langfuse.com/blog/joining-clickhouse", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:44.307441866Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "4e8ff98bb557" }, { "url": "https://langfuse.com/changelog/2026-10-14-python-sdk-v5-js-sdk-v6", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:48.563559758Z", "changedAt": "2026-10-21T00:29:03.204686539Z", "fingerprint": "51a1acd1fb4a" }, { "url": "https://langfuse.com/changelog/2026-10-23-fips-mode", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:50.340427497Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "67f89859d5fe" }, { "url": "https://langfuse.com/faq/all/deprecated-api-migration.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-05T12:57:52.333063262Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "013bcf676730" }, { "url": "https://langfuse.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-05T12:57:54.354343204Z", "changedAt": "2026-10-28T04:20:13.125779765Z", "fingerprint": "042a9cd0ddce" }, { "url": "https://langfuse.com/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-05T12:57:56.366082534Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9e1e582ef9a9" }, { "url": "https://clickhouse.com/legal/clickhouse-general-terms-and-conditions", "kind": "terms", "status": 304, "checkedAt": "2026-11-05T12:47:57.522270201Z", "changedAt": "2026-11-04T08:16:30.483741466Z", "fingerprint": "c9b7d6ee115c" } ], "github": { "repo": "langfuse/langfuse", "checkedAt": "2026-11-02T08:59:50.921543651Z", "stars": 36867, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T08:58:34Z", "openIssues": 329, "openPRs": 771, "issuesOpened90d": 424, "issuesClosed90d": 386, "prsMerged90d": 2249, "ci": { "branch": "main", "runs": 50, "success": 44, "failure": 0, "other": 6, "latest": "success", "latestAt": "2026-11-02T08:53:09Z" }, "advisories": [ { "ghsa": "GHSA-2524-j966-gfgh", "cve": "CVE-2026-41487", "severity": "low", "published": "2026-04-17T07:23:10Z" }, { "ghsa": "GHSA-pvq7-vvfj-p98x", "cve": "CVE-2026-24055", "severity": "medium", "published": "2026-01-21T20:54:58Z" }, { "ghsa": "GHSA-w9pw-c549-5m6w", "cve": "CVE-2025-65107", "severity": "medium", "published": "2025-11-19T23:28:36Z" }, { "ghsa": "GHSA-94hf-6gqq-pj69", "cve": "CVE-2025-64504", "severity": "medium", "published": "2025-11-09T18:26:33Z" } ], "replies": { "sampled": 25, "unanswered": 22, "medianDays": 0.1 } }, "updatedAt": "2026-11-06T09:47:35.08402759Z" } }, "edges": [ { "by": 33, "category": "schema", "leads": "langfuse", "name": "Schema \u0026 documentation", "reasons": { "a": "CLI reading. No machine-readable contract, -o json on read commands (10 of 25). No llms.txt; instructions bundled in the CLI for agents (5). The README says what it finds and when local or hosted fits (16 of 20). Commands with help text; typed flags (9 of 15). Worked examples, no error reference (8 of 15). Dated changelog and semver tags (12 of 15). 10 + 5 + 16 + 9 + 8 + 12 = 60.", "b": "Public OpenAPI at cloud.langfuse.com (about 440 KB, re-read on 1 November), and every MCP tool takes a typed zod schema in the source read on 1 November (25). llms.txt and Markdown docs, with every page available as Markdown at `.md` (10). Tool descriptions say what to use each one for and how to size the result. `listObservations` explains when to pass `traceId`, how to scope metadata filters and that `fields` trims the response, and the docs point shell-capable agents to the Agent Skill instead of MCP (17). Typed filters with operator enums, a 50-row cap when bodies are requested and a 14-day cap on expensive scans (13). Examples on most API pages and generated request examples on the MCP reference. Error bodies are less fully documented (13). Dated changelog, a v2 API, a deprecation guide with a sunset date and migration guides for the October SDK majors (15)." }, "scores": { "a": 60, "b": 93 } }, { "by": 33, "category": "transparency", "leads": "langfuse", "name": "Transparency \u0026 trust", "reasons": { "a": "MIT (30). Local data stays in .gauge/ and telemetry fields are listed; hosted data handling wasn't read (18 of 30). Dated changelog, no deprecation policy (10 of 20). Telemetry on by default, disclosed with an opt-out (20). 30 + 18 + 10 + 20 = 78.", "b": "MIT core with the ee directories under a commercial licence (27). Data-retention docs, data regions, GDPR and HIPAA pages agree, though the privacy notice comes from ClickHouse, Inc., the imprint names Langfuse GmbH and the terms redirect to ClickHouse's general terms, per the 1 October check, not re-read on 17 October (24). Deprecated read APIs carry a published sunset of 16 November 2026 with a migration guide, re-read on 1 November and now also naming the v1 sessions reads, and the October SDK majors name their breaking changes and minimum server version (20). Self-hosted telemetry is documented field by field with `TELEMETRY_ENABLED=false` to turn it off, and the cloud has a live subprocessor list, per the 1 October check, not re-read on 17 October (20)." }, "scores": { "a": 53, "b": 86 } }, { "by": 22, "category": "security", "leads": "langfuse", "name": "Security \u0026 auth", "reasons": { "a": "Local tool. Agent credentials stay on your machine in local mode; hosted login with a device flow (20 of 30). Test agents run in fresh Docker sessions with injected inputs, and the gateway brokers credentials in hosted mode (12 of 20). Agents under test read your product's docs and outputs, with no prompt-injection guidance (5 of 15). Local transcripts and SQLite evidence per run (10 of 15). No security policy found (8 of 20). 20 + 12 + 5 + 10 + 8 = 55.", "b": "Project-scoped key pairs over Basic auth, revocable, with organisation keys kept to admin APIs. Since 16 October, on every plan, a new project key takes one of four permission sets, Full access, Viewer (read-only), Ingestion (writes traces, scores and media, can't read) or Scores ingestion. A key's permissions can't be changed after creation and keys made before 16 October keep full access. Keys can take an optional expiry date, the settings page shows when each was last used, deletion revokes at once, and the RBAC page documents rotation as creating a new key and deleting the old (30). A Viewer key is read-only on the public API. The MCP server's source, re-read at v4.72.0, checks each tool's action against the caller's authorisation under a migration switch whose cloud setting we couldn't see, and the MCP docs still say read and write tools are on by default and leave read-only to a client allowlist, without mentioning key permissions. Annotations mark reads and destructive tools (14). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them through MCP (3). Audit logs on Enterprise only (10). Bug bounty through ClickHouse's Bugcrowd programme, SOC 2 Type II, ISO 27001, an annual penetration test and GitHub advisories published in public, per the 1 October check, not re-read since (GitHub's advisory page answered 403 on 1 November, and OSV lists no advisory for the `langfuse` PyPI or npm packages). langfuse.com/.well-known/security.txt returned 404 on 1 November (20)." }, "scores": { "a": 55, "b": 77 } }, { "by": 20, "category": "reliability", "leads": "langfuse", "name": "Reliability", "reasons": { "a": "Local package. Installs from npm as @withgauge/cli with Node 22.13 or later and Docker stated (20). checks.yml runs npm run check on push and pull request across a matrix, and the repository has 76 test files; whether main passes wasn't read (20 of 25). Issues weren't read (5, unchecked). A dated changelog with Added sections per release (15). Version 0.28.0 (0). 20 + 20 + 5 + 15 + 0 = 60.", "b": "incident.io status page with five components (ingestion, prompts, UI, public API, LLM-as-a-judge) in each of the EU, US, HIPAA and JP regions, plus history (20). The history page, re-read on 1 November, dates each component's impact. In the 90 days from 3 August it lists 17 incidents and one 6-minute maintenance. 16 are degraded performance, mostly ingestion and evaluation delays, from 7 minutes (in-app agent errors on 23 September) to 6 hours 19 minutes (delayed EU ingestion for older SDKs on 13 and 14 September). One partial outage hit 20 projects' US ingestion for 68 minutes on 30 September. Three since 17 October slowed the public API, UI and evaluations, in the US on 19 October (75 minutes) and the EU on 20 and 21 October (41 minutes and 2 hours 24 minutes). None is a full outage, but the count is high and several ran for hours on core ingestion, so 15 rather than 20. Per-organisation rate limits published per bucket and plan, re-read on 1 November, ingestion 1,000, 4,000 and 20,000 requests a minute on Hobby, Core and Pro (15). 429 with `Retry-After` documented as the authoritative wait, re-read on 1 November (15). Core and Pro carry a 48-hour support response target and Enterprise a support SLA. We found no uptime SLA (5). API and MCP are GA (10)." }, "scores": { "a": 60, "b": 80 } }, { "by": 6, "category": "maintenance", "leads": "langfuse", "name": "Maintenance \u0026 community", "reasons": { "a": "CLI 0.28.0 on 4 November 2026 (30). Six releases in 90 days (20). Issues and pull requests weren't read; a support address and issue tracker are published (12 of 25). Current official package (15). CI on push and pull request (5 of 10, results not read). 30 + 20 + 12 + 15 + 5 = 82.", "b": "Server v4.72.0 tagged on 2026-10-29 (30). Nine v4 server tags from v4.64.0 on 19 October to v4.72.0 on 29 October, after 14 from 2 to 16 October, and v3.225.13 to v3.225.15 for the older line (20). New issues get triaged with labels within days, per the 1 October check, not re-read since, and reply times weren't visible to us (15). Python SDK v5.1.0 tagged on 2026-10-30 and JS SDK v6.1.0, current majors built for Langfuse v4 (15). CodeQL, Semgrep, Snyk and zizmor run in CI alongside the build pipeline. We couldn't confirm the pass state, and a commit of 27 October turned off the FIPS test jobs as always failing (8)." }, "scores": { "a": 82, "b": 88 } } ], "facts": [ { "a": "cli", "b": "HTTP API", "name": "Kind" }, { "a": "Gauge", "b": "Langfuse (ClickHouse)", "name": "Vendor" }, { "a": "no (local only)", "b": "https://cloud.langfuse.com/api/public", "name": "Hosted endpoint" }, { "a": "", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "None", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "MIT (core), commercial licence for the ee directories", "name": "Licence" }, { "a": "none", "b": "98", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-04", "b": "2026-10-29", "name": "Last release" }, { "a": "no document linked", "b": "2026-06-24", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-08-21", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "35k stars, 3M npm/wk, 5.9M PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "4/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Langfuse API + MCP scores 71.8 (BB) on agent readiness against Gauge CLI's 60.4 (C), and leads in 5 of 7 scored categories.", "question": "Which is better for AI agents, Gauge CLI or Langfuse API + MCP?" }, { "answer": "No hosted endpoint is listed for Gauge CLI. Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public.", "question": "Can an agent call Gauge CLI and Langfuse API + MCP without installing anything?" }, { "answer": "Yes. Gauge CLI is open source (MIT). Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories).", "question": "Are Gauge CLI and Langfuse API + MCP open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "No key needed to call it", "No incidents deducted, where Langfuse API + MCP loses 5 points for them" ], "goodFor": "Teams that build skills, CLIs, SDKs or MCP servers and want to see where coding agents get stuck with them, and to test fixes before release.", "slug": "gauge-cli", "watchFor": "Collects anonymous command usage by default, with an opt-out" }, { "aheadOn": [ "Reliability, 80 against 60", "Schema \u0026 documentation, 93 against 60", "Security \u0026 auth, 77 against 55", "Maintenance \u0026 community, 88 against 82", "Transparency \u0026 trust, 86 against 53" ], "also": [ "Agent-ready, a grade of BB or better", "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.", "slug": "langfuse", "watchFor": "98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist" } ], "history": { "gauge-cli": null, "langfuse": [ { "causes": [ "event" ], "date": "2026-11-01", "delta": -3, "from": 74.8, "fromGrade": "BB", "to": 71.8, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 74.8, "fromGrade": "BB", "to": 74.8, "toGrade": "BB" }, { "causes": [ "product" ], "date": "2026-10-17", "delta": 2.1, "from": 72.7, "fromGrade": "BB", "to": 74.8, "toGrade": "BB" } ] }, "job": { "capability": "obs.evals", "name": "Evaluations" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agent-tree-vs-langfuse.json", "title": "Agent Tree vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/agent-tree-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/agents-tree-vs-langfuse.json", "title": "agents-tree vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/agents-tree-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse.json", "title": "Arize Phoenix vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-langfuse.json", "title": "Baserun vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/baserun-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/botgauge-vs-langfuse.json", "title": "BotGauge vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/botgauge-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-langfuse.json", "title": "Braintrust API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/braintrust-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-langfuse.json", "title": "Galileo API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/galileo-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/helicone-vs-langfuse.json", "title": "Helicone AI Gateway + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/helicone-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/honeyhive-vs-langfuse.json", "title": "HoneyHive vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/honeyhive-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/laminar-vs-langfuse.json", "title": "Laminar API + MCP vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/laminar-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-langsmith.json", "title": "Langfuse API + MCP vs LangSmith API + MCP", "url": "https://www.anchorterminal.com/compare/langfuse-vs-langsmith" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-langwatch.json", "title": "Langfuse API + MCP vs LangWatch", "url": "https://www.anchorterminal.com/compare/langfuse-vs-langwatch" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.json", "title": "Langfuse API + MCP vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-navige.json", "title": "Langfuse API + MCP vs Navige", "url": "https://www.anchorterminal.com/compare/langfuse-vs-navige" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-opik.json", "title": "Langfuse API + MCP vs Opik API + MCP", "url": "https://www.anchorterminal.com/compare/langfuse-vs-opik" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-overmind.json", "title": "Langfuse API + MCP vs Overmind", "url": "https://www.anchorterminal.com/compare/langfuse-vs-overmind" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-prefactor.json", "title": "Langfuse API + MCP vs Prefactor", "url": "https://www.anchorterminal.com/compare/langfuse-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire.json", "title": "Langfuse API + MCP vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-respan.json", "title": "Langfuse API + MCP vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/langfuse-vs-respan" }, { "json": "https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave.json", "title": "Langfuse API + MCP vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave" }, { "json": "https://www.anchorterminal.com/compare/arize-phoenix-vs-gauge-cli.json", "title": "Arize Phoenix vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/arize-phoenix-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/baserun-vs-gauge-cli.json", "title": "Baserun vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/baserun-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/botgauge-vs-gauge-cli.json", "title": "BotGauge vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/botgauge-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/braintrust-vs-gauge-cli.json", "title": "Braintrust API + MCP vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/braintrust-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-gauge-cli.json", "title": "DeepEval vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/deepeval-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/deepeval-vs-langfuse.json", "title": "DeepEval vs Langfuse API + MCP", "url": "https://www.anchorterminal.com/compare/deepeval-vs-langfuse" }, { "json": "https://www.anchorterminal.com/compare/galileo-vs-gauge-cli.json", "title": "Galileo API + MCP vs Gauge CLI", "url": "https://www.anchorterminal.com/compare/galileo-vs-gauge-cli" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-helicone.json", "title": "Gauge CLI vs Helicone AI Gateway + MCP", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-helicone" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-honeyhive.json", "title": "Gauge CLI vs HoneyHive", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-honeyhive" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-laminar.json", "title": "Gauge CLI vs Laminar API + MCP", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-laminar" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-langsmith.json", "title": "Gauge CLI vs LangSmith API + MCP", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-langsmith" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-langwatch.json", "title": "Gauge CLI vs LangWatch", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-langwatch" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-mlflow-tracing.json", "title": "Gauge CLI vs MLflow Tracing", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-mlflow-tracing" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-opik.json", "title": "Gauge CLI vs Opik API + MCP", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-opik" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-overmind.json", "title": "Gauge CLI vs Overmind", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-overmind" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-prefactor.json", "title": "Gauge CLI vs Prefactor", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-prefactor" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-pydantic-logfire.json", "title": "Gauge CLI vs Pydantic Logfire", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-pydantic-logfire" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-respan.json", "title": "Gauge CLI vs Respan API + MCP", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-respan" }, { "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-wandb-weave.json", "title": "Gauge CLI vs W\u0026B Weave", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-wandb-weave" } ], "panel": null, "scores": [ { "by": 20, "edge": "langfuse", "gauge-cli": 60, "key": "reliability", "langfuse": 80, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 33, "edge": "langfuse", "gauge-cli": 60, "key": "schema", "langfuse": 93, "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 1, "edge": "gauge-cli", "gauge-cli": 75, "key": "ergonomics", "langfuse": 74, "name": "Agent ergonomics", "weight": 13 }, { "by": 22, "edge": "langfuse", "gauge-cli": 55, "key": "security", "langfuse": 77, "name": "Security \u0026 auth", "weight": 14 }, { "by": 0, "edge": "", "gauge-cli": 40, "key": "payments", "langfuse": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 6, "edge": "langfuse", "gauge-cli": 82, "key": "maintenance", "langfuse": 88, "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 33, "edge": "langfuse", "gauge-cli": 53, "key": "transparency", "langfuse": 86, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "Langfuse API + MCP scores 71.8 (BB) on agent readiness against Gauge CLI's 60.4 (C), and leads in 5 of 7 scored categories. Both do evaluations.", "tasks": null, "tutorials": [], "verdicts": { "gauge-cli": "An open-source CLI that measures how coding agents get on with your product and checks fixes before you ship them, locally in Docker with no account. It's young and pre-1.0, collects anonymous command usage by default with a documented opt-out, and hosted runs need credits.", "langfuse": "MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse", "json": "https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse.min.md" }, "markdown": "Langfuse API + MCP scores 71.8 (BB) on agent readiness against Gauge CLI's 60.4 (C), and leads in 5 of 7 scored categories. Both do evaluations.\n\n- Gauge CLI: grade C, 60.4/100, rank #590 of 1354. Markdown https://www.anchorterminal.com/tools/gauge-cli.md · JSON https://www.anchorterminal.com/api/v1/tools/gauge-cli.json\n- Langfuse API + MCP: grade BB, 71.8/100, rank #132 of 1354. Markdown https://www.anchorterminal.com/tools/langfuse.md · JSON https://www.anchorterminal.com/api/v1/tools/langfuse.json\n- Best agent tracing, monitoring and evaluation tools: https://www.anchorterminal.com/best/agent-observability/index.md\n- All 250 evals comparisons: https://www.anchorterminal.com/compare/agent-observability/index.md\n\n## Which one, for what\n\n### Gauge CLI (C)\n\nGood for: Teams that build skills, CLIs, SDKs or MCP servers and want to see where coding agents get stuck with them, and to test fixes before release.\n\nAlso in its favour:\n- No key needed to call it\n- No incidents deducted, where Langfuse API + MCP loses 5 points for them\n\nWatch for: Collects anonymous command usage by default, with an opt-out\n\n### Langfuse API + MCP (BB)\n\nGood for: Teams that want open source they can self-host or a predictable cloud bill, across tracing, evals, prompts and datasets.\n\nAhead on:\n- Reliability, 80 against 60\n- Schema \u0026 documentation, 93 against 60\n- Security \u0026 auth, 77 against 55\n- Maintenance \u0026 community, 88 against 82\n- Transparency \u0026 trust, 86 against 53\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: 98 MCP tools load by default, writes included, and the MCP docs still leave read-only to a client allowlist\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Langfuse API + MCP +33\n\n- Gauge CLI (60): CLI reading. No machine-readable contract, -o json on read commands (10 of 25). No llms.txt; instructions bundled in the CLI for agents (5). The README says what it finds and when local or hosted fits (16 of 20). Commands with help text; typed flags (9 of 15). Worked examples, no error reference (8 of 15). Dated changelog and semver tags (12 of 15). 10 + 5 + 16 + 9 + 8 + 12 = 60.\n- Langfuse API + MCP (93): Public OpenAPI at cloud.langfuse.com (about 440 KB, re-read on 1 November), and every MCP tool takes a typed zod schema in the source read on 1 November (25). llms.txt and Markdown docs, with every page available as Markdown at `.md` (10). Tool descriptions say what to use each one for and how to size the result. `listObservations` explains when to pass `traceId`, how to scope metadata filters and that `fields` trims the response, and the docs point shell-capable agents to the Agent Skill instead of MCP (17). Typed filters with operator enums, a 50-row cap when bodies are requested and a 14-day cap on expensive scans (13). Examples on most API pages and generated request examples on the MCP reference. Error bodies are less fully documented (13). Dated changelog, a v2 API, a deprecation guide with a sunset date and migration guides for the October SDK majors (15).\n\n### Transparency \u0026 trust: Langfuse API + MCP +33\n\n- Gauge CLI (53): MIT (30). Local data stays in .gauge/ and telemetry fields are listed; hosted data handling wasn't read (18 of 30). Dated changelog, no deprecation policy (10 of 20). Telemetry on by default, disclosed with an opt-out (20). 30 + 18 + 10 + 20 = 78.\n- Langfuse API + MCP (86): MIT core with the ee directories under a commercial licence (27). Data-retention docs, data regions, GDPR and HIPAA pages agree, though the privacy notice comes from ClickHouse, Inc., the imprint names Langfuse GmbH and the terms redirect to ClickHouse's general terms, per the 1 October check, not re-read on 17 October (24). Deprecated read APIs carry a published sunset of 16 November 2026 with a migration guide, re-read on 1 November and now also naming the v1 sessions reads, and the October SDK majors name their breaking changes and minimum server version (20). Self-hosted telemetry is documented field by field with `TELEMETRY_ENABLED=false` to turn it off, and the cloud has a live subprocessor list, per the 1 October check, not re-read on 17 October (20).\n\n### Security \u0026 auth: Langfuse API + MCP +22\n\n- Gauge CLI (55): Local tool. Agent credentials stay on your machine in local mode; hosted login with a device flow (20 of 30). Test agents run in fresh Docker sessions with injected inputs, and the gateway brokers credentials in hosted mode (12 of 20). Agents under test read your product's docs and outputs, with no prompt-injection guidance (5 of 15). Local transcripts and SQLite evidence per run (10 of 15). No security policy found (8 of 20). 20 + 12 + 5 + 10 + 8 = 55.\n- Langfuse API + MCP (77): Project-scoped key pairs over Basic auth, revocable, with organisation keys kept to admin APIs. Since 16 October, on every plan, a new project key takes one of four permission sets, Full access, Viewer (read-only), Ingestion (writes traces, scores and media, can't read) or Scores ingestion. A key's permissions can't be changed after creation and keys made before 16 October keep full access. Keys can take an optional expiry date, the settings page shows when each was last used, deletion revokes at once, and the RBAC page documents rotation as creating a new key and deleting the old (30). A Viewer key is read-only on the public API. The MCP server's source, re-read at v4.72.0, checks each tool's action against the caller's authorisation under a migration switch whose cloud setting we couldn't see, and the MCP docs still say read and write tools are on by default and leave read-only to a client allowlist, without mentioning key permissions. Annotations mark reads and destructive tools (14). Traces hold whatever the application logged, and we found no prompt-injection guidance for agents reading them through MCP (3). Audit logs on Enterprise only (10). Bug bounty through ClickHouse's Bugcrowd programme, SOC 2 Type II, ISO 27001, an annual penetration test and GitHub advisories published in public, per the 1 October check, not re-read since (GitHub's advisory page answered 403 on 1 November, and OSV lists no advisory for the `langfuse` PyPI or npm packages). langfuse.com/.well-known/security.txt returned 404 on 1 November (20).\n\n### Reliability: Langfuse API + MCP +20\n\n- Gauge CLI (60): Local package. Installs from npm as @withgauge/cli with Node 22.13 or later and Docker stated (20). checks.yml runs npm run check on push and pull request across a matrix, and the repository has 76 test files; whether main passes wasn't read (20 of 25). Issues weren't read (5, unchecked). A dated changelog with Added sections per release (15). Version 0.28.0 (0). 20 + 20 + 5 + 15 + 0 = 60.\n- Langfuse API + MCP (80): incident.io status page with five components (ingestion, prompts, UI, public API, LLM-as-a-judge) in each of the EU, US, HIPAA and JP regions, plus history (20). The history page, re-read on 1 November, dates each component's impact. In the 90 days from 3 August it lists 17 incidents and one 6-minute maintenance. 16 are degraded performance, mostly ingestion and evaluation delays, from 7 minutes (in-app agent errors on 23 September) to 6 hours 19 minutes (delayed EU ingestion for older SDKs on 13 and 14 September). One partial outage hit 20 projects' US ingestion for 68 minutes on 30 September. Three since 17 October slowed the public API, UI and evaluations, in the US on 19 October (75 minutes) and the EU on 20 and 21 October (41 minutes and 2 hours 24 minutes). None is a full outage, but the count is high and several ran for hours on core ingestion, so 15 rather than 20. Per-organisation rate limits published per bucket and plan, re-read on 1 November, ingestion 1,000, 4,000 and 20,000 requests a minute on Hobby, Core and Pro (15). 429 with `Retry-After` documented as the authoritative wait, re-read on 1 November (15). Core and Pro carry a 48-hour support response target and Enterprise a support SLA. We found no uptime SLA (5). API and MCP are GA (10).\n\n### Maintenance \u0026 community: Langfuse API + MCP +6\n\n- Gauge CLI (82): CLI 0.28.0 on 4 November 2026 (30). Six releases in 90 days (20). Issues and pull requests weren't read; a support address and issue tracker are published (12 of 25). Current official package (15). CI on push and pull request (5 of 10, results not read). 30 + 20 + 12 + 15 + 5 = 82.\n- Langfuse API + MCP (88): Server v4.72.0 tagged on 2026-10-29 (30). Nine v4 server tags from v4.64.0 on 19 October to v4.72.0 on 29 October, after 14 from 2 to 16 October, and v3.225.13 to v3.225.15 for the older line (20). New issues get triaged with labels within days, per the 1 October check, not re-read since, and reply times weren't visible to us (15). Python SDK v5.1.0 tagged on 2026-10-30 and JS SDK v6.1.0, current majors built for Langfuse v4 (15). CodeQL, Semgrep, Snyk and zizmor run in CI alongside the build pipeline. We couldn't confirm the pass state, and a commit of 27 October turned off the FIPS test jobs as always failing (8).\n\n## Score by category\n\n| Category | Weight | Gauge CLI | Langfuse API + MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 80 | Langfuse API + MCP +20 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 93 | Langfuse API + MCP +33 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 74 | Gauge CLI +1 |\n| Security \u0026 auth | 14% (17.5 this run) | 55 | 77 | Langfuse API + MCP +22 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 40 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 82 | 88 | Langfuse API + MCP +6 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 53 | 86 | Langfuse API + MCP +33 |\n| Negative events | ≤15 | 0 | -5 | |\n| **Total** | | **60.4 · C** | **71.8 · BB** | |\n\n## Facts side by side\n\n| Fact | Gauge CLI | Langfuse API + MCP |\n| --- | --- | --- |\n| Kind | cli | HTTP API |\n| Vendor | Gauge | Langfuse (ClickHouse) |\n| Hosted endpoint | no (local only) | `https://cloud.langfuse.com/api/public` |\n| Transports | | HTTP, Streamable HTTP |\n| Auth | None | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | MIT | MIT (core), commercial licence for the ee directories |\n| Tools exposed | none | 98 |\n| Read-only variant documented | no | yes |\n| llms.txt | no | yes |\n| Last release | 2026-11-04 | 2026-10-29 |\n| Terms last updated | no document linked | 2026-06-24 |\n| Privacy policy last updated | no document linked | 2026-08-21 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 35k stars, 3M npm/wk, 5.9M PyPI/wk |\n| Agent reviews | none | 4/5 (2) |\n\n## How the scores have moved\n\n### Gauge CLI\n\nNo score change since it was listed.\n\n### Langfuse API + MCP\n\n- -3.0 on 1 November 2026: negative event\n- no change on 27 October 2026: checklist\n- +2.1 on 17 October 2026: product\n\n## Verdicts\n\n**Gauge CLI.** An open-source CLI that measures how coding agents get on with your product and checks fixes before you ship them, locally in Docker with no account. It's young and pre-1.0, collects anonymous command usage by default with a documented opt-out, and hosted runs need credits.\n\n**Langfuse API + MCP.** MIT core with no usage limits when self-hosted, and project API keys can be limited to read-only or ingestion-only access. 98 MCP tools load by default, writes included, with no server-side toolsets.\n\n## Before you call either\n\n### Gauge CLI\n\n1. npm install -g @withgauge/cli, then gauge local runtime pull and gauge init --local in the project\n2. Run gauge install-skill so your coding agent finds the CLI's own instructions\n3. Set GAUGE_TELEMETRY_DISABLED=1 in CI if you don't want command usage collected\n4. Rebuild and pack an npm CLI or SDK before rerunning, so test sessions get the new tarball\n5. Keep .gauge/ private; it holds measurements and analyses\n\n### Langfuse API + MCP\n\n1. Use a Viewer key for an agent that only reads traces. Keys created before 16 October keep full access and can't be narrowed\n2. Allowlist only the MCP tools the agent needs. All 98 load by default, writes included, and they share the General API bucket, so wait for `Retry-After` on 429\n3. Ask `listObservations` for specific `fields`. Requesting input, output or metadata caps the page at 50 rows and the range at 14 days\n4. Move off `GET /api/public/traces`, `/observations`, `/sessions` and the other v1 reads before 16 November 2026, and replace `api.scores_v3` when moving to Python SDK v5 or JS/TS SDK v6\n5. Pick the regional host (cloud, us.cloud, jp.cloud, hipaa.cloud) that matches the project's keys\n\n## Questions\n\n### Which is better for AI agents, Gauge CLI or Langfuse API + MCP?\n\nLangfuse API + MCP scores 71.8 (BB) on agent readiness against Gauge CLI's 60.4 (C), and leads in 5 of 7 scored categories.\n\n### Can an agent call Gauge CLI and Langfuse API + MCP without installing anything?\n\nNo hosted endpoint is listed for Gauge CLI. Langfuse API + MCP has a hosted endpoint at https://cloud.langfuse.com/api/public.\n\n### Are Gauge CLI and Langfuse API + MCP open source?\n\nYes. Gauge CLI is open source (MIT). Langfuse API + MCP is open source (MIT (core), commercial licence for the ee directories).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse.json, and with the fewest tokens: https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"gauge-cli\", \"b\": \"langfuse\"}`. From a terminal: `anchor compare gauge-cli langfuse`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/gauge-cli.json and https://www.anchorterminal.com/api/v1/tools/langfuse.json\n\n## Other comparisons with Gauge CLI or Langfuse API + MCP\n\n- [Agent Tree vs Langfuse API + MCP](https://www.anchorterminal.com/compare/agent-tree-vs-langfuse.md)\n- [agents-tree vs Langfuse API + MCP](https://www.anchorterminal.com/compare/agents-tree-vs-langfuse.md)\n- [Arize Phoenix vs Langfuse API + MCP](https://www.anchorterminal.com/compare/arize-phoenix-vs-langfuse.md)\n- [Baserun vs Langfuse API + MCP](https://www.anchorterminal.com/compare/baserun-vs-langfuse.md)\n- [BotGauge vs Langfuse API + MCP](https://www.anchorterminal.com/compare/botgauge-vs-langfuse.md)\n- [Braintrust API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/braintrust-vs-langfuse.md)\n- [Galileo API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/galileo-vs-langfuse.md)\n- [Helicone AI Gateway + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/helicone-vs-langfuse.md)\n- [HoneyHive vs Langfuse API + MCP](https://www.anchorterminal.com/compare/honeyhive-vs-langfuse.md)\n- [Laminar API + MCP vs Langfuse API + MCP](https://www.anchorterminal.com/compare/laminar-vs-langfuse.md)\n- [Langfuse API + MCP vs LangSmith API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-langsmith.md)\n- [Langfuse API + MCP vs LangWatch](https://www.anchorterminal.com/compare/langfuse-vs-langwatch.md)\n- [Langfuse API + MCP vs MLflow Tracing](https://www.anchorterminal.com/compare/langfuse-vs-mlflow-tracing.md)\n- [Langfuse API + MCP vs Navige](https://www.anchorterminal.com/compare/langfuse-vs-navige.md)\n- [Langfuse API + MCP vs Opik API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-opik.md)\n- [Langfuse API + MCP vs Overmind](https://www.anchorterminal.com/compare/langfuse-vs-overmind.md)\n- [Langfuse API + MCP vs Prefactor](https://www.anchorterminal.com/compare/langfuse-vs-prefactor.md)\n- [Langfuse API + MCP vs Pydantic Logfire](https://www.anchorterminal.com/compare/langfuse-vs-pydantic-logfire.md)\n- [Langfuse API + MCP vs Respan API + MCP](https://www.anchorterminal.com/compare/langfuse-vs-respan.md)\n- [Langfuse API + MCP vs W\u0026B Weave](https://www.anchorterminal.com/compare/langfuse-vs-wandb-weave.md)\n- [Arize Phoenix vs Gauge CLI](https://www.anchorterminal.com/compare/arize-phoenix-vs-gauge-cli.md)\n- [Baserun vs Gauge CLI](https://www.anchorterminal.com/compare/baserun-vs-gauge-cli.md)\n- [BotGauge vs Gauge CLI](https://www.anchorterminal.com/compare/botgauge-vs-gauge-cli.md)\n- [Braintrust API + MCP vs Gauge CLI](https://www.anchorterminal.com/compare/braintrust-vs-gauge-cli.md)\n- [DeepEval vs Gauge CLI](https://www.anchorterminal.com/compare/deepeval-vs-gauge-cli.md)\n- [DeepEval vs Langfuse API + MCP](https://www.anchorterminal.com/compare/deepeval-vs-langfuse.md)\n- [Galileo API + MCP vs Gauge CLI](https://www.anchorterminal.com/compare/galileo-vs-gauge-cli.md)\n- [Gauge CLI vs Helicone AI Gateway + MCP](https://www.anchorterminal.com/compare/gauge-cli-vs-helicone.md)\n- [Gauge CLI vs HoneyHive](https://www.anchorterminal.com/compare/gauge-cli-vs-honeyhive.md)\n- [Gauge CLI vs Laminar API + MCP](https://www.anchorterminal.com/compare/gauge-cli-vs-laminar.md)\n- [Gauge CLI vs LangSmith API + MCP](https://www.anchorterminal.com/compare/gauge-cli-vs-langsmith.md)\n- [Gauge CLI vs LangWatch](https://www.anchorterminal.com/compare/gauge-cli-vs-langwatch.md)\n- [Gauge CLI vs MLflow Tracing](https://www.anchorterminal.com/compare/gauge-cli-vs-mlflow-tracing.md)\n- [Gauge CLI vs Opik API + MCP](https://www.anchorterminal.com/compare/gauge-cli-vs-opik.md)\n- [Gauge CLI vs Overmind](https://www.anchorterminal.com/compare/gauge-cli-vs-overmind.md)\n- [Gauge CLI vs Prefactor](https://www.anchorterminal.com/compare/gauge-cli-vs-prefactor.md)\n- [Gauge CLI vs Pydantic Logfire](https://www.anchorterminal.com/compare/gauge-cli-vs-pydantic-logfire.md)\n- [Gauge CLI vs Respan API + MCP](https://www.anchorterminal.com/compare/gauge-cli-vs-respan.md)\n- [Gauge CLI vs W\u0026B Weave](https://www.anchorterminal.com/compare/gauge-cli-vs-wandb-weave.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-06", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Gauge CLI vs Langfuse API + MCP", "url": "" } ], "description": "Langfuse scores 71.8 (BB) to Gauge CLI's 60.4 (C) for evaluations. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Gauge CLI C 60.4", "Langfuse API + MCP BB 71.8", "scores" ], "h1": "Gauge CLI vs Langfuse API + MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/gauge-cli-vs-langfuse", "published": "2026-10-01", "section": "tools", "title": "Gauge CLI vs Langfuse for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-06", "url": "https://www.anchorterminal.com/compare/gauge-cli-vs-langfuse" }, "tokens": { "markdown": 4700, "slim": 2580 }, "version": 1 }