No more typing reviews! Try our Samantha, our new voice AI agent.

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
18th
Average Rating
7.8
Reviews Sentiment
6.5
Number of Reviews
48
Ranking in other categories
BI (Business Intelligence) Tools (6th), Business Performance Management (6th), Reporting (4th), Data Visualization (7th)
Qlik Compose
Ranking in Data Integration
49th
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 June 2026, in the Data Integration category, the mindshare of Domo is 0.7%, up from 0.5% compared to the previous year. The mindshare of Qlik Compose is 0.8%, 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 Compose0.8%
Other98.5%
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.
SA
Director - Metrics & Analytics at a computer software company with 1,001-5,000 employees
Efficient data warehouse automation with robust features, but may require enhancements in user-friendly self-service options and pricing flexibility for broader corporate appeal
It could enhance its capabilities in the realm of self-service options as currently, it is more suited for individuals with technical proficiency who can create pages using it. When it comes to end users who may lack technical expertise, they are limited to toggling between existing developments. To empower end users to make critical changes without relying heavily on technical expertise, it would be beneficial to introduce more user-friendly features for development and modification. If it could incorporate correlation analysis capabilities into its platform, especially in a user-friendly manner, it would greatly enhance the tool's overall utility and make it an even more outstanding solution. There is a room for improvement regarding stability.

Quotes from Members

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

Pros

"The best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources."
"Once the data source has been uploaded to Domo, making graphs is quite easy."
"Domo has a lot of connections using APIs where you can use data from different databases, such as NoSQLs, SQL databases, and other connections. These connections exist to obtain data and transform whatever that you want."
"In general, Domo is very powerful and very easy to use, relatively speaking."
"This solution allows us to change our performance metrics and tracks our goals in real-time."
"The flexibility and usability are probably the best features, and I really appreciate what they're doing now with workflow and AI agents, allowing users to build that kind of agentic flow where data analytics and traditional ETL can quickly and easily embed AI capabilities, which is extremely powerful."
"If you've actually lived the "Domo life," it's hard to get along with anything else after that."
"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."
"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 have found it to be a very good, stable, and strong product."
"The most valuable is its excellence as a graphical data representation tool and the versatility it offers, especially with drill-down capabilities."
"It can scale."
"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."
"There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms."
"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

"If we have unwanted data in our data set as raw data, we need to cleanse and structure it first because having excessive data in Domo will increase loading time and occupy large amounts of space."
"It was zero. We paid for a year's contract and made no money from its use."
"It is expensive."
"One of the improvements that could be made is related to improved storage options."
"Domo as a solution can be improved in various ways."
"The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta."
"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."
"The ETL way of storing is not up to mark. You have to rely on the naming convention that you're using in Domo because there are no folder systems where you can collate all your workflows and put them into separate folders. A folder system should be there so you can easily identify how you are working. Once you want to make some changes to your ETL, then you can see the whole lineage, identifying what is there and not there."
"There should be proper documentation available for the implementation process."
"I'd like to have access to more developer training materials."
"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."
"My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working."
"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."
"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."
"There could be more customization options."
"Qlik's ETL and data transformation could be better."
 

Pricing and Cost Advice

"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."
"I think it is reasonable."
"The solution is expensive compared to one of its competitors."
"The pricing differs from customer to customer, depending on the package."
"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."
"Because it's software as a service, it's more expensive on the face of it. But there are a lot of variables. I don't have to pay for servers or for infrastructure. I don't have to pay labor for my IT organization to set up or maintain the environment. I don't have to pay for them to upgrade the software, and test it, etc., because when it rolls out, it is transparent and seamless for us. But, because of that, it costs more, I imagine, than Sisense, or Yellowfin, or Power BI. A lot of those make it sound like they're inexpensive, but when you add in all the hidden costs and all of the overhead, it's probably comparable."
"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."
"It started out at about $600 a seat. However, then as we started to grow, it scaled that down to about $330 or 3$50 a seat, if I'm not mistaken."
"On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six."
"While they outperform Tableau, there's room for improvement in Qlik's pricing structures, especially for corporate clients like us."
"The price of the solution is expensive."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
10%
University
9%
Financial Services Firm
9%
Comms Service Provider
6%
Financial Services Firm
13%
Government
11%
Manufacturing Company
9%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business17
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: June 2026.
900,747 professionals have used our research since 2012.