Fivetran replicates applications, databases, events and files into a high-performance data warehouse, after a five minute setup. The vendor says their standardized cloud pipelines are fully managed and zero-maintenance. The vendor says Fivetran began with a realization: For modern companies using cloud-based software and storage, traditional ETL tools badly underperformed, and the complicated configurations they required often led to project failures. To streamline and accelerate…
$0.01
per credit
Maia by Matillion
Score 8.5 out of 10
N/A
Maia by Matillion is an autonomous data engineering platform designed to automate the lifecycle of data pipelines through AI-driven orchestration. The solution functions as an enterprise "digital workforce" that translates natural language requirements into production-ready DataPipelines, leveraging a Pushdown Architecture to execute transformations natively within cloud data warehouses.
$2.50
Pay as you go per user
SAP Data Quality Management
Score 8.9 out of 10
N/A
SAP Business Objects Data Quality Management embeds data quality functionality into SAP applications.
N/A
Pricing
Fivetran
Maia by Matillion
SAP Data Quality Management
Editions & Modules
Starter
$0.01
per credit
Standard
$0.01
per credit
Enterprise
$0.01
per credit
Developer: For Individuals
$2.50/credit
Pay as you go per user
Basic
$1000
per month 500 prepaid credits (additional credits: $2.18/credit)
Advanced
$2000
per month 750 prepaid credits (additional credits: $2.73/credit)
Enterprise
Request a Quote
No answers on this topic
Offerings
Pricing Offerings
Fivetran
Maia by Matillion
SAP Data Quality Management
Free Trial
Yes
Yes
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
Optional
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.
Matillion requires a lot more initial setup effort and the resulting schemas are also much more "raw" data than the nicely cleaned schemas which Fivetran provides. Therefore it would also require more (manual) post-processing efforts compared to Fivetran. So the savings on time …
Fivetran is much easier to set up and maintain. Airbyte still had a degree of technical knowledge requirement that we didn't have the resources to commit. Fivetran allowed a non-technical employee to establish pipelines and immediately start using the data without having to …
We never seriously considered using anything else. Our data engineers had used Fivetran extensively in previous roles so when it came time to make a decision, there wasn't much of a process. They gladly signed the contract with Fivetran pretty quickly.
Fivetran came well with the connectors' availability and updates with the source changes. We had an idea on data requirements in our case which helped us to work out on cost implication and take a decision for Fivetran as a data provider for our organization. These were 2 …
Fivetran is more intuitive and easier to use than code-based ETL/ELT tools. The data modelling Fivetran performs makes the data more usable more quickly. Fivetran's dbt support and integration is unique.
Honestly, we haven't done much investigation in a while, it just works 360 days of the year. The other five days there may be a hiccup that will throw us a day off of data, but it gets caught up in the end.
Matillion gives great ability to connect to variety of sources and bring data into cloud data warehouse using connector based approach with which we can build complex transformation jobs which can do automated data fetches from your sources.
Matillion has better capabilities and better built-in elements that saves your time and efforts. also the connectivity across multiple data warehousing tool is better in Matillion. even the performance of the pipeline and the time required to create a particular pipeline is …
My manager selected Million based on his previous work experience. He believes it is easy to use and maintain, cheaper than competitors, and suitable for our use case.
The only other ETL tool I've used was SSIS. At first I thought Matillion seemed "kiddish" after using the polished Microsoft tool but now I think Matillion is easier and can do much more as it has so many built-in connectors etc. We selected Matillion at our job because of …
n/a -- joined the team after they already were established in Matillion. Have had brief looks at other ETL products but found nothing compelling enough to suggest a change.
We selected Matillion primarily because of it's ability to connect to numerous data sources and easily create transformation jobs. While FiveTran does a better job managing and examining deltas, it is not easy to use and is very non user friendly. SSIS was not a good fit for …
Fivetran offers a managed service and pre-configured schemas/models for data loading, which means much less administrative work for initial setup and ongoing maintenance. But it comes at a much higher price tag. So, knowing where your sweet spot is in the build vs. buy spectrum …
Cost and ease of use were better for our purposes. Matillion distinguishes itself from Fivetran and Snaplogic through its user-friendly design, no-code interface, in-depth transformation capabilities, allowing for complex data manipulations directly within the platform, …
We decided to move forward with Matillion because it was the best tool among tools that support both ingesting data from a source system to a target database and running transformation workflows on it afterwards. Fivetran and Airbyte only support data ingestion and we had our …
The Matillion selection was not my decision. But I think it's a good enough choice. It is especially valuable that the team can learn Matillion easily and that the project can be understood by the entire team with the visual environment instead of complex ETLs.
Both the Databricks platform and Dbt Cloud are more powerful from the point of view of the development lifecycle and data use cases covered. They are also more complex and require specialized data engineering skills to be used. Matillion has a lower barrier of entry for small …
Removes most of the complexity around setting up and preparing things. If you could describe with words what needs to be done to move data from A to B, the implementation in Matillion would probably be the most similar in terms of simplicity of understanding what you are doing …
Matillion is a good tool for integrating multiple clouds. Informatica has been a market standard for many years, it provides multiple capabilities for data governance, data quality, etc. However, Informatica is pretty expensive compared to Matillion. Also, Matillion is more …
IDQ was a best fit for our data quality management, but we didn’t have a lot of Informatica services to integrate with it hence we implemented SDQ instead.
SAP Data Quality Management has close data monitoring, which helps in close data cleansing, and the entire filtration process. Besides, has proper address verification, with customer details being enhanced. Again, SAP Data Quality Management makes a profitable way of predictive …
SAP Data Quality supports the integration with significant sources, but security and accuracy are maintained and enhanced. Besides, SAP Data Quality eliminates the data duplicates, a solution that saves on space, and improves the loading power of any system. More so, SAP Data …
SAP Data Quality has the data connectivity part, that ensures quality and standard evaluations are made. Further, SAP Data Quality has an incredible service chart, that makes all the client's complaints extensively addressed and service satisfaction maintained. Finally, SAP …
I love the SAP Business Objects Data Quality Management and its ability to create reports quickly and accurately as well as being able to export information and send to others very quickly. My experience has been fantastic and has helped clean up so much bad and useless data …
The client was on a SAP platform for most of their applications and also is planning to implement SAP Hana very soon. This tool was fitting good for the requirement of the client to manage the quality of the data and hence adapt it in the system. Also, it can go well with the …
This is the only program of its kind that I have any experience with. I have heard of a few others. From people I have talked to, they have seen in other programs some of the options that I would like to see in SAP, but to me where our greater needs are, SAP is still the better …
[Fivetran is] very well suited when you are using popular and common data sources, such as the major ad platforms, and SaaS platforms such as Salesforce. If the majority of your data sources are custom internal applications or databases, may be less value as you aren't leveraging the delivered connectors.
Great: Need to query simpler APIs, or utilize well known services such as GSheets etc.? Matillion has got some of the best and easiest to use connectors out there. Not so great: Do you need have a competent CI/CD flow that you will be able to update / compare from Matillion as well as other sources at the same time? Good luck, you will need to be extra careful, as you might have to have a deeper dive into your servers Terminal each time you have a git conflict.
When reporting, we use accurate data with no duplications since they are addressed by SAP DQM, we get the right target audience by analyzing marketing data, and also helps us to understand the current situation of our firm by comparing metrics.
Static and monolithic, it will show its limits when running multiple concurrent jobs.
Github and versioning implementation is messy and broken. Don't use it.
There's not way to see/query the system resources, just wait for a server to crash due to out of memory. An admin panel would be appreciated + some env variables with updated info.
API implementation is cumbersome and limited.
There's no concept of hub and worker engine, everything happens of the same server (designing workflows and executing them). Having separate light ETL engines to run job could be better. (sort of docker/kubernetes/lambda functions).
Handling of variables is limited especially for returned values from sub components.
Some components could return more metadata at the end of their execution instead of the standard one.
Billing is badly designed not taking into account that the server is hosted by the client. Expensive.
We had several issue with migration where starting a new instance was required and then migrating the content. It was painful and time consuming also have to deal with support and engineering team on Matillion side.
CDC doesn't work as expected or it is not a mature product yet.
Matillion is easy to use and flexible to debug. Performance are good and support is giving us a good service level. There are still some technical points to be developed more (such as SAP extraction). but easy flows are really fast to be developed. We are also using a tool for migration from other tools, and it is useful as Matillion is producing XML code.
Very easy and intuitive to setup and maintain as there usually are not that many options. Very well documented (e.g. how to setup each connector, how the schema looks like, any specific features of this connector etc.). Also the operation is intuitive, e.g. you have status pages, log pages, configuration pages etc. for each connector.
Easy tasks are really easy, and complex tasks are still possible. With prior knowledge of general data warehousing principles and experience with other data transformation tools, it's straightforward to get familiar with and use Matillion. I initially used minimal external support from a partner for some more complex tasks but very soon could work entirely independently with Matillion.
It runs pretty well and gets our data from point A to point cluster quickly enough. Honestly, it's not something I think about unless it breaks and that's pretty rare.
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.
Fivetran came well with the connectors' availability and updates with the source changes. We had an idea on data requirements in our case which helped us to work out on cost implication and take a decision for Fivetran as a data provider for our organization. These were 2 places where Fivetran out-performed, other vendors.
We selected Matillion primarily because of it's ability to connect to numerous data sources and easily create transformation jobs. While Fivetran does a better job managing and examining deltas, it is not easy to use and is very non user friendly. SSIS was not a good fit for our team and required a significant amount of attention and server management that we did not want to invest in.
The client was on a SAP platform for most of their applications and also is planning to implement SAP Hana very soon. This tool was fitting good for the requirement of the client to manage the quality of the data and hence adapt it in the system. Also, it can go well with the BO reporting.
We're using Matillion on EC2 instances, and we have about 20 projects for our clients in the same instance. Sometimes, we're struggling to manage schedules for all projects because thread management is not visible, and we can't see the process at the instance level.
Time savings -- we could custom code nearly everything Matillion does, but it would take days/weeks instead of minutes/hours.
There's a bit of a learning curve to truly unlock Matillion's potential, and that can be frustrating for some new users, but once you get over that curve, the possibilities are endless.
It allows us to centralize the hundreds of way to bring data in, so that even if you have to troubleshoot what someone else wrote, it's easy to jump in and understand what is happening.