Collibra Governance Reviews

Collibra Governance is used as a data governance tool to manage your business metadata and technical metadata from various systems. Customers also use the tool to provide a data cataloging option, create a data lineage, and automate some of the business processes.

The solution's most valuable feature is data cataloging. The solution's data cataloging feature is mainly used for data discovery. Nowadays, data cataloging enables the data marketplace to share data within enterprises. That's another enablement that Collibra Governance does.

When you have a huge amount of hierarchical data to manage, the solution's performance tends to decrease.

I have been using Collibra Governance for six to seven years.

Sometimes, when we face an issue, we resolve it by ourselves. On other occasions, we contact the solution's technical support team. I wouldn't say that the technical support is excellent. The support team struggles to resolve the issues 60% of the time. However, they are able to resolve issues the remaining 40% of the time.

Neutral

Many of our customers I spoke to felt that the solution is a bit highly-priced.

I sometimes recommend Collibra Governance to our customers based on their requirements and environment. Most customers look forward to having a data lineage function, but I haven't seen any tool that satisfies the customer requirements, including Collibra Governance.

The solution has primarily enabled some of the compliance reporting through data lineage reporting. When you have data cataloging with complete metadata enrichment and identification of PII and non-PII, it helps customers control and manage them properly.

If a customer does not have the appetite to procure Collibra Governance because of the pricing models, we may recommend a different product with cheaper prices. Collibra is working on building a new product for AI governance. I want to see how Collibra's data governance and AI governance will relate to each other.

Most of the customers we deal with are looking for a tool to resolve the data lineage challenge. However, none of the products in the market seem to be resolving the customers' data lineage issues. Vendors like Collibra, Alation, and Informatica could work on it and provide a more comprehensible solution to the customer.

Overall, I rate the solution an eight out of ten.

There are different use cases, including integration with other applications, setting up operating models for specific business domains, such as finance or manufacturing, defining domain structures, and implementing data quality rules and scorecards. The specific use cases can vary from client to client, but they generally involve leveraging Collibra's capabilities to establish a strong governance framework and improve data management across the organization.

I appreciate its user-friendly interface. It facilitates explaining and handing over the data between the teams. It enables a linear view of the data assets across different levels, providing a comprehensive understanding. While other tools may offer similar features, Collibra Governance stands out for its integration capabilities, particularly with platforms like Google Cloud. It is also well-regarded for its modern and cloud-based approach, which aligns with the needs of clients that utilize multiple cloud solutions.

There are certain limitations and difficulties regarding the migration of complex data quality rules, as the tool may struggle with lengthy calculations and longer loading times. Our clients reported that they have experienced runtime errors in those scenarios, Also, setting up the tool and seeing real results can take a significant amount of time and manual effort. Many clients struggle to find experienced consultants due to the tool's extensive features, and this shortage impacts the deployment process and overall value realization. The pricing structure is significantly expensive and not affordable for all the clients. I would suggest that Collibra consider offering a lighter version of the tool for small companies. Currently, the main focus of their strategy lies in targeting medium and large enterprises.

I have been using this solution for a year now.

It provides good stability. We didn't have many complaints about it. There have been some challenges with complex rules, particularly about data quality.

It offers good scalability that is suitable for medium to large companies.

They provide excellent support, and there is positive feedback in the market regarding their support services. The collaboration between Collibra Governance and their clients fosters mutual learning and improvement. 

Positive

I previously used other solutions, like Azure and Informatica, but Collibra Governance offers the best experience regarding the user-friendly nature of the interface. While the other tools have their strengths, Collibra stands out for its compatibility features. It is a competitive solution that offers a variety of comprehensive capabilities.

Configuring is relatively easy with the right training and materials, which is essential for users to understand and utilize the tool effectively. The complexity of the configuration itself depends on the scope of the project, with smaller use cases typically taking one to two months. For larger projects, a team of three to four people, including a developer, engineer, and governance specialist, may be required for deployment. The maintenance is straightforward. Overall, it is a user-friendly tool for administrators.

Generally, it is a rather expensive solution compared to some other tools in the market, but I found it to be fair-priced for its capabilities. The cost barrier often causes potential clients, especially small companies, to opt for other choices. I saw many clients coming back to Collibra after realizing that other tools have significant limitations. The cost factor also varies depending on the size of the company, as larger organizations have a bigger capital to invest in multiple tools.

