Web Analytics Made Easy - Statcounter

Dremio vs. Starburst: A Comparative Analysis

by

Table of Contents

1. Report Framing: Context & Scope

 

This report provides a detailed, vendor-agnostic comparison of the Dremio and Starburst data platforms. Both are modern, high-performance SQL query engines designed to operate at the intersection of data lakes, data warehouses, and federated data sources. They are increasingly evaluated as foundational components of an enterprise data lakehouse or as a unified access layer for analytics and AI.

The primary evaluation lens for this report is that of a regulated financial institution, such as a global pension fund or investment bank. This context introduces specific, non-negotiable constraints that heavily influence the analysis. Key evaluation criteria include:

  • Data Federation: The ability to execute queries across a hybrid and multi-cloud environment, including data lakes (e.g., AWS S3, Azure Data Lake Storage), cloud data warehouses (e.g., Snowflake, Microsoft Fabric), and on-premises RDBMS (e.g., Teradata, Oracle).
  • Governance and Security: Robust, native, and verifiable support for fine-grained access control, data masking, and, critically, audibility (e.g., credential pass-through).
  • Data Residency and Sovereignty: Architectural patterns that allow for analysis of data in-place across geopolitical boundaries without requiring physical data movement.
  • Cost Control and TCO: A clear understanding of licensing, compute models, and the total cost of ownership, including operational overhead.

 

2. Executive Summary

 

This report is intended for technical leaders (architects, engineering leads) and senior executives (VPs, C-level) to inform a strategic technology decision.

 

Platform Overviews

 

Dremio positions itself as the “Agentic Lakehouse” 1, a unified and high-performance platform for self-service analytics and AI. Its architecture is built from the ground up on Apache Arrow for highly efficient, in-memory columnar processing.2 Dremio’s strategy centers on three pillars: a high-performance SQL engine, a “Zero-ETL” data federation capability, and an AI-powered semantic layer.1 Its most significant differentiator is “Data Reflections,” a query acceleration technology that functions as a transparent, automatically rewritten materialized view, designed to deliver sub-second BI performance directly from data lake storage.4 Dremio has a deep, native integration with open table formats, particularly Apache Iceberg and the “Git-for-data” catalog Project Nessie.6

Starburst is the commercial enterprise platform from the original creators of Trino (formerly PrestoSQL).7 It is a mature, battle-tested, massively parallel processing (MPP) federated query engine.9 Starburst’s core value proposition is “flexibility”—providing a single, secure point of access and a “single source of truth” for analytics on data wherever it lives.7 Its primary identity is that of a “query-anything-anywhere” engine, enabling complex, high-performance federated queries across dozens of connectors (e.g., on-prem, cloud, lake, warehouse) without data movement.10 It is strategically open and neutral, with first-class support for all major open table formats, including Apache Iceberg, Delta Lake, and Hudi.12

 

At-a-Glance Comparison

 

  • Key Similarities
  • Both are distributed SQL query engines built on the principle of separating compute and storage.
  • Both offer fully managed SaaS (Dremio Cloud, Starburst Galaxy) and self-managed, Kubernetes-based (Dremio Software, Starburst Enterprise) deployment models.
  • Both provide a single point of SQL access to federate queries across multiple data sources.
  • Both integrate with standard BI (Tableau, Power BI), data engineering (dbt, Airflow), and AI/ML (Python) tools.
  • Both provide native, fine-grained access control (row-level and column-level security).
  • Key Differences
  • Core Engine: Dremio is built on Apache Arrow for in-memory, vectorized processing.2 Starburst is built on the Java-based Trino MPP engine.15
  • Primary Acceleration: Dremio’s main accelerator is Reflections (automatic materialized views with query rewrite).4 Starburst’s main accelerator is its CBO and deep query pushdown into source databases.16
  • Federation Focus: Starburst’s core identity is its breadth and depth of federation, with 50+ connectors and granular pushdown.11 Dremio’s core identity is its integrated lakehouse platform; federation is a supporting feature.
  • Lakehouse Formats: Dremio is opinionated and deep on Apache Iceberg and Project Nessie.6 Starburst is neutral and broad, supporting Iceberg, Delta Lake, and Hudi as first-class citizens.12
  • Governance Features: Starburst has heavily marketed and customer-validated features for complex federated governance, such as credential pass-through and user impersonation, which are critical for auditing in financial services.17
  • Compliance: Dremio publicly advertises SOC 2 Type 2 and ISO 27001 certifications.19 Starburst’s public materials focus on solving compliance problems (like sovereignty) 21, but its platform certifications are not as prominently advertised and must be explicitly verified.
  • Where Dremio is Likely Stronger / More Appropriate
  • BI & Dashboard Acceleration: For organizations whose primary goal is accelerating BI tools (Tableau, Power BI) on a data lake, Dremio’s transparent Reflections 5 provide a simple, powerful, and often “set-it-and-forget-it” performance layer.
  • Unified Iceberg Lakehouse Management: For organizations standardizing on Apache Iceberg, Dremio’s native Nessie-based catalog (Dremio Arctic) 22 offers a complete, “Git-for-data” platform for both querying and managing the lakehouse.
  • Raw Performance (Lakehouse-only): The Apache Arrow-based engine is designed from the ground up for high-speed, in-memory, columnar-native analytics, which Dremio claims gives it a raw performance edge for queries on lake data.23
  • Where Starburst is Likely Stronger / More Appropriate
  • Complex, Hybrid-Cloud Federation: For organizations with a complex, heterogeneous data landscape (e.g., on-prem Teradata + AWS S3 + Azure Fabric + Snowflake), Starburst’s broad connector library 11 and powerful CBO/pushdown engine 16 are unmatched.
  • Data Sovereignty & Residency: Starburst’s query pushdown architecture is purpose-built to query data in-place, allowing analysis across geopolitical borders without physically moving the data, a key requirement for financial services.24
  • Strict Federated Governance & Audit: Starburst’s support for credential pass-through and user impersonation 17 is a critical, and reportedly decisive, feature for regulated industries needing to audit data access at the source.
  • Ecosystem Neutrality: In environments with a mix of Databricks (Delta Lake) and other platforms, Starburst’s first-class support for Delta 12 makes it a more flexible federator than the Iceberg-centric Dremio.

 

Recommendation Scenarios

 

This decision is not about which platform is “better,” but which architecture is right for the organization’s primary challenge.

  1. Scenario: “The Modern Lakehouse BI Platform”
  • Profile: The organization’s primary goal is to build a new, high-performance, self-service analytics platform on the data lake (e.g., S3, ADLS). The main use case is accelerating BI dashboards for internal analysts, and the organization is standardizing on Apache Iceberg.
  • Recommendation: Lean Dremio. The combination of its high-speed Arrow engine, integrated semantic layer 3, and (most importantly) the automatic, transparent query acceleration from Data Reflections 5 is purpose-built for this “lakehouse-first” BI use case.
  1. Scenario: “The Governed Federated Enterprise”
  • Profile: A large, global institution with significant, high-value data in on-prem legacy systems (e.g., Teradata, Oracle), multiple cloud warehouses (e.g., Snowflake, Redshift), and a growing data lake. The primary challenge is governed, federated reporting across these silos while respecting data residency and auditability.
  • Recommendation: Lean Starburst. The platform’s architectural focus is built for this exact problem. Its unmatched federation breadth 11, deep query pushdown CBO 16, and specific, finance-validated governance features (credential pass-through 17, data sovereignty-by-design 24) are the clear differentiators.
  1. Scenario: “The Databricks Co-Pilot”
  • Profile: The organization is already heavily invested in the Databricks ecosystem and uses Delta Lake as its primary table format. The need is for a high-performance federated engine to query both the Delta Lake and other satellite sources (e.g., on-prem SQL Server).
  • Recommendation: Lean Starburst. Starburst’s explicit, first-class support for Delta Lake 12 makes it a more natural federated query partner than Dremio, which is architecturally and strategically centered on Apache Iceberg.

 

3. Vendor & Product Overview

 

