What is our primary use case?
I have been using Veza for the past one and a half years, primarily for identity security and access governance. During this time, I have used it to gain visibility into permissions, understand who has access to what resources, and help improve access management across different systems.
In my day-to-day work, the common use case of Veza is access visibility and entitlement reviews. For example, I use it to identify who has access to critical infrastructure, cloud resources, and sensitive applications across the organization.
What is most valuable?
One significant benefit of Veza is how it helps centralize access visibility across different systems. Traditionally, access reviews require checking multiple applications, cloud platforms, and identity sources separately. With Veza, I can see permissions and relationships in a single place, which makes reviews much faster and more accurate. It is also useful for audit and compliance activities.
Veza offers great access visibility, identity intelligence, and governance capabilities. One of the standout features is end-to-end access visibility. Veza provides a clear view of who has access to what across cloud platforms, applications, data systems, and infrastructure, making it much easier to understand permissions and identify risks. Another key feature is its identity graph and relationship mapping.
Instead of looking at permissions, Veza allows me to directly show how users, role groups, and resources are connected. It is one of the most valuable features. Instead of simply showing that a user has access to a resource, it maps the entire relationship chain, such as the user, their group members, assigned roles, inherited permissions, and the actual resources they can access. This creates a clear picture of how and what access is granted.
Veza provides access risk analysis and least privilege recommendations. Beyond simply showing who has access, it helps identify excessive permissions, unused access, and potential security risks. This allows teams to proactively reduce their attack surface rather than waiting for an audit and security incident. I also appreciate its cross-platform visibility.
One of the biggest improvements since using Veza is that I have a much clearer understanding of who has access to critical systems and resources across the environment. This has significantly reduced the time spent on access reviews. I have also improved my least privilege initiatives by identifying excessive or unnecessary access and remediating it more efficiently. This has helped strengthen the overall security posture.
What needs improvement?
Veza is a strong platform, but there are a few areas where it could improve. One area is dashboard customization and reporting flexibility. Another improvement would be simplifying onboarding and initial integration, as well as adding advanced analytics and risk prioritization.
Additional points about needed improvements include the challenge I face in understanding very complex permission structures in larger environments. Another area of improvement is automation around implementing remediation. I would also like to see expanded integration coverage and out-of-the-box templates for access reviews, compliance reporting, and governance workflows.
For how long have I used the solution?
I have been using Veza for the past one and a half years.
What do I think about the stability of the solution?
Veza is very stable for my organization, and I have not experienced any outages or issues.
What do I think about the scalability of the solution?
Veza's scalability is very good. I have not faced any issues, and its elasticity is very good when compared to standard tools. I would recommend its scalability.
How are customer service and support?
The customer support for Veza is very useful. It is a ticket-based system where I raise a ticket, and the respective teams help to review and solve the tickets. Overall, the experience with customer support is very good.
Which solution did I use previously and why did I switch?
I did not use a different solution before. I only used native IAM tools, but this is the first switch that I am making.
What was our ROI?
I have seen measurable benefits with Veza, including a twenty-five to thirty-five percent optimization in access investigation and audit preparation, a thirty to forty percent reduction in access review efforts, and a twenty-five to thirty-five percent increase in speed for audits and investigations. It also reduced the manual overload for security and governance and improved productivity without needing any additional resources.
What's my experience with pricing, setup cost, and licensing?
The pricing is very competitive. When comparing to the large providers, it is somewhat reasonable. The setup cost is also comparative to the infrastructure, so if I am using on-premises, then I need to only pay for the licenses. Otherwise, I have to pay for every infrastructure cost as well.
Which other solutions did I evaluate?
I did not evaluate any other options and went directly to Veza.
What other advice do I have?
My advice for others looking into using Veza is to proceed with it, as it involves a very complicated graph relation. Overall, Veza is a very good platform. I would rate this review an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google