I recommend considering it, as it provides valuable features. It may be advisable to evaluate and assess the requirements and preferences of the client before making a final decision. I would rate the solution eight out of ten.

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.

We have benefited greatly from Collibra's data governance reporting. If we want to know more about a specific data element, we can use Collibra to get a picture of the whole history of it.

For example, who is the business owner for it? Where is the data coming from (especially when you have different sources which come through) and who was all touching it? And if I wanted to add a rule, like a business rule or a data quality rule for that particular data element, how or where do I keep it? It's like one central place, but for all these items.

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.

I don't think there's any other solution where you can view multiple systems and multiple sources and data places and you can just write it down. It's a lot of work to initially organize but there's no other tools to do lineage like Collibra does it.

The connectors are not very sophisticated. They can do, for example, Informatica and Tableau, but the connectors themselves could be improved.

I recently got a subscription for another 600K for Collibra for one more year, so the author licenses are not used much. And they keep changing the UI platform; that can also be improved.

From an administration perspective, I like the white-glove onboarding part of Collibra. That was actually nice and I really liked that. For administration in general, I like that you can use Collibra however you want. It's more raw and easily adaptable.

So you can cook it or you can steam it or you can make changes to it in a lot of different ways, but it would also be nice if there were an already available analytics tools like Tableau at hand. Though it is easily adaptable and you'll have a completed end product which you can really leverage.

I've been using Collibra Governance for five or six years.

In terms of scalability, it's more like adopting; it's more like a shark. You have to keep feeding it and then it will grow. It depends on how many systems you're using. I worked for a union bank earlier when we set up Collibra and we were able to push in 3000, 30,000, 30,000 data elements. It's great when all the data is available because the team had been doing data analysis for more than a year prior to getting onto Collibra.

At my current company, the data analysis started at the same time along with the data governance and I think I hardly have 300 data elements. So it works on however much you feed it.

And if you have a huge data dictionary and business glossary already available, well and good. Instead of putting it in an Excel sheet, you can put it on Collibra and then you can actually walk through it. But if not, then you have to start feeding it, and it might take at least two years until you get proper food for the tool.

The technical support is okay, definitely not bad. I think they have a 24 hour SLA, but again, it's a data governance tool, so if it breaks and it's not available for a day or so, it's not going to create any business loss. It's more of an understanding kind of tool, and if the SLA is a bit delayed it won't be much of a problem.

The only comment I have is that some of the technical support teams in privacy, security, infrastructure, etc., could be more available during US timezones. That would have made our onboarding process easier.

We went through setup with the white-glove onboarding program. I actually gave feedback to Collibra as well, because the process is a little unusual, but I appreciate it.

The one thing I found a bit difficult when properly onboarding with Collibra and setting it up is that some of the Collibra teams we're working with, like in the security, privacy, and infrastructure teams, are in the European timezone and not the US timezone. Because of this, it becomes a little uncomfortable. It would be great if they could change things around so that there's also somebody available in the US.

It's not just one single technical support team when you are setting up Collibra; you have a lot of different puzzle pieces to work with. That's what the white-glove onboarding is all about. So it actually takes five to six weeks to completely set up, from starting with the solution to getting the software installed and all the nodes set up.

Whether it's on-premises or online, in both cases the whole setup takes five to six weeks and in this time frame I also need to have the company-related IT support people available. And it's just hard for me because most of Collibra's support teams are on Europe time. It could even take up to eight weeks.

Regarding implementation, we need to have the role-setting, we need to have the workspace in the UI in the front end, we need to build the communities, the groups, etc. So it's more like a whole structure that you have to build, and it's a lot of work.

It's more raw, so you can change it however you want. But the thing is, there's not much of a guideline and it depends on your company and organization as well. So you have to ask, how do you want to do the structure? Then you first have to find the communities, and you'll have to set up the groups and the UI, and what comes back, and it's just more about adopting the software to your needs.

Our data officer was very interested in doing it. So she's fully on. And we had an administrator, a developer and the business. We had around three or four business owners to set up the first part before we adopted the rest of the businesses. Of course I was there, too, and there was one more project manager. All in all, we implemented Collibra with only about eight people. As for ongoing maintenance, we only require one administrator.

We have not seen ROI yet. Again, it's more like a dictionary. You buy a dictionary at home, so whenever you want it, you use it. What is the value of getting the dictionary? I don't know. It depends on your talent. If your team does not have good talent, then the dictionaries are more useful. It gets easier to navigate. And if you don't have the dictionary, it's going to be hard.

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.

