Actian Ingres vs Domo comparison

"The deployment of our solution across a number of servers using Ingres .NET has meant that we can protect the database server behind a highly secure firewall and deploy the front end solutions on a normal web server."

"The most valuable features for us are reliability and performance."

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

"The dashboard is the most valuable feature and allows for customization to create and share reports."

"The best feature of Domo is that it's completely on the cloud. I also like that you can handle data end-to-end without having to depend on multiple tools. Another specific feature I like the most about Domo is Magic ETL because, through it, you can do all your expression, transformation, and loading activities very smoothly. The tool also follows the lineage concept, so you can understand what kind of transformations took place on a particular data set. You can find end-to-end data from the source until it has become the final output or the final data set. Whatever happened to a particular data set, you can understand it through the Domo lineage, and that isn't possible in most of the tools available in the market, but in Domo, that's available. The tool is also solid and because it's on the cloud, it uses multiple data engineering in the backend and multiple algorithms in the back, behind the scenes, resulting in a great performance. For example, if an end user such as the CEO or COO opens a report or the dashboard and it takes more than ten seconds, the end user won't be interested in looking at that report or dashboard, but Domo enables better performance and there's usually no performance issues from that tool."

"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 find the ease of using the solution valuable."

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

"It has the best GUI. And it already has an ETL tool embedded in it..."

"In Workbench 5, they have come up with a very useful feature called Upsert. When you're pushing data into the data set, if the data is already available it will update the data, and if that the data is not there it will insert it. That is a beneficial feature that they introduced in the latest version."

"The ability to reset the log file without stopping the DBMS would be helpful for us."

"The seamless integration is a bit of an issue."

"In Tableau, you can create virtually any kind of visualization. Based on your creativity, you can create a visualization on a human body structure, you can create a visualization on anything that you want. But Domo is limited to a few kinds of visualization views: standard things like bar, pie, and some other charts... I would like to see them add new views for presenting the data in the visualization space."

"They could use more charts. They have had a very limited number of charts we can use. I believe, now, there are somewhere around 30 of them, but they could definitely use some more options."

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

"One of the improvements that could be made is related to improved storage options."

"Data integration is okay, but not the best."

"The preconfigured apps need to be more relevant to allow one, out of the box, to load data in order to use pre-set reports/views."

"There's a learning curve before you can get used to the solution."

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

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

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

"We are making money from Domo, and all our clients are happy with the information that they receive from it."

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

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

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