I used IBM watsonx.data in several client projects over the past few months, mainly for data-heavy tasks where we needed a lakehouse-style setup. What I liked most is that it allowed us to keep data in object storage while still querying it with SQL, without needing to move everything into a traditional warehouse. This cut down on a lot of unnecessary data duplication.

The support for open formats like Iceberg was truly helpful. In one project, we had schema changes halfway through. Being able to manage versioning without disrupting existing queries saved us time. Review collected by and hosted on G2.com.

The initial setup took us some time, especially when it came to configuring storage and access controls. It’s not exactly plug-and-play, so there is a learning curve for teams new to lakehouse architectures. We also needed to review the documentation closely to understand some configuration steps. Once it was set up, it worked well. However, onboarding could definitely be smoother. Review collected by and hosted on G2.com.

I like its open lakehouse architecture, seamless integration with multiple data sources, high-performance querying, and scalability. Together, these strengths make data management and AI analytics more efficient. Review collected by and hosted on G2.com.

The setup can feel complex, and some of the more advanced features come with a steep learning curve. The interface and documentation could also be made more beginner-friendly, as they aren’t always easy to navigate when you’re just getting started. Review collected by and hosted on G2.com.

I use IBM watsonx.data to centralize and manage both structured and unstructured data in a unified lakehouse for analytics and AI workloads. I like its ability to combine the flexibility of a data lake with the performance of a data warehouse in a single platform. It helps me access, process, and analyze data across hybrid environments to generate faster insights and support data-driven decisions. It also offers strong query optimization and supports open data formats, making it easy to scale analytics across hybrid environments. Additionally, it integrates well with BI tools for visualization, helping turn processed data into actionable insights. Transitioning to IBM watsonx.data helped me gain more flexibility and scalability, handle growing data volumes more efficiently while reducing costs, and support modern analytics and AI workloads. Review collected by and hosted on G2.com.

The setup and initial configuration can be a bit complex, especially for teams new to lakehouse architectures. Additionally, improving documentation, UI intuitiveness, and integration with some third-party tools would make the overall experience smoother. The initial setup was moderately complex and required some familiarity with data architecture and cloud environments. While the documentation helps, the process can be time-consuming, especially when configuring integrations and optimizing performance for specific workloads. Review collected by and hosted on G2.com.

I use IBM watsonx.data as a unified data platform to manage, access, and analyze large volumes of structured and unstructured data. I like its ability to unify data across multiple sources without requiring heavy data movement, which makes it easier to access and analyze data efficiently while maintaining performance. I also appreciate the scalability and flexibility it offers for handling large and diverse datasets. The platform supports both analytics and AI workloads in a structured way. Its data governance capabilities help ensure data reliability and security, enabling more efficient and data-driven decision-making. The initial setup was relatively smooth with proper planning and guidance, providing a structured setup process that made it easier to configure core components and connect data sources. Review collected by and hosted on G2.com.

IBM watsonx.data is a strong and scalable platform overall. Some advanced features may require initial familiarity to fully utilize, so a bit of onboarding or guidance can be helpful. Additionally, having more simplified out-of-the-box configurations for certain use cases could further enhance ease of use. Overall, these are minor areas, and the platform continues to evolve with improvements that enhance usability and performance. Review collected by and hosted on G2.com.

I like IBM watsonx.data for its ability to analyze a large scale of data and unify data from multiple sources into a single platform. It's flexible, scalable, and works well for both analytics and AI use cases. The fast delivery of queries and overall performance are impressive. It saves me time by avoiding the need to manage separate systems, making everything accessible in one place. This efficiency helps me get insights quickly. Review collected by and hosted on G2.com.

The initial setup of IBM watsonx.data was not very easy. I had to go through a lot of documentation, and setting up was moderately complex. It required some time to understand the architecture and configurations, especially during integrations. The initial learning curve is high, and it feels a bit complex initially. Review collected by and hosted on G2.com.

