Collibra Governance Reviews

We've used it for cataloging or defining our business data entities and their associated attributes or data elements. Where appropriate, we are defining their sources and their modes of derivation. Rising above that, we are also using Collibra for the definition of our business metrics that are calculated from those data elements and the derivation definitions associated with them.

We have folks in the field doing our clinical research operations, and they have the opportunity to refer to Collibra when they are examining a particular report. When they have a question about how something in that report is derived, they can pull a metric that is defined fully in Collibra. They have the opportunity to drill back into Collibra to see that.

It is a big library. It has a long list of data assets and their descriptions and lineage. It's fairly two-dimensional. For my use, it just has lists of things. There might be others in my organization who are tying the data elements, metrics, and other things together, but I don't rely on that, and I don't leverage that. For me, it is a fairly flat library for information.

What I use it for is fairly rudimentary, and I don't have any complaints about it. I haven't tried to stretch the boundaries at all, but it would be nice if there were capabilities built within the system to somehow help enforce the quality and consistency across related elements that are built in the catalog. It could have intelligent capabilities built in to help maintain the quality of the data and information, such as natural language processing, machine learning, and so on. 

I've been exposed to it for about seven years, but I have been using it more heavily over the past couple of years.

I've not seen or heard of any problems with its stability.

I haven't seen any impediments there. So, I have no concerns about scalability. It could be because I haven't been this involved in pushing the boundaries, but I've seen it accommodate new layers without hearing of any issues.

It is open to everybody in our organization. We have more than a thousand users. So, there are more than a thousand people out there who have lately used Collibra, but most of them have used it in the reference mode or read-only mode. In terms of their roles, we've got everybody from data engineers, data analysts, and systems developers to business analysts and business end-users. 

I've never called them, and I don't hear anybody complaining about it.

As far as I know, this was our first venture about seven years ago into data cataloging and data governance.

I wasn't involved in the setup, but I can see that the maintenance of information within the system is quite straightforward.

My guess would be that we took care of most of the things in-house.

I'm only involved in the use of it. My advice would be to make sure that the content is of quality because it tends to mushroom into lots and lots of information that can easily get out of sync. It should only be entered into by an organization that has the discipline behind it to maintain the information at a high level of quality. Otherwise, you end up with a lot of information that seems useful, but in effect, it could be more harmful than it's worth if things get out of sync. It takes an organization to maintain this kind of solution. The content is dependent on the quality of the maintenance of the content.

I see a small chunk of it, and I would rate it an eight out of ten.

We are focused primarily on the Data Governance Catalog (DGC) for our data dictionary use. We are not using it for information governance in terms of regulatory compliance, etc. We are focused on business glossary, data catalog, data dictionary, and some workflow processes to help with metadata management and other things.

We are fully updated, and we are using its latest version.

One of the workflows that we're just finishing and rolling out is a certification process. Collibra DGC has an attribute in there called "certified," and it is basically a yes/no choice. We wanted a lot more information about the certification of data sets, so I wrote this workflow, which is probably 30 or 40 steps long. We have a series of criteria that we have to meet in order for a data set to be considered certified. I was able to create attributes for all those and create a workflow that goes hand in hand with data set development so that when somebody competes their work, he or she can pop into Collibra and say, "I have finished this." It logs it and it becomes part of a trust score. It is really nice, and it is making our certification process more robust and the documentation easier to collect and maintain.

I like Collibra's flexibility. I like to be able to modify things for our own use. For example, we've chosen to use Collibra also as a knowledge management tool, even though it is not designed to be a knowledge management tool. That's the beauty of it. It can serve as a knowledge management tool by creating some custom assets specifically for knowledge management. I have a knowledge base domain and a knowledge base article asset type- along with a few other things. I really like the flexibility to be able to extend it in those non-traditional ways.

On the flexibility side, I've created some really nice and very useful custom workflows that have really helped with work processes and productivity. They've really helped us do things easier, faster, and better.

