Sold by
IBM watsonx.data as a Service - GenAI Ready Data Lakehouse for AWS
IBM watsonx.data is an open, hybrid data lakehouse with built-in data fabric and multi-engine optimization to prepare structured and unstructured data for AI.
Reviews (178)
Eric B.
Clean, Unobtrusive UI with Seamless Integrations and On-Demand AI Insights
Reviewed on Jul 29, 2026
Review provided by G2
What do you like best about the product?
I like that the UI stays out of the way, the integrations keep our data connected overall behind the scenes, and its most noticeable AI feature is there whenever I need an additional layer of insight.
What do you dislike about the product?
Well it wasn’t perfect from the start. AI occasionally requires a second thought before I move forward with its decisions. And it does demand some solid attention to make complete sense to us.
What problems is the product solving and how is that benefiting you?
We were putting too much effort into finding, preparing, and then validating data before making any analysis. Now that our data is synced with the best of the features, the entire process feels more connected, making it simpler for us to make informed decisions about data.
SHIWAM T.
Seamless Data Integration with Stellar Performance
Reviewed on Jul 29, 2026
Review provided by G2
What do you like best about the product?
I like how IBM watsonx.data unifies data from multiple sources into a single lakehouse platform while delivering fast query performance. Its strong data integration capabilities and open lakehouse architecture allow us to work with data in place instead of moving or duplicating it. I also appreciate that the platform scales well as our data grows, supports a wide range of analytics workloads, and integrates smoothly with AI business intelligence tools. The initial setup process was relatively straightforward, with well-documented installation and configuration steps, and connecting common data sources was uncomplicated.
What do you dislike about the product?
For me, everything is good.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data to consolidate data from multiple sources into one platform, improving access and analysis. It eliminates silos and enhances query performance for large datasets, providing faster insights without data duplication.
MOUNEES KUMAR C.
Great Platform for Unified Data and Analytics
Reviewed on Jul 27, 2026
Review provided by G2
What do you like best about the product?
You can use this response (more than 40 characters):
> What I like best about IBM watsonx.data is its ability to manage and analyze large volumes of structured and unstructured data efficiently. Its open data lakehouse architecture, scalability, and support for AI and analytics make it a powerful platform for modern data-driven applications.
> What I like best about IBM watsonx.data is its ability to manage and analyze large volumes of structured and unstructured data efficiently. Its open data lakehouse architecture, scalability, and support for AI and analytics make it a powerful platform for modern data-driven applications.
What do you dislike about the product?
You can use this balanced review:
> One drawback of IBM watsonx.data is that the initial setup and configuration can be complex for new users. Some advanced features also have a learning curve, and performance tuning may require technical expertise to get the best results.
> One drawback of IBM watsonx.data is that the initial setup and configuration can be complex for new users. Some advanced features also have a learning curve, and performance tuning may require technical expertise to get the best results.
What problems is the product solving and how is that benefiting you?
You can use this response:
> IBM watsonx.data helps solve the challenge of managing and analyzing large volumes of data from multiple sources in one platform. It improves query performance, reduces data management complexity, and supports AI and analytics workloads, enabling faster insights and more efficient decision-making.
> IBM watsonx.data helps solve the challenge of managing and analyzing large volumes of data from multiple sources in one platform. It improves query performance, reduces data management complexity, and supports AI and analytics workloads, enabling faster insights and more efficient decision-making.
Abhishek Y.
Powerful Data Management with Room for Easier Setup
Reviewed on Jul 27, 2026
Review provided by G2
What do you like best about the product?
I like IBM watsonx.data for its scalability, fast query performance, and the ability to integrate data from multiple sources in one platform. I appreciate its support for open data formats, flexible integrations, and the capability to scale as my data needs grow.
What do you dislike about the product?
I find the learning curve a bit steep, and I think the initial setup could be simpler. The onboarding process could be more guided, with clearer documentation, step-by-step setup wizards, and more practical examples for common deployment scenarios. Better error messages and troubleshooting guidance would also make the initial configuration easier.
What problems is the product solving and how is that benefiting you?
I use IBM watsonx.data for data storage, SQL analytics, and managing enterprise data efficiently in one platform, improving scalability and analytics performance.
Nikita S.
Open Lakehouse Architecture with Seamless Integration and High-Performance Querying
Reviewed on Jul 26, 2026
Review provided by G2
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
It helps break down data silos and makes it easier to access large datasets. As a result, I can analyze data more efficiently, with better performance and less time spent when working on AI and analytics projects.
Information Technology and Services
Robust Data Storage and Maintenance for Managing Complex Data Flows
Reviewed on Jul 24, 2026
Review provided by G2
What do you like best about the product?
IBM watsonx.data has robust data storage and maintenance capabilities. It’s a powerful tool that has helped me manage data flow for semantic platforms and for the tools built for business intelligence and reporting.
What do you dislike about the product?
The ecosystem and setup process feel somewhat complex. There’s a slow learning curve to get fully engaged, and the UI is less intuitive compared to other available tools that offer similar functionality.
What problems is the product solving and how is that benefiting you?
It helps organize and process large-scale TPA data by unifying it in a single platform, where later stages of ETL processes can run smoothly. It also serves as a single, governed data layer that is retrieved from many different sources.
Chirag S.
Flexible Open Lakehouse with Iceberg Support and Multi-Engine Choice
Reviewed on Jul 23, 2026
Review provided by G2
What do you like best about the product?
Its focus is on giving organizations flexibility without forcing them into a single storage format or query engine. A few aspects stand out as particularly compelling. The open data lakehouse architecture is designed to work with open table formats such as Apache Iceberg, which helps reduce vendor lock-in and makes data more portable across different tools and platforms. The separation of storage and compute also matters: you can scale compute resources independently of storage, which can improve cost efficiency for workloads that fluctuate over time. Finally, instead of relying on one query engine, it supports multiple engines optimized for different workloads, letting users choose the best fit for analytics, SQL, or AI use cases.
What do you dislike about the product?
IBM watsonx.data has several strengths, but it also comes with trade-offs that some users and organizations may find limiting. One is complexity: compared with fully managed cloud data warehouses, watsonx.data can require more upfront planning and ongoing operational expertise, particularly when you’re configuring multiple query engines, storage layers, and governance components. Another is the learning curve: teams that aren’t already familiar with lakehouse concepts, Apache Iceberg, or IBM’s data ecosystem may need additional time before they can become fully productive.
What problems is the product solving and how is that benefiting you?
IBM watsonx.data helps solve the problem of fragmented data and inefficient analytics by offering a unified, open lakehouse platform. For me, the main benefits are that it makes data easier to access, improves performance for AI and analytics workloads, helps lower infrastructure costs, and provides flexibility by supporting open data formats.
reviewer2715654
Collaborative analytics workspace has improved campaign insights and saves weekly manual effort
Reviewed on Jun 19, 2026
Review provided by PeerSpot
What is our primary use case?
IBM Watson Studio is our main platform for analytics workflows as a marketing agency. We use the platform's machine learning and data visualization capabilities, primarily for analytics and analyzing campaign performance.
A specific example of how I use IBM Watson Studio for campaign performance analytics is that because we use different channels and have different customers, we need one source where we can collect and view all the data. For this reason, we recently started using IBM Watson Studio.
I have nothing else to add about my main use case or how I integrate IBM Watson Studio with my other tools.
What is most valuable?
One of the best features IBM Watson Studio offers is the ability to collaborate across teams using a centralized workspace.
The centralized workspace helps my team collaborate because we did not need to spend excessive time on manual processes. This helped us collaborate across teams by selecting which data and which channels should be reflected in IBM Watson Studio. In this way, we saved time and could easily see campaign outcomes and make better data-driven marketing decisions.
IBM Watson Studio has positively impacted my organization by being time-efficient and enabling collaboration, as we can see everything in one screen. It helped improve our efficiency and provided deeper customer insights that enable better decision-making. It definitely helped our weekly time efficiency by saving manual workload because we have a lot of work going on. It really helped us in analyzing the data and analytics.
What needs improvement?
IBM Watson Studio can be improved because there is currently a learning curve. It would be better if it were not so difficult to learn for people without a data background or limited technical experience.
I do not have anything more to add about the needed improvements, including around documentation, support, or user interface.
For how long have I used the solution?
I have been using IBM Watson Studio for six months.
What do I think about the stability of the solution?
IBM Watson Studio is definitely stable.
What do I think about the scalability of the solution?
The scalability of IBM Watson Studio is good. We started using it during a period of fast growth and scaling, so it was the right time for a company in our position to implement it.
How are customer service and support?
The customer support was good in terms of helping answer any questions my team had.
Which solution did I use previously and why did I switch?
I did not previously use a different solution; IBM Watson Studio was our first solution in this area.
How was the initial setup?
My experience with pricing, setup cost, and licensing is that I think it is expensive.
Regarding pricing, because it is IBM, it is justified. However, it is an expensive cost. The goals and what we achieved through it justify the price.
What was our ROI?
I have seen a return on investment through time saved. With the time saved, my employees and I can put more time into other responsibilities.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that I think it is expensive.
Regarding pricing, because it is IBM, it is justified. However, it is an expensive cost. The goals and what we achieved through it justify the price.
Which other solutions did I evaluate?
We did not evaluate any other options before choosing IBM Watson Studio.
What other advice do I have?
I would rate IBM Watson Studio an eight out of ten.
I chose eight because I think it is great in terms of all the things I described, and the only two points I subtracted are due to the learning curve.
Regarding IBM Watson Studio's AI capabilities, IBM is a very trustworthy company. The AI capabilities were particularly valuable for our marketing analytics workflows. The platform's AutoAI features helped accelerate model development for my team by automating data preparation and model selection. This allowed my team to focus more on campaign strategy and insights, which was what we needed to do.
The accuracy and reliability of output for IBM Watson Studio is definitely reliable because from a governance perspective, IBM Watson Studio provides strong controls around model management and monitoring.
The advice I would give to others looking into using IBM Watson Studio is that they need to have a good team that can build the usage of this because it is not something you can start using immediately. You need to learn, as there is a learning curve.
Hennie Du Toit
AI-driven monitoring has reduced manual rule maintenance and now supports multi-tenant operations
Reviewed on Jun 18, 2026
Review provided by PeerSpot
What is our primary use case?
I have been in IT in this particular sphere for my whole career, basically spanning over 20 years. I remember approximately how much time deployment for IBM Watson Studio required, and it was a couple of days probably. The project span was complex given our environment, so we use it for multi-tenancy purposes. It was not that easy to do.
What is most valuable?
The best features in IBM Watson Studio for me personally are moving away from the alarm dictionary or moving away from the rule-based alarms to more the AI Ops portion where you have IBM Watson Studio with some of the machine learning to do the correlations and learning seasonality, et cetera. Having a smarter technology rather than strictly rule-based, fixed scenarios of reducing events has been beneficial.
The prebuilt model templates in IBM Watson Studio have helped us reduce time-to-value for our team by making it a lot easier for us to manage because previously, we had to build a lot of the rule-based correlations in a different tool, and now we have ported that into AI Ops IBM Watson Studio. It is looking a lot easier for us to manage that.
I do see some positive impact after implementing IBM Watson Studio. Otherwise, we would have moved on.
What needs improvement?
I face some difficulties and room for improvement in IBM Watson Studio. A lot of the functions they did bring in are what we asked for, and I think a lot of them are roadmap items, but perhaps tighter integrations to some of the products that they also own, such as Instana or Turbonomic, would be great. I think you still have to configure a lot of the webhooks, for example, where it would be nice if it was an out-of-the-box integration.
I assess the flexibility of IBM Watson Studio in integrating with open-source machine learning tools and frameworks, and I find that it is not always that easy, but with the PMRs, they normally help you quite quickly to solve it.
For how long have I used the solution?
I can tell you that I have been working with IBM Watson Studio for many years, and we still make use of the platform.
What do I think about the scalability of the solution?
I can confirm that IBM Watson Studio is a scalable product. We have a multi-tenanted environment operating across many markets, so for us, it is definitely one of the big benefits.
What about the implementation team?
For the deployment, a combined team with probably about five or six people was involved. This included engineers and administrators from our team and the IBM consulting team as well.
What was our ROI?
I do not track any return on investment or cost reductions after implementing the product because I am not personally involved in that. That is more on our finance side that they do that.
What's my experience with pricing, setup cost, and licensing?
My thoughts about licensing cost are that it is a bit of a tricky question to be honest, because it depends on what you compare it to. For the product suite, I think we have negotiated a good price. Obviously, all businesses want the price to go lower, so I think it is not that bad.
What other advice do I have?
Regarding deployment, we have not done a new deployment in the last couple of years since we upgraded to AI Ops, so I cannot really answer that for the recent. There were some challenges with the containerized solution, but we managed to sort it out.
My preference for the deployment model of IBM Watson Studio is that for IBM software or that portion, we still have on-prem, but obviously, if it makes sense, we deploy a SaaS service. For IBM, we still have on-prem at the moment.
I have not used the AutoAI feature in IBM Watson Studio closely at the moment with the tooling implementation, but I think it is something they were looking at. I am not sure if it was deployed.
We use some automated reports and things to evaluate the effectiveness of IBM Watson Studio's model development capabilities. We use BI reports to verify that it is effective, and we do some retrospective checks.
My understanding of integration with Instana, particularly, is that Instana and Turbonomics are part of their product suite because they also own them and bought them a couple of years ago.
I would rate this product an 8 out of 10.
Arkajit D.
Powerful Query Performance and Governance, But a Steep Onboarding Learning Curve
Reviewed on May 19, 2026
Review provided by G2
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.