Latitude

license

MIT(OSI, single root LICENSE

source

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

core features withheld

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

Latitude's whole platform - the web app, worker, CLI and SDKs - is MIT-licensed, with no enterprise-only directory in the repository, and self-hosts at any scale via Docker Compose, a Kubernetes Helm chart or one-click Railway. The hosted Latitude Cloud sells usage credits and retention beyond the free tier, a separate commercial offering rather than a gate on the published source.

• 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/LICENSE recorded 2026-10-07

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

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

  Self-host section says Latitude is self-hostable "at any scale, on fully open infrastructure", as "a production-grade instance on one machine with Docker Compose", "a scalable, highly-available deployment on Kubernetes via a Helm chart" or a one-click Railway deploy; the License section reads "Latitude is licensed under the [MIT License](LICENSE)."

Latitude deploys as Docker images, a Helm chart or a Railway template, none of which produces a countable download figure, leaving GitHub stars as the only adoption signal available. Telemetry-package downloads measure instrumented applications rather than running instances, and Docker Hub's pull counts are cumulative rather than a monthly figure, so neither can substitute for it.

• 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://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 reading.

• 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 reading.

Latitude combines tracing, dataset-based regression testing and monitoring with an autonomous triage-and-fix loop - automatic failure clustering, coding-agent dispatch and replay against failing traces - that no other product in this category offers. That keeps it level with Langfuse; nothing yet shows the loop working at the scale of the frontier platforms.

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

  The Why Latitude section: "one line of telemetry captures every trace: multi-turn sessions, tool calls, and full execution paths"; "failing traces are auto-grouped into tracked signals with status, size, and trend"; "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"; "fixes are replayed against the real failing traces".