
Overview
Dremio delivers lightning-fast queries and a self-service semantic layer directly on S3, so that you don't have to move the data into data warehouses, cubes or extracts.
Highlights
- Fast queries on S3 (4-100x faster & 10x more efficient than other SQL engines)
- Join between S3 and other AWS/on-premise databases
- Semantic layer to empower BI (Tableau, Power BI, etc.) users and govern data access
Details
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Cost/hour |
|---|---|
m5d.2xlarge | $0.78 |
m5d.xlarge | $0.39 |
m5d.8xlarge | $3.12 |
m5d.4xlarge | $1.56 |
i3.4xlarge | $2.15 |
r5d.4xlarge | $1.99 |
c5d.18xlarge | $5.96 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
No refunds
How can we make this page better?
Compliance
Compliance profile
- Source
- Vanta Trust Center





Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Dremio Deployment
Launches a coordinator node of the product, with the ability to dynamically provision additional engines to execute queries
CloudFormation Template (CFT)
AWS CloudFormation templates are JSON or YAML-formatted text files that simplify provisioning and management on AWS. The templates describe the service or application architecture you want to deploy, and AWS CloudFormation uses those templates to provision and configure the required services (such as Amazon EC2 instances or Amazon RDS DB instances). The deployed application and associated resources are called a "stack."
Version release notes
Additional details
Usage instructions
Quickstart Instructions:
Resources
Vendor resources
Support
Vendor support
Community Support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.


