6.3mediumCONDITIONAL GO

dbt Lineage Explorer

Standalone visual lineage and impact analysis tool for dbt projects, independent of VS Code

DevToolsData engineers and analytics engineers using dbt who want editor-agnostic lin...
The Gap

dbt users depend on the dbt Power User VS Code extension or clunky workarounds to visualize lineage; there's no polished standalone tool

Solution

A web-based or desktop app that parses dbt projects, renders interactive lineage graphs, shows impact analysis for changes, and works with any editor or CI environment

Revenue Model

Freemium — free for single projects, paid for team collaboration features, CI integration, and multi-project support

Feasibility Scores
Pain Intensity7/10

Real pain exists — dbt's built-in docs lineage is terrible for exploration, and depending on a VS Code extension frustrates non-VS Code users. However, this is a 'nice to have' pain for many teams, not a 'hair on fire' problem. Teams ship dbt code without lineage tools daily. The pain is sharpest during incident response (what downstream broke?) and PR review (what does this change impact?).

Market Size5/10

dbt has ~40,000+ active users and growing, but this is a niche within data engineering. TAM for a standalone lineage tool is likely $20-50M ARR at maturity. Most enterprise teams will gravitate to dbt Cloud or full observability platforms like Monte Carlo/Datafold. Your addressable market is dbt Core users on small-to-mid teams who won't pay for dbt Cloud — a passionate but price-sensitive segment.

Willingness to Pay5/10

Data engineers are notoriously resistant to paying for dev tools — they lean toward open-source. dbt Power User struggled to monetize its free user base. The free dbt docs and open-source alternatives set a low price anchor. Team/collaboration features and CI integration are the most likely paid levers, but you're competing against 'good enough' free options. Expect $15-30/user/month ceiling for individual plans.

Technical Feasibility8/10

Highly feasible for a solo dev. The core data is already structured — dbt generates manifest.json and catalog.json with all model metadata, dependencies, and column info. Parsing these files and rendering a graph (D3.js, Cytoscape, or React Flow) is well-understood. An MVP of 'upload manifest.json, see interactive lineage, click a model to see impact' is buildable in 4-6 weeks. Column-level lineage and SQL parsing are harder but not needed for MVP.

Competition Gap6/10

There IS a gap — no polished, standalone, editor-agnostic lineage tool exists today. But the gap is narrowing: dbt Cloud keeps improving its lineage, Datafold and Elementary are adding features, and dbt Power User works well enough for most VS Code users. Your differentiation window is real but not wide. The strongest angle is 'works in CI + any editor + interactive impact analysis' — nobody does all three well today.

Recurring Potential7/10

Lineage is checked regularly (every PR, every incident, every onboarding). Team collaboration (shared annotations, saved views, change tracking) and CI integration (impact analysis comments on PRs) create natural recurring value. However, the free tier must be genuinely useful or users churn — the core lineage rendering is hard to gate without feeling hostile.

Strengths
  • +Clear gap in the market — no standalone, editor-agnostic dbt lineage tool exists with good UX
  • +Technically very feasible — manifest.json parsing + graph rendering is well-understood territory
  • +Strong organic demand signal — Reddit thread with 99 upvotes, frequent complaints about dbt Power User lock-in
  • +Natural integration point with CI/CD that dbt Power User cannot offer
  • +Low CAC potential — dbt community is concentrated (dbt Slack, Reddit, blog posts) and responsive to good tools
Risks
  • !dbt Labs could ship a free standalone lineage explorer or significantly improve dbt docs, killing your differentiation overnight
  • !Willingness to pay is low in the dbt Core community — you may build a popular free tool that struggles to monetize
  • !Open-source competitors (Elementary, sqllineage, dbt-meshify) could add interactive lineage features quickly
  • !Market is niche — ceiling may be a solid lifestyle business ($500K-2M ARR) rather than venture-scale
  • !Column-level lineage (a key differentiator) requires SQL parsing which is significantly harder to build and maintain across dialects
Competition
dbt Cloud (dbt Labs)

Official dbt SaaS platform with built-in lineage visualization, IDE, job orchestration, and documentation hosting

Pricing: $100/developer/month (Team
Gap: Expensive for small teams, lineage is secondary to orchestration, locked into dbt Cloud ecosystem, no standalone lineage-only option, limited interactive impact analysis
dbt Power User (VS Code Extension by Altimate AI)

VS Code extension providing lineage visualization, column-level lineage, documentation generation, and health checks for dbt projects

Pricing: Free tier available, Pro at ~$30/user/month
Gap: Locked to VS Code — excludes Vim, Neovim, JetBrains, Cursor users. No CI integration. No web-based sharing. No multi-project views. Breaks for some users on updates
Elementary Data

Open-source data observability tool for dbt with lineage visualization, test results dashboard, and data quality monitoring

Pricing: Open source (free
Gap: Lineage is a secondary feature to observability, not purpose-built for lineage exploration and impact analysis, limited interactive graph manipulation, setup requires running dbt packages
Datafold

Data diff and lineage platform that provides column-level lineage, CI testing, and impact analysis for dbt and other tools

Pricing: Free for open-source projects, paid plans starting ~$500/month for teams
Gap: Expensive for small teams, lineage is bundled with data diff (can't buy lineage alone), complex setup, enterprise-focused sales motion, overkill if you just want lineage visualization
dbt Docs (built-in dbt docs generate/serve)

Built-in dbt command that generates a static documentation site with a DAG lineage viewer

Pricing: Free (included with dbt Core
Gap: Extremely basic UX — no interactive impact analysis, no filtering by tag/folder, no column-level lineage, no change-aware highlighting, ugly and slow with large projects (500+ models), no collaboration features, no CI integration
MVP Suggestion

Web app where users upload or connect their dbt manifest.json. Renders an interactive DAG with search, filter by tag/folder/package, and click-to-expand impact analysis (upstream + downstream). Highlight changed models (via git diff of manifest) to show 'what does this PR affect?' No auth, no backend database — purely client-side processing of the manifest file. Ship in 4-6 weeks.

Monetization Path

Free: single project, local manifest upload, full lineage + impact analysis → Paid ($20/user/month): team workspaces, shared annotations, persistent project history, CI bot (GitHub/GitLab PR comments showing impact), multi-project lineage → Scale ($50/user/month): column-level lineage, cross-project lineage, SSO/RBAC, API access, custom integrations

Time to Revenue

8-12 weeks to first dollar. 4-6 weeks to build and launch MVP (free), 2-4 weeks to add team features and CI integration as paid tier. First paying customers likely come from dbt Slack and Reddit organic posts. Expect slow initial revenue ($1-5K MRR) in first 6 months, growing as word-of-mouth compounds in the tight-knit dbt community.

What people are saying
  • so I dont have to depend on dbt power user anymore or vscode
  • super useful