Data and analytics

DAG control plane for warehouse pipelines

Tracewell · One control plane for pipeline lineage, masking, cost and replay across warehouses

WatchingDraft scoreEstablished market · since 2018 · Verified

47PWAS score

Confidence

Based on 9 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: Data teams using cloud warehouses (Databricks, Snowflake, BigQuery) lack a control plane that manages pipeline dependencies, governs data lineage and masking, and enables reproducible workflows—these capabilities stay siloed across the warehouse, making drift detection, cost tracking, and compliance auditing manual and fragmented.
Solution concept: A control plane that sits atop existing warehouses and owns the pipeline DAG, compiler, and schema. It provides compile-time column lineage (not post-hoc), unified governance surfaces (classification tagging, per-environment masking policies, audit trails), cost attribution per model, and Git-like workflows (branches and replay) without replacing the warehouse or orchestration layer.
Who has it: Data engineers and pipeline teams at companies running warehouse-centric analytics, particularly those handling governed or sensitive data across multiple environments.
How they handle it today: Today, teams keep storage and compute in their warehouse (Databricks, Snowflake, BigQuery) and manage pipelines through separate tools like dbt or Dagster for orchestration, but governance—column classification, masking, audit trails, cost attribution—remains manually enforced or patchy because the DAG owner does not see the full data lineage or compliance requirements end-to-end.
Why now: Regulatory pressure (data governance, audit trails), cloud warehouse adoption at scale (Databricks, Snowflake gaining enterprise footprint), and the rise of sensitive/regulated data in analytics (health, finance, PII) make end-to-end governance and lineage urgent. Data teams increasingly need reproducibility and cost visibility in their pipelines.
How it could charge: Likely a per-seat subscription, per-DAG complexity tier, or usage-based pricing (based on pipeline runs, warehouse volume scanned, or compliance checks). Could bundle orchestration or offer premium governance modules.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 95 · 5 evidence · Hacker News post on the problem received 122 points and 48 comments (E4), showing clear demand; multiple established competitors (Dagster, dbt, Databricks Unity Catalog, Snowflake) address parts of this workflow (E5, E7, E9, E10), indicating an active market for pipeline tools.

Revenue evidence

Confidence 95 · 6 evidence · Multiple established competitors charge for closely related products: dbt Labs generates over $100M ARR (E13), Dagster offers paid plans from $10–$100/month (E9), and the combined dbt + Fivetran entity is nearly $600M ARR (E12), demonstrating substantial revenue in the adjacent orchestration and transformation market.

Growth

Confidence 40 · 1 evidence · Evidence shows existing orchestration tools (Dagster founded 2018, dbt established) have active pricing and customer bases, but no specific evidence of breakout growth in the DAG control plane or unified governance category itself.

Problem severity

Confidence 70 · 3 evidence · The evidence describes cost attribution gaps (E2), compliance and audit trail fragmentation (E8), and lineage precision issues (E3) that cost teams time and prevent reproducibility; these are recurring friction points but not critical blockers.

Economic proximity

Confidence 30 · Judged from the description · A DAG control plane for warehouse pipelines sits at the boundary between data infrastructure and cost/compliance visibility; it enables cost attribution (E2) and governance enforcement but does not directly generate revenue for the customer the way sales automation would.

Distribution

Confidence 30 · Judged from the description · Pipeline orchestration tools typically produce shared reports and audit logs visible to team members and compliance auditors, but are not inherently collaborative or embedded in public-facing outputs.

Buildability

Confidence 30 · Judged from the description · A multi-warehouse control plane requires integrations with Databricks, Snowflake, BigQuery, and DuckDB APIs, compile-time lineage analysis, governance rule engines, and cost attribution logic—substantial but not research-grade; similar complexity to Dagster or dbt.

Differentiation

Confidence 70 · 5 evidence · Evidence identifies clear gaps that users name: unified multi-warehouse control plane (E7), compile-time column lineage (E3, distinct from post-hoc), cost attribution (E2), and Git-like workflows (E6) that existing tools (Dagster, dbt, warehouse-native governance) do not fully combine.

Retention and timing

Confidence 30 · Judged from the description · Pipeline orchestration and governance are recurring daily workflows for data teams managing sensitive or multi-warehouse environments; timing tailwind includes rising cloud warehouse adoption and compliance pressure, though not a breakout moment.

Risk penalties

Depends on one platformThe product depends on stable, sustained APIs from multiple large cloud providers (Databricks, Snowflake, BigQuery). Changes to their governance, API stability, or competitive positioning (e.g., Databricks adding deeper control-plane features, or Snowflake bundling competing tools) could erode the value proposition.−6
Extreme competitionDagster (backed, $7.2M estimated ARR), dbt Labs (over $100M ARR, now part of $600M combined entity), and warehouse-native governance (Databricks Unity Catalog, Snowflake native masking) are entrenched incumbents with strong developer mindshare and integration depth; market is crowded.−6

