Domo vs Looker comparison

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

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

"In general, Domo is very powerful and very easy to use, relatively speaking."

"I mostly see it as an ETL which has many system connectors. It does a good job of ETL."

"This solution allows us to change our performance metrics and tracks our goals in real-time."

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

"We find the ease of using the solution valuable."

"I would rate the stability a ten out of ten. I didn't face any issues with stability."

"The stability of Looker has been good since I have been using it. However, it depends on what components are being used."

"We can centralize all our data models."

"The product is easy to use."

"From a developer's perspective, the way the functionality's being handled is great."

"It's quite effortless to navigate through various applications and review their updated data in real-time."

"Looker allows you to generate the most optimal SQL queries in a DC through UI actions. We had signed a contract with Google Cloud to use BigQuery. That was the primary reason we adopted Looker. It works better with BigQuery than any other BI platform. We also like how this tool was developed. It was designed with an eye toward microservices architecture."

"It is a pretty stable solution because it is a cloud-based product."

"It is expensive."

"The forecasting feature, the regression features, and the Python libraries could all be improved. They're all in beta."

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

"I would like to see more flexibility in their pricing structure. The trend is moving from database pricing to a user-license pricing model. That would be a benefit if they wanted to reevaluate their pricing structure."

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

"It's quite slow. We are using about 2,000,000 rows of data. Creating certain reports takes almost a couple of minutes, which should not be the case."

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

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

"The visualization capability of the product is limited."

"The main area of concern in Looker is probably related to blending the data from the different sources, including the data present internally in the company and on the cloud."

"Looker doesn't connect to Excel, which is a huge disappointment because a lot of data is presented in Excel. Also, it can't consume data directly from REST APIs, which is necessary. Looker needs to expand its horizons when it comes to data sources. The inability to connect to different data sources is hampering our use cases. Currently, it only has an ODBC connection that connects to a database. It needs to connect to other data sources, such as Excel, APIs, and different platforms."

"Stability needs improvement."

"Integrations with other BI tools could be better."

"The product does not have documented material."

"It needs to be more user-friendly."

"The integration with different databases must be improved."

"It is on the pricier end."

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

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

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

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

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

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

"The price of Looker usually depends on the solution's provider, but it is usually cheaper than the other products in the market. Looker is offered at different prices for different companies."

"Looker is expensive and could be made better by reducing it."

"It is cheap."

"I do not have to make any payments to use the solution."

"It's not cheap, but it's not expensive for big companies."