Dremio

 

  • Company Background: Dremio was founded in 2015 25 and is headquartered in Santa Clara, California. Its co-founders were instrumental in the creation of Apache Arrow 1, a technology that is foundational to Dremio’s architecture.
  • Core Products: Dremio offers two primary products that share the same core engine 27:
  1. Dremio Cloud: A fully-managed SaaS platform.28 It simplifies operations by handling all infrastructure management, automatic scaling, and zero-dime-to-value.27 For security and data residency, its execution engines are deployed within the customer’s own cloud environment (VPC/VNet).28
  2. Dremio Software: A self-managed, enterprise-grade offering designed for Kubernetes-based deployment. This allows for full control and can be deployed on-premises or in any public or private cloud (AWS, Azure, GCP).27
  • Strategic Positioning: Dremio is strategically positioned as the “Agentic Lakehouse,” a platform for both human-led analytics and AI agents.1 Its strategy rests on three pillars: 1) Zero-ETL Federation for unified access, 2) an AI-enabled Semantic Layer for business context 3, and 3) Autonomous Optimization via its high-speed Arrow engine and Data Reflections. Dremio is strategically and deeply invested in Apache Iceberg and Project Nessie, promoting this combination as the open standard for modern, “data-as-code” lakehouse management.6

 

Starburst

 

  • Company Background: Starburst was founded in 2017 33 by the team that created Presto at Facebook. After leaving Facebook, the founders (Martin Traverso, Dain Sundstrom, David Phillips, and Eric Hwang) forked the open-source Presto project (PrestoDB, still controlled by Facebook/Meta) to create PrestoSQL, which was later renamed Trino to avoid confusion.7 Starburst is the enterprise company built around the Trino open-source project and is its primary developer, contributing the vast majority of its advancements.36
  • Core Products: Starburst also offers two primary products:
  1. Starburst Galaxy: The fully-managed SaaS platform, built on Trino.10 It is available on all major cloud providers (AWS, Azure, GCP) and abstracts away all cluster management.
  2. Starburst Enterprise (SEP): The self-managed, enterprise-grade distribution of Trino.10 SEP includes additional features not in the open-source version, such as a large library of enterprise connectors, enhanced security and governance features, and performance optimizations like Warp Speed.8
  • Strategic Positioning: Starburst’s strategy is federation-first. It is positioned as the single point of access to all of an organization’s data, regardless of location.7 It is not just a lakehouse engine; it is the universal query layer that connects the lakehouse (in any format) to all other data sources (warehouses, RDBMS, SaaS).39 Its positioning is built on openness, flexibility, and neutrality, particularly regarding table formats (Iceberg, Delta, Hudi are all supported).12

 

Competitive Landscape Snapshot

 

  • Cloud Data Warehouses (Snowflake, BigQuery): These are closed, proprietary systems that co-locate compute and storage (or use proprietary storage formats). Dremio and Starburst compete against them by offering an open, flexible architecture that separates compute from open, low-cost object storage, eliminating vendor lock-in and allowing for querying of data outside the warehouse.41
  • Lakehouse Platforms (Databricks): Databricks is a comprehensive, all-in-one platform for data engineering (Spark), AI/ML, and SQL analytics.43 Dremio and Starburst compete with its Databricks SQL offering, positioning themselves as more “best-of-breed” SQL engines with superior federation capabilities and a more open, non-proprietary SQL layer.41
  • Data Virtualization (Denodo): Denodo is the traditional leader in data virtualization.44 Dremio and Starburst are differentiated by their MPP, high-performance query engines designed for massive-scale analytics (petabytes), whereas traditional virtualization tools were often built for lighter-weight, schema-heavy data integration.45
  • Trino OSS: Starburst’s closest competitor is its own open-source foundation. Starburst Enterprise adds crucial enterprise-grade features, including security, governance, 24/7 support, and performance-enhanced connectors that are not available in Trino OSS.8

 

4. Technical Architecture & Design

 

This section details the core engines, data models, and optimization strategies, which represent the most significant technical differences between the two platforms.

 

Dremio: Apache Arrow & Reflections

 

Core Engine Architecture

 

Dremio’s architecture is a distributed system composed of Coordinator nodes and Executor nodes.49 Coordinators handle client requests, parse SQL, optimize queries, and manage metadata. Executors are responsible for the actual execution of query fragments.49

The engine’s foundation is Apache Arrow.2 Dremio’s co-founders were co-creators of Arrow, and the engine is built to use it natively.1 Arrow is a language-independent, in-memory columnar data format. By using Arrow as its internal processing format, the Dremio engine achieves:

  1. Zero Serialization/Deserialization: When reading columnar formats like Parquet, data can be loaded directly into Arrow in-memory buffers without a costly conversion.
  2. Efficient Data Exchange: Data is exchanged between executor nodes in the efficient Arrow format, eliminating CPU overhead.50
  3. Vectorized Execution: This design enables modern, CPU-efficient vectorized processing (SIMD), which processes data in batches (vectors) rather than row by row.51

Dremio claims this Arrow-native design provides a fundamental raw performance advantage over traditional Java-based engines like Trino.23

 

Storage and Data Model

 

Dremio’s strategy is a deep, opinionated bet on Apache Iceberg as the premier open table format.3 While it can query other sources, its data lakehouse management capabilities are centered on Iceberg and Project Nessie.6

Nessie is an Iceberg catalog that provides “Git-like” data management.6 It replaces a traditional Hive Metastore and adds transactional capabilities, allowing data engineers to use:

  • Branches: Create isolated “work” branches to experiment with data or run ETL jobs without affecting production.52
  • Commits: Perform atomic, multi-table updates (e.g., INSERT to one table and UPDATE another in a single transaction).
  • Merges: Atomically promote changes from a dev branch to the main branch.

Dremio’s managed catalog, Dremio Arctic, is a service built on Project Nessie, providing these data-as-code capabilities in a user-friendly package.18

 

Connectors and Data Federation

 

Dremio supports a wide range of sources, including lakehouse catalogs (Glue, Nessie, Unity), object storage, and databases (RDBMS, Snowflake, etc.).32

For relational sources, Dremio can push down some query operations.54 It also features an “External Query” capability.55 This allows users to wrap a native SQL SELECT statement (in the source’s dialect, e.g., Snowflake SQL) and have Dremio pass it directly to the source database for execution.55 This is a pass-through mechanism, useful for complex operations Dremio cannot parse, but it is less sophisticated than a CBO-driven, granular pushdown of individual operations within a larger federated query.

 

Performance and Optimization

 

Dremio’s performance strategy is multi-layered, with its flagship feature being Data Reflections.

  1. Data Reflections: A Reflection is a precomputed, optimized physical data structure (e.g., a materialized view) that Dremio creates and manages, stored as an Iceberg table.4 There are two main types 57:
  • Raw Reflections: Optimized copies of the source data (e.g., different sort/partition, columnarized).
  • Aggregation Reflections: Pre-aggregated data (e.g., GROUP BYs, SUMs) for dashboards.

The single most important feature of Reflections is Dremio’s CBO-driven transparent query rewrite.4 A user can write a simple SQL query against a 100TB raw table, and Dremio’s optimizer will automatically and transparently rewrite that query to use a 10MB Aggregation Reflection, returning the result in sub-seconds. Autonomous Reflections 5 extend this by analyzing query patterns to automatically create, refresh, and drop Reflections, aiming for a zero-maintenance experience.

  1. Columnar Cloud Cache (C3): This is a separate mechanism. C3 is a disk-based cache on the executor nodes (e.g., using local NVMe drives) that caches raw data blocks from remote object storage like S3.49 This accelerates queries that miss a Reflection, by avoiding repeated, high-latency S3 GET requests.

 

Query Flow (Narrative Example)

 

A BI tool sends a SQL query for “monthly sales by region” to Dremio (1). The Dremio Coordinator parses the query (2). The Cost-Based Optimizer (CBO) analyzes the query and checks its metadata catalogs (3). It determines that this query can be satisfied by an existing Aggregation Reflection (4). The CBO transparently rewrites the query to read from the small, pre-computed Reflection instead of the 10TB raw sales table (5). The execution plan is sent to the Executors (6). The Executors (which may already have the Reflection data on their local C3 cache) read the data into Apache Arrow in-memory buffers (7). The query is processed in-memory using Arrow’s vectorized engine (8). A sub-second result is returned to the BI tool (9).

 

