Starburst Data

This table mixes verified financing facts, company-claimed traction metrics, and one third-party headcount estimate. Exact customer count, cash, debt, gross margin, and profitability remain undisclosed.

Public leadership visibility is good at founder and board-signal level, but the company does not publish a comprehensive live board roster, committee map, or ownership breakdown.

The public record is richer on capital chronology and ecosystem positioning than on hard cap-table economics, concentration, or strategic side-letter terms.

This chronology intentionally combines financing, product, partnership, scale, and adverse-security events because later chapters depend on one consolidated milestone record.

The boundary intentionally includes adjacent federation and lakehouse spend but excludes broad BI and storage categories that would overstate Starburst’s true addressable market.

Rows mix published market reports with explicitly labeled derived estimates used only to bound Starburst’s likely beachhead, not to claim a precise market share figure.

The payer is usually a central platform budget, but the proximate trigger is often a painful local workload that exposes the cost or latency of migration-first architectures.

The table combines analyst-market drivers with practical implementation frictions from review and comparison sources; both matter for adoption speed.

This table prioritizes the rivals most likely to appear in a real Starburst enterprise evaluation rather than an exhaustive list of every data product touching analytics.

Cells summarize fetched product pages and review sources, so they describe positioning and surfaced strengths rather than lab-tested benchmark truth.

Official sources provide clear economic framing for Starburst, Athena, and Databricks, but comparable realized enterprise pricing remains opaque across the category.

Severity is strategic, not existential. The biggest risk is gradual narrowing of differentiation rather than overnight displacement.

Only Galaxy consumption and aggregate AI ARR are explicitly public. The rest are inferred from product packaging, enterprise positioning, and deployment model and therefore require management-room validation.

This table compares monetization framing rather than apples-to-apples price points because realized enterprise rates are private across most of the category.

Public unit economics evidence is unusually strong for revenue quality and unusually weak for cost structure, so the missing margin and CAC data are the main diligence blockers.

The public record supports a view of substantial historical capitalization but not a view of current runway or financing urgency.

These gaps are the critical blockers between a directional public-source narrative and investment-grade financial underwriting.

The matrix separates long-established federation surfaces from newer AI and Iceberg-operating layers.

This table is workflow-based because buyers purchase operational outcomes, not feature lists.

Public architecture evidence is sufficient to map major layers, but not every internal implementation detail.

Trust surfaces are visible, but they shift diligence toward patching discipline, data handling, and vendor dependence.

The roadmap table uses only public releases and announcements, not management promises.

The segment mix is inferred from named references and company disclosures, with financial services the clearest strategic concentration.

Public growth disclosure is unusually helpful for expansion proxies, but still omits customer counts, GRR, and concentration.

The named sample shows real production usage with measurable or clearly described operational outcomes, supplemented by qualitative quotes from additional customers.

Public durability evidence is mostly inferential except for one company-level NDR figure.

The public record supports expansion logic, but not concentration safety.

The fetched record shows visible legal surfaces but not enough contract or audit detail to treat legal risk as fully mitigated.

The main operational risk is not absence of controls, but the ongoing burden of operating them at scale across multiple deployment modes.

Most major Starburst dependencies are strategic assets and strategic risks at the same time.

Execution risk is highest where complex product ambition meets regulated-enterprise delivery expectations.

Kill criteria convert today’s public-source ambiguity into monitorable diligence thresholds.

The summary separates company quality from what the current public record can actually support on price.

The anti-thesis is driven more by evidence gaps and scaling economics than by disbelief in the product.

Scenario logic is intentionally tied to hidden economics and concentration rather than to TAM optimism alone.

Comparable values are contextual anchors, not direct apples-to-apples pricing formulas for Starburst.

These are the minimum asks needed to turn a credible company into a priced investment view.

These triggers convert the risks chapter into valuation discipline.