Score history

58 · confidence 61 · config v1First score · 29 Oct 2026
47 · confidence 56 · config v1Evidence changed · 30 Oct 2026

Evidence · 16 items

Market validation

Hacker News post received 122 points and 48 comments
Verified
Hacker NewsRetrieved 29 Oct 2026
Existing orchestration and transformation tools (dbt Cloud, Dagster) do not provide the DAG control plane and governance integration that pipeline teams need.
Public claim
Not dbt Cloud — no hosted UI, no managed scheduler. First-class Dagster integration if you need orchestration.
Hacker NewsRetrieved 29 Oct 2026
Multiple warehouse platforms (Databricks, Snowflake, BigQuery, DuckDB) are in production use, but fragmented governance tooling across them.
Public claim
Adapters: Databricks (GA), Snowflake (Beta), BigQuery (Beta), DuckDB (local dev / playground).
Hacker NewsRetrieved 29 Oct 2026

Revenue evidence

Dagster's pricing page lists 2 paid plans, from $10 to $100 a month, plus prices on request for larger customers
Verified
Solo Plan $10 per month · Starter Plan Recommended $100 per month · Pro Plan Contact Sales
dagster.ioRetrieved 29 Oct 2026
dbt (dbt Labs)'s pricing page lists 1 paid plan, at $100 a month, plus a free plan and prices on request for larger customers
Verified
Starter For teams collaborating on their first dbt project. $100 per user/month · Enterprise For organizations scaling data collaboration and governance. Custom pricing · Enterprise+ For complex deployments requiring advanced security and control. Custom Pricing
getdbt.comRetrieved 29 Oct 2026
Fivetran (merged with dbt Labs): about $325M ARR at year end 2024 (2024)
Estimate
By year end 2024, Fivetran was at about $325M ARR
sacra.comRetrieved 30 Oct 2026
Fivetran + dbt Labs combined: nearly $600M ARR combined (merger announcement, Oct 2025)
Estimate
the combined company would have nearly $600M in annual recurring revenue
sacra.comRetrieved 30 Oct 2026
dbt Labs: past $100M ARR (2025)
Estimate
dbt Labs Surges Past $100 Million in Annual Recurring Revenue
sacra.comRetrieved 30 Oct 2026
Fivetran + dbt Labs: all-stock merger completed June 1, 2026 (June 2026)
Public claim
On June 1, 2026, Fivetran and dbt Labs completed an all-stock merger first announced in October 2025.
peliqan.ioRetrieved 30 Oct 2026
Dagster Labs: about $7.2M a year (Growjo estimate, Dec 2023); company has not published revenue (December 2023)
Estimate
at about $7.2M a year (December 2023)
getlatka.comRetrieved 30 Oct 2026

Differentiation

Data teams using cloud warehouses lack a DAG control plane that unifies governance, lineage, and cost attribution across multiple warehouse environments.
Public claim
Rocky owns the graph — dependencies, compile-time types, drift, incremental logic, cost, lineage, governance. The things your current stack can't give you because it doesn't own the DAG.
Hacker NewsRetrieved 29 Oct 2026
Column-level lineage is typically computed post-hoc via graph crawls rather than at compile time, limiting precision and real-time feedback.
Public claim
Column-level lineage from the compiler, not a post-hoc graph crawl. The type checker traces columns through joins, CTEs, and windows.
Hacker NewsRetrieved 29 Oct 2026
Governance features (masking, audit trails, classification) are scattered across warehouse-native tools and lack unified CI gates.
Public claim
Governance as a first-class surface. Column classification tags plus per-env masking policies, applied to the warehouse via Unity Catalog (Databricks) or masking policies (Snowflake). 8-field audit trail on every run. `rocky compliance` rollup that CI can gate on.
Hacker NewsRetrieved 29 Oct 2026
Cost attribution and budget tracking are absent from typical pipeline tools, making cost visibility and control difficult.
Public claim
Cost attribution. Every run produces per-model cost (bytes, duration). `[budget]` blocks in `rocky.toml`; breaches fire a `budget_breach` hook event.
Hacker NewsRetrieved 29 Oct 2026
Teams need Git-like workflows (branches, replay) for pipelines but cannot easily achieve reproducibility and testing in warehouse environments.
Public claim
Branches + replay. `rocky branch create stg` gives you a logical copy of a pipeline's tables (schema-prefix today; native Delta SHALLOW CLONE and Snowflake zero-copy are next). `rocky replay <run_id>` reconstructs which SQL ran against which inputs. Git-grade workflow on a warehouse.
Hacker NewsRetrieved 29 Oct 2026

Retention and timing

Dagster Labs: 2018
Estimate
Founded 2018
getlatka.comRetrieved 30 Oct 2026

DAG control plane for warehouse pipelines

Overview

Build this business

Verdict

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 16 items

Market validation

Revenue evidence

Differentiation

Retention and timing

Market

Existing products

Build

Legal reconstruction check

Community