And they're also very hard. They don't negotiate much: The first price is the first price. We tried our vendor management team contracts that our negotiation people use, but they did not negotiate at all, nothing at all. The very first price they quoted, they almost always stuck to the same price, within 95-98%. Always the same price; hardly anything went down. So that's one thing. They shouldn't do that.

Generally, when all the vendors quote, first they quote and then we start negotiating it. They might then reduce the quote or just provide a different way of getting around. Collibra were very rigid cost-wise, so they should improve that or maybe come up with some plan on how to negotiate.

I think we considered Informatica and one or two others that I can't remember off the top of my head. Informatica was the actual challenger to Collibra before we finalized the cost and everything.

It was cheaper, and it was another good one from an analytics perspective. But we know that, industry-wise, Collibra is number one from a data governance perspective. That's one of the reasons why we went with Collibra, even though the rest of the tools' setup cost and maintenance were cheaper.

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 governance and data quality rules, everything in one place, is nice to have. If you try to utilize it, the data lineage is number one, because there's awesome capability in it. So just try to use it and you'll start loving it.

I would rate Collibra a seven out of ten.

Collibra Governance is used to maintain and govern our company's data and evaluate the data quality. 

Collibra Governance allows users to scan the data in the Schema and check its quality. Our organization's business customers add their company data to Collibra Governance and use data visibility to evaluate how the data can be increased or utilized for some business decisions.

For example, if you have ten columns in one table and assume one column has a couple of null values, Collibra Governance will identify and show you the number of null values present. The identified columns can be further manually checked and altered to enhance the total data quality. 

The solution's search functionality can be improved. For instance, if I search with one piece of data, the tool provides a granular level of data and sometimes billions of data results, among which it's extremely difficult to find a relation. Instead of the aforementioned type of results, the solution can provide a hierarchy based on levels that reveal data upon click. 

I have been using Collibra Governance for three months. 

I would rate the stability a nine out of ten. The product is highly stable. 

I would rate the scalability an eight out of ten. It's a satisfying data quality evaluation tool. 

I would rate the tech support an eight out of ten. The response time from the support team can be further improved. But an immediate response cannot be expected for Collibra Governance because it's not a critical product with urgent use cases.

Whenever, our company has faced issues or bugs while implementing an update of Collibra Governance, an extensive wait time has been encountered. The response time from the support team can be improved based on the issues faced or in an ad hoc format. 

Positive

For the initial setup of Collibra Governance, the vendor's product team assists our company. At our company, we deploy Collibra Governance on the cloud. 

Collibra Governance is extremely expensive. The solution is provided as a whole package, and users cannot avail of only a particular set of features; the whole package must be purchased even if it's not required. 

Collibra Governance will face competition once a data governance tool hits the market that provides basic features at the ideal cost. The pricing model of Collibra Governance should be more flexible for clients.  

At our company, we have used the data catalog feature. Collibra Governance is the top data governance tool in the market. AI capabilities are already being introduced in Collibra Governance. The data lineage feature is also used in our company for data harvesting.

Based on the business requirements, we customize the solution if needed. I would rate the solution an eight out of ten. I would recommend Collibra Governance to others. 

I worked with this solution a few months ago and the main use case of Collibra was as the central metadata tool for the enterprise. The plan was to have all of our data dictionaries, our business glossary, to expose data lineage through Collibra and show all of the relationships and connections between our various tables and databases and the actual semantic business layer, in Collibra. It was a way to unify our technical metadata with our business metadata and with our actual applications.

Recently, a lot of work has been done around sensitive data elements. Collibra is really a good tool for centralizing a list of elements that could either be first or second order PII and connecting the top policies around those specific PII elements to the systems they're found in, and how they are implemented. If they're used as different names in different systems, that's valuable because it's helping the company meet its goals in terms of new legal regulations for the EU as well as for California. Those two are our GDPR and CCPA which are the two most recent policies from that domain. It's also very good for data quality issue management. Collibra is essentially the main tool for that. It's a valuable tool in many different companies.

The interface itself is very useful. I think what I find most useful about the tool, if I'm looking at it from the perspective of a data user, would be the search capability. The fact that I can search for any data elements that are in the table and there will be a pretty comprehensive list that are either identical or very similar to one another in the tables where they are found. I think in terms of sourcing, it's really valuable. I also think that the ability to connect your business metadata with your technical metadata, is something that's very valuable from the perspective of the business. People on the business side need to understand where data is coming from, how it's connected. Doing that through one centralized repository, or document, is useful.