Standard contract
Customer reviews
Data platform has unified diverse sources for mesh use but has needed query cache tuning
What is our primary use case?
As the data platform architect, I use Dremio as the main component of our platform to serve our business needs, acting as an integrator and as a meta user of it. My colleagues use it to serve their business needs, to query their data, and so on, which is the way we use it in the company.
What is most valuable?
The primary value I find in Dremio is that this tool is mainly used to query data that are split amongst several sources and to virtualize those sources so that the end user faces it as a single source of truth of data. This is particularly useful to propose a Data Mesh organization of the data. That's the main advantage of this kind of product. It is not the only product in this segment that serves this feature, but I believe it does it pretty well, with a focus on virtualization and acceleration of queries.
What needs improvement?
Something I dislike about it is the performance optimization concerning a special feature known as Reflection, Data Reflection, which is basically a cache of the data sources behind it. This Reflection is sometimes not well optimized in the way it is built or refreshed.
For how long have I used the solution?
I have been using it in my career overall for three years.
What do I think about the stability of the solution?
I have seen some instability; I would say seven out of ten on that scale. We had some crash issues concerning part of the engine caused by one query that made the engine crash. The support explained a probable reason for the crash but didn't clarify why it happened. We refactored the query, and that worked, but it still doesn't make you confident to go to production with a product that might crash depending on the query you send it.
What do I think about the scalability of the solution?
Dremio is designed to be scalable, and I can confirm that it is, so that requirement is perfectly met.
How are customer service and support?
We contact the technical support at least weekly; currently, it's more or less daily because we face performance issues, crashes of queries sometimes, and we also need support for configuration of the query engines and so on. We are using the support extensively, and we are under a Gold support plan.
The quality and speed of the support are satisfactory. Sometimes it depends on which support engineer is taking up the case, but very often it's quite responsive, reactive, coherent, and the response is of good quality. I would give the support an eight on a scale from one to ten, with ten being the highest.
Which solution did I use previously and why did I switch?
I have used several alternatives.
The one that I prefer most is Trino, which is a famous alternative. It's open-source and it lacks some features, such as security features and data governance features, but from a performance point of view, I think it is ahead. Another solution is Starburst, which is also renowned, though I haven't tried it myself. Another option is Hive, but it doesn't offer the virtualization part of the job.
How was the initial setup?
The initial deployment of Dremio was easy because it is a cloud-native deployment that we are using. Dremio has several installation modes and supports different ways of deployments. We used the Kubernetes one, so the cloud one, and that went pretty well. It's pretty up to standard, and it's great to work with.
What's my experience with pricing, setup cost, and licensing?
Dremio does have a core of the engine that is open-source, but all the important features for the enterprise version are under license.
Regarding the license and pricing, we have an agreement, a commercial agreement, for the pricing. It has been discussed, and I have nothing more to say about that. My company signed and they were okay with that, so I think it's a fair deal so far.
Which other solutions did I evaluate?
Between Dremio and Trino, we have chosen Dremio based on some features that we absolutely require regarding security and data governance, but for performance purposes, I would prefer Trino.
What other advice do I have?
I have been working in my current field overall for ten years.
As any query engine, Dremio needs maintenance. It requires attention regarding the storage it uses, and you have to also refresh all the metadata of the catalog and so on. It's not due to the product itself; it's due to the usage by our users. Any query engine would have the same needs, but otherwise, it's pretty resilient.
Overall, I would give Dremio a score of seven out of ten for everything.
Centralized our lakehouse data and has streamlined BI analytics and AI use cases
What is our primary use case?
My main use case for Dremio is building a lakehouse data platform, integrating several sources, other databases, and Parquet files from S3 buckets, building Iceberg tables to provide the company a central platform where all data are available for a couple of use cases such as BI analytics and AI.
One specific example of how I have used Dremio in a project is addressing a challenge with a heterogeneous BI landscape where they have grown a lot of applications, such as Qlik, where they extract data from different databases and then they have decentralized versions of the data. Dremio could help to centralize all data that are used for analytics in the company.
How has it helped my organization?
Dremio has positively impacted our organization by streamlining the whole BI and analytics processes and reducing the heterogeneous landscape, allowing us to have everything in one place under one hood, which reduced a lot of maintenance and processing efforts in our everyday work.
What is most valuable?
In my opinion, the best features Dremio offers are the catalog, which is Polaris-based, and also data federation, allowing you to query across several other vendors' databases. Additionally, reflections and automatic reflections speed up queries automatically based on usage, which means it detects what dimensions and measures are used the most and then materializes the answers upfront, speeding up the whole BI and analytics use case.
The catalog and reflections features specifically help my work by speeding up access to data on S3 buckets, for instance, and reflections pre-calculate results which are then just delivered instantly. This means you do not need to wait to run a query for a longer time on huge amounts of data, and the user gets very quick answers.
What needs improvement?
One area where Dremio can be improved is the lack of tooling or functionalities for importing data in a pipeline way, as it is not an ETL or ELT component. This is somehow missing, and we are doing this now separately using other tools and Python scripts, but I think this is a missing feature in the whole platform. I choose to rate Dremio a nine out of ten because this ETL and ELT functionality is missing and some effort is needed to build up all those data pipelines around Dremio and to create all these Iceberg tables and other components. It requires some engineering to bring everything in place, which should actually be supported inside of Dremio.
Before we wrap up, I want to add that Dremio is lacking a semantic layer in a manner that the user can just choose dimensions, metrics, and filters to query the data. What Dremio considers a semantic layer is a layer of bronze, silver, and gold level semantic views or SQL views on top of the data, but this is not very flexible. This means you need another product beside Dremio to support ad-hoc analysis, so I think that a semantic layer should be part of Dremio.
For how long have I used the solution?
I have been using Dremio for around five years now, but in a customer project with a real license on it, I am using it for two years with the on-premise version.
What do I think about the stability of the solution?
Dremio is very stable.
What do I think about the scalability of the solution?
Dremio's scalability depends on your hardware and your deployment. We have deployed it to Kubernetes, and there is some auto-scaling, and we did not face any problems with that.
How are customer service and support?
My experience with customer support has been very good so far, but we did not have many cases, only some for sizing on the Helm charts at the beginning, and that was very good from our German Dremio partners. I would rate customer support a ten out of ten.
Which solution did I use previously and why did I switch?
We did not use a different solution before Dremio because there is nothing similar on the market.
What was our ROI?
I cannot provide any return on investment metrics with Dremio, such as money saved, time saved, or fewer employees needed.
What's my experience with pricing, setup cost, and licensing?
I had a good experience with pricing, as the pricing seems okay to me and the client, and the setup could be done by ourselves.
Which other solutions did I evaluate?
Before choosing Dremio, we evaluated different options, but as I mentioned, there is no similar platform, so it was easy to decide.
What other advice do I have?
Regarding Dremio's AI capabilities, I cannot say much about governance and security because I have not used it yet. I have not used Dremio's AI capabilities yet, so I cannot judge anything about it. What I have seen looked to me more to be a showcase demo case rather than real capabilities for productive use, but I could be wrong.
Dremio is deployed in my organization on-premises. My advice to others looking into using Dremio is to just try it out yourself, as there is also a community edition you can play around with upfront. I would rate Dremio a nine out of ten overall.
Unified data sources have accelerated lakehouse development and enabled faster cross-source queries
What is our primary use case?
I have been using Dremio to select multiple data sources, retrieve multiple data sources, and create and maintain Iceberg tables for the data lakehouse.
My main use case for Dremio is to actively create queries for multiple data sources. For example, I work with data marts and databases. I also create new tables on the data lakehouse and perform cross-joins from multiple data sources.
One project was to predict income, and I used multiple income tables from the data warehouse. I created pipelines from the data warehouse to the data lakehouse and selected all the old tables using Dremio.
How has it helped my organization?
Dremio has positively impacted my organization by creating faster development and POC projects. I create the data lakehouse and develop lakehouse tables, for example, creating Iceberg tables.
I have noticed time saved, improved collaboration, and improved multiple data connections.
What is most valuable?
The best features Dremio offers in my experience include native data catalogs because my company didn't create new data catalogs, but Dremio can use a native data catalog.
The native data catalog feature has made the development cycles faster. Multiple data sources can be queried in one query, and it is not just a query engine.
What needs improvement?
I think Dremio can be improved to query faster than multiple sources and big data lakehouses. The community version could be updated for new data catalog connections.
I think the documentation is sufficient. For support, the Enterprise version is adequate.
For how long have I used the solution?
I have been actively using Dremio for one year in my work, and I have used Dremio Enterprise for six months.
What do I think about the stability of the solution?
Dremio is stable in my experience.
What do I think about the scalability of the solution?
Dremio's scalability is good, but I use on-premises models, so I do not have experience with the cloud.
How are customer service and support?
Customer support is great. I would rate the customer support an eight.
Which solution did I use previously and why did I switch?
I worked on Trino before Dremio, but it is a query engine. I needed other techniques for how it works.
What's my experience with pricing, setup cost, and licensing?
I chose eight out of ten because Dremio is expensive for the Enterprise version, particularly regarding licensing.
Which other solutions did I evaluate?
Trino was the only option I evaluated because I need to connect multiple tools.
What other advice do I have?
Regarding Dremio's AI capabilities, I think its governance and security is good, but I did not use Dremio's AI because my company's security is high.
I do not have enough experience with Dremio's AI capabilities to comment on its accuracy and reliability of output.
I would advise using Dremio if you have a small project using a data lakehouse or if you need to connect multiple data sources. You might consider switching from Trino to Dremio. I would rate this product an eight overall.
Evaluating Dremio for Enterprise Data Analytics
The user interface is clean and intuitive. It is web-based, which means no client installations to manage, and the layout is straightforward. The SQL editor is responsive with autocomplete and syntax highlighting, making query writing feel natural. The visual query builder is helpful for users who are not comfortable with SQL, though most of our team prefers writing queries directly. The dashboarding and visualization features are functional but not as polished as dedicated BI tools like Tableau or Power BI. For quick exploratory analysis, they work perfectly, but for polished executive presentations, we still export to other tools. Overall, the user experience is pleasant and focused on getting work done without unnecessary friction.
The integrations are where Dremio truly excels. The platform connects to over 36 different data sources, including all the major databases, data warehouses, and cloud storage platforms. We have it connected to PostgreSQL for transactional data, Snowflake for our warehouse, and S3 for our data lake files. The integration process is straightforward. You add a source, provide credentials, and the system catalogs the metadata automatically. No complex configuration required. The federated query engine means we can join data across these sources in a single query, which was impossible for us before. The platform also integrates well with BI tools like Tableau and Power BI through standard JDBC and ODBC connectors, allowing our analysts to work in the tools they already know.
The performance gains are genuinely impressive. When we first set up Dremio, we ran a test query that used to take about 8 minutes in our legacy environment. Dremio returned it in about 12 seconds. I actually thought it was broken. The Autonomous Reflections feature is magical. It learns what queries we run most frequently and automatically creates optimized data structures in the background. We do not have to think about performance tuning anymore. It just happens. Even with complex joins across multiple data sources, the query engine handles it efficiently. We have seen query times improve by 10x to 100x depending on the complexity of the workload.
The cost savings are another major win. We were paying a fortune for cloud data warehouse storage because we were duplicating everything. We had data in S3, data in Snowflake, data in Redshift, and we were paying for all of it. Dremio let us store everything in open formats on S3 and query it directly. We cut our storage costs by about 60 percent and our compute costs by about 40 percent. The open architecture is a big part of this. We are not locked into any proprietary format. If we decide to move away from Dremio, our data is still there in standard formats like Apache Iceberg. No vendor lock-in, no expensive migration project. The pricing model is consumption-based, so we only pay for what we use, which aligns well with our variable workload patterns. For organizations with significant data volumes, the ROI is substantial and measurable within the first year.
The onboarding experience was remarkably smooth compared to other enterprise platforms we have implemented. Dremio offers a Community Edition that we used to prototype and test before committing to the enterprise version. This allowed us to validate the platform's capabilities without any financial risk. The enterprise version includes formal support, and we have found the support team to be responsive and knowledgeable. Tickets are resolved quickly, and the documentation is thorough and well-organized. The platform is self-managed in our environment, which gives us full control, but Dremio also offers a fully managed cloud option if you prefer not to handle the infrastructure. The open-source community is active and helpful, which is a nice supplement to the formal support channels. Overall, getting started was straightforward and we were productive within weeks rather than months.
The AI Agent is a nice addition. It handles basic natural language questions well. A user can ask "Show me revenue by region for the last quarter" and it will generate the SQL and visualize the results instantly. It saves time on simple queries and helps non-technical users get started. The AI_GENERATE function is particularly interesting. It can extract structured information from unstructured files like PDFs or text documents directly within a SQL query, which opens up new use cases for us. The AI Semantic Layer ensures that both human analysts and AI tools are working with consistent business definitions, which improves the accuracy of AI-generated answers. However, the AI capabilities are not yet at the level where they can replace a skilled analyst for complex analytical questions. For day-to-day exploration and quick insights, it is genuinely helpful, but complex multi-condition analysis still requires human expertise.
Overall, Dremio has made us more agile, more cost-effective, and more data-driven as an organization. The reduction in complexity has been liberating. We are spending less time moving data and more time actually analyzing it. I would recommend it to any organization struggling with data silos, high costs, or slow access to insights. It is not perfect, but for what it does, it is remarkably effective.
Integrations are a particular sore spot. The connection with Power BI has been described as problematic by multiple reviewers, with customer support teams apparently having a poor understanding of how this integration works internally. This makes troubleshooting incredibly difficult when something goes wrong. The CI/CD capabilities also feel incomplete. There is an unsupported Python script available to handle development and production environments, but it cannot deal with some native Dremio objects like Row-Level Security policies. This means you might develop a dataset with proper access controls in your development environment, but the script simply will not deploy it to production, forcing you to find workarounds.
Performance at enterprise scale has been a documented weak point. The federation engine struggles with concurrency on large datasets, and standardized performance testing shows that the architecture routinely fails to complete queries when multiple users are running queries simultaneously. For AI use cases, this is more pronounced because an AI agent querying your data may be running dozens of complex federated queries in parallel as part of a single task, and the failure mode compounds quickly.
There are also technical limitations to be aware of. The platform enforces various system limits, such as maximums on autoingest pipes, sources, spaces, and total reflections. Query results returned via the console are limited to one million records, though you can use ODBC or JDBC to see the full result set. The platform also has limits on leaf columns in tables and queries, which can impact organizations working with wide datasets.
Support quality has been inconsistent. Some users have noted that support can be lacking at times, which they attribute to Dremio being a younger company compared to its competitors. The documentation around certain features, like Kubernetes deployment requirements, indicates significant administrative overhead, and managing the Kubernetes cluster requires considerable effort.
The AI capabilities, while promising, are somewhat lagging compared to other platforms. In a world where competitors have already integrated the latest AI techniques, Dremio is still catching up. The AI Semantic Layer, while useful for labeling data, does not enforce business rules. It organizes and labels data without packaging metadata, access rules, or business constraints into an enforceable framework. Different teams and AI agents can still interpret the same underlying data in incompatible ways, and the platform has no mechanism to stop them.
There is also a broader strategic concern. Dremio was recently acquired by SAP, which puts its roadmap in question. Features that Dremio was building independently now have to compete for budget and attention inside a much larger organization. Strategic shifts are already visible, with some cloud editions effectively put on hold while the deal works through approvals. For organizations with strict data governance requirements, the mandatory transmission of operational telemetry data back to Dremio's corporate endpoint introduces a compliance headache that cannot be ignored.
Despite these challenges, I still find Dremio valuable for our use case. The query performance is genuinely impressive, the cost savings are real, and the platform has transformed how we access data. The downsides are real and you need to go in with your eyes open. Budget extra time for troubleshooting integrations, be prepared for some administrative overhead, and have realistic expectations about the AI capabilities. If you have a focused use case like fast SQL acceleration on an Iceberg lakehouse where you own all the data, Dremio's core engine is still remarkably capable. But for teams needing broad federation across many sources, high concurrency, and polished enterprise features, it is worth evaluating carefully.
The most significant business problem Dremio solved for us is eliminating the traditional ETL bottleneck. Instead of building complex pipelines to extract, transform, and load data into a central warehouse, we now query data directly where it lives. This "query, don't move" approach has dramatically accelerated our time to insight. When we need to combine data from our transactional database with our data lake, we simply write a query and Dremio handles the federation. What used to take days of pipeline development now takes minutes of query writing.
We were also struggling with data silos that made it nearly impossible to get a unified view of our business. Different teams had different versions of the truth, leading to endless debates about whose numbers were correct. Dremio connects to all our data sources and presents them through a unified semantic layer, creating a single source of truth for the entire organization. Our finance team can now confidently use the same data as operations, and we no longer waste time reconciling conflicting reports.
The cost savings have been substantial as well. We were paying a premium to store duplicated data across multiple cloud warehouses. Dremio's open architecture, built on Apache Iceberg, allows us to store data once in open formats on object storage and query it efficiently without duplication. We eliminated redundant storage costs and reduced our cloud compute spending because we are not constantly moving and transforming data.
Perhaps most importantly, Dremio has enabled self-service analytics across our organization. Previously, every data request had to go through a centralized IT team that was perpetually backlogged. Business users waited weeks or months for access to the data they needed. Now, our analysts can query data independently using standard SQL, without waiting for engineering support. The platform has democratized access to data, and we have seen adoption grow as more teams realize they can explore data on their own terms.
Dremio has fundamentally shifted our organization from being reactive to proactive with data. We can now answer business questions in hours instead of weeks, spot trends earlier, and make decisions based on current information rather than stale reports. The platform has given us the agility we needed to compete in a data-driven world, and I would not want to go back to our old way of working.