The UI is good if you happen to be an administrator and are familiar with the technical side of the administration. If you're a business user, the UI is not good. It is hard to learn. It is hard for those who are administering it to teach to end-users and it can take hours of training to do it. Because it is difficult and non-intuitive, business users resist using it. It is a battle to get them on board and to keep them engaged because of the UI. On the other hand, Collibra just hired a person specifically to revamp the UI. So, they're dealing with it, but it isn't there yet.

They're working on the lineage harvesting for technical lineages. I don't know this for a fact, but my feeling is that this is new to them. So, they're still developing it and it feels awkward.

I have been using this solution for eight months.

Its stability is very good. Out of 10, I'd probably give it a nine. We've had a couple of little glitches where something happened, but they were minor and we were able to create tickets and get issues resolved within a week and usually within just a day or so.

So far, we haven't had any major problems. We're ingesting metadata from AWS Redshift. We've also got connectors built for S3 but we haven't used them yet. We're importing from Oracle and working on lineage harvesting from DBT, Data Services, and few other places. So far, everything has been really good. We're importing metadata from Tableau, and there are no problems there, either.

In terms of the roles of its users, we've got product managers and solution managers. (A solution manager is the IT coordinator who works with the product manager.) We've also got analysts, engineers, reviewers, editors, data stewards, and data coordinators or custodians. We also have technical stewards, admins, and a group of people we call "normal" who are business users that have read-only access.

In terms of Collibra's usage, I would love to have it used 10 times more than it is, but because of the difficult UI, I am getting resistance from the users. It is hard for them to navigate and learn the interface. Once you know it, it is easy to get around and find what you need. It is just about learning the interface and dealing with some poor choices of how to use the screen real estate. So, right now, the user engagement is lower than I would like it to be. 

Their technical support is very good. On a scale of one to 10, I would give them a seven. We've probably had four or five tickets open and were able to get them resolved quickly. 

It feels like they may be sensitive--possibly they've had some bad reviews regarding their customer service--so it seems like they may be going overboard there. For example, they have scheduled a meeting every month for our team to meet with what they call a customer success manager.  I feel like this is too often.  They're responsive about stuff, but it feels like they're trying too hard.

Prior to this and strictly for our data dictionary, I used Dataedo. They are very good at what they do, but have a much more focused solution.

For knowledge management, I used Confluence and really liked it, but we came up against the issue of access levels for for non-registered users; we didn't want to pay license fees for a large number of "read-only" users. Basically, it is either full (paid) access or free access to "the world" and like everyone else, we have information that we don't want to expose to the world.

Setup was really straightforward. Collibra was very good with holding meetings and being responsive to requests. I was pleased with the setup and configuration process. They were really good at the initial stages of learning and understanding what we were doing.

Those of us who are working on this project also have "day jobs" so we were not focused solely on this. The focused time on it among members of the team was probably less than a hundred hours extended over a period of several weeks.

In terms of maintenance, we have a small, three-person team of people who are actually working on the technical maintenance side. All told, the actual time that we spend in administration at this point is very low--perhaps 20 hours a month spread between three people.

We did it in-house with direct interactions with the Collibra team. Our experience with their team was very good. They have an onboarding process and a roadmap they like to follow. We were just one department with a small team working on the actual setup and use case. Several of their steps didn't apply to our use case so we skipped these and even took some of the other steps out of order simply because it made sense for us. The onboarding team at Collibra was 100% supportive of making those changes and doing things the way we needed instead of the way they ordinarily would have done.

It is substantial, and we pay yearly. 

The thing that made our onboarding really simple was that we understood beforehand our use case and our needs. We understood what our roles were and who needed to be involved. We also understood our communities and our setup structure. We had all of that from the beginning. They mentioned several times that we were extremely well-prepared. So we learned that the more users know about the needs of the department or the company, and the more advance prep work they can do, the easier the onboarding process is.