The issue may be the way it's been implemented in my company but, for Collibra to be really useful, what's missing is an easy way to connect to different data sources and different types of data sources and actually ingest and profile some of that data. That's the trouble we've always had in getting wider adoption of the tool. Unless there's a mandate from the enterprise data office or the like, regular users are not going to use the tool for really robust business use cases without having some actual data in there. I know there is some out of the box capability for this, but I think it needs to be easier for Collibra to actually ingest and run some basic profiling on the data itself. That's currently missing from the tool. 

I think that today this is a stable solution which wasn't the case in the past. For a couple of years, there were certain outstanding issues and bugs that took a really long time to fully address. Those have been taken care of at this point.

It's a very scalable tool. There is a ton of metadata in there. If they were to roll this out to other lines of business and start getting more adoption, I don't think they would have a problem with scalability. I think the problem is really with getting that adoption in the first place.

The company is very hands-on providing support and solutions but I think the problem is that they might be stretched a little thin. It's a fairly small company, I believe, and there have been cases where we had to wait months to get support to fully patch something that was wrong in the tool. It's even more of an issue if you are connecting Collibra with another third party tool because you have to get everybody on the call. You have to make sure that they're corresponding, following up in a timely manner. It's just not easy.

I have previously used the Sandbox versions of Alation, and Informatica. I remember Alation being overall very similar to Collibra. I think Collibra's UI may be a little better. I think it's very user-friendly. I would say definitely superior to Informatica. I haven't really heard many good things about the Informatica business glossary metadata solution although it has been a while since I have seen or used that and it may have changed. I definitely think Collibra is the gold standard in terms of combining user experience with the actual capabilities. Again, at the end of the day, it's really a matter of implementation as to how good it actually is and how positively it will be adopted.

There have been some issues with the implementation and the adoption rate has not been high. It's not being used extremely extensively. It's being used for those use cases already mentioned, meaning at the enterprise level for identifying PII and complying with regulations. It is being used for data quality issue management in finance but as far as I'm aware it's not being used for data quality issue management for other lines of business.

I don't exactly remember the pricing but my impressions from everybody that I've talked to is that it's an expensive tool. It's more expensive than its competitors. It may well be worth it in terms of how it's being used. I think it's a superior tool, but it's also a premium tool. 

Before purchasing a license or licenses for Collibra, you need to have a data strategy or data governance and a management strategy defined beforehand. You need to have at least some semblance of an idea of how you want the various spaces and communities in Collibra to be organized. Obviously, certain things will change as you get familiar with the tool, but you can't just wing it. You need to have a strategy that also takes into account other tools and other solutions that you want Collibra to be connected to because there could be an issue where maybe you have a data lineage tool that is getting upgraded in three months from now, and your current version of Collibra will be better suited to connect with that tool once it's been upgraded. You're never going to be able to know 100% beforehand when those types of events will happen, but you need to have some kind of strategy in mind. This is where you really need the investment in data governance and management before you define the tool that you're going to use. That has to come before any implementation of Collibra. 

It's a big tool, so it can potentially be difficult to implement if you don't have the right investment in place before deployment. It's also user-friendly with a lot of great out-of-the-box capabilities. There is some room for improvement in certain areas, but overall it's a good solution. 

I would rate this solution a seven out of 10. 

Collibra is generally used as a data governance tool, maintaining all metadata repositories. For each and every data that has been cataloged in Collibra, there'll be an owner assigned to it, whether it's a subject matter expert, a data streamer, data owner, etc. All the data is catalogued into Collibra. It has a single source of truth for data. I'm a senior Collibra consultant and we are customers of the company. 

We have data that people want to access and that's where Collibra fits in. They provide the SSO authentication so that anyone in the organization using the login can find what they want. 

Collibra is evolving their connectivity towards all programs across the IT landscape. The solution has good workflows and they now offer nine dimensions of data quality and provide a lot of features. The solution is based on AIML, Artificial Intelligence Machine Learning so that even if you don't know SQL, you can operate Collibra Data Quality. Collibra Workflows, Collibra Data Quality, are two good aspects that I would highlight from Collibra. Governance provides a user access mechanism, where you have all the data assets cataloged in Collibra. Not everyone can access all the data which is where the governance process comes in. They are constantly coming up with new features, and provide a monthly release.