Starburst: Trino MPP & Federation

 

Core Engine Architecture

 

Starburst’s architecture is the Trino architecture: a classic, distributed Massively Parallel Processing (MPP) SQL query engine.10 It consists of two node types:

  • Coordinator: A single node per cluster that manages parsing, planning, and scheduling. It parses the SQL, uses the CBO to create a distributed query plan, and assigns tasks to Workers.10
  • Workers: A large cluster of nodes that execute tasks in parallel. They pull data from data sources (via connectors) and exchange data with each other to complete stages of the query.10

A key recent enhancement to this architecture is Fault-Tolerant Execution (FTE).60 This (known as Project Tardigrade in Trino) allows workers to spill intermediate data to disk, enabling query retries and handling large-scale ETL/batch jobs that would otherwise fail or exhaust memory.

 

Storage and Data Model

 

Starburst’s storage strategy is neutrality and openness.12 It does not have its own “native” catalog or table format. Instead, it provides first-class, high-performance connectors for all three major open table formats:

  • Apache Iceberg
  • Delta Lake 62
  • Apache Hudi

This neutrality is a key strategic difference from Dremio. It makes Starburst an ideal federated engine for organizations that have a heterogeneous data lake, such as an existing Databricks (Delta Lake) environment that needs to be queried alongside a new Iceberg-based one.12

 

Connectors and Data Federation

 

This is Starburst’s core strength. The platform includes over 50 enterprise-grade connectors.11 The power lies not just in the number of connectors, but in their depth. The Starburst Cost-Based Optimizer (CBO) has deep, semantic knowledge of each connector’s capabilities.63

This enables sophisticated, granular query pushdown.16 When Starburst receives a federated query, the CBO analyzes it and pushes down as much of the computation as possible to the source databases:

  • Predicate Pushdown: WHERE clauses are sent to the source.
  • Aggregation Pushdown: GROUP BY, SUM(), COUNT() operations are sent to the source.
  • Join Pushdown: Joins between two tables in the same source are pushed to the source.
  • Limit / Top-N Pushdown: ORDER BY… LIMIT N clauses are pushed down.

This pushdown is critical for performance (reducing network data transfer) and, for financial services, for governance and data residency. By pushing computation to the data, Starburst can analyze data across geographies without physically moving it.21

 

Performance and Optimization

 

  1. CBO and Query Pushdown: This is the primary optimization.16 Its effectiveness is highly dependent on table statistics.11 This implies an operational requirement to run ANALYZE or similar commands to keep statistics up-to-date, which the CBO relies on for optimal plan generation.
  2. Starburst Warp Speed: A caching and indexing layer.8 It asynchronously creates indexes and caches frequently accessed data on the local storage (e.g., NVMe) of the worker nodes, similar in concept (though not implementation) to Dremio’s C3 cache.
  3. Materialized Views: Starburst also supports materialized views.23 However, a critical point of comparison is that Starburst’s MVs historically have not supported transparent, automatic query rewrite. This means users must be aware of the MV and query it directly. This presents a significant usability and maintenance disadvantage compared to Dremio’s Reflections. This is a critical point to validate in any proof-of-concept.

 

Query Flow (Narrative Example)

 

A BI tool sends a SQL query to Starburst, joining an on-prem Teradata table (in London) with a Snowflake table (in Azure) (1). The Starburst Coordinator parses the query (2). The CBO analyzes the distributed query plan (3). It splits the plan: it pushes the WHERE clause and an aggregation for the Teradata table down to the Teradata connector (4), which sends that partial query to the Teradata database in London (5). Simultaneously, it pushes the WHERE clause for the Snowflake table to the Snowflake connector (4), which executes it in Azure (5). The source databases (Teradata, Snowflake) execute their partial queries on their own hardware (6). A minimized result set from each (e.g., a few thousand rows, not billions) is returned to the Starburst Workers (7). The Workers perform the final federated join in parallel (8). The result is sent to the Coordinator and back to the user (9).

 

5. Deployment, Operations, and Scalability

 

Dremio

 

  • Deployment Models:
  • Dremio Cloud: A fully managed SaaS, primarily on AWS (with Azure in preview).27 It uses a hybrid-VPC model where the control plane is Dremio-managed, but the execution plane (engines) deploys into the customer’s AWS account.28 This is a strong architecture for security and data residency.
  • Dremio Software: A self-managed deployment that requires Kubernetes.27 It can be deployed on-premises or in any cloud (AWS, Azure, GCP).27
  • Scalability & Elasticity:
  • Dremio Cloud provides auto-scaling and zero-downtime upgrades.27
  • Dremio Software relies on manual scaling via Kubernetes configurations.27
  • Dremio provides workload isolation through “Engines,” which are user-defined groups of executors. This allows an organization to create separate compute clusters (e.g., for “BI” vs. “Data Science”) that share the same catalog, isolating workloads and managing costs.49
  • Operational Tooling:
  • Dremio provides query history, logs, and metrics. The self-managed version integrates with standard stacks like Prometheus.
  • The primary operational overhead for Dremio is managing the refresh and storage costs of Reflections. The Autonomous Reflections feature 5 is designed to minimize this, but it is still a consideration.

 

Starburst

 

  • Deployment Models:
  • Starburst Galaxy: A fully managed SaaS available on all three major cloud providers (AWS, Azure, GCP).10
  • Starburst Enterprise (SEP): A self-managed deployment with more flexibility. It supports Kubernetes but can also be deployed on bare metal or VMs using Ansible.10
  • Scalability & Elasticity:
  • Galaxy provides auto-scaling.
  • SEP scales horizontally by adding more Worker nodes to the Trino cluster.10 It supports multi-cluster, multi-tenant setups and uses resource groups for fine-grained workload management, queuing, and concurrency controls.47
  • Operational Tooling:
  • SEP provides detailed query history, audit logs 68, and metrics, integrating with standard enterprise monitoring tools.
  • The primary operational overhead for Starburst is maintaining the table statistics required by the CBO.64 This often involves scheduling ANALYZE jobs to run on key tables to ensure the optimizer can generate efficient query plans.

 

6. Governance, Security, and Compliance

 

For a regulated financial institution, this section is paramount. A failure in governance, audit, or compliance is a non-starter.

 

Authentication & Authorization

 

Both platforms provide robust, enterprise-grade authentication and authorization:

  • Dremio: Integrates with IdPs via SAML, OIDC, and LDAP, and provides native Role-Based Access Control (RBAC).19
  • Starburst: Integrates with IdPs via LDAP, Kerberos, and OAuth, and provides native RBAC.10

 

Fine-Grained Access Control (FGAC)

 

