🩺 Vitals
- 🟢 Last active: 2026-07-16
- 📦 Latest release: 0.3401.1 (2026-07-16)
- 🐞 Open issues: 1554
- 🌟 Stars: 6k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent tagged, packaged version the maintainers published. Not every healthy project tags releases.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: lightdash.com
- Source: github.com/lightdash/lightdash
- License: MIT (Core) | Commercial (EE)
- Deployment: Docker / Kubernetes
- Data Model: dbt-native / PostgreSQL metadata
- Jurisdiction: United Kingdom 🇬🇧 (Telescope Technology Ltd, VC-backed)
- Compliance (SaaS): SOC 2 Type II | HIPAA
- Compliance (Self-Hosted): Self-Hosted (User Managed)
- Complexity: Medium (3/5) - Docker/K8s + Postgres + a dbt project
- Maintenance: Medium (3/5) - Continuous releases, frequent updates
- Enterprise Ready: High (4/5) - SSO, RBAC, SCIM (Enterprise tier)
1. The Executive Summary
What is it? Lightdash is a business intelligence tool that lives inside the dbt workflow. (dbt is the standard tool data teams use to define and transform data in the warehouse.) Instead of rebuilding metric definitions inside a separate BI interface, Lightdash reads the metrics already defined in your dbt project and turns them into charts and dashboards. Every dashboard exports to version-controlled YAML, so your BI layer lives in git alongside your code rather than locked in a vendor's UI.
This is the sharpest expression of BI-as-code in the open source landscape. Where Metabase and Redash connect to a database and let analysts build queries in their own interface, Lightdash treats your dbt project as the single source of truth, so metric definitions move into code review instead of living as clicks. The trade-off is scope: the free MIT core is a genuine BI platform, but the governance features enterprises expect (SSO beyond Google OAuth, fine-grained RBAC, SCIM) sit behind the paid Enterprise tier.
The Strategic Verdict:
- 🔴 For Teams Without dbt: Caution. Lightdash's value depends on an existing dbt project and git discipline. Without them, the BI-as-code model adds overhead rather than removing it, and SSO and custom RBAC still require the paid tier.
- 🟢 For dbt-Based Data Teams: Strong Buy. Define a metric once in dbt and consume it everywhere, keep dashboards under version control, and self-host the MIT core with full data ownership and no per-seat fees.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Looker (SaaS) | Lightdash (Self-Hosted) |
|---|---|---|
| Semantic Layer | LookML (proprietary, Looker-locked) | dbt (open, git-tracked) |
| Analyst & Viewer Seats | Per-user platform licensing | $0 (Unlimited, Core) |
| SSO & Custom RBAC | Bundled in platform | Enterprise tier (paid) |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: Runs via Docker or Kubernetes with a PostgreSQL database for its own metadata. The deployment must point at a dbt project (synced from git) and your data warehouse.
- Scalability: Lightdash stays a thin layer. Heavy queries execute in the warehouse rather than inside Lightdash, so the app scales horizontally behind its Postgres metadata store.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Geopolitics (United Kingdom 🇬🇧): Lightdash is built by Telescope Technology Limited, a VC-backed UK company. UK headquartering keeps it outside US CLOUD Act reach, though it remains subject to UK GDPR and Five Eyes intelligence-sharing arrangements. Self-hosting the core removes the vendor from the data path entirely, placing all query traffic and credentials under your own jurisdiction.
- The Compliance Shift and Enterprise Tax: The managed cloud holds SOC 2 Type II and HIPAA. Self-hosting the MIT core moves every infrastructure control to your team, and the features that make a deployment enterprise-grade are paywalled: SAML/Okta SSO, custom roles and groups, SCIM provisioning, SSH tunnels to cloud warehouses, and the HIPAA BAA all require the Enterprise tier. Read the free core as a capable analyst tool, not a governed enterprise platform.
- License Risk (The Open-Core Trap): The core is MIT, so it is safe to fork, embed, and self-host. Two cautions apply. First, the proprietary Enterprise code ships inside the same repository, so you must deploy the genuine OSS image and leave commercial features unlicensed to avoid running paid code without a key. Second, a single VC-backed vendor controls where the free-versus-paid line sits, and that line can move over time. The MIT core caps the downside, since a fork remains possible.
4. Market Landscape
🏢 Proprietary Incumbents
- Looker: Google Cloud's BI platform, built on the proprietary LookML modeling language. Teams adopt Lightdash to define the semantic layer in open, portable dbt instead of LookML, and to escape per-seat platform pricing.
- Omni: The dbt-native cloud BI challenger from former Looker leaders. Lightdash is the self-hostable, open-core counterpart for teams that want the code-first model without a mandatory SaaS.
🤝 Open Source Ecosystem
- Metabase: The no-SQL, non-dbt option for fast self-service; Lightdash is the choice when your metrics already live in dbt.
- Apache Superset: The broader, warehouse-agnostic platform with its own semantic layer; Lightdash trades that breadth for tight dbt-native metrics-as-code.