The Collibra interface is not very user-friendly because it has a lot of features that business users find difficult to navigate. Anyone using the device needs some knowledge about how to use the tool and it takes a while to access and get used to the interface. I'd like to see them build a simple interface with only four dropdowns in order to get access to the request. If you're using it for the first time, it's difficult.

There are widgets in the dashboard and if they could make it more like a webpage instead of a Word document, that would be helpful. They have alternatives, but it takes a lot of work and even Collibra developers don't necessarily know how it works. Some changes are needed. 

I've been using this solution for three years. 

The stability is good, I've never felt any performance issues. 

It is highly scalable, we have around 4,500 users.

When you buy a Collibra license, they offer some training. If we have any issues, we can have a coaching call with them. In addition, they have a support portal. If you raise a ticket with them, they'll respond. 

Collibra provides support to anyone deploying the cloud version and implementation generally only takes a couple of hours. They are also responsible for maintenance.

There is a standard license for Collibra Governance and an additional cost for Collibra Lineage and for Collibra Data Quality. Author licenses have a set maximum limit; if you want extra there's an additional cost. That's their marketing strategy. 

I recommend going to the Collibra University web portal where you can register and log in. They provide a lot of basic information and the functionalities they provide. For anyone wanting to get into governance you can easily get certified as a Collibra consultant. Collibra has its own product roadmap. They have an ideation platform, where you can suggest ideas and if they get a sufficient number of responses in a particular area, they will add it to their roadmap and work on it. Collibra provides a lot to their customers as well as continually improving the product.

Anyone wanting data analytics uses Collibra. I rate this solution seven out of 10. 

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 if you include what the developers work on, so it is a bit tedious to upgrade. 

In Europe, it is quite good for documenting your DPIAs, and you have to do that if you have to be compliant with GDPR. That's one of the main use cases that I see over here.

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.

I've been working with Collibra for almost two years.

It usually is stable. It doesn't really require maintenance, and it doesn't go down. The only maintenance that is required is the upgrade, which is not that frequent. However, after our latest upgrades, when we ran some of the workflows, the form doesn't respond. Even if you open developer options on your browser and if you try clicking next or back, it doesn't work, but if you close it and then you open the form again, it works. I don't know why that's happening with this version, but because we are planning to move to SaaS, I'm not really bothered about it so much for now.

It is pretty new for this client, and we are in the initial phase. All the applications are not even on board yet. We are slowly trying to move towards the ideal scenario where we have things from your catalog to even integrations with Denodo and Feebo. These are the standard things for virtualization and everything.

We definitely know the capabilities of the tools. I have been working on it technically for almost a couple of years now, and we also have business users and consultants who have implemented a proper governance structure for the entire organization including everything from your roles and responsibilities to the line of businesses and how they should be. We have people who are experts at that, so it's slowly evolving. Our users are data stewards, business stewards, subject matter experts, IT owners, data owners, and stakeholders.

Most of the time, as soon as I raise a ticket, they revert back, and I get the correct thing. However, sometimes, for things like the workflow issue that I just mentioned, they aren't that good, but usually, they're good.

I have worked on SAS DataFlux, Ab Initio Express, and Ab Initio Metadata. All of them are data governance tools. Some of them are data quality engines. Collibra is not one. 

Collibra Governance is totally different from Dataflux. DataFlux usually is just for your data quality. That's the data quality engine that will run your data quality rules and store the data in a place, just like Trillium or exPress IT. After that, you have to integrate it with something like Ab Initio or Collibra to govern the data quality results that are coming from it.

I have also used the Collibra Privacy & Risk. It is the GDPR Accelerator. In fact, we cannot call it an accelerator after 5.7.

If you have someone who knows what they're doing, then it is pretty straightforward, but you have to get the business on board as well, and then you have to show them how to use the tool. That's usually a challenge for any new data governance tool that you get into place. 

If you're on-prem, then the setup is pretty straightforward, but if you're deploying on the cloud, it becomes a bit tricky because usually what happens in banks is that each line of business has its own AWS account. You use your servers to scan their metadata, but then you have to establish some connectivity between different accounts and all those things. That part is usually a bit complex, but if you're on-prem or if you're on SaaS, then it's going to be pretty straightforward.

