Domo vs Jedox comparison

"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 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 best thing is that the data storage is pretty much free. I can store as much data as I want, from different sources."

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

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

"The data certification feature, where the admin user can put a certified stamp on a data source so that other users can know that that is the correct and accurate data flow or data source to use, is a good feature."

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

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

"The ease of reporting is one of Jedox's most valuable features."

"The solution is very versatile."

"The customer porting is the most valuable feature."

"The system is quite flexible. Based on our requirements, we create different cubes that can help us to do complete planning."

"We can configure and have complete freedom while creating solutions."

"The Excel interface is designed to retrieve data from the database and send it back, which is a significant advantage."

"The ETL itself was pretty useful and it's integrated in the tenant itself. So the Olap service technology was impressive to me. In order to extract that and load it in the tube in the same tenant or the same tool that was something magnificent because I actually missed this in SEB. SEB requires another tool, and you have to integrate all the tools together. But for Jedox, it was in the one tool."

"We use the tool for performance management and planning."

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

"Their STK is not up to date and you can't access it on their website. They have a private STK to access resources in Domo."

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

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

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

"I would like to be able to drill down more when there is a particular area where there is a problem. I don't clearly see that in Domo at the moment."

"Jedox should improve the design and server issues."

"More emphasis is needed on the availability of the learning aspect of the solution. Because unless you take up their course that enables you to be an expert in creating the report, you must seek help."

"From a development perspective, there's room for improvement in the area called the designer, where you actually build your reports to make it easier to manage the process."

"I don't find it particularly user-friendly."

"The tool has changed its pricing and it's now too expensive for small and medium organizations. I miss the open-source version which was free and we could do a lot of things with it."

"There is not much training for Jedox."

"The solution should enable a modern look and feel in the front end."

"Being an analytical solution, it should have more visualization options like graphs. When we are putting it, it should have more options. The UI can be made more modernized based on today's market. Sometimes, when we are doing heavy reports or dashboarding, there is a bit of a performance issue because it is pulling up a huge amount of data. That can be improvised by buffer memory and getting some buffer memory feature into it. It is a bit complex because it is a CPM solution. It helps you to get the information based on the different tools that we are using, which is a bit of a complex thing. It is not as easy as Microsoft Power BI. It is also not that easy as an implementation piece. It takes time to convert the business requirement into the proper solutions in the tool, which is time-consuming. It took about eight months to do the complete implementation. We got some training from the partner and the Jedox team, which helped us later on in pulling things forward, but too much learning is required, and too many possibilities are there."

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

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

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

"They've built an "app economy." Some of them are really expensive, so they're not for startups and smaller companies. They're more like enterprise tools. We couldn't afford some of them, because they were so crazy expensive. But if I was working for a bank, insurance company, or some bigger corporation then, for sure, you could justify those prices... It was silly expensive back then and it probably still is, or even more expensive."

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

"It is on the pricier end."

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

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

"The solution's pricing is specific to your requirements."

"Jedox was a bit cheaper compared to Calumo."

"We paid a one-time fee, which included product purchase, licensing, and first-time implementation. We are paying for the maintenance regularly."

"Excellent value for money."

"The product’s pricing will not be suitable for setting up a small solution."

"If you are using SAP, then you will have to take an SAP Connector license. The license across the tool is paying for the people who are using it as an admin or as a normal user. They can work out those costs in a manner that can help. This can also be a point of improvement where they can work out the costing, and the developers have a specific licensing cost. The normal users, who are going to do probably data entry or just going to view the dashboard, can have a separate license cost."