Both platforms provide strong, native FGAC capabilities:

  • Dremio: Implements native row-level and column-level security.19 These security policies are defined as SQL User-Defined Functions (UDFs) (e.g., CASE WHEN is_member(‘finance’) THEN ssn ELSE ‘REDACTED’ END). These UDFs are applied at query planning time.74
  • Starburst: Implements native row filters and column masks.75 It also supports Attribute-Based Access Control (ABAC), a more flexible model that allows policies to be based on metadata tags (e.g., “Allow ‘Finance’ role to see all columns tagged ‘PII'”).10

A key architectural difference is in Starburst’s execution: Row filters are appended to the query and pushed down to the source database, while column masks are applied by the Starburst engine after data is returned.77 Pushing row-level security down to the source is highly efficient and secure.

 

Data Governance

 

  • Dremio: Features an integrated semantic layer 3 and data lineage capabilities.80 It also integrates with external governance platforms like Apache Ranger and Privacera.19
  • Starburst: Provides deep integrations with all major governance platforms, including Apache Ranger, Immuta, and Privacera.10

A critical differentiator for federated governance, as cited in a customer testimonial, is Starburst’s mature implementation of credential pass-through and user impersonation on sources like Teradata.17 This allows an audit log at the source database to show the end user’s ID, not a generic service account—a fundamental requirement for many financial audit and compliance bodies.

 

Security & Compliance (The Decisive Factor)

 

This is where the two platforms show markedly different strengths:

  • Dremio (Platform Certification):
  • Certifications: Dremio provides clear, publicly-advertised compliance certifications, including SOC 2 Type 2, ISO 27001, and HIPAA-ready status.19 For a procurement process, these verifiable, third-party audits are a significant strength.
  • Data Residency: Dremio’s Cloud architecture, which runs the execution plane in the customer’s VPC, is explicitly designed to solve data residency by keeping data and processing within the customer’s secure boundary.19
  • Encryption: Provides full end-to-end encryption (at-rest and in-transit).19
  • Starburst (Federation & Governance Certification):
  • Certifications: The provided research does not highlight SOC 2 or ISO 27001 certifications for Starburst. While the company discusses building compliant architectures for financial services 21, the lack of easily-verifiable platform certifications is a gap that must be addressed in an RFP.
  • Data Residency: This is Starburst’s core architectural strength. Its query pushdown model is designed to solve data sovereignty.21 It allows a query to be run from New York that joins data in-place in London and Frankfurt, with only the final, aggregated (and often anonymized) result returning. No sensitive data is moved or copied across borders.
  • Auditability: Starburst provides detailed, native audit logging 68 and the previously mentioned credential pass-through 17, which together create a powerful and auditable governance framework for a complex, federated estate.

The choice presents a key trade-off: Dremio offers a platform that is verifiably secure (via SOC 2, ISO). Starburst offers an architecture that is purpose-built to solve complex, multi-jurisdictional federated governance and data sovereignty challenges.

 

7. Ecosystem, Integrations, and Developer Experience

 

BI & Analytics Integrations

 

Both platforms provide standard and robust JDBC/ODBC connectors for all major BI tools, including Power BI, Tableau, and Looker.86

Dremio’s key differentiator in this category is its built-in Semantic Layer.3 This allows data teams to define business logic, calculations, and friendly names in a single, governed layer within Dremio. All BI tools then connect to this semantic layer, ensuring consistency and accelerating self-service analytics.

 

Data Engineering & DevOps

 

Both Dremio and Starburst are first-class citizens of the modern data stack and integrate cleanly with standard data engineering and DevOps workflows.

  • dbt (data build tool): Both have dedicated adapters for building and managing data transformations. Dremio is supported via the dbt-dremio adapter.92 Starburst is supported via the mature, widely-used dbt-trino adapter.71
  • Orchestration (Airflow): Both integrate with Apache Airflow. Dremio has a provider package and can be called via Python.97 Starburst/Trino has a mature TrinoOperator and hook that integrates directly with Airflow, including leveraging the Fault-Tolerant Execution mode for reliable ETL.61

 

AI/ML and Advanced Analytics

 

Both platforms position themselves as the ideal data access layer for machine learning and AI workloads.

  • Dremio: Dremio’s primary story for AI/ML is speed. It promotes Apache Arrow Flight 2, an ultra-high-speed data transfer protocol, for moving data from Dremio to Python notebooks (Pandas, PyTorch) with extreme efficiency. Its Nessie integration is also a strong value proposition for model reproducibility, allowing data versions to be tagged and managed alongside model versions.103
  • Starburst: Starburst’s value is its ability to federate all the disparate data sources needed for feature engineering.104 It provides direct integrations with ML platforms like Amazon SageMaker, Google Cloud Vertex AI, and others.105 Starburst is also actively embedding AI functions, such as vector search capabilities, into its engine 107 and positioning itself as the governed data-serving layer for RAG (Retrieval-Augmented Generation) LLM applications.108

 

8. Pricing, Licensing, and TCO

 

Exact pricing is vendor-confidential. This section explains the pricing models and key cost drivers.

 

Dremio Pricing Model

 

  • Dremio Cloud: Billed via a consumption-based model. The primary unit of cost is the Dremio Compute Unit (DCU), which is consumed as queries execute.27 A free tier is available for initial use.110
  • Dremio Enterprise (Self-Managed): Also a consumption-based model, but licensing is customized. Requires contacting sales.27
  • TCO Factors: Dremio’s primary TCO argument is one of efficiency.23 The claim is that its high-performance Arrow engine, combined with the query acceleration from Reflections, results in queries finishing faster. This means less compute time is used, leading to fewer DCUs consumed and a lower overall bill for the same amount of work. TCO calculations must also include the compute and object storage costs associated with refreshing and storing Reflections.111

 

Starburst Pricing Model

 

  • Starburst Galaxy (SaaS): Also a consumption-based model. The primary unit of cost is the “credit,” a universal unit of compute.112
  • Starburst Enterprise (Self-Managed): Licensing is customized and requires contacting sales.
  • TCO Factors: Starburst’s primary TCO argument is based on avoiding data movement. By querying data in-place via federation, organizations save on:
  1. Data Egress Costs: No massive, expensive data transfers between clouds or from on-prem.17
  2. Storage Costs: Eliminates the need for redundant, stale copies of data.
  3. ETL Pipeline Costs: Reduces the need for complex pipelines that just copy and move data.
    A key nuance in Starburst Galaxy’s pricing is its tiered credit model.113 The price per credit increases as you move up tiers (e.g., Pro at $0.50/credit, Enterprise at $0.75/credit, Mission-Critical at $1.00/credit). Since features like advanced governance (ABAC) or private links are only available in higher tiers, this means using advanced features will increase the compute cost for all queries.113

 

Pricing & TCO Model Comparison

 

Capability Dremio Starburst
SaaS Product Dremio Cloud 27 Starburst Galaxy 10
Self-Managed Product Dremio Software 27 Starburst Enterprise 10
SaaS Billing Model Consumption-Based 27 Consumption-Based 113
SaaS Core Unit Dremio Compute Unit (DCU) 27 Credit 112
SaaS Tiered Cost Not specified (single tier) Yes, price-per-credit increases with feature tier 113
Primary Cost Drivers Compute (DCUs), Reflection storage/refresh 111 Compute (Credits), Data Ingest, PrivateLink 114
Primary TCO Argument Performance Efficiency: Faster engine (Arrow) + Reflections = less compute used per query.23 Federation Efficiency: No data movement = zero egress costs and no data duplication.17

 

9. Use Cases and Patterns (with a financial-services lens)

 

Core Analytics Use Cases

 

  • BI and Dashboard Acceleration: This is Dremio’s core value proposition.3 The FactSet case study highlights a 20x acceleration in data access for their financial analytics applications.115
  • Federated Reporting: This is Starburst’s core value. It excels at providing a single, federated view for reporting across disparate systems like Snowflake, Microsoft Fabric, and on-prem RDBMS.24
  • Ad Hoc Analytics: Both platforms empower ad hoc queries. Starburst’s “query-anything” model is particularly powerful for quants and portfolio analysts who need to explore and join new, disparate datasets without waiting for engineering.

 

AI/ML Use Cases

 

  • Unified Data Access for Feature Engineering: Both Dremio and Starburst can serve as a unified, governed access layer for ML platforms (SageMaker, Vertex AI).103 Data scientists can access a consistent, governed view of data for feature engineering without needing to understand the complex underlying sources.
  • RAG / LLM Use Cases: Starburst is actively positioning itself as the ideal data-serving layer for Retrieval-Augmented Generation (RAG) models, providing governed, secure SQL access for LLM agents to query enterprise data.108

 

Financial-Services Specific Concerns

 

  • Anti-Money Laundering (AML) & Fraud: Starburst has a very strong, public-facing case study with a global investment bank specifically for AML.116 They use Starburst Enterprise to federate queries across petabytes of data in multiple global warehouses.116 This allows their data science teams to rapidly test and update ML fraud detection models and gives investigators real-time access to federated data, dramatically reducing false positives and improving detection.116
  • Data Residency and Cross-Border Data Access: This is a primary concern for global funds.
  • Starburst solves this via architecture: its query pushdown model allows an analyst in one region to run a query that executes on data in situ in another region, with only the final, aggregated result returning. No sensitive raw data crosses the border.21
  • Dremio solves this via deployment: its Dremio Cloud architecture runs the execution plane within the customer’s local VPC 28, ensuring that data processing physically occurs within that region.19
  • Strict Auditability and Lineage:
  • Dremio provides data lineage 80 and audit logging.118
  • Starburst provides explicit audit logs 68 and, critically, federated governance features like credential pass-through 17, which are essential for maintaining a clear, end-to-end audit trail in a multi-system environment.

 

Illustrative Reference Architectures (Narrative)

 

  • Illustrative Architecture 1: Dremio (The Lakehouse Acceleration Pattern)
    A financial institution’s BI team is struggling with slow Power BI dashboards connected to a large Parquet-based data lake on AWS S3. They deploy Dremio Cloud. The Dremio execution plane deploys into their existing AWS VPC.28 They connect Dremio to their AWS Glue catalog and an on-prem Oracle database.53 Dremio’s Autonomous Reflections 5 analyze the slow dashboard queries and automatically create several Aggregation Reflections, stored as Iceberg tables in S3.56 The BI team’s queries, which are not modified, are transparently rewritten by Dremio to hit these Reflections. Query times drop from 2 minutes to 3 seconds. The security team uses Dremio’s native row-level policies 74 to ensure analysts can only see data for their specific funds.
  • Illustrative Architecture 2: Starburst (The Federated Governance Pattern)
    A global pension fund’s risk management team needs a single, real-time view of market exposure. This data is fragmented: 1) legacy holdings in an on-prem Teradata warehouse (Europe), 2) market data in Snowflake (US), and 3) new trade history in an S3 data lake (Asia).24 Moving this data daily is slow, costly, and violates data residency rules. They deploy Starburst Enterprise.10 The risk analyst runs a single SQL query from their New York office. Starburst’s CBO 64 pushes the Teradata part of the query down to the Teradata cluster in Europe 16, the Snowflake part down to Snowflake, and executes the S3 part on its own workers. Critically, user impersonation 17 is used, so the Teradata and Snowflake audit logs show the analyst’s credentials, not a generic service account. The data is joined in-memory by Starburst workers, and the final risk report is returned to the analyst in minutes, not days. No raw data was moved across borders.

 

