Collibra Platform Reviews

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.

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.

The enterprise data analytics and data science team are able to use the solution for analytics, utilizing the filtered finalized metadata from Collibra, which helps them acquire accurate details. 

There's also a lot of time-saving and they're able to use appropriate data sets. We have a bunch of data sets, however, we've been able to bring and filter, and finalize the proper data sets for our users. These data sets can be used on the data mining side, where, due to the accurate datasets acquired, appropriate data is available and better results are achieved. They're much more likely now to be able to provide good input to the company based on sound data. 

The data security lineage is the solution's most valuable aspect for our organization.

The product offers very good artificial intelligence capabilities.

The automation process is very strong.

The whole company can utilize the product. Once we ingest the metadata from the technical side and we enable the security, if any user wants to know anything from business asset information to which component it is been assigned where, et cetera, they can do so. They don't need to be technical or get a technician to pull the data for them. 

There is a lineage, which helps us to track down and drill down on details. It helps with data analytics and data science. 

Earlier we used to have a third party tool like MuleSoft for connectors. On the architecture side, they are introducing new features that allow us to phase out the third-party connector.

Collibra itself is building and providing some out of the box workflows. These features allow you to automate the process and strictly align the compliance of the company.

There are many new aspects of the solution, however, I haven't yet gone through the documentation to see if they really help solve for issues or not.

Many features have recently changed their appearance and I need to re-learn how they work.

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.

The technical support is very poor.

I've been using the solution on a few projects now.

We don't have any concerns regarding stability. It doesn't crash or freeze. It doesn't have bugs or glitches. It's reliable and easy to use.

The solution scales well for the most part.

Collibra, as a SaaS model, defines every functionality. What happens is that when you are trying to deploy the solution to the customer, some customers may have a lack of knowledge or, because of compliance issues, they might not like the SaaS approach. That said, if a new customer wants to deploy governance but they do not have any knowledge about governance and they've chosen the Collibra, the solution will 95% meet their expectations. Customers that are well-versed in governance will also be mostly pleased in its capabilities.

The issue is that if you are a client and you want me to customize the product in a particular way, while the solution may not allow my team to make the customization, if the client directly reaches out to Collibra, no doubt they can make it happen for the client directly.

Technical support could use some improvements.

One of the concerns I have is the Collibra response time. For example, if you have an issue and you log the call with Collibra for support, the response from Collibra will take a long time. 

For every service request of support from Collibra, the response time is slow. For each of requests, as well they say the client needs to take coaching. They recommend the user to go for coaching. They need to change that support process. The answer can't always just be "learn more". 

Even with debugging issues, they respond properly. There are just a lot of problems with the way they handle calls from us. 

I have previously used different solutions. I've used, for example, Infomatica Axon. Out of all the products I've used, however, I really like Collibra.

There is another product called Alation, which is a very sophisticated product in the market of governance. Alation has more advanced features than Collibra. While it may be expensive, it might be worth the cost to get something more sophisticated. It's possible that Collibra might be updating to those more sophisticated features in the future. Cost-wise, compared to the Alation, Collibra is a cheaper product and much more economical. Also, on the web interface side, Collibra is more hands-on and it's easy for any customer to add and update. 

The initial setup is very straightforward. The Collibra product itself is pretty easy to implement and they have it designed in a way that can make the process pretty smooth. They've defined all of the processes so that they are easy step-by-step scenarios.

That said, the implementation of governance from a customer perspective is not so easy. That's not the product's fault. When we try to implement governance, a couple of stakeholders might agree, and others might not agree. There are internal differences. It depends on the customer.

With any new project, when you are launching it, you will face these roadblocks from the customer's side from time to time. From Collibra side, the product is very smooth and easy.

The deployment also depends on the customer, and therefore it can take anywhere from months to years to fully implement the process.

Typically, you need a minimum of three people to handle the deployment process. If a company's size is bigger, or their requirements are more intensive, you may need more.

Post-deployment, as well, you will need someone to handle some occasional maintenance on the product. How many individuals you may need will depend on the parameters. Governance is an ongoing process. It's not a set it and forget it scenario. Tweaks need to consistently be made.

As a consultant, I never really get into pricing and licensing. However, comparatively speaking, I'd say that it's not as expensive as other options. It's probably about average within the industry. It's not so expensive that companies can't afford it. 

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 the solution to others. I'd rate it at a seven out of ten. I'd rate it higher, however, the technical support is really quite bad.

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.

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. 

Our clients are typically using it for metadata management. From a broader perspective, Collibra establishes an excellent foundation on which to build an enterprise data governance program. 

The most valuable aspect of the solution is its collaboration platform, which includes the workflows, the data lineage, and some of the communities. The ability to collaborate and approve business terms for the business glossary data dictionary is excellent.

The breadth of available connectors for metadata ingestion need to grow quickly to support customers as they expand their data governance programs to include a diverse list of source systems from which they want to derive business value. The connectors are needed  to bring metadata into Collibra and enable lineage, workflows, definitions, etc.  That said, this is not just a Collibra problem - this is an everybody problem. The central challenge is the availability of APIs to ingest text structural metadata, which is a common problem across any data governance platform or even any integration platform, honestly.

To be fair, I would say that Collibra's purpose and primary value is as a collaboration platform, which is the core value of business-centric data governance, and not as an integration platform.  For this purpose, they are clearly the leading solution.

We've been using the solution for six or seven years. We've used it longer than almost anybody.

The stability is very good. It's not buggy and it doesn't have glitches. It doesn't crash or freeze. It's reliable.

