Collibra Governance Overview

Collibra Governance is the #1 ranked solution in our list of Data Governance tools. It is most often compared to Informatica Axon: Collibra Governance vs Informatica Axon

What is Collibra Governance?

Collibra Data Governance Center is an enterprise-wide data governance solution that puts people and processes first, automating data governance and management to quickly and securely deliver trusted data to the business users who need it.

Collibra Governance is also known as Collibra.

Collibra Governance Buyer's Guide

Download the Collibra Governance Buyer's Guide including reviews and more. Updated: June 2021

Collibra Governance Customers

Ministry of Economy Science and Innovation, Aspen Insurance, Barry Callebaut, Colt

Collibra Governance Video

Pricing Advice

What users are saying about Collibra Governance pricing:
  • "I would say it's probably in line with what other vendors charge for licensing."
  • "I think they have a trust issue. I did not like the way they recently went through the process. They were like, "Finish this SOW first, only then will we sign the other SOW." Or, "Finish this code." I didn't like that much."
  • "I am not so much aware of price details. Initially, there was an add-on NuSoft license to use the DVC connector that NuSoft gives to create integrations, but Collibra is now phasing out of it slowly. Collibra is cutting ties with them is what we have been led to believe, and we have started developing on Spring Boot, which is open source."
  • "I think it is on a yearly basis, but I'm not involved with the pricing session, so I have no idea. There are several licenses for different models. You get one license per product, but a lot of features are controlled separately through different licenses. So, as and when you want to use a feature, you have to procure the license for that feature."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Chris Allen
Technical Product Lead at a insurance company with 5,001-10,000 employees
Real User
Top 5
Offers many features for the best relative price.

What is our primary use case?

Our use cases include connecting a lot of legacy data systems to our logical components. For example, if somebody has a question that they post to us and say, "Tell me everywhere in our organization where we have a policy stored?" the primary use case is to logically define what a policy is, and then we use Collibra to tie that logical construct to a technical implementation. We may have six or eight, however many, different admin systems. We bring in the schemas of the way that those systems look, and then how a policy exists in this database and this table and this column, for example, in… more »

Pros and Cons

  • "Collibra is very good at talking to modern database systems like a normal RDBMS, a DB2, or a SQL server or an Oracle."
  • "Where it isn't great is on older technologies that you'll typically find in finance or insurance industries, such as older types of data with VSAM or ISAM, or those types of older technologies. It just doesn't connect with them very easily."

What other advice do I have?

Everything seems to be going the route of software as a service these days. It does take away somewhat your ability to customize like you want. Some products allow you to do that better with their SaaS offering than others. I would say that the data catalog space changes quite rapidly. When we did our investigation a couple of years ago, Alation hadn't been in business that long, they've continued to grow and maybe their offering has become better. Just because we chose something two or three years ago, doesn't mean that we shouldn't re-evaluate that in another couple of years to say, "Is this…
Peggy McCoy
Stewardship Coordinator at a healthcare company with 10,001+ employees
Real User
Transformed our cross-functional business teams into one enterprise-facing view

What is our primary use case?

Previously, I was in high-tech, now I'm in healthcare. In both instances, we used this solution to increase data literacy and business literacy. In short, we were building out business glossaries, coming to an agreement on term definitions, understanding what reports mean, what the metrics and calculations mean — essentially getting it all documented in an enterprise-facing view. That was the bulk of the focus in my prior company — along with some reference data. At my current company, we are focused heavily on bringing in data dictionaries, including schema tables and columns, and… more »

Pros and Cons

  • "As far as the functionality of the tool is concerned, it's pretty slick."
  • "There's a lot of things available in their Data Intelligence Cloud that are not available on-premise."

What other advice do I have?

The question is how do you help new users understand and leverage this solution to get people to come in, start using it, and understand what they're doing? Well, we've got three people that help onboard our business users. Every use case is different because every business team wants to use the tool in a different way. It's all about business consultation, but Collibra doesn't have anything to do with that. I used to run a users meetup group for Collibra in the Bay Area. I've talked to many customers who have used Collibra, and all of them experience the same challenges — how do I get my…
Learn what your peers think about Collibra Governance. Get advice and tips from experienced pros sharing their opinions. Updated: June 2021.
512,711 professionals have used our research since 2012.
SS
Group Manager at a tech services company with 10,001+ employees
Real User
Top 10
Massive benefits to be reaped, but serious knowledge is required to operate it properly

What is our primary use case?