When we started, the Collibra team sent us two huge Excel files that were basically questionnaires that they wanted us to go through to prepare for onboarding. We already had all of that done. It was finished but wasn't in the same format.  We wrote back and asked, "Do you really want us to fill out these Excel sheets? We've already gathered this information." They said, "Oh, great. We will skip the first two steps of onboarding because you've already got it." That really accelerated the process.

I'd give Collibra a nine out of 10. I am really happy with it though there are few things that I wish were different, especially in the UI.

Collibra Governance is a stable solution.

The solution's data lineage is a little difficult and will not support all the source systems on the database.

I have been working with Collibra Governance since last year.

Collibra Governance is a scalable solution.

Collibra Governance's documentation is clear. We can get all the documents from Collibra University.

Collibra Governance's initial setup is complex.

It takes more than 15 to 20 days to deploy Collibra Governance.

Collibra Governance is an expensive solution.

Collibra Governance is a good tool that has some pros and cons.

Overall, I rate Collibra Governance a seven out of ten.

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. 

There is a master glossary which includes all of our business fields. The fields are related to particular lines of business such as account numbers. We then build business rules around these fields and complete data integrity checks. 

We plan to increase our usage of this solution over time. We will have to use other functionality within this application as it is currently limited. We currently have 12 team members using this solution. 

This solution is user friendly and offers multiple functionalities. It operates like a kind of a repository that allows you to find anything about a particular data set or field.

This solution could be improved with the the addition of process diagrams to help the many users of the platform understand all the fields.

We have used this solution for six months. 

This is a stable solution. 

The initial setup was straightforward. It was made easier due to the access we had to the Collibra team. The deployment took three months and involved three to four people.

I would rate this solution an eight out of ten. 

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 understanding what data is in which database. We also look at what data is flowing from database to database and how it's used in Tableau reports or in a business or archive.

Currently, we're on-premises, but we're planning on moving to the cloud later this year.

Over the last 12 months, we've had 643 unique new users. Most of our users tend to be what I would call "data geeks". They are the ones that understand the value of and/or the aspect of leadership to catalog their metadata for their data dictionaries, etc. The business users have not had as much adoption at my current company because that's not the particular strategy at this time. At my prior company, that was the singular strategy — to increase business literacy.

In regard to my previous company, for eight years, our primary customers were business users, not technical users. They just wanted to come in and say, "What does it mean? Who do I talk to if I have questions? Where do I go for more information? How does this relate to that, and how do those things affect me in my business world?" That was a fantastic use case at my prior company. In my current company, we're utilizing the tool specifically to support our data management strategy. Our technology risk office is very much supporting us in the effort to do the cataloging of all of the metadata for all of the systems that we're utilizing, cross-functionally.

Maintenance must be defined. As with any software product that exists, there are regular maintenance upgrades that occur that the company pushes out. If you're on-prem, you can choose to do it sooner versus later. In the Cloud, they push it to you unless you state that you wish to wait. From a maintenance perspective, I have talked to other customers who are in a cloud environment. They say that the maintenance has basically dropped to nil. For on-prem customers, it does require a little more maintenance because obviously, you've got to make sure that the servers are up and running, etc. In my prior role at my previous company, I was responsible for the business IT side of it, which meant I kind of managed the platform. I just didn't manage the server.

I took care of the customers, etc. I'm not even a technical person at all, but still, it was not difficult for me. From a maintenance perspective, I don't feel that it is difficult.

If you have custom integrations that have been created, then it will require a little bit more maintenance because those integrations need to be monitored. Some customers require a lot of integration, and some customers don't. It really depends upon the use case. Custom integration is really where it gets more challenging. Depending on whether it's a one-way integration or a two-way data feed, it can get pretty complex. Two-way data feeds are always custom. But that's something that will be on the customer anyway, not Collibra.

