Matillion is a data pipeline platform used to build and manage pipelines. Matillion empowers data teams with no-code and AI capabilities to be more productive, integrating data wherever it lives and delivering data that’s ready for AI and analytics.
$2.50
Pay as you go per user
SAP Integration Suite
Score 8.5 out of 10
N/A
SAP Integration Suite is an integration platform-as-a-service (iPaaS) that helps quickly integrate on-premises and cloud-based processes, services, applications, events, and data. It is used to accelerate innovation, automate more processes, and realize a faster time to value.
$11,199
per year
Pricing
Matillion
SAP Integration Suite
Editions & Modules
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
Matillion
SAP Integration Suite
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
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.
Access to free tier services does not expire while there is an active Pay-As-You-Go or CPEA account with SAP. Once a free tier service limit has been reached users have the option to update from a free to a paid service plan in the same account.
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.
In our case to have a such a poweful middleware in the cloud, give us a lot of benefits such as maintenance and support. In the integration part to be able to connect SAP and Non SAP applications makes SAP Integration Suite a good investment when our master data in this case is in S4HANA. Less appropriate is that sometimes the updates in production tenant failed and they have to downgrade or repair the issues. Affecting the usage of the tool. I guess SAP team have to be more aware of performing the changes and tested well on development environments and then when they know for sure that is the correct way to go with the update put it in production.
Matillion is brilliant at importing data -- it would be amazing to have more ways to export data, from emailed exports to API pushes.
Any Python that takes more than a few lines of code requires an external server to run it. It would be great to have more integration (perhaps in a connected virtual environment) to easily integrate customized code.
Troubleshooting server logs requires quite a bit of technical expertise. More human readable detailed error handling would be greatly appreciated.
Provide more pre-built integrations to use within SuccessFactors or other modules instead of everything having to be custom built
Support is unable to provide advice on custom builds so you often have to engage a 3rd party partner
Works best when you have the functional and technical teams working together. Otherwise, the system is too technical for a functional user to create integration and a technical user not always understand the functional perspective
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.
It is in place, our system integrators are familiar with it, and it fits into the ecosystem. A better user interface, flow build and debugging experience would see it grow, many technical staff do not enjoy using it for this reason, however it is quite capable and powerful behind this one shortcoming.
We are able to bring on new resources and teach them how to use Matillion without having to invest a significant amount of time. We prefer looking for resources with any type of ETL skill-set and feel that they can learn Matillion without problem. In addition, the prebuilt objects cover more than 95% of our use cases and we do not have to build much from scratch.
The user interface is messy and not intuitive. It has a steep learning curve, and flows developed around are easy to make a mess with layout and can be difficult to follow. The debugging is also quite difficult, it takes some time to figure out how to follow the flow and examine data. Error handling is also difficult and not intuitive, it is better to let some errors leak and monitor through ALM.
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 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 is essential to deciding which tool fits better. For the transformation part, dbt is purely (SQL-) code-based. So, it is mainly whether your developers prefer a GUI or code-based approach.
SAP Integration Suite was already part of our SAP stack, part of Business Technology Platform, with out-of-the-box integration with S/4 HANA transactional and ERP system that we are using as our main back-end. Thus, we are achieving significant Total Cost Optimization benefits or running both solutions on the same platform, hosted on Azure cloud.
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.
