
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
Unlock automation with AI agent solutions

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 |
Vendor refund policy
No refunds
How can we make this page better?
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
Unified lakehouse platform for Analytics and Al
This approach simplifies data integration and reduces engineering overhead.
The SQL query engine is highly performant, delivering sub-second response times even on large datasets, and supports live data visualization and dynamic previews during query preparation.
Data reflections feature acts as an intelligent caching layer, optimizing query performance and enabling low-latency dashboard refreshes for BI workloads.
The platform’s virtual datasets allow for complex query logic to be encapsulated and reused, supporting data-as-code principles such as Git-like version control and experimentation.
Cloud-native architecture offers elastic compute scaling and is available as a managed service on AWS and Azure, making it suitable for both on-premises and cloud deployments. It supports role-based access control and multitenancy, which is essential for enterprise environments with strong data governance requirements.
While the UI is functional, some administrative and monitoring functions feel less intuitive compared to other modern analytics platforms.
I have also found that fine-grained access controls and tenant isolation require careful configuration to avoid inadvertent data exposure in multi-tenant scenarios.
This has resulted in faster dataset creation cycles and reduced bottlenecks between data engineering and analytics teams.
The platform’s autonomous performance optimization and use of data reflections have significantly improved query speeds, enabling real-time analytics and interactive BI dashboarding even on large, complex datasets.
By adopting Dremio, I achieved unified access to both structured and semi-structured data in a single platform, which streamlined data governance and cataloging.
The self-service model empowered business analysts to experiment and iterate on data products without constant engineering intervention, accelerating time-to-insight for AI and analytics projects.
The platform’s open, standards-based approach has also made it easier to integrate with existing tools and future-proof my data infrastructure against vendor lock-in concerns.
âś… My overall insight: Dremio has enabled a more agile, scalable, and cost-effective analytics environment, supporting both operational BI and advanced data science initiatives in a unified, governed, and performant manner.
Easy Direct Access
Review for Dremio product
its very helpful for data analytics and visulizations.
Work
Solution offers quick data connection with an edge in computation
What is our primary use case?
I use Dremio for proof of concept purposes. I haven't used it in a real-time project, however, I explore Dremio as a data virtualization application in the ecosystem. It is relatively new, possibly a one-year or two-year-old system.
What is most valuable?
It's almost similar, yet it's better than Starburst in spinning up or connecting to the new source since it's on SaaS. It is a similar experience between the based application and cloud-based application. You just get the source, connect the data, get visualization, get connected, and do whatever you want.Â
They say data reflection is one way where they do the caching and all that. Starburst also does the caching. In Starburst, you have a data product. Here, the data product comes from a reflection perspective. The y are working on a columnar memory map, columnar computation. That will have some edge in computation.
What needs improvement?
They need to have multiple connectors. Starburst is rich in connectors, however, they are lacking Salesforce connectivity as of today. They don't have Salesforce connectivity. However, Starburst does. Starburst has all these capabilities. Dremio has only 15 to 20 connectors, however, Starburst comes with around 50 now.
For how long have I used the solution?
I have used it for just one month for proof of concept purposes.
What do I think about the stability of the solution?
I cannot comment on stability as I just worked with it for one month. I haven't worked with large data. When I worked with small data, it was fine at that time.
What do I think about the scalability of the solution?
Internally, if it's on Docker or Kubernetes , scalability will be built into the system. In the SaaS, I'm unsure as I haven't set it up. I don't know how the integrated SaaS works inside. If it were an enterprise setup like Starburst, I know how it works since I have worked there, using Kubernetes , Docker , and everything. I'm not familiar with Dremio's backend, however, it also works on Kubernetes and similar technologies. Hopefully, scalability will be there for sure.
How are customer service and support?
It was just proof of concept, and we were just exploring the product. We did not deal with technical supportÂ
How would you rate customer service and support?
Neutral
How was the initial setup?
It is a SaaS, so it is straightforward to set up.
What other advice do I have?
Regarding features, I'm not sure if they have all the tools like data governance, data quality, and data lineage integrated. If not, they need to build those tools as well to check the data quality and lineage. Data discovery is there. Connectivity-wise, Starburst is way better, however, Dremio might have a better computing path, possibly delivering data faster than Starburst. No direct comparison can be made, so I cannot comment further.Â
Overall, you can rate it as eight out of ten.