Matillion is a productivity platform for data teams. Matillion's Data Productivity Cloud helps data teams – coders and non-coders alike – to move, transform, and orchestrate data pipelines with the goal of empowering teams to deliver quality data at a speed and scale that matches the business’s data ambitions. The vendor states enterprises including Cisco,
N/A
Yurbi
Score 8.0 out of 10
N/A
Yurbi is a business intelligence solution that is designed to bridge the gap between business users and intelligent data. It provides the business user with the ability to connect, secure, and collaborate with data to make better business decisions. According to the vendor, Yurbi brings the powerful reporting and analytical capabilities of traditional BI, but takes out the coding jargon – so that people can actually use it themselves.
As a 100% HTML5 application, Yurbi gives users and…
$24,000
per year
Pricing
Matillion
Yurbi
Editions & Modules
No answers on this topic
Yurbi
24,000
per year
Offerings
Pricing Offerings
Matillion
Yurbi
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
Billed directly via cloud marketplace on an hourly basis, with annual subscriptions available depending on the customer's cloud data warehouse provider.
Yurbi's pricing model is simple and predictable. User licenses start at just $495 per year and that includes all the powerful features of our platform. We offer named users, concurrent users, and public view or anonymous report licensing options. We also offer custom/hybrid pricing for vendors looking to OEM Yurbi.
It is very well suited for ETL on the cloud. Whenever there is something that can be accomplished with no code or little code, Matillion is a good tool. However, if your pipeline requires a lot of customizations, Matillion should be avoided.
The Yurbi Poduct is extremely well suited for organizations looking for a mature Business Intelligence and ad-hoc reporting tool. The strength of Yurbi is that it is highly customizable and can work in various environments.
We leveraged Matillion’s no-code principals to make data manipulation easy for our internal customers. People who don't know how to use SQL no longer need to. Everything in Matillion is self-explained with no or little coding.
We connected Matillion to our data warehouse to allow people to read raw data, transform it, then write results back to their sandbox databases. The drag and drop component design allowed customers to create complex data models at the speed of thought without any risk to production data.
With sharing capabilities between projects enabled, everyone was able to help each other when questions arose which instilled a strong sense of collaboration and community.
Yurbi allows us to build customized Dashboards for specific users. Once the initial Dashboard is created, the user themselves have permissions to customize the Dashboard to suit their needs. The flexibility is there for a wide set of users.
Yurbi product is highly customizable. We looked for a Business Intelligence product for quite some time that could be customized to work with different types of data sets. When we started considering Yurbi, it was evident from the beginning that the product could be customized very quickly to work within our environment and our specific data types.
The Yurbi product stays a step ahead with the changing market being focused more for the tablet and smart phone user population. As our customers first started to use iPADs and iPhones, it was great to see that an upgraded Yurbi product was readily available for use for the iPAD/iPhone set of users.
I think a non-CLI approach to installing and uninstalling python libraries would be nice. I mean, it isn't difficult to install a python library via Linux or CLI, but I imagine most companies don't feel comfortable allowing Matillion users to go on a virtual server and installing it themselves. Requirement.txt file for installing libraries would be simple, and maybe that could also be used to uninstall libraries as well......or maybe the library gets automatically downloaded if it is imported into a python script but the library doesn't exist.
Python Component is lacking very much in terms of UI. It would be unrealistic for me to suggest Matillion build its own EDI, but it would be nice if a python component could connect to a local IDE. Right now, if you want to write any decent length python code, you are going to be stuck copying and pasting your code from your local IDE.
It is also very difficult to debug in Matillion because you can't set breakpoints. Local IDE integration can resolve that.
I would like to have more templates to copy from for certain simplistic scenarios. For instance, a template for a job that fails which sends an AWS SNS with the Job name, component it failed on, and the error message. It wasn't as simple as I thought it would be to figure out and having to use a shared job for such circumstances can be painful because you have to export a bunch of variables.
There should be a drop down list for Global Matillion variables as it is difficult to remember at times.
While the Yurbi Developer tool is highly mature, there have been cases where building specific complex reports within Yurbi required extensive support directly from the vendor (and even some Yurbi product customizations). It would be great if the Yurbi Developer tool could be slightly refreshed to make it easier for more non-technical users to build more complex reports within Yurbi.
Over years of usage of the Yurbi product with growing set of available reports to run for users, it's easy to get unorganized in terms of being able to find the correct report to run. It's highly adviseable if future releases of Yurbi began offering features to organize all reports a little better within the product (including an audit trail of reports that users typically run to make it easier for them to go back to the right reports).
We heavily use the SMTP configuration within Yurbi to set up auto-email notifications to specific set of users with requested reports. At times, the SMTP service becomes unavailable and Yurbi product is unable to send these emails to the users. Besides not receiving the email, it's easily evident that the SMTP service connection failed. It would be great if future versions of the Yurbi product would alert the user of the failed SMTP connection on initial Yurbi login so the administrator becomes aware of the issue and can take action to resolve the problem.
With the current experience of Matillion, we are likely to renew with the current feature option but will also look for improvement in various areas including scalability and dependability. 1. Connectors: It offers various connectors option but isn't full proof which we will be looking forward as we grow. 2. Scalability: As usage increase, we want Matillion system to be more stable.
The Yurbi product has been perceived very well by our customers. They have continued to use it for years and the user population has only expanded. Customers love the flexibility and large set of Dashboards and reports that can be made available within the product quickly and efficiently.
It has been easy to train new employees who don't have previous experience with Matillion. It is quite self-explanatory. There are quite a few things that can be done with Python, however, we have not really looked into this feature much but likely will do in the future. Mostly, it is drag and drop of components and environments can be set up so easy to set up connections as well.
The Yurbi product is incredibly easy to use and very intuitive for the user. The environment is highly customizable to the user's own preferences which is the best part.
Overall, I've found Matillion to be responsive and considerate. I feel like they value us as a customer even when I know they have customers who spend more on the product than we do. That speaks to a motive higher than money. They want to make a good product and a good experience for their customers. If I have any complaint, it's that support sometimes feels community-oriented. It isn't always immediately clear to me that my support requests are going to a support engineer and not to the community at large. Usually, though, after a bit of conversation, it's clear that Matillion is watching and responding. And responses are generally quick in coming.
Matillion ran circles around Stitch and Striim both in functionality, setup, and performance. There was no real comparison. Fivetran massively outperforms Matillion in pretty much every facet of the production from setup, maintenance, visibility, and usability. It already has the ability to connect any data source to a destination regardless of database type. Why we chose Matillion over Fivetran is that, for our current needs, Matillion provides us with the functionality that we need and a much more competitive price for a smaller company.
I have been able to connect Matillion to AWS Aurora Databases, MySQL databases, Rest APIs, Files in AWS S3, etc. Being able to load all of that disparate data into one datalake has made data mining and reporting a lot simpler. I wish everything could be implemented as easily as Matillion.