10. Broader Competitive Context

 

  • vs. Databricks: Databricks is a comprehensive, all-in-one platform for data engineering (Spark), AI/ML, and SQL.43 Dremio and Starburst compete as more “best-of-breed,” open SQL engines focused on federation and BI, arguing for a more flexible, multi-vendor architecture over Databricks’ (increasingly open but still) integrated ecosystem.41
  • vs. Snowflake: Snowflake is a highly successful cloud data warehouse “walled garden.” Dremio and Starburst are the “anti-lock-in” alternative, built on open formats and open storage.41 They can also federate Snowflake, querying it as just one of many sources alongside data outside the warehouse (e.g., on-prem RDBMS), which Snowflake itself struggles to do.
  • vs. Denodo: Denodo is the traditional market leader in data virtualization.44 Dremio and Starburst compete by offering a modern, MPP-based engine built for high-performance, petabyte-scale analytics, not just the lighter-weight, schema-heavy data integration Denodo was historically known for.45
  • vs. Trino OSS: Starburst’s primary open-source alternative is Trino.47 Starburst provides enterprise-grade enhancements, including 24/7 support, enhanced security, more stable and performant connectors, and performance boosts like Warp Speed.8

 

11. Pros, Cons, and Risks

 

Dremio

 

  • Strengths (Pros):
  • Best-in-Class BI Acceleration: Data Reflections are a powerful, easy-to-use acceleration layer. The transparent, automatic query rewrite 4 is a major usability and performance advantage.119
  • High-Performance Core Engine: The Apache Arrow-native engine is built from the ground up for high-speed, in-memory, vectorized processing.2
  • Unified Lakehouse Management: Deep, native support for Apache Iceberg and Project Nessie provides a powerful, “Git-like” data management and transaction framework.6
  • Integrated Semantic Layer: Provides a consistent, governed business view for all BI tools.3
  • Verifiable Platform Compliance: Public, third-party compliance certifications (SOC 2 Type 2, ISO 27001) are a significant asset for procurement.19
  • Weaknesses (Cons):
  • Federation capabilities, while present, are not as broad or deep as Starburst’s.17
  • The “External Query” pushdown logic 55 is a pass-through, which may be less sophisticated and less performant than Starburst’s CBO-driven granular pushdown.
  • Highly “opinionated” on Apache Iceberg, which becomes a con if the organization is standardized on or has a large investment in Delta Lake.
  • Risks:
  • Vendor lock-in to Dremio-specific features (Reflections, Arctic/Nessie) that are not easily portable to other engines.
  • The Dremio Cloud SaaS offering is younger than some competitors, having launched in 2022.120

 

Starburst

 

  • Strengths (Pros):
  • Best-in-Class Federation: Unmatched breadth (50+ connectors) 11 and architectural depth.
  • Superior Query Pushdown: The CBO-driven, granular pushdown of predicates, joins, and aggregations 16 is a core architectural strength for performance and governance.
  • Mature Fin-Serve Governance: Specific, customer-validated features like credential pass-through, user impersonation, and data sovereignty-by-design are purpose-built for regulated industries.17
  • Open Format Neutrality: First-class, equivalent support for Iceberg, Delta Lake, and Hudi 12 provides maximum flexibility.
  • Mature Ecosystem: Built on the battle-tested, widely adopted Trino engine.7
  • Proven Use Cases: Strong, public case studies for high-stakes financial services (AML).116
  • Weaknesses (Cons):
  • Acceleration is more complex. The platform relies heavily on CBO statistics 64, which adds operational overhead (running ANALYZE jobs).
  • The lack of automatic query rewrite for materialized views 23 is a significant usability and maintenance disadvantage compared to Dremio’s Reflections. This makes MVs a developer-only feature, not a self-service accelerator.
  • Risks:
  • Compliance Certification Gap: The lack of clearly advertised SOC 2 / ISO 27001 certifications in the researched materials 84 is a major risk that must be clarified and verified during procurement.
  • Cost Predictability: The tiered pricing model for Starburst Galaxy 113 (where features increase the per-credit cost) and the potential for complex, runaway federated queries could lead to unpredictable TCO.122

 

12. Comparative Tables and Decision Framework

 

Feature Comparison Matrix

 

Feature Dremio Starburst
Core Engine Apache Arrow (Vectorized) 2 Trino (MPP) 15
Primary Acceleration Data Reflections (Materialization) 4 CBO + Query Pushdown 16
Automatic Query Rewrite Yes (for Reflections) 4 No (for MVs, per Dremio claim) 23
Open Table Formats Iceberg (Native) 3, Delta (Read) Iceberg, Delta Lake, Hudi 12
Data-as-Code (Git) Yes (via native Nessie/Arctic) 6 No (Catalog-only)
Federation Breadth Good 53 Excellent (50+ connectors) 11
Query Pushdown Fair (External Query pass-through) 55 Excellent (Granular CBO-driven) 16
Built-in Semantic Layer Yes 3 No (via BI tools or partners)
Governance (Native) RBAC, Row/Column Policies (UDF) 74 RBAC, ABAC, Row Filters, Column Masks 77
SaaS Model Dremio Cloud 27 Starburst Galaxy 10
Compliance Certs Yes (SOC 2, ISO 27001) 20 Verification Required

 

Decision Matrix (Financial Institution Context)

 

