Latitude

license

MIT(OSI, single root LICENSE

source

public(apps/web, the worker, the CLI and every SDK ship in this repository

core-gated

ungated(no ee/ or enterprise-only directory found in the recursive tree

The whole platform - the web app, worker, CLI and SDKs - is MIT-licensed and self-hostable at any scale on infrastructure the README calls "fully open infrastructure": single-host Docker Compose, a Kubernetes Helm chart for a cluster, or one-click Railway. A recursive tree search for enterprise/ee/premium paths found none. The hosted Latitude Cloud sells usage credits and retention beyond the free tier, which is a separate commercial offering rather than a gate on the published source.

• https://raw.githubusercontent.com/latitude-dev/latitude-llm/development/LICENSE recorded 2026-09-02

  MIT License text, Copyright Latitude Data SL, the root license.

• https://api.github.com/repos/latitude-dev/latitude-llm/git/trees/development?recursive=1 recorded 2026-09-02

  The whole repository tree, 7,650 paths. No `/ee/` or `enterprise` gating directory exists; packages/cli/LICENSE is Apache-2.0 and packages/sdk/python/LICENSE.md and packages/telemetry/python/LICENSE.md are both MIT, none more restrictive than the root.

• https://raw.githubusercontent.com/latitude-dev/latitude-llm/development/README.md recorded 2026-09-02

  The Self-host section: "Latitude is self-hostable at any scale, on fully open infrastructure," naming Single-host (Docker Compose), Cluster (Kubernetes Helm chart) and one-click Railway deploy as the three paths, alongside "License: Latitude is licensed under the MIT License."

4,613 GitHub stars on latitude-dev/latitude-llm, which lands in the 1K-10K stars band of the stars scale, level 2. The platform is deployed as Docker Hub images, a Helm chart or a Railway template, and none of those is a declarable artifact kind, so no download count of the platform itself exists to band on. The telemetry packages (latitude-telemetry at 15,728 PyPI downloads a month, @latitude-data/telemetry at 27,563 npm downloads a month) are one component of the platform - the instrumentation library an application imports - and count instrumented applications rather than running Latitude instances, so they are recorded as context and not banded. Docker Hub reports between 22,922 and 29,501 cumulative pulls per image across the six platform images, a lifetime total that corroborates a small deployed base without being a monthly figure.

• https://api.github.com/repos/latitude-dev/latitude-llm recorded 2026-09-02

  stargazers_count = 4,613, forks_count = 387, pushed_at 2026-09-02, for latitude-dev/latitude-llm.

• https://hub.docker.com/v2/repositories/latitudedata/?page_size=25 recorded 2026-09-02

  Six images under the latitudedata namespace with lifetime pull_count - web 22,922, api 24,418, workers 23,845, ingest 24,982, workflows 29,501, migrations 27,349 - all last updated 2026-09-01. Cumulative totals, not a monthly window; recorded as corroboration of the deployed base.

• https://pypistats.org/api/packages/latitude-telemetry/recent recorded 2026-09-02

  last_month = 15,728 downloads for latitude-telemetry (last_week 3,331, last_day 632). A measurement of one component package's channel, recorded as context and explicitly not the basis of the band.

• https://api.npmjs.org/downloads/point/last-month/@latitude-data/telemetry recorded 2026-09-02

  downloads: 27,563 for @latitude-data/telemetry, 2026-07-31 to 2026-08-29. A measurement of one component package's channel, recorded as context and explicitly not the basis of the band.

Covers tracing, dataset-based regression testing and monitoring - the dimensions this category grades - and adds an autonomous triage-and-fix loop (failure clustering, agent dispatch, verified replay) that no other product in this category offers. That is a genuinely distinctive capability set, held at level with the Langfuse anchor at 4 rather than above it: the category's top rung is reserved for Arize AX's frontier-scale closed platform, and Latitude's own dispatch loop is not yet evidenced at that scale.

• https://raw.githubusercontent.com/latitude-dev/latitude-llm/development/README.md recorded 2026-09-02

  The Why Latitude section: "Observe: one line of telemetry captures every trace"; "Understand: failing traces are auto-grouped into tracked signals with status, size, and trend"; "Fix: Latitude dispatches your coding agents (Claude Code, Cursor) with the full context, sample traces, and a deep link. It writes the smallest correct fix and opens a PR"; "Verify: fixes are replayed against the real failing traces."