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
OpenText Availability
Score 10.0 out of 10
N/A
Carbonite acquired Double-Take, a data replication and disaster recovery option, in early 2017. The technology now powers OpenText Availability, the high availability and data replication product.
N/A
Pricing
Matillion
OpenText Availability
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
OpenText Availability
Free Trial
Yes
No
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.
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.
I believe it would work well with continuous replication in a DR scenario with no time limits and having the ability to fail back is a bonus, but in a one off move the decision to restrict the time it can sync for has proven to be an issue for us.
A product is worthless in my opinion if you don't have a great support team to work with. I've had issues with replication jobs that were resolved quickly and easily by the support team.
DR - Doubletake is the only tool that I'm aware of that can handle DR replication of both physical and virtual environments. There sre others, but they use a snapshot technology, where doubletake has continuous replication of data.
Move - we have moved physical and virtual environments from around the world without ever having to leave the office. One of the companies we migrated started off with their equipment in Switzerland, and after the servers were in a fully protected state in the US, that failover to the new location took 45 min.
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.
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.
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.
Cabonite Availability is a very practical and useful tool that can help any business weather any type of IT disaster. The ease and quickness of restoring data helps us provide as seamless an experience as possible. Many times our customers will never know there was an outage. This brings confidence in our brand and improves our organization's standing and reputation.
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.
Once through to support it is very good and they have assisted us through a number of issues. I don't always think that they provide a solution, more a workaround, but in a move situation where each copy is moving once, that isn't an issue. I'd be more concerned if we were using it to manage a DR scenario.
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.
It is better for critical apps than Veeam due to the lower RPO. Veeam is favoured by some customers due to it's attractive price point. Zerto is a very strong product and is innovating continuously. I don't see so much of this from DoubleTake.
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.