Evaluation Criteria Dremio Starburst Justification
Federation (Hybrid/Multi-Cloud) Fair Excellent Starburst’s architecture, CBO, and 50+ connectors are purpose-built for complex federation.11
Governance (Granularity & Audit) Good Excellent Starburst’s support for credential pass-through and user impersonation is a decisive, audit-critical feature.17
Data Sovereignty/Residency Good Excellent Starburst’s query pushdown is the solution for data sovereignty.24 Dremio’s exec-in-VPC is a good deployment solution.28
BI Acceleration (Ease-of-Use) Excellent Fair Dremio’s Reflections with automatic rewrite 5 are far simpler for non-technical users than Starburst’s MVs/CBO tuning.23
Lakehouse Maturity (Iceberg) Excellent Good Dremio’s native, “Git-like” Nessie integration 6 makes it a full lakehouse management platform, not just a query engine.
Lakehouse Maturity (Delta Lake) Fair Excellent Starburst’s neutrality and first-class Delta support 12 make it the clear choice for Databricks-centric environments.
Compliance (Platform Certs) Excellent Gap Dremio provides SOC 2 and ISO 27001 certifications upfront.20 Starburst’s must be verified.

 

Decision Framework Narrative

 

A large financial institution should approach this choice as a strategic decision about its primary data architecture. The choice is a function of the organization’s primary center of data gravity.

  • If the organization’s strategy is to build a new, unified data lakehouse (likely on Iceberg) and the primary challenge is BI and self-service performance, Dremio is the stronger candidate. Its integrated platform, semantic layer, and powerful, simple-to-use Reflections are a compelling solution.
  • If the organization’s reality is a permanently distributed, heterogeneous data estate (on-prem, multi-cloud, multi-format) and the primary challenge is governance, federation, and data sovereignty, Starburst is the stronger candidate. Its architecture is purpose-built to solve this complex federated governance problem.

 

Key Questions to Ask Each Vendor (RFP/POC)

 

  1. To Starburst: Provide the company’s full SOC 2 Type 2 audit report and ISO 27001:2022 certificate.
  2. To Starburst: Demonstrate automatic query rewrite for your materialized views. If this feature does not exist, provide the standard operational procedure and associated overhead for managing MV-based acceleration.
  3. To Dremio: Demonstrate a federated query joining our on-prem Teradata, Snowflake, and an Azure data lake table. Provide the raw query profile and detail exactly what predicates, aggregations, and joins are pushed down to each source.55
  4. To Dremio: Demonstrate user impersonation and credential pass-through to an on-prem SQL Server database. We must see the end-user’s credentials in the SQL Server audit log, not a Dremio service account.17

 

Suggested POC Scenarios

 

  1. Federated Governance Test: (Targets Starburst’s strength, Dremio’s gap)
  • Goal: Validate federated auditability.
  • Test: Define a query joining an on-prem RDBMS (with sensitive PII) and a cloud data lake. Apply a row-level policy. Execute as a user with partial rights.
  • Success: (a) The query succeeds, (b) the row-level policy is enforced, and (c) the on-prem database audit log shows the end-user’s credentials.17
  1. BI Acceleration Bake-off: (Targets Dremio’s strength, Starburst’s gap)
  • Goal: Validate ease-of-use and performance for BI.
  • Test: Identify a high-value, slow-running (e.g., 90-second) Power BI dashboard. Point both Dremio and Starburst at the same data lake tables. Enable Dremio Reflections 5 and Starburst MVs/Warp Speed.8
  • Success: Measure (a) final query time, (b) time-to-value (setup complexity), and (c) operational cost/overhead of the acceleration.
  1. Lakehouse Data-as-Code Test: (Targets Dremio’s unique value)
  • Goal: Validate modern lakehouse management.
  • Test: Use Dremio with its Nessie-based catalog.6 Create a “dev” branch of a production Iceberg table. Ingest new data, run DML, and verify results in isolation. Then, perform an atomic merge to production.
  • Success: The test completes, demonstrating transactional, Git-like control over the data lake.

 

13. Conclusion & Recommended Next Steps

 

Main Findings

 

  • Dremio and Starburst are both elite, modern SQL engines, but they are built to solve different primary problems. They are not as interchangeable as they first appear.
  • Dremio is a product: An integrated, opinionated lakehouse platform optimized for performance (via Apache Arrow) and BI acceleration (via Data Reflections).2
  • Starburst is a platform: A flexible, federated query engine optimized for heterogeneity (via Trino) and complex, federated governance (via query pushdown and credential pass-through).16
  • For a regulated financial institution, the decision hinges on a key trade-off:
  • Dremio provides verifiable, third-party platform compliance (SOC 2, ISO 27001).20
  • Starburst provides battle-tested federated governance features (pass-through, data sovereignty) and proven financial-services use cases (AML).24
  • The primary technical trade-off is Dremio’s “easy but proprietary acceleration” (Reflections) vs. Starburst’s “complex but open federation” (CBO/pushdown).

 

Recommended Next Steps

 

  1. Internal Stakeholder Alignment: Convene a review meeting with leaders from Data Engineering, Security, Governance, and FinOps.
  • Security & Governance: Must be mandated to sign off on the governance and auditability POC (Scenario 1) and to obtain and validate Starburst’s SOC 2 / ISO 27001 compliance reports.
  • Data Engineering: Must be mandated to own the BI Acceleration Bake-off (Scenario 2) and Lakehouse Test (Scenario 3).
  • FinOps: Must be tasked with modeling the TCO for both platforms, paying close attention to Dremio’s Reflection costs 111 versus Starburst’s tiered credit model.113
  1. Launch a 4-8 Week Proof of Concept (POC): Do not make a paper-based decision. The architectural differences are too significant. A hands-on POC is mandatory. Execute the three scenarios defined in Section 12.
  2. Define POC Success Metrics:
  • Performance: Query completion time (p50, p90) for the BI Acceleration Bake-off.
  • Governance: A binary Pass/Fail on the Federated Governance Test. A “Fail” on credential pass-through or policy enforcement should be a show-stopper.
  • Cost: Estimated cost-per-query for the BI workload, as reported by each platform’s billing/usage dashboard.
  • Time-to-Value: Time (in hours) from initial setup to a passing query for each POC scenario.

