Coalesce
Standardized ELT templates have accelerated delivery while API and UI flexibility still need improvement
What is our primary use case?
I have chosen Coalesce.io to replace PowerCenter, and we are doing the ELT work for VodafoneZiggo with the help of Coalesce, which provides a way to streamline and standardize our working process.
For VodafoneZiggo, we have created templates from data ingestion, starting from data ingestion through exports, which we provide to downstream applications as a file. When I need to onboard a source in VodafoneZiggo or in our data warehouse, we use a data ingestion template that we have created which can read files from S3, whether XML, JSON, or CSV. Using that template, we can load the data into Snowflake, and then when the data is in Snowflake, we load the data using another three templates of Data Vault: hub, link, and satellites. That is our warehouse where we store the data for years, and from there, when the data is loaded, we load the data into our business data vault, which has another three templates that we have created for users to use. Finally, when the data is in the business vault, we load the data into Data Marts, which are dimensions and facts. If someone wants to give a file to a third party or within VodafoneZiggo, we have created export templates that can be used to export the data into a file. The advantage of Coalesce.io is that if a company has a good naming convention, a lot can be done under the hood in the template, and developers have to do very minimal work on the template, so there are fewer chances of making mistakes or typos.
Regarding my main use case with Coalesce.io, I would say the APIs are really helpful in retrieving log information and dumping it into Snowflake. We are looking for those APIs to create nodes in bulk, which helps us in migrating simple mappings of PowerCenter into Coalesce, and the advantage of Coalesce.io is the bulk edits that we can do at the node or column level. For example, if we want to change a column end-to-end, we can just do a bulk edit and replace the source with a new source. I also appreciate the column level lineage; if the developer fills in the source column correctly, you can see the usage of that column along with the transformation from the ingestion node to the export node. If there is any change in the middle of your pipeline, you can easily find out where the change will impact and who will be impacted by it. The introduction of the SQL node is a game-changer, at least in VodafoneZiggo, because many SQL enthusiasts can simply write their SQL, and based on the template, it will create the mapping grid, map the data type, and create a table or view based on the template we have set behind it.
What is most valuable?
The best features Coalesce.io offers in my experience include lineage, which is the most important from the Ziggo perspective, and the APIs, which I would rank as the second most valuable. The third feature is the bulk edit option, so we don't have to do repetitive tasks again and again. The new SQL feature they are introducing, where you can dump your SQL and have your table or view created without manually creating columns, is also valuable. These are the four features I appreciate the most, and the fifth one would be the recently implemented GUI change where you can put a node in a spotlight to see the upstream and downstream based on what you need, setting up the depth and those settings.
Coalesce.io has positively impacted my organization by reducing our development time and the time to market from around 15 days to a couple of days. This is the biggest impact we have experienced, and we are able to enforce a standardized way of working among developers, eliminating silos or customized solutions that developers create for themselves. If a satellite is loaded by ten different processes, all ten different processes generate the same type of SQL, making it easier to debug later if someone new joins the team. Additionally, since it is a SaaS solution, there is no need to maintain any software or install anything on laptops, which has helped us at VodafoneZiggo. Another feature is the API feature and the CLI command tool, which aid us significantly in moving from PowerCenter to Coalesce, enabling the migration of mappings from PowerCenter to Coalesce in bulk.
What needs improvement?
Coalesce.io can be improved regarding the APIs that still do not support all types of scenarios within a node, which is a blocking issue for us and potentially for other companies as well. If they could strengthen their APIs, that would help. The SQL node I mentioned can also be improved, as there are some issues or features that need refinement. Furthermore, the GUI can still be somewhat cluttered, and there could be more filters available in the deploy section to filter jobs and search for different jobs.
For how long have I used the solution?
I have been using Coalesce.io for almost two and a half years.
How are customer service and support?
I chose a rating of seven because the aspects VodafoneZiggo wants to achieve, such as customization, a standardized way of working, templating, lineage, and customer support for Coalesce have improved, particularly with the addition of new features which were quite slow in 2025 but now are more proactive and useful. Another thing I should mention is the AI part, which is improving. Coalesce.io's Co-pilot has evolved significantly from the first version to the current one, but there is still a need for improvement, such as losing context and other issues. The AI Co-pilot could be noted as a sixth feature that I appreciate about Coalesce.io, as it handles basic tasks if I give it an example.
Regarding Coalesce.io's AI capabilities, I would rate the accuracy and reliability of the output from Co-pilot at about 60 percent because it sometimes hallucinates or gives a different answer for the same question. Therefore, I would estimate it at 60 or at most 70 percent.
What was our ROI?
I don't have specific numbers or costs because I don't look into that part, but I can say, for example, that when transitioning from PowerCenter to Coalesce.io, initially we would estimate it would take one sprint, around 10 working days, for one developer to create one hub link and satellite. When that developer started working on Coalesce.io, he finished in a couple of days or at most three days, including testing. Thus, I would say we saved about 70 percent, as one developer booked for 10 days eventually had an extra seven days for other tasks.
What other advice do I have?
From the governance and security perspective, Coalesce.io looks good from a user standpoint. However, we haven't yet explored the MCPs and those aspects of Coalesce.io; we are just using the inbuilt Coco. By nature, Coalesce.io is a metadata tool, so there is not too much worry until we start using MCP servers extensively, which we plan to do in the near future.
If you want to standardize your ELT process and are more into SQL-related tasks, then I think Coalesce.io can be your way forward, as it offers low-code development and allows you to define your path for your organization. In such scenarios, Coalesce.io can be a good choice, but I haven't yet explored whether Spark can be utilized or if those functionalities are feasible using DataBricks.
I believe our relationship with this vendor is just as a customer; I don't know if we have any other business relationship such as a partner or reseller. My overall rating for this product is seven.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Visual data pipelines have accelerated migration projects but still need broader platform support
What is our primary use case?
My main use case for Coalesce.io typically involves building pipelines, as I was working in a data migration project where I source data from the source system and move it to the target view using intermediate stages such as stage nodes and dimension nodes.
There was one module for which I had to work, so I created sources for that module, including customer dimensions and raw data for customer sales. Once that data became available from the upstream process, our pipeline started executing, reading data from the raw sources, staging them in stage nodes, and moving it to the dimension node where I created type two dimensions, after which the data moved to the fact node. Once the data was available in the fact node, that data was consumed by the downstream team for reporting purposes.
I have covered my main use case with Coalesce.io.
What is most valuable?
The best features Coalesce.io offers include the user interface and column-level lineage, which allows me to add an extra column to upstream and downstream stages by clicking on one stage and selecting others to propagate that column, making it easy to manage lineage at the column level. Unlike DBT, which shows only job level or model level lineage, Coalesce.io provides a great column-level lineage feature.
Coalesce.io has positively impacted my organization by making it easy to build and maintain the pipeline, providing traceability, and enabling easy debugging at both the pipeline level and Snowflake level. If I create a node and declare the metadata, I can refer to a specific source, and any issue will be highlighted for fixing there. If there is also a SQL level issue, it is highlighted at the interface, making debugging easy.
What needs improvement?
Coalesce.io is compatible with Snowflake only, so it must be configured with other platforms such as Databricks and BigQuery, which is a limitation and a drawback.
Coalesce.io should work on the aspects I highlighted, particularly making it compatible with other popular platforms such as Databricks, BigQuery, and Redshift, among other tools.
For how long have I used the solution?
I have been working in my current field for almost five years.
What other advice do I have?
I chose a rating of seven out of ten because of its limitations with compatibility to platforms such as Databricks and BigQuery, which prevents me from giving it a perfect score. However, it is still a good tool, being easy to implement, maintain, and featuring a good user interface that requires no coding work.
If others are not much interested in writing code or SQL, then they should definitely consider Coalesce.io, which provides a good user interface that is easy to maintain and trace in case of a pipeline failure. With the column level lineage feature, backtracking errors and finding data propagation roots becomes easier, decreasing implementation time significantly. What previously took three months can now be done within four weeks.
Coalesce.io has helped me develop projects faster, as it is easy to implement and maintain, reducing execution time by thirty to forty percent, while also helping me design a modular approach.
I rate Coalesce.io a seven out of ten.
Visual data modeling has accelerated non-technical workflows but still needs richer edge-case support
What is our primary use case?
My main use case for Coalesce.io was with a healthcare provider client whose team was not particularly tech savvy, so we wanted something easy to use. I was debating between two options: Coalesce.io and DBT. Coalesce.io had a GUI interface where I could drag and drop objects and build easily, so I was exploring it for building data vault models.
For that specific use case, I was able to accomplish what I was trying to do during the demo, but we encountered certain scenarios such as post-hooks, update statements, edge cases, or particular SQL query modifications and custom cases that could not be implemented through the GUI interface. Additionally, jobs that were interdependent on each other and orchestration features were not available at that time, which made us reconsider our options and ultimately go with DBT since it was open source and DBT Cloud had all the features we wanted.
I used Coalesce.io to build a data vault model by reaching out to the Coalesce.io team when the initial account provided to us did not have access to packages used for data vault modeling. They enabled a package specific for data vault modeling within the account. In that specific scenario, we wanted to replicate or build a small demo for the client to show them how we could leverage Coalesce.io to build data vault models. In data vault, we have a use case of needing to build multiple objects for creating dimensions and facts with an intermediate layer of hubs, links, and satellites. We used the package provided by the Coalesce.io team, which streamlined the process of creating these objects and provided a template that had all these columns in a particular format. We only needed to enter the column names and drag and drop to create our final model, which was very convenient. However, there were some problems and nuances due to which we went with DBT.
What is most valuable?
Some of the best features that Coalesce.io offers include the easy graphical interface where I can see the data flow, lineage graph, and how the data is moving from the source to the end target table. It has an easy drag and drop interface so I do not need to write SQL queries. Especially for my use case of data vault modeling, which required a lot of coding, using Coalesce.io would reduce the development process and I could quickly develop models.
Coalesce.io has positively impacted my organization by being a tool that can be leveraged by a non-technical team, especially business analysts who are working on bringing data from different sources. This is particularly beneficial for those who do not prefer coding or want to build their data models as quickly as possible. That is what I would consider to be the best use case for any organization.
What needs improvement?
Coalesce.io can be improved by making it handle more edge cases and providing better documentation. When I was initially working and trying to find information, there was not much available on their official website. Documentation with screenshots and steps on how to leverage this tool should be developed. An online community was not present either, which would help users deal with any issues or errors they are facing or ask developmental questions related to edge cases that are not generally used. I believe those are some of the things that can help the community of developers using Coalesce.io.
For how long have I used the solution?
I have been using Coalesce.io for two months for a demo in my previous company.
What other advice do I have?
I cannot think of anything else to add about the features since I used it only for two months, and it has been a while since I used it.
I saw measurable benefits during my demo since I found that the general impression was that I was developing much faster, and the development time was saved significantly. Work that could take me a day could be done in an hour or so, so I believe time saving is the most important factor.
I did not explore Coalesce.io's AI capabilities much, so I cannot provide an opinion on its governance and security.
While I was using Coalesce.io, it was a very new tool and I did not come across its AI capabilities, because it was mostly an open account I was using and it did not have those capabilities at that point in time, which was around last year, probably in 2024. So it did not have many capabilities at that point in time.
I would rate this product a six out of ten.
Streamlined data pipelines have accelerated student survey reporting and simplified handover
What is our primary use case?
I have used Coalesce.io for one year and twelve months, setting up a data pipeline for the student survey system at the University of Sydney.
The main use case for Coalesce.io is the developed data pipeline that was used by Coalesce.
We had an Oracle database that I connected, and for orchestration, we used Control-M. For the pipeline development in terms of setting up the workflows, we used Coalesce.io.
What is most valuable?
The best features Coalesce.io offers include lineage and ease of use, allowing us to easily create workflows in both the dev, test, and prod environments, and we were able to replicate those fairly quickly and create those pipelines much more easily.
The lineage feature helped our team significantly because once we completed the project and it was given off to the data engineering team, they were able to follow the workflows, which was a very big plus. We did not have to do an extensive amount of documentation, and all of that was embedded in the workflows and very easy to provide information to the data engineering team for business as usual.
Coalesce.io has positively impacted my organization by allowing us rapid build of data pipelines so that workflows and deploying the solution much more quickly increased the velocity of implementation.
What needs improvement?
Some of the improvements for Coalesce.io could be related to the artificial intelligence feature, perhaps some sort of a wrapper around it.
If the AI-driven feature is embedded, it can guide workflows and make the pipeline development even much faster, acting as an agent that assists people to develop in hours rather than in months. That would be a great improvement.
For how long have I used the solution?
I have used Coalesce.io for one year and twelve months, setting up a data pipeline for the student survey system at the University of Sydney.
What other advice do I have?
My advice for others looking into using Coalesce.io is to give it a go and compare it against other pipeline tools such as DBT, Fabric, or Databricks to see how it stacks up. My review rating for Coalesce.io is eight out of ten.
Effortless Deployment, Exceptional UI
Streamlined Data Warehousing
Bulk Editing and Modular Pipelines Make Building Workflows a Breeze
Effortless Data Transformation with Coalesce
Coalesce Supercharges Data Warehousing with No‑Code Speed and Best Practices
Coalesce writes complex transformations for you and with proper best practices, allowing you to stand up an integrated data warehouse in significantly less time. The lineage feature makes it easy to troubleshoot errors and trace the root cause. The ability to propagate columns changes to downstream transformations with a few clicks saves hours of time per task. Using the software development best practices makes deployment fast and reliable. Onboarding new team members is very efficient - if they know SQL and understand data pipelines, then Coalesce is the most effective tool to quickly bring new team members up-to-speed.
It's also flexible enough to easily migrate from other platforms because you can easily drop your code into their AI engine and it will create the transformations for you. Whether it's a new project or moving away from an existing technology, you can implement fast and efficiently.
On top of the tools amazing features, the sales and support team members are the most responsive, knowledgeable, and helpful compared to any other software vendor I've ever worked with.
Lastly, they continue to add new features based on real feedback from customers to ensure we're always getting the best value for our money. Coalesce is easily one of my favorite products.
Low-code pipelines have accelerated team collaboration and simplified CI/CD development
What is our primary use case?
Coalesce.io is used as a main platform for developing ETL pipelines.
What is most valuable?
Coalesce.io allows you to create ETL pipelines in a low-code approach. It natively supports templates for integrating with different systems and is built to deeply integrate with Snowflake.
Coalesce.io is a very complete platform because it also integrates all the tools needed for building CI/CD pipelines and an AI agent to support developers in their activities.
Coalesce.io has impacted our organization positively by providing a low-code approach. It supports different sources, so we don't need to write custom code. It is also a collaborative tool, making it suitable for teams with a large number of developers.
What needs improvement?
At the moment, the only improvement I see is deeper support for AI agents to support the developer's job.
Coalesce.io is a very complete platform, but it could be an even better product if it supported more developer jobs, speeding up development.
For how long have I used the solution?
Coalesce.io has been used for one year and a half.
What do I think about the stability of the solution?
Coalesce.io is stable.
What do I think about the scalability of the solution?
As far as I have seen, Coalesce.io is very scalable. In case of excessive load, we can easily handle it by adding more resources.
How are customer service and support?
When Coalesce.io needs to be updated or maintained, we need to declare the maintenance window. We cannot use the tool during maintenance, but we try to keep maintenance time low to avoid any issues.
Which solution did I use previously and why did I switch?
We did not use any solution before Coalesce.io. We used a more raw approach for development and deploying on Snowflake. That's why we decided to standardize, improve, and be more efficient with development by introducing Coalesce.io.
How was the initial setup?
The setup of Coalesce.io was not complex, and the licensing is very clear.
What about the implementation team?
We were provided with official documentation and also had some introductory courses and lessons by support.
What was our ROI?
Unfortunately, I don't have any numbers to share, but Coalesce.io had a very good impact on development and was very appreciated by the development team.
What's my experience with pricing, setup cost, and licensing?
Coalesce.io was purchased through the AWS marketplace.
Which other solutions did I evaluate?
Different tools were evaluated as far as I know. I did not participate directly in the selection, and I cannot say what other tools were compared.
What other advice do I have?
Developers can share within Coalesce.io.
I would rate Coalesce.io as nine out of ten.
We do not track any metrics at the moment.
Coalesce.io is deployed in a private cloud.
When Coalesce.io needs to be updated or maintained, we must declare the maintenance window. We cannot use the tool during maintenance, but we try to keep maintenance time low to prevent any issues.
I don't have much information about security features.
Coalesce.io offers capabilities that we managed to use, but we also use external tools.
The Coalesce.io integration was planned to be smooth because before it, we used another tool, so we had to migrate what we had on the previous tool to Coalesce.io and then switch off when everything was done.
I suggest Coalesce.io to everyone who wants a collaborative environment deeply integrated with Snowflake that supports developers in their job.