We're a very large pharmaceutical organization so it's difficult to quantify exactly how many users are using Collibra. Within our organization, there is a data governance team that we had set up. I am the person in charge of that team. While working on the data governance processes, we thought of leveraging Collibra for things like data dictionaries, developing data lineage, ensuring that business artifacts like KPI catalogs and board catalogs can be built within Collibra itself.

Pros and Cons

  • "In terms of data governance, as I mentioned, it can be a one-stop solution for all of your data governance needs."
  • "Recently, I find that the default process of issue management in Collibra is really complex — It wasn't really helpful to us."

What other advice do I have?

Before you deploy or implement Collibra, just ensure that you have certain use cases that really qualify for leveraging Collibra. Assessment and evaluation are really important, first. Benefit analysis is the most important key. What are the transformational changes that Collibra is going to bring? If it's going to improve your ROI by deploying it, then migrate over to it; just don't do it because everyone else is doing it — that's not a good enough reason. There are certain tools out there that can analyze data and generate reports with a few simple clicks. Collibra doesn't work like that…
SuChatla
Sr Manager - Enterprise Data Office at a healthcare company with 10,001+ employees
Real User
Top 5Leaderboard
Shows the whole history of data elements, though connectors could be improved

What is our primary use case?

I've been working with multiple companies, but with two of the companies we have been using Collibra mostly for data governance. With these companies, our use case is all about metadata governance, lineage, and data-related policy management. We're doing policy management directly inside Collibra and we're also using it for issue management on the analytics side. If someone has a data concern, they just call me in and then put that concern into Collibra as a front-end UI for the data stewards and data scientists, and we start processing them.

Pros and Cons

  • "I like the lineage feature the most because I don't think there's any other tool that actually depicts the data flow from multiple sources and the connectivities between every data element inside those sources."
  • "The connectors are not very sophisticated. They can do, for example, Informatica and Tableau, but the connectors themselves could be improved."

What other advice do I have?

It's a very niche product. It's nice to use and easy to promote. You don't have to have all the user licenses - you can also get the author licenses. If you have 10 author licenses, you can get up to 50,000 consumer licenses. It's nice to know you have a mobile component in that regard. If you're doing a lot of training as well, you need to do proper training with your data team, and with your business team, try to use it as a business tool instead of a technical tool. Employ it as much as you feed it, because then it's that much more useful. And then having the business rules, the data…
IS
Consultant II at a tech services company with 51-200 employees
Consultant
Top 10
User friendly and easy to set up with good documentation

What is our primary use case?

We have a client that was planning to do a digital transformation. They came up with the use cases and they have a couple of departments. They are mainly based on legal systems including corporate trust, etc., that they want the data to govern. Their requirement was basically if any new person is hired, they would have everything in Collibra, including all of the business glossary or the tables or the reports. Basically, everything for their onboarding process was available there. It was also necessary to give that to anyone that wanted to know about their department.

Pros and Cons

  • "It's not a complicated product."
  • "While connecting with the data source, it's not very easy. If there's a firewall, it is difficult to connect with the database. It's not easy when you are configuring on the database."

What other advice do I have?

We are Collibra Partners. We have a business relationship with the organization. If we have a Collibra expert on your team, it will be easy. Otherwise, new users should expect a bit of a learning curve. ANyone working closely with it should take some Collibra training alongside the product purchase. Professionals will help you and guide you in creating an organization level or department level unit with a glossary and everything. They can give you more insight. I'd also advise users to try to take the certification, which is free of cost in Collibra University, or try a partner training…
VB
Technology Analyst at a tech services company with 10,001+ employees
Real User
Top 10
A developer-friendly solution that lets you easily ingest the metadata and is good for documenting DPIAs

What is our primary use case?

I am using it essentially for the GDPR implementation over here in Europe. This is my second project on Collibra. Before that, I have worked on the CCPA part for a US-based project. I have worked on an on-prem solution and a solution on the cloud. I was the one who had created all the components on AWS because our client was not ready to move onto Collibra's cloud solution, but I believe they will be moving to SaaS soon. We are on version 5.7.5. Version 5.7 is the latest, but because we're not on SaaS, it's quite tedious to upgrade each and every environment. We have four environments or five… more »

