Starburst Galaxy

What do you like best about the product?

I love using Starburst because it makes it easy to run SQL queries, investigate issues, validate changes, and quickly gather information without moving data between systems. It's a useful tool for day-to-day development work and troubleshooting. The query editor is especially easy to use, making it simple to investigate issues and find data. Additionally, the initial setup was quite easy, and I had no issues setting it up. Starburst also provides a more unified way to query data across multiple sources.

What do you dislike about the product?

I find the user interface could be simpler, and better onboarding for new users would be beneficial. It would be helpful if the menus were simpler and user actions were easier to find. Interactive walkthroughs for new users would also be a great addition.

What problems is the product solving and how is that benefiting you?

I use Starburst to query and analyze data across different sources, making it easy to run SQL queries, investigate issues, and gather information without moving data. It offers a more unified way to query data across multiple sources.

What do you like best about the product?

I like that Starburst lets us query data across multiple sources without having to move everything into a central database. It’s fast and scalable, and it makes it much easier to access and analyze data from different systems in one place.

What do you dislike about the product?

Starburst is a powerful platform, but there are a few areas that could be improved. The initial setup and configuration can be complex, especially for teams that are new to distributed SQL or data lake architectures. Some parts of the UI could be more intuitive, as finding certain settings or monitoring query performance sometimes requires extra effort. While integrations with major data platforms are strong, configuring and maintaining them can take time. Performance is generally excellent, but complex queries may require careful tuning to achieve the best results. Pricing may also be a challenge for smaller organizations, as it can become expensive as usage grows. More guided onboarding, additional AI-powered query optimization suggestions, and clearer troubleshooting documentation would make the platform easier to adopt and manage.

What problems is the product solving and how is that benefiting you?

Starburst helps us analyze data across multiple data sources without having to move or duplicate it into a single warehouse. This reduces data silos, saves storage costs, and allows analysts to access up-to-date information more quickly. It has improved reporting efficiency, simplified data access for business users, and enabled faster decision-making by providing a unified view of data across different systems. The platform's scalability also makes it easier to handle growing data volumes while maintaining strong query performance.

What do you like best about the product?

What I like best about Starburst is how it simplifies querying and analyzing data across multiple sources without requiring data movement. The platform's data virtualization capabilities make it easy to access data from different cloud storage systems, databases, and data lakes through a single interface. The UI is intuitive and makes managing queries and datasets straightforward, even for users who are not data engineering experts.

Performance has been consistently strong, especially when working with large datasets, and the query optimization features help reduce processing times significantly. Starburst's integrations with major cloud providers and analytics tools make it easy to fit into existing data workflows. I also appreciate the governance and security features, which help maintain control over data access without adding unnecessary complexity.

Another major benefit is the cost efficiency gained from avoiding data duplication and reducing the need for complex ETL pipelines. The onboarding experience was smooth, and the documentation and support resources made it easy to get started. Overall, Starburst has improved our ability to access and analyze data quickly while maintaining performance, scalability, and strong governance.

What do you dislike about the product?

One downside of Starburst is that there can be a learning curve when setting up and optimizing more complex data architectures, especially for teams that are new to data virtualization concepts. While the platform offers extensive functionality, some advanced configuration and performance tuning options may require deeper technical knowledge to fully leverage.

The AI-powered features are promising, but they are still evolving. In some cases, AI-generated query suggestions or natural language capabilities may require refinement and validation before being used in production workflows. Users with highly specialized data environments may find that the AI assistance does not always fully understand their specific business context or data models.

In certain scenarios involving highly complex queries across multiple data sources, troubleshooting performance bottlenecks can take time. The user interface is generally well designed, but some administrative and governance features can feel overwhelming for new users during the initial onboarding phase. Pricing may also be a consideration for smaller organizations with limited data infrastructure needs, as the platform is primarily geared toward enterprise-scale workloads.

Although documentation and support resources are helpful, there are occasions where more detailed examples for advanced AI, governance, and optimization use cases would make implementation easier. Overall, these challenges are relatively minor compared to the benefits, but they are worth considering when evaluating the platform.

What problems is the product solving and how is that benefiting you?

Starburst helps solve the challenge of accessing and analyzing data that is spread across multiple systems, cloud platforms, and data lakes without requiring data to be copied or moved. Before using Starburst, working with data from different sources often required complex ETL processes and maintaining multiple data copies, which increased costs and introduced delays.

By providing a unified data access layer, Starburst allows us to query data from various sources through a single platform, making analytics faster and more efficient. This has improved productivity by reducing the time spent preparing data and enabling quicker access to insights. The platform's performance optimization capabilities also help accelerate large-scale queries, allowing teams to make data-driven decisions more quickly.

