Try our new research platform with insights from 80,000+ expert users

Domo vs Qlik Compose comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Domo
Ranking in Data Integration
15th
Average Rating
7.8
Reviews Sentiment
6.5
Number of Reviews
48
Ranking in other categories
BI (Business Intelligence) Tools (4th), Business Performance Management (5th), Reporting (4th), Data Visualization (5th)
Qlik Compose
Ranking in Data Integration
47th
Average Rating
7.6
Reviews Sentiment
6.5
Number of Reviews
12
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of March 2026, in the Data Integration category, the mindshare of Domo is 0.7%, up from 0.4% compared to the previous year. The mindshare of Qlik Compose is 1.0%, down from 1.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
Domo0.7%
Qlik Compose1.0%
Other98.3%
Data Integration
 

Featured Reviews

RD
Assistant Manager at a tech services company with 10,001+ employees
Have improved workflow efficiency through custom reports but encountered formatting limitations
The downsides of Domo are that we don't have a feature in the same column. When data comes in a time format, text format, and number format, we cannot segregate and create conditional formatting in that column. If in the future they develop this feature, it will benefit more users. Domo requires maintenance on my end, such as updates. I am maintaining some dashboards on a weekly basis and monthly basis daily reports. Because we need to upload in SFTP, we cannot schedule or auto-schedule due to rate purposes. We manually handle the data sets. If there were an option to reduce the cost, it would be easier to access.
Sahil Taneja - PeerSpot reviewer
Principal Consultant/Manager at Tenzing
Easy matching and reconciliation of data
The initial setup was easy for the data warehousing concept. But for a person who is new to ETL and warehousing concepts, it may take some time. If someone is familiar with these concepts, they could understand and learn the tool quickly. However, compared to other tools, the UI is complex. It would be helpful to have a better UI and documentation for new users. As of now, there is a challenge in learning the Compose tool for new users altogether. Qlik Compose was deployed on-premises. But the servers, like the SQL servers were maintained on the cloud—the managed instances.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"We find the ease of using the solution valuable."
"One feature which I have found to be very interesting is the Beast manager, where you can create calculated fields. They are shared in one common repository so someone else can use the same calculated fields; they don't have to rewrite or reinvent the APIs."
"The ETL tools they have in Redshift are pretty awesome... I can work in Redshift to get the data from AWS and work in Redshift, in Domo, to create Transforms and the data structure we need..."
"What makes me really fond of Domo is the ETL because it enables us to maximize a single platform for pulling reports and automating things. We can send the raw data from a third-party platform and do the rest of the ETL in Domo, including transforming data, adding columns, etc."
"The dashboarding itself was pretty easy. So both the front and the back end were positive in this case."
"Domo is not a difficult tool to learn. All you need to know is the SQL for the ETL part. You don't need to write much code. That's the great part. It uses legacy languages, like SQL, which is very common among developers who then don't have to go and learn Domo's own syntax. Therefore, you don't have to learn another hard language to use Domo."
"There are many valuable features, especially the charts and graphs that make it easy to pass information to people that are not really technical."
"Distribution of visualizations via a web portal is valuable, but really is basic table stakes."
"I have found it to be a very good, stable, and strong product."
"One of the most valuable features was the ability to integrate multiple source systems that mainly used structured IDBMS versions."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years."
"It is a scalable solution."
"It can scale."
"The technical support is very good. I rate the technical support a ten out of ten."
"One of the most valuable features of this tool is its automation capabilities, allowing us to design the warehouse in an automated manner. Additionally, we can generate Data Lifecycle Policies (DLP) reports and efficiently implement updates and best practices based on proven design patterns."
 

Cons

"Data integration is okay, but not the best."
"More functions on the ETL side for the drag and drop ETL."
"We were vastly over-sold. Domo was sold as an easy-to-implement-yourself product, but this is completely unrealistic."
"It is very difficult too, if we do have specific requests or errors that we can't get figure out - especially when it comes to the development platform, developing custom connectors or doing any kind of API work, custom cards - in that there's a lag in the response time."
"I would also like to see improvements to their drag and drop Magic ETL tool. You can drag and drop your ETL tool, but it doesn't really work for a large amount of data. It struggles with that. In a real-world application, where you're working with 30 million rows or 100 million rows, it takes a bit longer to process the data. If you do it in the Redshift ETL tool, using your own code, it's much faster."
"It was zero. We paid for a year's contract and made no money from its use."
"The UI has issues with some browsers and small glitches that hinder performance or functionality."
"It's too early for me to say that something needs improvement, but there are times when there have been some flexibility issues with Domo... Tableau has a window function which can be integrated into a calculated field. That is missing in Domo so you have to make changes to the data set using ETL or SQL."
"The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring."
"I believe that visual data flow management and the transformation function should be improved."
"There should be proper documentation available for the implementation process."
"Qlik's ETL and data transformation could be better."
"I'd like to have access to more developer training materials."
"It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model."
"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."
"There could be more customization options."
 

Pricing and Cost Advice

"I believe that the investment in Domo was worthwhile because it allowed for the organization to jump in quickly, with little training. There are different plans available based on the requirements."
"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."
"For about 100 users our cost is $95,800."
"We are making money from Domo, and all our clients are happy with the information that they receive from it."
"The solution is expensive compared to one of its competitors."
"The price that they offered was around $200 per user license. It was pretty cheap at that time compared to other companies. I think they have revamped their pricing structure since then."
"Domo has more than one licensing model. You can choose between the yearly subscription and the per-user licensing model. The tool is flexible in terms of licensing. As for the cost, Domo is an end-to-end BI tool so its pricing is a little higher than other players in the market, for example, non end-to-end BI tools such as OBIEE and Tableau specific only for business intelligence and presenting data to the end users, unlike Domo which handles everything. You want to get Domo as an integration tool, an ETL tool, etc. As the tool is end-to-end, its cost is always going to be a little higher than other BI tools, but it's worth paying because you won't have to spend extra for other activities. After all, Domo can do those activities."
"It is on the pricier end."
"The price of the solution is expensive."
"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."
"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
University
10%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
6%
Financial Services Firm
12%
Government
12%
Manufacturing Company
10%
Insurance Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business16
Midsize Enterprise13
Large Enterprise20
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise6
 

Questions from the Community

What is your experience regarding pricing and costs for Domo?
My experience with pricing, setup cost, and licensing is that there was very little.
What needs improvement with Domo?
I'm not sure how Domo can be improved overall, as it's a really good experience.
What is your primary use case for Domo?
My main use case for Domo involves building different tables and different cards so I can look at different data points. A quick specific example of a table I have built or a data point I often loo...
Which ETL tool would you recommend to populate data from OLTP to OLAP?
There are two products I know about * TimeXtender : Microsoft based, Transformation logic is quiet good and can easily be extended with T-SQL , Has a semantic layer that generates metat data for cu...
 

Comparisons

 

Also Known As

corda
Compose, Attunity Compose
 

Overview

 

Sample Customers

Capco, SABMiller, Stance, eBay, Sage North America, Goodwill Industries of Central Indiana, Telus, The Cliffs, OGIO International Inc., and many more!
Poly-Wood
Find out what your peers are saying about Domo vs. Qlik Compose and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.