By 2020, development teams could provision cloud infrastructure independently, while security teams remained responsible for the resulting exposure. Tools built around installing software on individual servers required cooperation from teams that owned those servers. Separate products for containers, configurations and vulnerabilities also left security staff to determine which findings formed a serious attack path. WZ1 WZ2
Wiz
Wiz made cloud security easy to evaluate, then turned a risk map into a shared tool for security and development teams.
Arena: Market Conditions Before Wiz
What shaped the outcome
Step 1 of 4 · 2020
Security interviews changed what the founders built
The founders left Microsoft intending to build a network-security business. Conversations with CISOs redirected them toward the difficulty of understanding an entire cloud environment. In Harry Spitzer’s Sequoia account, those calls continued alongside development, with engineers joining customer discussions. An engineer’s graph of relationships between resources and vulnerabilities became a way to explain the broader product. WZ2
Their experience at Adallom and Microsoft supplied access to buyers and knowledge of large cloud deployments. Interviews still changed the initial plan: customers needed a usable account of their exposure across tools and teams. That made the central product decision consequential. A narrow network tool would have addressed only part of the work those buyers described. WZ1 WZ2
Rivals The relevant alternative was a collection of point products and a narrower network-security offer. Participant testimony documents why the initial idea changed.
Step 2 of 4 · 2020–24
A customer could see its own risks during the evaluation
Wiz connected to cloud environments through permissions and agentless scans, avoiding a rollout of scanning software to each server. Colgate-Palmolive’s CISO says the proof of concept found previously unseen issues within minutes and prompted immediate changes to configurations. The buyer obtained evidence from its own environment before committing to a wider deployment. WZ1 WZ3
This shortened the distance between a sales claim and something a security leader could act on. It also reduced the coordination required to begin an evaluation: the security team could inspect its estate without persuading every development team to install another agent. The initial buying benefit was getting useful visibility quickly. WZ3
Rivals Colgate describes seeking an agentless alternative to deployment-heavy scanning. The customer account is a direct test of the setup benefit, although it does not name every product evaluated.
Step 3 of 4 · 2021–26
The graph helped developers act on security findings
The graph connected vulnerabilities with their surrounding infrastructure, permissions and exposure. At Colgate-Palmolive, developers could inspect and prioritize findings themselves; more than half of its over 60 Wiz users sat outside security. The company connected findings to ticketing and Splunk SOAR so remediation could enter existing work processes. WZ3
The value continued after the first scan. A shared explanation of a risk reduced the handoff from security specialists to the people who could change the system. Spitzer’s account traces the graph to an early design experiment; the customer account shows the resulting tool in use. That connection explains why a quick demonstration could develop into an ongoing workflow. WZ2 WZ3
Rivals Colgate’s prior process made developers wait for security to identify problems. Its reported workflow change is more informative than a feature checklist against another security vendor.
Step 4 of 4 · 2020–26
Experienced enterprise selling amplified the product advantage
Rappaport repeatedly sought investor introductions and help closing major accounts. That access complemented a demonstration based on the prospect’s own cloud. Index reported $350 million in annual recurring revenue for 2023; Contrary’s analysis also emphasizes the combination of rapid deployment and enterprise selling. WZ1 WZ2 WZ5
Large contracts could follow quickly because the founders had both a route to decision makers and a product that made the problem visible. Google’s March 11, 2026 announcement confirmed completion of the acquisition and said Wiz would retain its brand and support the major cloud providers. The completed sale is the endpoint of this independent-company story; the value of later integration belongs to a separate period. WZ4
Rivals Cloud providers sell their own security products, while independent vendors compete across clouds. Google’s commitment to continued multicloud support preserves an important part of the offer customers bought.
Key dates
- 2020Interviews redirect the product
- 2020-10An initial product is ready
- 2021Investors help reach enterprise accounts
- 2023ARR reaches $350 million
- 2024A broader enterprise organization
- 2026-03-11Google completes the acquisition
Sources
Oldest first.
- WZ2 With a Little Help From Their Friends. Investor and founder account
- WZ4 Google completes acquisition of Wiz. Primary disclosure
- WZ1 Cloud Captains: How Assaf Rappaport and his co-founders built Wiz. Investor history
- WZ3 Colgate-Palmolive case study. Customer interview published by vendor
- WZ5 Wiz business breakdown. Outside analysis