It's really scalable, it's really solid. If an organization needs to expand their solution, they should be able to do so easily.

We've reached out to technical support rather frequently. That said, it depends on the topic. I would say that their tech support is excellent, but it is not necessarily an overly large team because they are still a growing company.

They have some really good, smart people, however, they don't have a team of experts for each target subject area.  They don't have a team of 20 people for each application component that can just go, "Oh, yeah. We set an appointment tomorrow!" You might have to wait a few days for the right person.  Having said that, their focus on making detailed self-driven education and training available online enables clients easily to investigate application areas.

The way we view data governance is this: it has to be led by the business. It has to be business-facing. Although there's a number of applications that might have a data catalog, for instance, like Alation, Informatica or Talend, we're vendor-neutral. If we find something better, we'll switch. We're open about that.

With Collibra, their strength is that they were the only data governance platform built specifically to address data governance as it was being formed as a discipline. Virtually every other solution in the marketplace is built as some sort of data management application aimed at IT, and has either morphed from an ETL or something else into that. Alation morphed from a code scanning application into data governance solution (data catalog) for instance. 

Collibra also took a business-centric approach. Their application is the only one that you could throw a business person in front of, and they would understand it intuitively, they'd say, "Oh, okay. So this is where I approve items. This is where I request them. This is where I see things. This is a dashboard that I can look at our progress." You're not going to get a sales VP going into Collibra, but if a sales VP went into Collibra, they would understand it. That's another reason why this has been the data governance solution we have recommended to clients, and still do.

The setup is not complex. It is straightforward. Collibra's very good at doing setups very quickly, so we typically leave this to them. They sell a cloud installation. Essentially, they formerly were both on-prem and cloud, however, now they're focused only on a cloud delivery model based on customer demand.  Thankfully, it is extremely straightforward, as this is the box we need to check prior to helping clients move forward on their data governance program.

The costs vary. I don't have details on the exact pricing of the solution as we do not resell it even though we recommend it.  This enables us to maintain our neutrality as a client advisor.

Their licensing model focuses primarily on the advanced technical users to help to establish the data governance foundation and manage and maintain it as more and more business groups are brought on board.  What I like about their licensing model is that they try to remove barriers to adoption by making it very inexpensive to add "data citizens" across the organization, i.e.  normal, "lite" users who are using, but not developing, connectors, workflows, communities, etc.

In that sense, the marketplace perhaps is not aware of the beneficial TCO of Collibra's license structure, because it causes them to focus on the initial cost of the heavy advanced users, while not realizing that they will be able to bring the overall corporate community onboard at a relatively minimal cost. Therefore, their pricing can appear high per user, however, in fact, for a community or population of data governance users, it's, not actually that high, it's just front-end loaded to establish the technical foundation and basis for the data governance program.

We are experts on implementing business-centric data governance programs, as that is the only model for success.  As such, we are implementation partners with Collibra, and in fact are one of, if not the, longest-standing Collibra partners globally.

The advice I'd give to other potential users would be the same I'd give to people implementing any sort of governance. I would first advise clients to have your data governance business cases ready in advance, or at least start by identifying potential business outcomes that can be delivered through clear and documented access to data. From there, they can target the relevant source systems needed to delivere on these business cases.

From a technical perspective, there are different approaches to ingest structural metadata, i.e.  tools and connectors that are available to assist with this.  While Collibra is hands-down the best data governance collaboration platform, clients should review the different options to ingest metadata based on the targeted source systems.  Of course, Collibra's catalog is the first option that should be considered, but available connectors need to be reviewed.

Overall, on a scale from one to ten, I'd give it a nine. based on its excellence as a data governance business collaboration platform.  From the perspective of metadata ingestion,  I'd probably give it a seven - I like their current roadmap and designated approach, but connectors are a work in progress, as they are for everyone.

Collibra Governance helps us set the business rules and define critical data elements.

It is user-friendly, and other companies use Collibra Governance as well.

I have been using this solution for about a year and a half.

It is a stable solution. 

It is a scalable solution. When we initially migrated, it was a little tough, but we are getting used to it.

We had issues during setup, so we had to bring in a third party for the initial setup and migration from IGC to Collibra Governance. We didn't have technical knowledge then, so we needed help.

I do not have details on the licensing costs.

I rate this solution a seven out of ten. However, we like the solution, and I recommend it to others. It is better than the IGC solution we used in the past.

I am part of implementing the workflow through it, setting up the glossaries, and importing the assets to Collibra Governance. 

I would say customization is the most valuable. The workflow is very good and has been embedded. It also has a great user interface.

I would like to see a feature using the runtime dashboard. As of now, we can create the dashboard using the snapshot of the report. But I would recommend having a dashboard that runs the data on the back end.

I have been using Collibra Governance for the past eight months.

I am finding that there is stability in Collibra Governance.

It is scalable and we have the ability to add more users.  Currently, we have one hundred and fifty users.

I was not involved during the setup.

I would say definitely worth the expense. Data governance takes time to see the output and results.

I would rate Collibra Governance an eight out of ten.

We use Collibra Catalog for the business glossary.

We have found that Collibra Catalog is very easy to use. We suggest a small proof of concept because businesses look at things differently in different parts of the company. 

I think they can bring a few more features and align better with other quality products.

I have been using Collibra Catalog for one year now.

We have not had many complaints about stability so I believe it is stable.

Since I have only used the product for a year now I can not really comment on how scalable it is currently.

I would rate Collibra Catalog an eight out of ten.

Neutral

The setup is easy to implement in your market.