Pros and Cons

  • "The catalog feature is definitely valuable because it makes ingesting the metadata of any application quite simple. You don't have to do things manually. You can just schedule an import, and it will just refresh the metadata of whatever application you want. That's what I like. I usually work on the technical side, and other than that, I usually create integrations. I integrate Collibra with different environments or applications. I'm a developer, so I cannot vouch for the business, but for me, it is quite developer-friendly with the Java API interface and the REST API interface that they have provided. It is good for creating dashboards based on the needs of each and every role. It can be user-specific or group-specific. We usually create dashboards and give them to our business users, and they are quite happy with that."
  • "It should have more integrations with things like CyberArk because its main purpose is GDPR implementation. We have to have more scope for things that implement more privacy. CyberArk makes sure your credentials are vaulted and your things are secure when you're creating your integrations or connecting to an application. I do believe that they are working on this feature."

What other advice do I have?

I would recommend this solution to others, and I would ask them to directly go for SaaS instead of going for on-prem because you get a lot more features. I believe the license is the same or similar, but I'm not really aware of the price points. The biggest lesson that I have learned from using Collibra is that being compliant is important, and we are helping our clients do that. You must have read about H&M and Citibank. They got charged a lot. I would rate Collibra Governance an eight out of ten. Because I'm not involved with SaaS, I am keeping two points away for that. After using SaaS for…
Ankur Agrawal
Data Governance Manager at a tech services company with 10,001+ employees
Real User
Top 10Leaderboard
Allows us to see end-to-end data life cycle and provides a lot of flexibility for customizations and options for implementing for different purposes

What is our primary use case?

We use it for metadata management, data lineage, and automated governance processes. I am working on the SaaS deployment, but I have also worked on the on-premise deployment. I am currently using its latest version.

Pros and Cons

  • "The end-to-end solution itself is great. The most valuable is the workload feature that Collibra offers. There is a vast amount of flexibility in terms of how much we can customize. It gives us a lot of options to implement for a lot of purposes."
  • "One problem is the data lineage, especially extracting the ETL transformation from different ETL tools and identifying how the data is getting changed from one layer to different layers and how the transformation is applied. It doesn't support all the ETL tools for extracting the transformation logic. It supports some of the tools, but there are still some tools that need to be supported. There is also a small pain point in terms of integration. There is a little bit of change in their strategy from Collibra's end. Earlier, they used to offer two solutions. One was out of the box, and one was a custom-built solution for which they used to provide a dual connector. Now the focus from the Collibra side is more on using the out of the box connector. They are discouraging doing the custom integration. That leaves us with two problems. The first problem is that the out-of-the-box connecter is not yet enabled for a lot of systems, and the second problem is that the out-of-the-box connecter has certain limitations. If we want to tweak those as per our needs, it is not possible. However, the custom-built is still supported, and you can still build a custom integration by using the API, but it is not very encouraged by Collibra. Its dashboard also needs to be improved. There are options to use the HTML code to customize your dashboard, but it has a lot of limitations."

What other advice do I have?

I would definitely recommend this solution, but I would say that before starting the implementation, just understand what the product is, what it can do, and what it cannot do. Don't focus too much on the technical aspects of the product. Data governance should be used from the business point of view. Data governance was a new concept for me. By using this product, I got to know a lot of different aspects of data governance, and how should you go about implementing it. One main lesson that I have learned from using this solution is that don't just focus on bringing the metadata from the whole…
Narsimha Reddy.Desidi
Solution Architect at a financial services firm with 10,001+ employees
Real User
Top 5Leaderboard
Good automation and AI capabilities but has terrible customer service

What is our primary use case?

My company, a financial institution, decided to implement data governance for data analytics, et cetera. We designed an entire metadata management system using Collibra. Initially, we designed the metadata management, and then we enabled the receivership at the organization-level and also roles and responsibilities. After that, we created the lineage between the technical and business assets, and we automated the process of insertions and updates.

Pros and Cons

  • "The automation process is very strong."
  • "Sometimes, if a client needs a specific customization, we cannot do it directly. The client needs to reach out to Collibra and request the customization."

What other advice do I have?

I work on governance modules. I'm not related to Collibra. I'm an external consultant and a governance consultant. We adopt any technology which is related to governance. We prepare ourselves and we'll learn it and we'll get hands-on experience so that we have a good understanding of it for our clients. My experience with Collibra has been amazing. I've been working on Collibra within a couple of fields and my journey through Collibra was very fabulous all the way across. I'm using the SaaS version of the solution. It ensures we're always up to date on the latest features, etc. I'd recommend…
See 7 more Collibra Governance Reviews
Product Categories
Data Governance
Buyer's Guide
Download our free Collibra Governance Report and get advice and tips from experienced pros sharing their opinions.