Free tools Windows power users keep installed
One-click scans. No signup required.
On August 10, 2023, identity-security company Veza announced strategic investments from Capital One Ventures and ServiceNow Ventures. TechCrunch reported the investment at $15 million, taking Veza’s total financing to $125 million and putting its valuation at approximately $415 million. The later development is just as important: ServiceNow agreed to acquire Veza in December 2025, and said the transaction closed on March 2, 2026. Veza is therefore no longer an independent startup; its technology is now sold as Veza from ServiceNow.
What Veza announced on August 10, 2023
Veza described the transaction as strategic investments rather than a conventional named equity round such as a Series D. The company’s announcement confirmed Capital One Ventures and ServiceNow Ventures as investors and said total financing had reached $125 million. TechCrunch supplied the $15 million round figure and reported a valuation of about $415 million.
| Item | Verified detail |
|---|---|
| Announcement date | August 10, 2023 |
| Investors | Capital One Ventures and ServiceNow Ventures |
| Investment amount | $15 million, according to TechCrunch |
| Total financing afterward | $125 million, according to Veza |
| Reported valuation | Approximately $415 million, according to TechCrunch |
| Individual check sizes | Not disclosed in the cited sources |
Veza’s April 2022 emergence-from-stealth announcement said it had raised $110 million. The additional $15 million mathematically aligns with the later $125 million total, but the company’s 2023 release did not present a detailed financing breakdown.
What Veza built
Veza positioned itself as an identity-security and authorization-intelligence platform, not as a traditional single sign-on or directory product. Its central concept was the Veza Authorization Graph: a normalized map connecting identities, entitlements and protected resources.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
- Identities: employees, contractors, service accounts, workloads, bots and other machine identities.
- Entitlements: roles, group memberships, permissions and inherited access.
- Resources: SaaS applications, on-premises systems, databases, data lakes, cloud infrastructure and custom applications.
For example, an employee might belong to a directory group, inherit a cloud role, retain a dormant SaaS permission and reach a sensitive data warehouse through several linked grants. Veza’s thesis was that security teams need those relationships in one access picture rather than in separate application inventories.
The platform aimed to help organizations find excessive or dormant permissions, risky access paths, policy violations and privilege mismatches, then route findings for review or remediation. That was a product positioning claim, not proof that every connector delivered complete or real-time coverage.
Why fragmented identity tools left a gap
| Category | Typical focus | How Veza was positioned |
|---|---|---|
| IAM | Authentication, single sign-on, MFA and lifecycle access | Visibility into effective permissions across systems |
| IGA | Governance, certifications and joiner-mover-leaver processes | Authorization intelligence spanning heterogeneous systems |
| PAM | Privileged accounts, credentials and sessions | Broader context for privilege and entitlement risk |
| CIEM | Cloud entitlements | Cross-environment access relationships |
| DSPM and data security | Data discovery and data-access risk | Identity-to-permission relationships around data |
| Veza | Authorization graph and access intelligence | A unifying view across identity, permissions and resources |
Enterprises still may need an identity provider, directory, PAM, IGA, cloud-security and data-security controls. Veza was presented as a layer that could connect their access information, not as an automatic replacement for every adjacent system.
Rank #2
Why Capital One and ServiceNow mattered
Capital One Ventures
Veza highlighted Capital One’s experience operating at enterprise and cloud scale and its security expertise. Capital One was an early large-scale cloud adopter, making its perspective on cloud authorization strategically relevant. The available announcements do not establish that Capital One became a Veza customer, reseller or integration partner because of the investment.
Recommended Free Tools
Veza explained the rationale in its company blog, while the formal announcement appears at Veza’s press room.
ServiceNow Ventures
ServiceNow’s workflow, security, risk and enterprise-platform products could use normalized authorization data for identity governance, permission monitoring, access requests, remediation workflows, cloud access management and data-security processes. In 2023, that was an investor relationship; in retrospect, it became an ownership path.
Rank #3
What Veza said it would do with the money
Veza said the capital would support:
- Faster product development
- More integrations with enterprise systems
- Expanded sales capacity
- Broader go-to-market execution
The company said it had exceeded 100 integrations and reached more than 125 integrations by the August announcement, including an integration for Azure OpenAI Service. Integration count alone does not show how deeply a connector can read, interpret or enforce permissions.
Veza’s reported 2023 traction
TechCrunch reported that Veza had more than 100 customers, expected to employ about 150 people by the end of 2023 and listed companies including Wynn Resorts, Blackstone, Expedia, SoFi, Warby Parker, Wayfair, Zoom and Intuit among its customers or claimed customer portfolio. TechCrunch also reported that the client portfolio had more than tripled since Veza emerged from stealth.
Veza separately said it had quintupled revenue and doubled headcount in the preceding fiscal year. Those growth figures are company-reported claims, not independently audited results in the cited material.
Rank #4
Where Veza fit competitively
TechCrunch identified overlap or competition with SailPoint, CyberArk, Saviynt, Okta, Obsidian Security and other identity, access-governance, privilege-management and cloud-security vendors. The practical comparison depends on the problem being solved:
- Authentication and workforce identity: Okta and Microsoft Entra are more directly associated with identity-provider functions such as SSO, MFA and conditional access.
- Governance: SailPoint and Saviynt emphasize access certifications, lifecycle management and compliance workflows.
- Privileged access: CyberArk concentrates on privileged identities, secrets and sessions.
- Cloud exposure: Wiz focuses on cloud-security posture and exposure, including identity-related cloud risk.
- Authorization intelligence: Veza’s distinction was the cross-system graph connecting permissions to identities and resources.
A graph abstraction can simplify analysis, but buyers must confirm how nested groups, inherited roles, application-local permissions and machine identities are represented. Broad visibility is not the same as safe enforcement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened after the investment
ServiceNow announced an agreement to acquire Veza on December 2, 2025. ServiceNow’s updated announcement says the transaction closed on March 2, 2026. The acquisition price was not stated in the reviewed sources.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
ServiceNow now markets the product as Veza from ServiceNow. Its current positioning covers human, non-human and AI-agent identities, with access intelligence, risk scoring, governance, reviews and remediation. The AI-agent emphasis is more prominent in the post-acquisition product story than it was in the 2023 funding announcement.
ServiceNow’s broader integration context is described in its enterprise identity control-plane update and its 2026 security-portfolio announcement at ServiceNow’s newsroom.
What enterprise buyers should test
The right evaluation is a proof of coverage, freshness and safe action—not a count of marketing integrations.
- Map real systems: Test the company’s actual SaaS, cloud, databases, data warehouses, custom applications and infrastructure.
- Trace effective access: Ask the vendor to explain a named employee, service account and AI agent, including nested groups and inherited permissions.
- Check data freshness: Confirm synchronization frequency for each connector and whether “real time” applies to all systems or only selected ones.
- Test remediation: Determine whether the product can revoke or modify access, or only identify risk. Require approvals, rollback and change records for automated actions.
- Review governance fit: Establish whether it complements or replaces existing access reviews, certification campaigns, separation-of-duties controls and joiner-mover-leaver processes.
- Validate machine-identity ownership: Include service accounts, API keys, bots and workloads that may lack accountable owners.
- Check operations and data handling: Confirm workflow integrations, hosting regions, residency, metadata retention, encryption, tenant isolation and required privileges.
- Clarify commercial terms: ServiceNow does not publish list pricing in the cited material. Ask whether licensing is based on users, identities, connectors, assets, data volume or modules, and verify which capabilities are generally available.
Who benefits most—and who may not
Veza from ServiceNow is most compelling for large organizations already invested in ServiceNow workflows, risk management or security operations and trying to connect identity findings to remediation. It is less suited to a small organization seeking transparent self-service pricing, a lightweight SSO product or only password and MFA controls.
Organizations that do not want to center identity workflows on ServiceNow may prefer a standalone governance, privileged-access, identity-provider or cloud-security specialist. The key question is whether the buyer needs a broad authorization graph and workflow integration, or deeper control in one narrower identity domain.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