Additionally, Starburst improves data governance and security by providing centralized access controls across different data sources. Its integrations with existing analytics and cloud tools have made adoption straightforward, while the AI-assisted features help users discover data and generate queries more efficiently. Overall, Starburst has reduced operational complexity, lowered infrastructure costs, and enabled faster, more reliable analytics across the organization.

What do you like best about the product?

Connect everything—databases and cloud—faster. They eliminate the need to move data around. You can work with clean data and use natural language by asking simple questions, without any migration.

What do you dislike about the product?

Well, what I didn't like much is that the beginning is a bit difficult, you don't know how to unconnect and use it, not to mention that you need to know SQL-based systems. Since data streaming is very dependent on the network, if a database has a slow connection, the entire Stardust query will be slowed down.

What problems is the product solving and how is that benefiting you?

The main problem this helped me solve was the chaos of fragmented data—when information is spread across different servers and sources like AWS, Google Cloud, local databases, or even Excel. It supports real-time decision-making, boosts my productivity right away, and gives me strong control over my data.

What do you like best about the product?

I particularly appreciate the robust query capabilities and user-friendly interface of Starburst. The ability to execute complex queries against diverse data sources without writing extensive SQL code is a game-changer. For instance, I often need to analyze large datasets from multiple cloud storage systems simultaneously, and Starburst's unified catalog allows me to do this efficiently with just a few clicks. This significantly reduces the time spent on manual integration and data preparation tasks.

Additionally, the dynamic schema discovery feature automatically detects table schemas for new data sources, which is incredibly helpful when working with constantly changing datasets in my organization. This saves hours each week that would otherwise be wasted setting up and maintaining connections to different databases manually.

What do you dislike about the product?

One area for improvement is the initial setup and onboarding process, which can be quite complex and time-consuming. Configuring the unified catalog requires meticulous attention to detail and an understanding of each data source's schema and metadata. While the documentation provides a good starting point, it lacks detailed examples for more advanced configurations involving third-party systems.

Another pain point is the performance when handling extremely large datasets in real-time analytics scenarios. Although Starburst performs well under most conditions, there are occasional delays and scalability issues during peak usage times or when querying very large tables. This can impact productivity and user satisfaction, especially for time-sensitive projects.

Improving the onboarding experience through more interactive tutorials and guided setup wizards could alleviate some of these initial frustrations. Additionally, enhancing query optimization techniques and resource management features would help maintain performance even under heavy loads, ensuring a smoother user experience throughout all phases of data analysis.

What problems is the product solving and how is that benefiting you?

Before using Starburst, we struggled to integrate and analyze data from multiple, disparate sources, including cloud databases, SaaS applications, and on-premises systems. This fragmentation created inefficient workflows: team members spent a lot of time manually preparing, reconciling, and syncing datasets before any analysis could even start. Without a unified catalog, finding and accessing the most up-to-date data was cumbersome and frequently led to delays.

Since implementing Starburst, we can seamlessly query across these diverse data sources through a single interface, which has dramatically improved our overall efficiency. Instead of spending days setting up connections and preparing datasets, I can now run complex analytics queries within minutes, supported by the unified catalog and dynamic schema discovery. As a result, we’ve achieved substantial time savings—about 30 hours per week across my team—and we’re able to spend more time on generating insights rather than managing data.

In terms of measurable impact, we’ve reduced project timelines by roughly 50%, and our ability to respond to business needs with real-time analytics has improved significantly. This strengthens decision-making and helps drive better ROI by enabling faster deployment of data-driven initiatives.

What do you like best about the product?

I found Starburst very useful overall, especially because it made it easy to query data across different systems without having to move everything into one place. The experience felt practical and efficient, and it was a good fit for working with distributed data.

UI / UX
I liked the UI because it was clean and easy to use. It made common tasks feel straightforward, and I didn’t spend much time figuring out where things were.

Integrations
One of the biggest positives for me was the integrations. It connected well with multiple data sources, and that saved a lot of time in setup and day-to-day work.

Performance
Performance was a strong point. Queries felt fast, and that made analytics and reporting much smoother than I expected from a federated setup.

Pricing / ROI
From my perspective, the value came from reducing data movement and saving engineering time. Even if the pricing isn’t the cheapest, the ROI makes sense when you factor in faster access, simpler architecture, and less operational overhead.

Support / Onboarding
Onboarding was smooth, and the support was responsive when I needed help. The documentation and guidance made it easier to get up and running without a lot of friction.

AI / Intelligence
I also liked that Starburst is moving toward AI-ready use cases. The idea of combining federated data access with governance and AI-friendly features makes it feel more future-proof.

Overall, I’d describe Starburst as a strong platform for teams that want fast, federated SQL access across many systems, with good usability and solid support

What do you dislike about the product?