I have actually created a Jenkins pipeline that works with the latest installable file that Collibra gives. It just does everything by itself. It is pretty straightforward for me now, but reaching that point took a while and a decent amount of effort. We have a DNS resolver using Route 53, which will then go to a load balancer, and the load balancer essentially is then connected to your receive tool that has the tool hosted on that. We take care of security groups and make sure that no unauthorized access takes place. We have implemented Azure AD authentication. Our client uses Azure AD for all their authorization, so we implemented that using the SAML functionality that's available in Collibra.

If there is any change in the asset models, then we have a team that does that. As of now, if we need someone who will deploy the actual tool or upgrade it, then I'm the one who currently takes care of that.

Most of our clients have seen ROI from using Collibra. Some of them are still getting up to speed. Usually, financial institutions have legacy systems where people will just use Excel for their DPIAs. It is somewhat of a drastic change for a lot of them, so it sometimes takes time to see the ROI.

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 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 a year, I can say more, but for now, it is eight.

Collibra Governance has many use cases. I'm part of the enterprise data team and I also focus on other types of data enterprise, wherein governance is one of the workstreams. I'm working for a pharmaceutical company, so I try to onboard people on Collibra Governance from various verticals such as HR, vaccines, pharma supply chain, etc. Sample use cases for the solution include data quality for cloud stream software, automated data lineage, and other types of lineage. In general, I'm using it mainly for data governance.

The feature I like most in Collibra Governance is the lineage. It lets me do lineage that you can set up, for example, technical lineage and business lineage. The solution lets me associate the right people with the right assets, so anybody who has to look at end-to-end instances can use Collibra Governance and figure it out in terms of who to contact, what to do, and where to find what you need.

There's still room for improvement in Collibra Governance. Right now, the solution focuses more on publishing and subscription where metadata is being consumed from all systems and processes within Collibra Governance. I'd like to see more features around external systems that let those systems start consuming or start referring things from Collibra Governance automatically, in particular, more API-based integrations, so the solution can truly work as an enterprise governance tool at the heart of the organization.

There have been many cases where business stakeholders feel, "Okay. I'll be doing a manual activity because every time I have to maintain and make sure that the solution is working, for example, ensuring the reporting works, I have to go to Collibra Governance." I want this step taken out of the equation, and it has to be an automatic conversion or automatic notification that something has changed.

Scalability also needs improvement in the solution.

If there could be some sort of self-service where people can customize the solution a bit more, that would make Collibra Governance better.

What I'd like to see in the next release of the solution is an enhanced search feature because it's what users want to use. You want to search for a term and get all details in one go. Right now, if you type a term in the Collibra Governance global search function, it returns a lot of results that you need to know how to filter and what to filter, so there should be automatic filters that give accurate information to somebody who does a search on the solution. I want Collibra Governance to provide a capability where you can search and get relevant information.

I've been using Collibra Governance for two years now.

Collibra Governance is a stable solution. It has no downtime or issues, based on my experience.

Collibra Governance is not a scalable solution, and this is one of its areas for improvement. The solution needs more integration, and I'm also looking at how Collibra Governance can be more scalable.

The technical support team for Collibra Governance is very responsive and knowledgeable. On a scale of one to five, I'm rating support a five. My team gets very good support from Collibra Governance whenever required.

The initial setup for Collibra Governance isn't that complex. The UI is pretty straightforward and the structure is quite standard, so people can come and map. The main problem my team is facing is working in a federated environment, so every business or every unit you've given leverage designs it their way, and in that way, people can customize a tech model, so you have no control over that. It's more of how people perceive the business, business terms, and business data that varies. I'm struggling to build more standardizations around it, but I have no solution to it yet because, in my company, you don't work like a centralized organization. People research and build designs their way, so at times, this leads to different conclusions, and that's what I'm struggling to solve.

I'd rate the setup for Collibra Governance as three out of five, though I didn't do the setup myself. Another team was responsible for setting up the solution.

I'm not familiar with the pricing or licensing cost of Collibra Governance.

I've not used any other data governance tool apart from Collibra Governance. I've used a data quantity tool, a data reference tool, and a master data management tool, but not a data governance tool similar to Collibra Governance. In my previous organization, I did governance through files, SharePoint, etc., not a centralized tool such as Collibra Governance.

In the company, there are more than three thousand users of Collibra Governance.

My team has been using the solution daily, but I'm unsure of how frequently it's used by other teams.

My rating for Collibra Governance is seven out of ten.

My company is a customer of Collibra Governance.