We've only just relaunched this solution within the last 15 months. Currently, we only have about 240,000 assets in the tool, but we have a roadmap and plan to onboard a number of our customers. We'll probably double or triple our users over the next 12 months. 

This solution has brought our very diverse cross-functional business teams to one enterprise-facing view, where they can see business glossaries that have been compiled by other teams. From here, they can leverage and understand what reports have been created. If the report exists already, why recreate it? 

Our data management strategy is to start cataloging our data dictionaries and our business glossaries to ensure that we have a common platform across the company. This is helpful when a database is being retired or being converted over to another one. A lot of work goes into documenting what that data attribute means, or what that field name means in regard to a particular report, or in a particular database.

I'm always putting in enhancement requests because we want everything to be perfect for us. We understand that there are thousands of companies that use the tool and many of them use it in different ways. They should allow the customer to have some additional flexibility.

Take Microsoft for example. Sometimes companies do something cool because their software programmer thinks it's cool, but for the user experience, it stinks. Something as simple as "Why did you decrease the font size from 12, down to nine on every page? Now eyes over 40, can't read it". As it relates to this specific software, I think that getting more feedback from users on changes to the software before implementing it would increased value for them. Overall, they're really great. We meet with our Collibra rep every other week. We talk about what's working, and what's not working. They're a fantastic company to collaborate with. Still, when they just go ahead and implement new things, a bunch of new tickets open, wanting it to go back to the way it used to be. 

As far as the functionality of the tool is concerned, it's pretty slick. It's very comprehensive. Still, sometimes they create an interface or an integration without thinking about how the business is going to use it. Virtually all software companies do this. Oracle does it, Informatica does it — every tool does it. They make changes and then they're like, "Oh, I didn't know you were going to use it like that". Why? nine-tenths of their customers use it like that. I think it's a common business challenge that any company has. They're just trying to appeal to a vast audience of customers.

They should consider that what makes a financial institution happy will not necessarily make a healthcare institution happy, which will not necessarily make a high-tech vertical happy either.

There's a lot of things available in their Data Intelligence Cloud that are not available on-premise. For me, if they could boost the search functionality so that if somebody types in a word, it automatically will pull up similar terms first — that would be nice. For business users, instead of what is just the most common volume of content in your tool, now they have a very cool faceted search. It would be very similar to Amazon. You can refine your search down to a fly's eyelash if you'd like. I see a lot of people in the community commenting that this would be a big help.

I have used this solution every day for the last eight years.

It's a pretty stable tool. In the last year, we've only had one time where there was a significant issue. We found out that it was simply because during an upgrade it required more server memory than the prior version did. Overall, that was a minor hiccup and it was quickly resolved.

Collibra has roughly half a dozen different products with which you can buy additional licenses for that will do amazing things. If you're interested in GDPR, you can buy that software — a module. If you're interested in what I would call a significant data lineage, you can buy that product, get a catalog, and it's available for data ingestions automatically. In today's world, this is pretty much essential. There's a lot of capabilities as far as scalability and expanding usage across the business.

It's easy to do that if the business users are being encouraged by their management to use it. I think you might agree that no matter what company you work for, nobody's going to use the tool unless their leadership tells them to — they're comfortable in their own box. It's like, "I'm busy. Don't bother me unless I have to do something." That's the case for what we have done both at the company I'm at now and my prior company. It's that leadership gained, cross-functionally that we have as one enterprise united under one tool. That's a pretty powerful thing to encourage people to do. The implementation of a tool like Collibra is far more effective if you have leadership executive sponsorship. I think that's hands-down, one of the most important things to ensure the healthy adoption of a solution.

Sure, you can use it without embracing it, but the teams that have embraced it are the ones that have leadership that says, "I understand the value of it, let's do this and get creative with it." These are the teams that are the most robust at using it; they have really learned how to use the tool and are constantly pushing the limits of it. From a scalability standpoint, the workloads come out of the box, but a lot of the workflows are made for the most common use case. As such, most customers customize the workflows. From that standpoint, it's very scalable.

