IBM Watson Studio is used primarily with our customers, though we have also tested it in our company and laboratories. I am also dealing with products like IBM Watson Studio and IBM Cognos.
External reviews
166 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Powerful Query Performance and Governance, But a Steep Onboarding Learning Curve
What do you like best about the product?
One feature that stood out for us was the query performance optimization, especially for large reporting and analytics workloads. We process high-volume financial and customer behavior data, and the platform handled complex queries much more efficiently than our previous setup.
I also appreciate the interoperability with existing tools and open formats. Our engineering team didn’t have to completely rebuild pipelines or retrain users from scratch, which made adoption smoother internally.
Another big advantage has been governance and data visibility. In a regulated fintech environment, having stronger control over data access and lineage tracking became extremely important, especially for audit and compliance requirements.
From a business perspective, watsonx.data helped reduce infrastructure inefficiencies while improving access to analytics across teams. Analysts, data engineers, and operations teams were able to work from a more unified environment instead of constantly moving data between disconnected systems.
I also appreciate the interoperability with existing tools and open formats. Our engineering team didn’t have to completely rebuild pipelines or retrain users from scratch, which made adoption smoother internally.
Another big advantage has been governance and data visibility. In a regulated fintech environment, having stronger control over data access and lineage tracking became extremely important, especially for audit and compliance requirements.
From a business perspective, watsonx.data helped reduce infrastructure inefficiencies while improving access to analytics across teams. Analysts, data engineers, and operations teams were able to work from a more unified environment instead of constantly moving data between disconnected systems.
What do you dislike about the product?
One challenge with IBM watsonx.data is that the platform can feel quite complex during the initial onboarding phase, especially for teams that are newer to lakehouse architectures or hybrid data environments. There are a lot of capabilities available, but understanding how to configure and optimize everything properly takes time.
We also experienced a steeper learning curve around setup, integration, and governance policies compared to some lighter-weight analytics platforms we evaluated. Certain workflows required more technical involvement from our data engineering team than we originally expected.
Another area that could improve is the user experience within parts of the interface. While the platform is powerful, some administrative and configuration tasks don’t always feel as intuitive or streamlined as newer cloud-native tools in the market.
Performance has generally been strong for large workloads, but during early implementation we had to spend time tuning queries and optimizing storage configurations to get consistent results across different environments.
Pricing and infrastructure planning can also become a consideration for organizations scaling large enterprise deployments. Smaller teams without dedicated data engineering resources may find adoption more challenging initially.
We also experienced a steeper learning curve around setup, integration, and governance policies compared to some lighter-weight analytics platforms we evaluated. Certain workflows required more technical involvement from our data engineering team than we originally expected.
Another area that could improve is the user experience within parts of the interface. While the platform is powerful, some administrative and configuration tasks don’t always feel as intuitive or streamlined as newer cloud-native tools in the market.
Performance has generally been strong for large workloads, but during early implementation we had to spend time tuning queries and optimizing storage configurations to get consistent results across different environments.
Pricing and infrastructure planning can also become a consideration for organizations scaling large enterprise deployments. Smaller teams without dedicated data engineering resources may find adoption more challenging initially.
What problems is the product solving and how is that benefiting you?
IBM watsonx.data helped us solve a major issue around fragmented data management and slow analytics processing across multiple business systems. Before implementation, our teams were pulling data from separate cloud platforms, transactional databases, and reporting tools, which created delays, duplication, and inconsistent reporting.
One of the biggest problems was handling growing volumes of financial and operational data efficiently without constantly increasing infrastructure costs. Traditional warehouse scaling was becoming expensive, especially as our analytics workloads expanded across departments.
With watsonx.data, we were able to centralize access to structured and semi-structured data while still keeping flexibility in how the data was stored and queried. That significantly improved reporting speed and reduced the amount of manual data movement our engineering team had to manage.
A major benefit for us has been faster analytics and better visibility across teams. Earlier, generating large operational or customer-risk reports could take hours because data pipelines were fragmented. After implementation, analysts were able to query datasets more efficiently and collaborate from a more unified environment.
One of the biggest problems was handling growing volumes of financial and operational data efficiently without constantly increasing infrastructure costs. Traditional warehouse scaling was becoming expensive, especially as our analytics workloads expanded across departments.
With watsonx.data, we were able to centralize access to structured and semi-structured data while still keeping flexibility in how the data was stored and queried. That significantly improved reporting speed and reduced the amount of manual data movement our engineering team had to manage.
A major benefit for us has been faster analytics and better visibility across teams. Earlier, generating large operational or customer-risk reports could take hours because data pipelines were fragmented. After implementation, analysts were able to query datasets more efficiently and collaborate from a more unified environment.
Advanced models have driven actionable insights from complex data and support custom predictions
What is our primary use case?
What is most valuable?
The features I find most valuable in IBM Watson Studio are machine learning support and testing different models for a use case, which is one of the best features on the system.
IBM Watson Studio's features assist my customers in driving actionable insights from complex data sets because some models are very satisfying for the customer, mainly prediction models using different techniques, and selecting the best technique for them. Some of them are good and the customer is very satisfied, while other models were not satisfying. However, most of the cases where there was dissatisfaction, the issue was the data itself, not the model, because sometimes I train models with very small data sets and that would not be good.
What needs improvement?
I have not used the AutoAI feature yet, if it is a feature in IBM Watson Studio.
I think the user experience of IBM Watson Studio can be improved, as I am trying to use other products outside IBM and the user experience is much easier on these products.
I need to link IBM Watson Studio with IBM Orchestrate in an easier way to use generative AI. I know it exists and in some cases, we have already linked it with IBM Orchestrate, but it has to be done in a very hard way.
For how long have I used the solution?
I have been working with IBM Watson Studio for five years.
How are customer service and support?
I would rate their technical support a seven.
What's my experience with pricing, setup cost, and licensing?
The pricing for IBM Watson Studio is very high, but we are talking about an enterprise solution. Most of the time we try to convince the customer with the price because it is a robust and enterprise solution, so you pay for what you deserve. The price is very high.
What other advice do I have?
I assess the flexibility of IBM Watson Studio in integrating with open-source machine learning frameworks as good. I have already used some open-source models and it is easy to use it with them. It is not hard.
Sometimes I use the pre-built model templates in IBM Watson Studio, but most of the time I customize my solution by myself.
I do not use standard metrics to evaluate the effectiveness of IBM Watson Studio's model development capabilities. I use my own results, performance, and some other measurements to measure the quality of the prediction model, for example. My overall rating for this solution is eight.
Unified Data Management with Learning Curve
What do you like best about the product?
What I like most about IBM watsonx.data is its ability to unify data from multiple sources without complex migrations or duplication, which saves time and reduces storage costs. Its open lakehouse architecture delivers strong performance for analytics, reporting, and AI workloads while remaining cost-efficient and scalable. I also appreciate the clean and organized UI/UX, which makes navigating datasets, managing workloads, and monitoring data operations more efficient for enterprise teams. The built-in governance, hybrid cloud flexibility, and smooth integrations further simplify data management and support scalable AI and analytics initiatives across environments.
What do you dislike about the product?
One area IBM watsonx.data could improve is the initial setup and configuration, which can feel complex for new users or smaller teams. Some integrations and advanced features also come with a learning curve and would benefit from clearer, more detailed documentation. In certain situations, query performance and troubleshooting can take extra effort, especially when working with very large or highly diverse data environments.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to manage and analyze large data sets across hybrid cloud environments. It streamlines integration, boosts query performance, and provides trusted data access for AI. It simplifies complexity, enhances team collaboration, and controls costs across multiple sources.
Efficient and Scalable Lakehouse Platform for Modern Data Analytics
What do you like best about the product?
What I like most about IBM watsonx.data is how it lets us query and manage data across multiple sources without needing complex data movement. Its open lakehouse architecture makes it easier to work with structured and unstructured data side by side, which has improved performance and reduced storage duplication for our analytics workloads. The integration with AI and analytics tools also helps teams process large datasets more quickly and generate insights more efficiently.
Another major advantage is its scalability and governance. The platform reliably supports high-volume enterprise data workloads while also providing strong security controls and solid data governance features.
Another major advantage is its scalability and governance. The platform reliably supports high-volume enterprise data workloads while also providing strong security controls and solid data governance features.
What do you dislike about the product?
One area where IBM watsonx.data could improve is the initial setup experience and the learning curve for new users. While the platform is powerful, configuring integrations and optimizing workloads can sometimes require advanced technical knowledge, especially for teams that are new to lakehouse architectures. Clearer onboarding documentation, along with more guided setup workflows, would make adoption smoother and reduce the effort needed to get started.
I also think some UI workflows and monitoring features could be more intuitive. At times, troubleshooting performance issues or managing integrations across different environments takes extra effort than it should. Additionally, pricing and resource consumption can become expensive for large-scale deployments, so more transparent cost-optimization tools and simpler management features would help improve the overall experience.
I also think some UI workflows and monitoring features could be more intuitive. At times, troubleshooting performance issues or managing integrations across different environments takes extra effort than it should. Additionally, pricing and resource consumption can become expensive for large-scale deployments, so more transparent cost-optimization tools and simpler management features would help improve the overall experience.
What problems is the product solving and how is that benefiting you?
Before using IBM watsonx.data, we struggled to manage and analyze large volumes of data distributed across multiple systems and cloud environments. Moving data between platforms was time-consuming and costly, and it often introduced delays in our reporting and analytics workflows. We also found it challenging to maintain consistent governance and reliable performance while working with a mix of structured and unstructured data.
With IBM watsonx.data, we can now query data across different sources more efficiently, without unnecessary duplication or migration. This has improved analytics performance, lowered storage and operational costs, and helped our teams reach insights faster to support decision-making. The platform’s scalability, along with its integration with AI and analytics tools, has also boosted productivity by simplifying big data processing and enabling quicker development of data-driven solutions. Overall, it has helped us streamline our data architecture while strengthening governance, flexibility, and operational efficiency.
With IBM watsonx.data, we can now query data across different sources more efficiently, without unnecessary duplication or migration. This has improved analytics performance, lowered storage and operational costs, and helped our teams reach insights faster to support decision-making. The platform’s scalability, along with its integration with AI and analytics tools, has also boosted productivity by simplifying big data processing and enabling quicker development of data-driven solutions. Overall, it has helped us streamline our data architecture while strengthening governance, flexibility, and operational efficiency.
Scalable Platform with Robust Analytics, Needs Setup Improvement
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to centralize data in a unified lakehouse for analytics, solving the challenge of managing large data volumes by unifying lakes and warehouses. It improves query performance and reduces costs with efficient data access and workload optimization.
Flexible Lakehouse Platform with Good Performance and Scalability
What do you like best about the product?
What I like most about IBM watsonx.data is how it brings together a lakehouse approach without making things overly complicated. It feels flexible enough to handle both structured and unstructured data, and the performance with query engines is quite solid, especially when working with large datasets.
What do you dislike about the product?
Initial setup can feel a bit complex, especially for new users. Also, performance tuning and cost optimization sometimes require extra effort compared to more mature, plug-and-play platforms.
What problems is the product solving and how is that benefiting you?
It helps consolidate data from multiple sources into one platform, reducing silos and improving data accessibility. This makes analysis faster and more reliable, which ultimately supports better decision-making and reduces overall data management costs.
Flexible Integration, Complex Learning Curve
What do you like best about the product?
I like that IBM watsonx.data allows us to access data from multiple sources and can run on cloud and hybrid environments. I also appreciate its open and flexible architecture. It helps me connect data across sources and manage it effectively.
What do you dislike about the product?
The initial learning can be complex for beginners, could be made simple with instruction steps. Fix AWS S3, need more stable and plug and play connectors. The setup was not instant, it was somewhat complex.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to search and organize data. It lets me connect data across sources and manage it effectively.
Streamlines Data Management with Robust Features
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to centralize scattered data for easy access and analytics, saving time on data prep and improving performance for large datasets. It simplifies governance and control, letting me focus more on analysis rather than data wrangling.
Powerful Platform with Complex Setup
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to eliminate data silos, enabling unified data access across sources without heavy data movement. It enhances performance and governance, making it easier to prepare reliable, analytics-ready data for BI and AI use cases.
Robust Data Security with a Learning Curve
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to solve data silos, cost, performance, and complexity issues, streamlining data engineering and analytics.
showing 1 - 10