I like how IBM watsonx.data simplifies the process of working with distributed data, allowing me to query it in a unified way and making my workflow much smoother. I really appreciate the performance aspect, as handling large datasets feels much faster and more efficient compared to traditional data warehouse setups I've used before. The flexibility is another benefit; it works well with different data formats and integrates nicely with existing tools, so I didn't have to completely change my workflow. I find the query engine based on Presto/Trino very helpful because I can run SQL directly on data sitting in different sources without moving it first. The data virtualization capability is quite useful for creating a unified view across multiple datasets, and the open table format support, like Iceberg, is a big plus for managing large datasets reliably. The governance features also stand out, as they make managing access controls and ensuring proper data usage straightforward. Overall, these features reduce a lot of manual effort and let me focus more on building useful data models and insights rather than handling infrastructure. Review collected by and hosted on G2.com.

It's solid overall, but there are a few areas that could definitely be better. One challenge is the initial learning curve. If you're new to the ecosystem, it takes some time to understand how everything fits together, especially with concepts like data virtualization and open table formats. Performance is generally good, but for very complex queries or heavily concurrent workloads, it can sometimes need extra tuning to get the best results. It’s not always “plug and play” in those scenarios. The UI and overall user experience could also be more intuitive. Some workflows feel a bit clunky, and finding certain settings or configurations isn’t always straightforward. Integration is good, but not always seamless with every external tool—sometimes you need additional setup or workarounds depending on your stack. Lastly, documentation is decent but could be more practical and example-driven. Having more real-world use cases and clearer guides would make onboarding much smoother. Review collected by and hosted on G2.com.

I use IBM watsonx.data primarily because of its ability to provide a unified access layer to data across multiple sources without the need for heavy data movement. I like the flexibility it offers with multiple query engines, which optimizes both performance and cost for different workloads. The data virtualization feature is valuable as it allows me to access data across different sources without moving it, saving time and reducing duplication. I also find the governance and metadata management features important as they provide better control, data lineage, and trust in the data used for analytics and AI. Review collected by and hosted on G2.com.

Some areas of IBM watsonx.data could definitely be improved. The initial setup and configuration can be a bit complex, especially when integrating multiple data sources and engines. Also, performance tuning and troubleshooting can sometimes require deeper expertise, and the UI/UX isn’t always very intuitive, which makes it slightly harder for new users to get comfortable quickly. The main challenge during setup was the complexity of integrating multiple data sources and query engines— it often requires a lot of manual configuration, handling credentials, and understanding how different components interact. Getting everything (like storage, compute engines, and access policies) aligned correctly can take time, especially without clear step-by-step guidance. Review collected by and hosted on G2.com.

I use IBM watsonx.data as a central data platform, which is great for storing, accessing, and analyzing data, especially in data engineering and AI-related tasks. I find the built-in governance and security features very helpful; they give me confidence that the data is well-managed and secure. The access control feature is particularly useful as it allows me to decide who can view or modify specific data, reducing the risk of data misuse. I also appreciate the data lineage and tracking capabilities, as they help me understand where the data is coming from and how it is being transformed—this is very useful when debugging issues or validating data for reports. Furthermore, the data quality and governance policies ensure that the data I use is reliable and consistent across different datasets, which is crucial for analytics and decision-making. Review collected by and hosted on G2.com.

IBM watsonx.data is powerful, but it has a learning curve, and the initial setup can be complex. It would also benefit from better documentation, a more intuitive UI, and simpler performance tuning. Review collected by and hosted on G2.com.

I like that with IBM watsonx.data, data governance is integrated, allowing me to see who accessed what and apply security rules across all data sources, which usually feels like a boring chore when separate. I enjoy how it simplifies the setup of data sources and engine configurations through conversational interactions guided by official documentation. I also appreciate using standard ANSI SQL to join data from disparate sources, making interactive analysis effective. Setting it up was very easy for me. Review collected by and hosted on G2.com.

I think more 'one click' templates for common use cases, like standard RAG, would be helpful to bridge the gap for non-experts. Also, for small to medium enterprises, the prices can feel high and difficult to predict. Review collected by and hosted on G2.com.

What stands out to me about IBM watsonx.data is the flexibility. You can run different query engines based on your workload, which helps optimize performance and cost. I also like that governance is built in — that’s really important for enterprises. Review collected by and hosted on G2.com.

Because watsonx.data supports multiple engines and hybrid environments, sometimes tuning performance or cost requires more expertise than simpler, opinionated platforms. It’s powerful — but you do need time to get the most out of it. Review collected by and hosted on G2.com.