I always recommend to anyone who is considering going with Collibra, to ensure that they have someone that will be trained on building the customized workflows — you're going to need them. Sure, you can pay Collibra to do that; you can pay the professional services to do that and they'll do a fantastic job, but it's expensive. It's a lot cheaper to invest in somebody in your own company to get some training. You can really scale quickly if you have somebody in-house that can create customized workflows and manage them.

The technical support is very good. 

As with any vendor, you can get out-of-the-box support, or you can buy additional support. Both at my prior company and at my current company, we have engaged with professional services and we meet with them once a month just to say, "Hey, I've got this weird thing I'm trying to do and I ran into this problem." Although it's not required, if you really want to accelerate the usage of the tool and the adoption of it, I always advise other people to talk with users at other companies and to consider paying for some coaching services or professional services. Even if it's just one call a month for an hour, it's still worth it, especially when you're trying to do very creative things, as most customers want. You gave me Mickey Mouse and I want to make it Donald Duck — a lot of companies do that.

The Collibra Professional Services guides are great — they're fantastic actually. I've never had a bad experience in the eight years I've been using this solution. I've never had a bad experience with their support staff, both on the technical side and on the business side.

The initial setup is not that difficult. I cannot speak to moving to the cloud because we have not done that yet, but I hear that it's not very difficult. It's been a couple of years since I have set up the platform, but as far as upgrading to a major new version, it's actually pretty straightforward. Collibra has actually done a fantastic job over the last few years to make this whole experience a lot easier. Years ago it was not as easy as it is now.

It's matured a tremendous amount over the last few years. absolutely tremendously. The company has been around for over 12 years now. When they first launched, it was a completely different animal. Now, it's a very robust metadata management and data governance tool.

One and a half, full-time employees are required for maintenance. 

I am not sure how long deployment took at our current company. I have heard from other customers who use the platform that it can take anywhere from one to three months, depending upon the complexity and how much testing they want to do. It also depends on the amount of customization they want to do. That's one of the great things about this tool — you can customize the heck out of it. If you go with everything out of the box, it's pretty straightforward and doesn't take very long. I would say deployment takes less than a month.

It's more of a soft benefit versus a hard benefit. What is the value of saving someone time? I did a cost analysis at my previous company. Our CFO used some vocabulary and some acronyms that I had never heard of — and I'd been with the company for 13 years. It took me 20 minutes — and I'm really good at sleuthing — to figure out what those things meant. I added those into our Collibra instance so that other users could quickly find out what those things meant. If you look at it from that standpoint, right after an "all-hands", our usage of our Collibra solution always spiked.

Everybody was like, "What did he mean when he said that? If it took me 20 minutes to find out what X, Y, Z meant, and it took me two minutes to get it into Collibra, then if a hundred people saved time because it took them only two minutes to find out, too — can you put a value on that? Yes. You can say, X dollars per hour, FTE, and how much time that saves. I did that very briefly just for one use case and my boss said, "Nevermind, they get it." 

I think that's the biggest value — how do you save employees time? Because everybody's too busy to waste time.

I think all software is expensive, but that's just me. Still, I would say it's probably in line with what other vendors charge for licensing. I would just say it's probably comparable. I have not done a side-by-side comparison in about three years, so I can't speak as to what's going on currently.

There's a baseline product called Data Governance Center. That is what I would consider their baseline product. You can choose to purchase other licenses, whether it's the data catalog, their privacy module for GDPR, or their Data Lineage modules — there are plenty of different licensing options. Some of them are user-based, and as with any company, the more you buy, the more of a discount you get.

You can buy as little or as much as you want. It just depends upon what your budget is. I've talked to some financial institutions that have just thrown so much money at the tool. It just makes my jaw drop to the floor — it's insane. We're doing almost what they're doing at a third of the cost. It really just depends upon your strategy.

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 business users? Even technical users that are on the business side want to know how to get them to onboard and adopt.