I’d say my biggest dislikes are the steep learning curve, the setup/configuration complexity, and the fact that it can feel expensive as usage grows. For smaller teams, that combination can make it harder to justify unless the federation and performance benefits are clearly worth it.

UI / UX
The UI is usable, but it doesn’t completely hide the complexity underneath. When a platform has a lot of configuration and governance depth, the day-to-day experience can feel heavier than simpler tools.

Integrations
Even though the integrations are a strength, the breadth of connectors can also add operational complexity. In practice, that means there can be more moving parts to manage and more places where setup needs to be exact.

Performance
Performance is generally strong, but it isn’t always perfect for every workload. Some users mention slow queries or performance issues, especially when they’re asking very specific or demanding questions.

Pricing / ROI
Pricing is probably the part I’d question most. The value can be great at scale, but for smaller teams or tighter budgets, the cost can rise quickly as query volume grows.

Support / Onboarding
Onboarding is where I’d expect the most friction. It seems like you need enough technical depth to configure things correctly from the start, otherwise the learning curve can slow the team down.

AI / Intelligence
The AI direction is promising, but I’d still treat it as emerging rather than fully proven for every use case. For me, it wouldn’t be the main reason to choose Starburst today.

What problems is the product solving and how is that benefiting you?

Starburst is mainly solving the problem of data silos: instead of copying data into one central place, it lets you query data where it already lives across warehouses, lakes, databases, and SaaS tools. That also helps with slow, fragmented analytics, because federated query, pushdown, parallelization, and cost-based optimization can make cross-source queries faster and less operationally painful.
For me, the biggest benefit is that I can get a single SQL layer over distributed systems, which means less ETL, less duplication, and less time spent stitching data together manually. It also reduces operational overhead because I don’t need to build and maintain as much custom query infrastructure just to unify sources.
In practice, that means faster access to data, easier cross-system analysis, and quicker decision-making. It’s especially valuable when I need to join data from different platforms in real time or when I want to modernize an architecture without moving everything first.
The real value is not just convenience; it’s that Starburst helps keep data in place while still making it usable for analytics and AI workflows. That gives me more flexibility, better governance, and a cleaner path to scaling analytics without constantly rebuilding pipelines.

What do you like best about the product?

It has better performance, UI/UX and support. Also we consider cost efficiency for this purchase. It has rich integration options for our use case. I will highly recommend.

What do you dislike about the product?

Licensing can get expensive as clusters scale, especially compared to running open-source Trino yourself. For teams already comfortable managing infrastructure, the premium can feel hard to justify.

What problems is the product solving and how is that benefiting you?

Starburst lets you query data across multiple sources (data lakes, warehouses, databases) through one SQL interface, without moving or duplicating everything into a single system first. That's the core problem it solves: data fragmentation across teams and platforms.

What do you like best about the product?

What I like most is that Starburst makes it easier to work with data located in different places. Instead of constantly transferring and copying data, it is possible to simply access different sources through a single interface. This way, teams can quickly get the information they need and work more efficiently with large amounts of data.

What do you dislike about the product?

What I like less about Starburst is that it takes a little time for users to get accustomed to all the features of the platform. For new users, it can seem complex at first, especially when dealing with larger amounts of data. I wish there were more simple guides and examples for everyday user scenarios.

What problems is the product solving and how is that benefiting you?

Starburst helps us to combine data from different sources and quickly access useful information. We mostly use it for reporting, data analysis, and making decisions based on up-to-date data.

What do you like best about the product?

I use Starburst to 'dismantle' our data from D365FO efficiently using BYOD, and it's great for querying large amounts of data quickly. I like how Starburst allows me to join large datasets across silos without needing custom pipelines. The separate computing from storage feature and its parallel processing capabilities help in making data processing faster than our current methods.

What do you dislike about the product?

I wish Starburst had a direct connection to D365FO because using BYOD or any middleman adds extra cost, specifically in Azure. The initial setup was a bit harder since we had to create a separate BYOD database. If a direct connection were possible, it would definitely be easier.

What problems is the product solving and how is that benefiting you?

I use Starburst to dismantle data from D365FO, enabling us to query data faster and join large datasets across silos. It separates computing from storage and works in parallel, enhancing speed.

What do you like best about the product?

Starburst has good and user friendly UI. It also provides a very good performance. The out of the box integrations saves hours of work every week.

What do you dislike about the product?

So far I haven't found any downsides of using starburst. Everything is really good. The AI Integration is really good. And it can be improved further to increase the AI coverage throughout the product.

What problems is the product solving and how is that benefiting you?

Starburst acts as a one-stop-shop tool for analytics. It helps me get meaningful insights from my data, and it takes less than a day to set up. With other tools, it typically takes at least a week to reach the same point.