Works cited

  1. About Us | Dremio, accessed November 15, 2025, https://www.dremio.com/about/
  2. How It Works – Dremio Modernization Workshop, accessed November 15, 2025, https://dremio.awsworkshop.io/10-section1/101-deploying-dremio.html
  3. 10 Use Cases for Dremio in Your Data Architecture | by Alex Merced – Medium, accessed November 15, 2025, https://medium.com/data-engineering-with-dremio/10-use-cases-for-dremio-in-your-data-architecture-64a98d2be8bc
  4. Accelerate Queries – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/acceleration/
  5. Reflections Query Acceleration – Dremio, accessed November 15, 2025, https://www.dremio.com/reflections/
  6. Nessie | Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/data-sources/lakehouse-catalogs/nessie/
  7. The Seeds of Revolution – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/the-seeds-of-revolution/
  8. The journey from Presto to Trino and Starburst, accessed November 15, 2025, https://www.starburst.io/blog/the-journey-from-presto-to-trino-and-starburst/
  9. About | Starburst, accessed November 15, 2025, https://www.starburst.io/about/
  10. Starburst | Choose your Starburst product – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/introduction/choose-your-starburst-product.html
  11. Connectors | Starburst, accessed November 15, 2025, https://www.starburst.io/platform/connectors/
  12. Apache Iceberg vs Delta Lake – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/iceberg-vs-delta-lake/
  13. Iceberg, Delta Lake, & Hudi: Open data lakehouse architecture – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/iceberg-delta-lake-hudi/
  14. Vectorized Query Processing with Apache Arrow | Webinar – Dremio, accessed November 15, 2025, https://www.dremio.com/resources/webinars/vectorized-query-processing-apache-arrow/
  15. What is Trino? – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/what-is-trino/
  16. Pushdown — Starburst Enterprise – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/latest/optimizer/pushdown.html
  17. What is Dremio | Starburst, accessed November 15, 2025, https://www.starburst.io/dremio/
  18. The Nessie Ecosystem and the Reach of Git for Data for Apache Iceberg | Dremio, accessed November 15, 2025, https://www.dremio.com/blog/the-nessie-ecosystem-and-the-reach-of-git-for-data-for-apache-iceberg/
  19. Platform Security – Protecting Your Data | Dremio, accessed November 15, 2025, https://www.dremio.com/platform/security/
  20. Compliance | Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/dremio-cloud/security/compliance/
  21. How Does AI Change Data Governance? – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/ai-data-governance/
  22. A Notebook for getting started with Project Nessie, Apache Iceberg, and Apache Spark, accessed November 15, 2025, https://www.dremio.com/a-notebook-for-getting-started-with-project-nessie-apache-iceberg-and-apache-spark/
  23. Dremio vs. Starburst Data: The Truth of Why Companies Choose Dremio, accessed November 15, 2025, https://www.dremio.com/blog/dremio-vs-starburst-data-the-truth-of-why-companies-choose-dremio/
  24. Financial Services | Starburst, accessed November 15, 2025, https://www.starburst.io/solutions/industry/financial-services/
  25. Dremio History: Founding, Timeline, and Milestones – Zippia, accessed November 15, 2025, https://www.zippia.com/dremio-careers-1498794/history/
  26. Dremio | Company Overview & News – Forbes, accessed November 15, 2025, https://www.forbes.com/companies/dremio/
  27. Dremio Pricing, accessed November 15, 2025, https://www.dremio.com/pricing/
  28. What is Dremio Cloud?, accessed November 15, 2025, https://docs.dremio.com/cloud/about
  29. AWS Marketplace: Dremio Cloud – Enterprise Edition, accessed November 15, 2025, https://aws.amazon.com/marketplace/pp/prodview-pnlijtzyoyjok
  30. Why Dremio Cloud?, accessed November 15, 2025, http://www.dremio.com/wp-content/uploads/2024/03/Why-Dremio-Cloud.pdf
  31. Dremio Software, accessed November 15, 2025, https://www.dremio.com/software/
  32. Building a Universal Semantic Layer with Dremio, accessed November 15, 2025, https://www.dremio.com/blog/universal-semantic-layer/
  33. Starburst — What Should we know about it | by Eleanor Watson | Medium, accessed November 15, 2025, https://medium.com/@eleanor.watson/starburst-what-should-we-know-about-it-d8c19594a890
  34. Starburst: How This Rapidly Growing Data Lakehouse Provider Is Transforming A $30 Billion Market – Pulse 2.0, accessed November 15, 2025, https://pulse2.com/starburst-justin-borgman-profile/
  35. What is Trino (Presto SQL) and Starburst? – promethium.ai, accessed November 15, 2025, https://promethium.ai/what-is-trino-presto-sql-and-starburst/
  36. PrestoDB vs PrestoSQL vs Trino – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/prestodb-vs-prestosql/
  37. Starburst Enterprise and Starburst Galaxy on Google Cloud – YouTube, accessed November 15, 2025, https://www.youtube.com/watch?v=bFEzOhPWFy4
  38. Starburst – Microsoft Marketplace, accessed November 15, 2025, https://marketplace.microsoft.com/en-us/marketplace/apps/starburstdatainc1582306810515.starburst-enterprise
  39. Federated data: How does a data lakehouse help? | Starburst, accessed November 15, 2025, https://www.starburst.io/blog/data-federation-and-data-lakehouse/
  40. The Data Lake Water and Starburst’s federated query engine are Hot – theCUBE Research, accessed November 15, 2025, https://thecuberesearch.com/the-data-lake-water-starbursts-federated-query-engine-are-hot/
  41. The Snowflake vs. Databricks War and The Shift Towards Federated IT | Dremio, accessed November 15, 2025, https://www.dremio.com/newsroom/the-snowflake-vs-databricks-war-and-the-shift-towards-federated-it/
  42. Need a faster and cheaper compute resource for processing data stored in snowflake : r/dataengineering – Reddit, accessed November 15, 2025, https://www.reddit.com/r/dataengineering/comments/1dinqod/need_a_faster_and_cheaper_compute_resource_for/
  43. Databricks vs Snowflake – 2025 take – Blueprint Technologies, accessed November 15, 2025, https://bpcs.com/blog/databricks-vs-snowflake
  44. Top 10 Starburst Alternatives & Competitors in 2025 – G2, accessed November 15, 2025, https://www.g2.com/products/starburst/competitors/alternatives
  45. Denodo vs Starburst: Which Data Platform is Right for You? – Snic Solutions, accessed November 15, 2025, https://snicsolutions.com/compare/denodo-vs-starburst
  46. The 8 Best Data Mesh Software Companies & Vendors for 2025 – Solutions Review, accessed November 15, 2025, https://solutionsreview.com/data-management/the-best-data-mesh-software-companies-vendors-tools/
  47. Trino vs Starburst: Which Data Tool is Right for You? – Snic Solutions, accessed November 15, 2025, https://snicsolutions.com/compare/trino-vs-starburst
  48. Leading Telecom Provider Case Study | Starburst, accessed November 15, 2025, https://www.starburst.io/resources/leading-telecom-provider-case-study/
  49. Architecture | Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/what-is-dremio/architecture/
  50. Vectorized Query Processing using Apache Arrow – Conferences, accessed November 15, 2025, https://conferences.oreilly.com/strata/strata-ca-2018/cdn.oreillystatic.com/en/assets/1/event/269/Vectorized%20query%20processing%20using%20Apache%20Arrow%20Presentation.pdf
  51. Vectorized Query Execution – Dremio, accessed November 15, 2025, https://www.dremio.com/wiki/vectorized-query-execution/
  52. Project Nessie, Iceberg & Spark Tutorial Notebook – Dremio, accessed November 15, 2025, https://www.dremio.com/blog/a-notebook-for-getting-started-with-project-nessie-apache-iceberg-and-apache-spark/
  53. Manage Sources | Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/data-sources/
  54. Identify pushdown SQL from raw query profiles – Dremio Support, accessed November 15, 2025, https://support.dremio.com/hc/en-us/articles/38797046703131-Identify-pushdown-SQL-from-raw-query-profiles
  55. Querying Relational-Database Sources Directly – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/help-support/advanced-topics/external-queries/
  56. What’s New: Reflection Improvements & Caching | Dremio, accessed November 15, 2025, https://www.dremio.com/blog/whats-new-in-dremio-enhanced-performance-with-reflection-improvements-result-set-caching-and-merge-on-read-2/
  57. 3. Accelerate Queries Using Reflections – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/tutorials/zero-to-lakehouse/accelerate-using-reflections/
  58. Dremio C3 cache versus reflections, accessed November 15, 2025, https://community.dremio.com/t/dremio-c3-cache-versus-reflections/9748
  59. Accelerating Queries with Reflections – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/24.3.x/sonar/reflections/
  60. The architecture behind fault tolerant execution | Starburst Virtual Events – YouTube, accessed November 15, 2025, https://www.youtube.com/watch?v=IqrZV60i2xA
  61. How to use Airflow with Trino, accessed November 15, 2025, https://trino.io/blog/2022/07/13/how-to-use-airflow-to-schedule-trino-jobs.html
  62. Delta Lake: Home, accessed November 15, 2025, https://delta.io/
  63. Exploring query plans – Starburst Academy, accessed November 15, 2025, https://academy.starburst.io/exploring-query-plans
  64. Starburst Data – Technical Solution Brief – TechTalk Summits, accessed November 15, 2025, https://techtalksummits.com/MediaLibraries/Files/Starburst-Technical-Brief.pdf
  65. Trino query plan analysis | Session 2 of 3 – YouTube, accessed November 15, 2025, https://www.youtube.com/watch?v=Yem1eKcj5f8
  66. Data Lakes and Lakehouses: 2024 GigaOm Radar Leader – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/2024-gigaom-radar-data-lakes-lakehouses/
  67. Dremio Editions | Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/editions/
  68. Query audit — Starburst Enterprise, accessed November 15, 2025, https://docs.starburst.io/latest/security/audit.html
  69. Built-in access control audit log — Starburst Enterprise, accessed November 15, 2025, https://docs.starburst.io/latest/security/biac-audit-log.html
  70. Access control policy types – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/starburst-galaxy/security-and-compliance/manage-data-access/access-control-policy-types.html
  71. dbt – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/clients/dbt.html
  72. Dremio-Native: Row-Access & Column-Masking Policies, accessed November 15, 2025, https://docs.dremio.com/24.3.x/sonar/security/rbac/row-column-policies-udf/
  73. Row-Access and Column-Masking Policies Enterprise – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/current/data-products/govern/row-column-policies-udf/
  74. New: Row-Level and Column-Level Access Controls – Dremio, accessed November 15, 2025, https://www.dremio.com/blog/new-row-level-and-column-level-access-controls/
  75. Starburst Enterprise Security Guide, accessed November 15, 2025, https://www.starburst.io/info/starburst-enterprise-security-guide/
  76. How row filtering & column masking enables enterprise grade security | Starburst, accessed November 15, 2025, https://www.starburst.io/blog/row-filtering-column-masking-enterprise-grade-security/
  77. Built-in access control masks and filters — Starburst Enterprise, accessed November 15, 2025, https://docs.starburst.io/latest/security/biac-masks-filters.html
  78. Fine-grained governance & security to your cloud data sources with ABAC – Starburst, accessed November 15, 2025, https://www.starburst.io/blog/abac-fine-grained-governance-cloud-data/
  79. Dremio vs. Starburst Enterprise Comparison – SourceForge, accessed November 15, 2025, https://sourceforge.net/software/compare/Dremio-vs-Starburst-Enterprise/
  80. Why Your Data Strategy Needs Data Products: Enabling Analytics, AI, and Business Insights, accessed November 15, 2025, https://www.dremio.com/blog/why-your-data-strategy-needs-data-products-enabling-analytics-ai-and-business-insights/
  81. Starburst Data Security | Immuta, accessed November 15, 2025, https://www.immuta.com/partners/starburst/
  82. Navigating Finance and Insurance Data Regulations with Dremio’s Intelligent Lakehouse, accessed November 15, 2025, https://www.dremio.com/blog/navigating-finance-and-insurance-data-regulations-with-dremios-intelligent-lakehouse/
  83. Compliance – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/security/compliance/
  84. Starburst achieves AWS Financial Services Competency Partner, accessed November 15, 2025, https://www.starburst.io/blog/starburst-aws-financial-services-competency-fsi/
  85. Dell Data Lakehouse 1.4.0 Administrator’s Guide, accessed November 15, 2025, https://www.dell.com/support/manuals/en-us/dell-data-lakehouse/ddl_p_admin_guide_140/enable-audit-logs?guid=guid-03409290-88ff-4483-b7ef-35db4cd9ec04&lang=en-us
  86. Dremio | Looker – Google Cloud Documentation, accessed November 15, 2025, https://docs.cloud.google.com/looker/docs/db-config-dremio
  87. Microsoft Power BI – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/24.3.x/sonar/client-applications/clients/microsoft-power-bi/
  88. 4. Visualize Data Using Tableau or Power BI – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/tutorials/zero-to-lakehouse/visualize-data/
  89. Microsoft Power BI – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/clients/powerbi.html
  90. Starburst – Tableau Exchange, accessed November 15, 2025, https://exchange.tableau.com/products/274
  91. Tableau overview – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/clients/tableau/
  92. Build a data lakehouse with dbt Core and Dremio Cloud | dbt Developer Hub – dbt Docs, accessed November 15, 2025, https://docs.getdbt.com/guides/build-dremio-lakehouse
  93. dbt – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/sonar/client-apps/dbt/
  94. dbt – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/dremio-cloud/developer/dbt
  95. Starburst/Trino setup | dbt Developer Hub – dbt Docs, accessed November 15, 2025, https://docs.getdbt.com/docs/core/connect-data-platform/trino-setup
  96. Connect Starburst or Trino | dbt Developer Hub – dbt Docs, accessed November 15, 2025, https://docs.getdbt.com/docs/cloud/connect-data-platform/connect-starburst-trino
  97. Automating Reflections Management with the Dremio-Airflow Plugin – YouTube, accessed November 15, 2025, https://www.youtube.com/watch?v=1Ae3ujtVLQc
  98. Orchestration of Dremio with Airflow and CRON Jobs, accessed November 15, 2025, https://www.dremio.com/blog/orchestrating-dremio-with-airflow/
  99. Automating Reflections Management with the Dremio-Airflow Plugin, accessed November 15, 2025, https://www.dremio.com/subsurface/on-demand/automating-reflections-management-with-the-dremio-airflow-plugin-2/
  100. Airflow DAG: Use Starburst and Airflow to create resilient data pipelines, accessed November 15, 2025, https://www.starburst.io/blog/airflow-dag/
  101. Quickstart Guide to Using Airflow with Starburst Galaxy – GitHub, accessed November 15, 2025, https://github.com/YCat33/galaxy_airflow_quickstart
  102. Orchestrating Airflow DAGs with GitHub Actions — A Lightweight Approach to Data Curation Across Spark, Dremio, and Snowflake – Medium, accessed November 15, 2025, https://medium.com/data-engineering-with-dremio/orchestrating-airflow-dags-with-github-actions-a-lightweight-approach-to-data-curation-across-19c6abff3401
  103. Accelerate AI/ML Model Development – Dremio, accessed November 15, 2025, https://www.dremio.com/solutions/ai-ml/
  104. Starburst expands partnership with Google Cloud and the reach of Vertex AI with their federation engine, accessed November 15, 2025, https://www.starburst.io/blog/starburst-expands-partnership-with-google-cloud-and-vertex-ai/
  105. Machine learning – Starburst documentation, accessed November 15, 2025, https://docs.starburst.io/clients/machine-learning.html
  106. Google Cloud data cloud partners support generative AI, accessed November 15, 2025, https://cloud.google.com/blog/products/data-analytics/google-cloud-data-cloud-partners-support-generative-ai
  107. Starburst Adds AI to Its Federated Data Lakehouse Platforms – The New Stack, accessed November 15, 2025, https://thenewstack.io/starburst-adds-ai-to-its-federated-data-lakehouse-platforms/
  108. Simplifying Data Exploration with Starburst and AI – YouTube, accessed November 15, 2025, https://www.youtube.com/watch?v=FmH49_ofP3g
  109. Dremio – Spendflo, accessed November 15, 2025, https://www.spendflo.com/vendors/dremio
  110. Managing Your Subscription – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/subscription/
  111. Cost Optimization – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/24.3.x/help-support/lakehouse-arch/cost/
  112. Starburst | Usage and billing, accessed November 15, 2025, https://docs.starburst.io/starburst-galaxy/cluster-administration/monitor-and-manage-cost-and-performance/usage-billing.html
  113. Plans and Pricing | Starburst, accessed November 15, 2025, https://www.starburst.io/pricing/
  114. Pricing Details – Starburst, accessed November 15, 2025, https://www.starburst.io/pricing/pricing-details/
  115. FactSet Modernizes Applications with Dremio, Accelerating Data Access and Eliminating Complexity, accessed November 15, 2025, https://www.dremio.com/wp-content/uploads/2022/07/Dremio-Factset-Case-Study-Final.pdf
  116. Global Investment Bank Case Study | Starburst, accessed November 15, 2025, https://www.starburst.io/resources/global-investment-bank-case-study/
  117. Modern standards for anti-money laundering monitoring | Starburst, accessed November 15, 2025, https://www.starburst.io/blog/modern-standards-for-anti-money-laundering-monitoring/
  118. Managing Security – Dremio Documentation, accessed November 15, 2025, https://docs.dremio.com/cloud/security/
  119. Dremio vs Starburst : r/dataengineering – Reddit, accessed November 15, 2025, https://www.reddit.com/r/dataengineering/comments/17svlvl/dremio_vs_starburst/
  120. Why do you think Dremio is not as popular as Databricks or Snowflake? – Reddit, accessed November 15, 2025, https://www.reddit.com/r/dataengineering/comments/1futf1y/why_do_you_think_dremio_is_not_as_popular_as/
  121. Connectors — Starburst Enterprise, accessed November 15, 2025, https://docs.starburst.io/latest/develop/connectors.html
  122. Dremio vs Starburst 2025 | Gartner Peer Insights, accessed November 15, 2025, https://www.gartner.com/reviews/market/analytics-query-accelerators/compare/dremio-vs-starburst

Leave a Comment