That's the piece that will really make or break in your implementation. So, make sure you have some type of stewardship team in place, whether it's on the business side or the technical side, just to help onboard new users. This is absolutely critical because as with any tool, it takes some adoption and some communication and collaboration.

When you first buy the software, you could just buy it and figure it out yourself, or you could buy their Coaching Services and their Quick Start packages. I would strongly recommend investing upfront. There is a Quick Start package, which is basically paying Collibra to help you, whether it's standing it up, whether it's your initial implementation, etc. I think it takes 10 days. I highly encourage taking this route. It will really accelerate your installation and decrease frustration. Make sure you've got leadership or executive support regarding what you're trying to do for your strategy.

The biggest lesson I've learned is that you can never assume what somebody means when they use a word. I've got 35 years of business experience under my belt. I've come to coin the phrase "What's your operational definition of that word?" You can be 45 minutes into a meeting with 10 people using the same word and find out halfway through the meeting that you're talking about four different things or two different things and everybody's frustrated and walks away.

You need to understand the meaning of the vocabulary, whether it's data vocabulary or business vocabulary. Doing so will absolutely accelerate your business and save people so much time. That's one of the things I really like about the Collibra platform. From talking to other companies, other people, and friends of mine, I know that other companies that use tools similar to Collibra — even they say the same thing. You need a data catalog, that will allow your business to quickly find what they're looking for and help you understand what that means in the context of the conversation they're having.

Overall, on a scale from one to ten, I would give Collibra Governance a rating of eight.

We mostly use Collibra Governance for governance-related tasks like building business glossaries and creating policies.

Collibra Governance comes with a lot of features, and we have used it in one of our projects for metadata management and data lineage. I have used the solution to create governance rules and a centralized repository for business glossaries.

The solution's metadata management is pretty novice and could be improved.

I have been using Collibra Governance for around one year.

I rate Collibra Governance a nine out of ten for stability.

Collibra Governance is more suitable for medium-level and enterprise businesses.

I rate Collibra Governance a nine out of ten for scalability.

The solution's technical support was good, but there was a delay in their response time, possibly because of the time zones.

Positive

The solution’s initial setup is simple.

The solution's deployment will not take more than a week and can be done in five working days.

The solution's pricing is moderate and not very expensive.

Informatica is coming up with some level of data governance. erwin Data Modeler is quickly emerging as a competitor for Collibra in the coming days.

Collibra Governance is deployed on the cloud in our organization.

Overall, I rate Collibra Governance an eight out of ten.

In my company, we use Collibra Governance for data catalog.

Pricing policy of the product is an area with certain shortcomings that needs improvement. I would like to see better pricing in future releases of the product. Collibra Governance needs to develop some new technology, like Atlan, that has been incorporating AI in the automation area of its products.

I have been using Collibra Governance for five years. I have ensured that one of my company's customers uses the solution's latest version. My company has a partnership with Collibra.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

Around 30 people in my organization use the solution.

The solution's technical support is helpful and responsive. I rate the technical support an eight out of ten.

Positive

I have probably worked with most of the products in the market related to data governance and data catalog, including products like Informatica Axon. I still do work with Informatica Axon at times.

The product's deployment phase was straightforward.

The solution is deployed on an AWS Cloud, which is a private cloud.

The deployment process is carried out by Collibra Governance's technical team.

There is definitely a return on investment from using the product, especially if you associate it with a data catalog tool. The return on investments is in terms of optimizing the process of development, data quality improvement, and having a single repository source of information for the metadata of the entire organization.

I don't know the licensing costs of the product since it is a SaaS solution.

I rate the pricing a three on a scale of one to ten, where one is expensive, and ten is cheap.

The maintenance is something that is carried out automatically by Collibra Governance.

I rate the overall solution an eight out of ten.