Apache Superset vs Domo comparison

"The no-code interface is the most valuable as it allows us to operate without constant support from the data engineering team, fostering a self-service environment."

"When you click on any chart, you can apply the filter without any effort."

"The most valuable feature of Apache Superset is the easy way to configure dashboards as reports or analyses and it's easy to use and intuitive. Users do not need a lot of training to use the solution."

"It is a good visual solution tool in an open-source category."

"The solution supports a rich set of charts and enables users to create their own dashboards."

"The fact that you can add any data source is valuable. The entire data handling suite they have, all the apps, etc., is pretty amazing. One of the key things, not being a techie or a data-warehouse guy, is that you can connect data sources, and do all kinds of pretty amazing things."

"The ease of use, overall, is one of the valuable features, as is the ease of setup. Other than making sure IT was aware of, and agreed with our proceeding, we did not need IT for any of the setup. The ease of setup is more valuable than you might think. The ease of configuring the security policies, setting up groups, and setting up personalized data permissions so that only certain people can see certain data — that stuff is amazing... Domo really is extraordinarily full-featured, but it's really easy to use."

"With ETL transformations in SQL lists, you often write a lot of queries. You have to build a bunch of code for the data. With Domo, one of the pieces we have is Magic ETL. In Magic ETL, you don't need to write code. You don't need to be a specialist in SQL or any database query language."

"We have found securing data valuable because it allows us to provide information without identifying individuals."

"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."

"The ability to create custom connectors was useful because you never know, with customers, what platform they want to utilize or what data they have. It gave us a lot of flexibility in being able to bring data in from different places."

"The solution is highly stable."

"The dashboarding itself was pretty easy. So both the front and the back end were positive in this case."

"Automation in terms of APIs for creating roles, and giving privileges to the user can be improved."

"Apache Superset could be improved by enhancing its interactivity and engagement capabilities."

"The platform's reporting feature needs enhancement."

"With Apache Superset, we had some problems with the permissions when we had too many users."

"Dynamic dashboarding could improve to enable smooth navigation when transitioning from a higher to a lower view, allowing for easy accessibility."

"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."

"I would like to see better data intake."

"In terms of the analytics, there is quite a limited set of options when using Domo. Whereas with Tableau we can perform heavy statistical computations, Domo doesn't have that capability. Domo is quite limited on that side."

"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."

"If your ETL runs more than 24 hours, it always fails because we are logging a lot of historical data, and there is a restriction on the amount of data (in rows) that you can run. The technical support has not found a solution for this yet."

"When you're exporting a graph out of Domo — suppose it is in the form of a donut chart or it is in form of a stack — the data comes out in tabular format, not as a graph. When exporting the data, I would like them to create a tab for graphs and another tab with the data in tabular format."

"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 like to publish a dashboard for the employees so that they can also see the performance of our organization. But that is not a feature in Domo, although it's something that Zoho provided."

"Apache Superset is an open-source solution."

"Apache Superset has a three-year licensing model."

"Apache Superset is open-source and free."

"The price of Apache Superset is less than some of its competitors."

"For about 100 users our cost is $95,800."

"Domo is slightly costly but it's much cheaper than some."

"The pricing differs from customer to customer, depending on the package."

"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."

"No matter if you're a developer or an end-user, the licensing cost is around $12 per user per month."

"I'm not sure about pricing, but I believe Domo is quite costly. Prior to joining this organization, I had a Domo license with my former employer and I think that license was around $500 to $600 annually. That was for a single license. I think it varies, depending on the organization that is acquiring Domo."

"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."

"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."