What do you like best about Starburst?
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 Review collected by and hosted on G2.com.
What do you dislike about Starburst?
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. Review collected by and hosted on G2.com.