Exit value 01
32000 USD M [CO006] Diligence report
Wiz
Cloud Security Platform — September 2026 Refresh
Wiz remains a category-defining cloud security platform, but after Google's $32B acquisition the right lens is post-close product continuity rather than fresh standalone valuation upside.
Coverage and disclosure
This refresh uses the canonical run date from the chapter runtime context and emphasizes volatile facts that can move month to month: acquisition status, funding history, revenue scale, customer proof, product scope, and post-close roadmap risk. Public financial disclosure remains limited after Google's acquisition, so valuation and operating conclusions are intentionally conservative.
Cover facts
Company profile
Wiz is a cloud security platform that connects code, cloud, runtime, and AI security into a single context layer for enterprise cloud estates. Public evidence shows broad adoption, agentless deployment, and strong multi-cloud positioning, but the company is now a Google Cloud asset, so the diligence question has shifted from standalone growth to post-close product continuity and roadmap priority.
- Website
- www.wiz.io
- Founded
- 2020-01-01
- Founders
- Assaf Rappaport, Ami Luttwak, Yinon Costica, Roy Reznik
- Founding location
- Tel Aviv, Israel
- Headquarters
- New York, NY, United States
- Product
- Wiz sells a cloud security platform spanning posture, runtime, CI/CD, and AI security, with agentless scanning and a shared context graph.
- Customers
- Enterprise security, cloud engineering, and platform teams running multi-cloud estates
- Business model
- Enterprise SaaS priced against protected cloud workload footprint and expansion modules
- Stage
- Acquired
- Funding status
- Publicly reported $1B round at a $12B valuation before Google's $32B acquisition
Executive summary
Top strengths
- Category-leading scale and a realized $32B exit
- Strong enterprise adoption with multi-cloud and AI-security relevance
- Low-friction deployment model with a deep cloud-context graph
Top risks
- Standalone asset no longer exists after acquisition
- Post-close roadmap and support priority depend on Google
- Public operating economics remain opaque
Open gaps
- Post-close packaging and operating economics inside Google Cloud
- Whether multi-cloud support remains first-class over time
- Public margin, NRR, and retention detail are still undisclosed
Contents
01Company Overview
1.1 Identity and product model
Wiz presents itself as a cloud and AI security platform that helps organizations create secure environments across all major clouds. The current public record matters because the company is no longer a standalone venture: Google says it completed the acquisition, retained the Wiz brand, and will continue to support multiple clouds. That makes Wiz best understood as a platform brand inside Google Cloud rather than as a fresh private-market security startup. The product story is still coherent. The company’s own materials emphasize a normalizing layer across cloud environments, with code, cloud, and runtime context feeding a single risk view. That positioning is central to the rest of the report because it explains why Wiz can convert technical visibility into enterprise adoption and why it is often discussed as a CNAPP-style platform rather than a narrow scanner.[CO001, CO003, CO006, CO010]
| metric | value/status | date | confidence | gap |
|---|---|---|---|---|
| Founding | Launched in Jan 2020 | 2020-01 | medium | |
| Founders | Assaf Rappaport, Ami Luttwak, Yinon Costica, Roy Reznik | 2020 | medium | |
| Headquarters | New York, NY | 2026-09 | medium | |
| Current status | Part of Google Cloud; Wiz brand retained | 2026-03 | medium | |
| Latest public exit value | 32000 | 2026-03 | medium | USD M; acquisition price rather than an operating valuation |
| Latest public ARR reference | 1000 | 2026-03 | medium | USD M; last public run-rate before exit |
| Fortune 100 customers | 65% | 2026-09 | medium | |
| Cloud workloads protected | 5000000 | 2026-09 | medium | |
| Files scanned daily | 230000000000 | 2026-09 | medium | |
| Employee count | 1,001-5,000 range on public profile | 2026-09 | medium | Approximate external profile range, not a verified headcount |
Public profile figures mix direct company claims, acquisition disclosures, and third-party estimates; treat ARR and headcount as the latest public references rather than audited financials.
[CO001, CO002, CO004, CO005, CO006, CO007, CO008, CO009, CO010, CO012]1.2 Leadership, funding, and scale
The founding team remains the main continuity asset. Public and partner sources consistently name Assaf Rappaport, Ami Luttwak, Yinon Costica, and Roy Reznik, and Insight’s profile of the founders is explicit that the team had already worked together at Adallom and Microsoft. That background matters because Wiz’s credibility is partly a founder story: the same group already learned how to ship and scale a cloud-security product before founding Wiz. Funding and scale also look unusually strong for a security company. Public references point to a $100M Series A, a later $1B round, and a pre-acquisition ARR path that crossed $1B. Wiz’s own about page adds customer-scale proof with the Fortune 100 and workload metrics. For diligence, that combination supports a conclusion that Wiz reached genuine enterprise scale before Google bought it.[CO002, CO004, CO005, CO008, CO009]
| person | role | background | founder-market fit | key-person dependency |
|---|---|---|---|---|
| Assaf Rappaport | CEO | Co-founder; previously built Adallom and led cloud-security work at Microsoft | High | high |
| Ami Luttwak | CTO | Co-founder; cloud-security and architecture background | High | high |
| Yinon Costica | VP Product | Co-founder; product and customer context | High | medium |
| Roy Reznik | VP R&D | Co-founder; engineering and scale | High | medium |
This is a short founder/leadership enumeration based on the public record; it is not a board or org-chart audit.
[CO002, CO010]| stakeholder | role | importance | diligence ask | note |
|---|---|---|---|---|
| Google Cloud | Acquirer / operating owner | very high | Preserve multi-cloud support and product continuity | Current owner |
| Founders | Operators / continuity holders | very high | Maintain product strategy and culture | Founding team remains central |
| Early investors | Equity backers | high | Understand exit economics and any rollover terms | Includes the Series A backers |
| Enterprise customers | Revenue base | very high | Check retention and expansion quality | Scale is broad but opaque |
| Partners / marketplace ecosystem | Distribution | high | Confirm channel economics and priority | Important for go-to-market |
This map is a public-stakeholder view, not a legal cap table or full organizational chart.
[CO001, CO006, CO008, CO010]1.3 Milestones, credibility, and remaining gaps
The public chronology is straightforward: launch in 2020, rapid enterprise traction, larger funding, then a March 2026 Google acquisition. The external validation stack is also notable. Reuters coverage shows Wiz still participating in security research and public security commentary, while LinkedIn and startup databases place the company in New York and describe a sizable workforce. Those are not perfect diligence substitutes, but they do reinforce that Wiz was already operating at broad enterprise scale before the exit. The main gap is post-close economics. Public sources clearly support the acquisition value and the pre-close ARR storyline, but they do not provide a fresh standalone financial picture after the Google transaction. That is why this report treats valuation, revenue, and headcount carefully and carries the missing disclosure forward as a diligence gap rather than inventing precision.[CO007, CO011, CO012]
Wiz moved from stealth launch to Google Cloud acquisition while keeping its multi-cloud security positioning.
[CO001, CO002, CO003, CO006, CO008, CO009, CO012]02Market Analysis
2.1 Market boundary and substitutes
The public evidence supports a market boundary around cloud-native application protection rather than a single point category. Wiz, Omdia, AWS, and Google all describe the problem in terms of cloud context, posture, runtime, and response. That makes the real market larger than CSPM alone and narrower than all of enterprise cybersecurity. The practical substitute set includes native cloud controls, spreadsheets, and broader security suites. For diligence purposes, the important takeaway is that Wiz is competing in a category where value depends on how much context it can assemble, how quickly it can surface critical risk, and how much it can compress the number of tools a buyer needs to stitch together. The market is therefore driven by visibility and remediation workflow, not just by alert volume.[CM001, CM002, CM012]
| segment | included spend | excluded spend | buyer/payer | relevance |
|---|---|---|---|---|
| CNAPP / posture | Cloud vulnerability, misconfiguration, and identity risk tooling | Endpoint-only or SOC-only budgets | CISO / cloud security | Core |
| Runtime / workload | Runtime threat detection and workload controls | Seat-based productivity security | SecOps / platform | Core |
| AI security | Visibility and policy around AI apps and agents | Generic ML platform spend | Security + AI engineering | Emerging |
| Cloud engineering | Read-only cloud context and graphing | Infra monitoring not tied to risk | Platform engineering | High |
| Regulated workloads | Medical, financial, and public-sector cloud estates | Consumer-only utilities | Security and compliance | High |
| Status-quo alternatives | Native cloud controls and spreadsheets | Traditional SIEM replacement only | Cloud owners | Medium |
| Incumbent suite buyers | Platform consolidation spend | Best-of-breed only procurement | Enterprise security | High |
| AI transformation programs | Cloud and AI app security modernization | Pure data-science tooling | CIO / AI leads | Emerging |
| Adoption triggers | Audit findings, cloud sprawl, AI launches | No-change environments | Security leadership | High |
| Primary constraint | Procurement and trust calibration | No budget constraint | CISO / risk | High |
This is a qualitative market map built from public product, analyst, and partner references; it is not a formal TAM model.
[CM001, CM002, CM003, CM004, CM005, CM008, CM009, CM010, CM011, CM012]Wiz sits in the middle of a layered market that starts with cloud visibility and ends with AI-aware security operations.
Layer widths indicate hierarchy, not quantitative proportions.
The layers are an evidence-based synthesis of product and analyst sources rather than a formally published market hierarchy.
[CM001, CM002, CM004, CM008, CM010, CM012]2.2 Buyer segments and adoption triggers
Buyer demand appears to span security operations, cloud engineering, platform engineering, application security, and increasingly AI-security teams. AWS’s medical-center example and Omdia’s analyst framing both support the view that regulated, large-enterprise environments are the natural first buyers, because they feel the pain of cloud sprawl, compliance pressure, and cross-cloud complexity most acutely. Adoption is triggered less by generic awareness than by audit findings, migration initiatives, or an AI launch that suddenly exposes a new class of risk. Wiz’s own messaging about a normalizing layer and agentless deployment helps the buyer path, but the SecurityScientist Q&A pattern shows that customers still need education on implementation, trust, and value proof before the budget closes.[CM003, CM004, CM005, CM006, CM009, CM011]
| lens | source | value/status | confidence | limitation |
|---|---|---|---|---|
| Cloud security budget | Analyst / vendor commentary | large and growing | medium | No single audited market number |
| CNAPP spend | Analyst framing | meaningful but fragmented | medium | Varies by cloud mix |
| AI security spend | Company and partner claims | emerging | low | Category is still forming |
| Large enterprise buyer pool | AWS / Google / partner proof | concentrated | medium | Adoption is uneven |
| Regulated workloads | Public case studies | high-fit segment | medium | Needs further sizing |
| Multi-cloud estates | Company positioning | core target | high | No precise share disclosed |
| Post-acquisition cross-sell | Google Cloud integration | potential upside | medium | Not yet a public revenue line |
| Native cloud substitutes | Hyperscaler offerings | meaningful competition | high | Not a pure budget line |
| Operational risk budget | Security and compliance teams | recurring | medium | Often hidden in broader security spend |
| AI transformation programs | Enterprise roadmap | early-stage | low | Still developing |
This sizing lens is deliberately directional; public sources support the categories but not a reliable single-point TAM.
[CM001, CM003, CM004, CM008, CM009, CM010, CM012]| segment | buyer | user | payer | adoption trigger |
|---|---|---|---|---|
| Security operations | CISO | SecOps analyst | Security budget | Audit or incident pressure |
| Cloud engineering | VP Eng / platform lead | Platform team | Infra budget | Cloud sprawl or migration |
| Application security | AppSec lead | DevSecOps | Security budget | CI/CD risk reduction |
| AI security | AI platform lead | ML / platform team | Security + AI budget | Agent or model launch |
| Regulated enterprise | Compliance / risk | Security and audit teams | Enterprise security | Regulator or customer demand |
| Public sector / healthcare | CISO / security officer | Infrastructure team | Central budget | Cloud modernization |
| Partner-led channel | MSP / MSSP | Services team | Joint deal | Need for deployment help |
| Google Cloud customer | Cloud security buyer | Security and platform teams | Cloud + security budget | Vendor consolidation |
| Mid-market starter | Security manager | Small security team | Security budget | Startup program / credits |
| Large multi-cloud estate | Enterprise security leadership | Platform + SecOps | Shared budget | Cross-cloud risk visibility |
The segment map reflects public buyer and partner evidence, not a full customer segmentation study.
[CM002, CM003, CM005, CM006, CM008, CM009, CM010, CM011]2.3 AI-era growth and the consolidation signal
Google’s acquisition of Wiz is also a market signal. The buyer value proposition now includes AI-security coverage, not only classic cloud posture management. Google explicitly says Wiz will continue to support major clouds, which suggests that the acquisition is being positioned as a platform expansion rather than a retrenchment into a single hyperscaler environment. The broader consolidation signal is that buyers increasingly prefer integrated platforms that can connect cloud visibility, runtime response, and AI context. Reuters’ adverse coverage and the public partner ecosystem both show that security is not a solved problem; the market still rewards platforms that can normalize context across many environments.[CM007, CM008, CM010, CM012]
03Competitors
3.1 Competitive set after acquisition
Wiz’s competitive set changed once Google closed the acquisition. The company is no longer a pure startup competing on product alone; it is now a brand inside Google Cloud, so distribution leverage and bundling matter more. That does not eliminate competition. It changes it. In practice, the relevant field now includes hyperscaler-native security, broad suite vendors, and specialist CNAPP companies that still promise faster time-to-value. Public comparison pages consistently treat Wiz as a benchmark company rather than a fringe vendor. That is a sign of strength, but also of category maturity: buyers evaluate Wiz against platform suites and native cloud controls, not only against niche posture scanners.[CP001, CP002, CP003, CP009]
| segment | examples | why buyers care | Wiz implication | limitation |
|---|---|---|---|---|
| Hyperscaler-native | Google Cloud, Microsoft, AWS | Bundle power and native integration | Wiz must stay multi-cloud and differentiated | May win on platform tie-in |
| Suite incumbents | Palo Alto, CrowdStrike | Budget consolidation and existing contracts | Wiz must justify standalone value | Deeper suite footprint |
| CNAPP specialists | Orca-style peers | Agentless and quick time-to-value | Wiz competes on graph depth and enterprise scale | Some have similar deployment model |
| Open-source / DIY | DIY / self-managed stacks | Control and sovereignty | Wiz must beat flexibility with ease | Higher operational burden |
| Niche point tools | CSPM/CWPP point products | Lower immediate cost | Wiz offers broader context | May be cheaper for one use case |
| Internal build | Platform teams | Maximum control | Wiz must reduce build-versus-buy friction | Engineering effort |
| Channel bundles | MSP / MSSP bundles | Procurement simplicity | Wiz must keep partner economics healthy | Partner margin pressure |
| Adjacent AI security | AI app security tools | AI launch risk | Wiz can expand the TAM | Category still emerging |
| Compliance-only | Audit tools | Regulatory reporting | Wiz must show operational remediation | No runtime depth |
| Cloud-native alternatives | Native cloud controls | Default procurement path | Wiz must outperform native tooling | Cloud vendors can subsidize |
This is a qualitative competitive synthesis using public coverage of Wiz and its market position; it is not a live vendor benchmark or pricing scrape.
[CP001, CP002, CP003, CP005, CP006, CP007, CP009, CP010, CP011, CP012]Wiz sits near the top-right of the CNAPP market, but hyperscalers and suite vendors pull hard on distribution and bundling.
| Item | Distribution leverage (0-10 ordinal) (3–10) | Buyer optionality / deployment flexibility (0-10 ordinal) (4–10) | Context |
|---|---|---|---|
| 1. Wiz | 8 | 6 | Strong product context with multi-cloud reach. |
| 2. Hyperscalers | 10 | 4 | Strong bundle power, lower buyer optionality. |
| 3. Suite incumbents | 9 | 5 | Cross-sell depth and procurement leverage. |
| 4. CNAPP specialists | 6 | 7 | Often agile but narrower scale. |
| 5. Open-source / DIY | 3 | 10 | High control, low turnkey simplicity. |
| 6. Channel bundles | 7 | 5 | Partner routes can widen reach but add complexity. |
Ordinal scores synthesize public product, distribution, and ownership evidence rather than reported vendor metrics.
[CP001, CP003, CP005, CP006, CP009, CP012]3.2 Moat and substitute pressure
The public moat story is still the graph and the context layer. Google’s acquisition blog emphasizes code, cloud, runtime, and AI context, while Sacra and other market pages frame Wiz as a category benchmark. That suggests the real moat is not lock-in but the ability to normalize multi-cloud data, prioritize risk, and keep the product easy enough to adopt at enterprise scale. Substitute pressure remains real. Suite incumbents can bundle; hyperscalers can subsidize; open-source or DIY paths can satisfy control-oriented buyers; and niche tools can win narrow use cases. For underwriting, the question is not whether competition exists. It is whether Wiz’s context graph and brand strength are enough to keep conversion and retention strong against these substitute classes.[CP004, CP005, CP006, CP007, CP010, CP011, CP012]
3.3 What is still missing from the public record
The competitive record is still incomplete on one obvious point: there is no clean, current, product-by-product public benchmark that proves where Wiz wins on every workload or where it loses on price. That gap matters because pricing and suite consolidation are often decisive in cloud security. Reuters’ adverse security story also reminds the reader that reputation risk can move alongside category leadership. In other words, Wiz is still a strong competitive reference point, but the evidence set is now more about strategic positioning than about a neatly publishable feature matrix. That is a normal consequence of being acquired by a hyperscaler and of operating in a market where many vendors compete with overlapping claims.[CP008, CP009, CP012]
| competitor class | buyer concern | Wiz strength | competitor pressure | implication |
|---|---|---|---|---|
| Hyperscaler-native | Bundle and native integration | Multi-cloud reach | Strong distribution leverage | Must preserve neutrality |
| Suite incumbents | Procurement consolidation | Context depth | Cross-sell and contract bundling | Must justify standalone spend |
| CNAPP specialists | Fast adoption | Brand and scale | Similar deployment model | Competition is feature-close |
| Open-source / DIY | Control and sovereignty | Ease of rollout | Maximum flexibility | Need lower operational burden |
| Point tools | Cost for one use case | Broader platform coverage | Cheaper for narrow budgets | Win on breadth and context |
| Internal build | Engineering control | Faster time-to-value | Tailored architecture | Reduce build-vs-buy friction |
| Channel bundles | Partner convenience | Ecosystem presence | MSP / MSSP packaging | Keep partner economics aligned |
| Adjacent AI tools | AI launch risk | Cloud context foundation | Emerging category claims | Expand into the adjacent budget |
This lens separates the competitive field into buyer-facing classes rather than named vendors only.
[CP001, CP002, CP004, CP005, CP006, CP007, CP008, CP010, CP011]| substitute | typical buyer trigger | why it wins | why Wiz still wins |
|---|---|---|---|
| Native cloud controls | Default procurement | Already bundled | Broader context and workflow |
| Spreadsheet / manual review | Small or early teams | Cheap and simple | Scales better with cloud sprawl |
| Narrow CSPM | Cost-sensitive posture buy | Lower price | Faster context across more surfaces |
| Security suite add-on | Consolidation deal | Contract leverage | Better cloud-native depth |
| DIY graphing | Platform team appetite | Full control | Faster to deploy and maintain |
| Point runtime tool | Incident-driven purchase | Strong on one use case | Better tie-in to cloud posture |
| MSP bundle | Outsourced operations | Operational convenience | Direct product control and visibility |
| Internal development | Large engineering orgs | Custom fit | Lower maintenance burden |
The substitute set matters because Wiz must win on workflow and context, not just on feature count.
[CP004, CP005, CP006, CP007, CP009, CP010]04Financials
4.1 How Wiz made money
Public sources consistently describe Wiz as a subscription SaaS business that priced against the number of cloud workloads it protected. That matters because it means revenue should scale with customer cloud footprint, not with employee headcount. The model also explains why land-and-expand mechanics were so powerful: once a customer proved value on one cloud estate, additional workloads could be brought into the contract. The clearest public revenue signal is the ARR timeline. Third-party trackers and company references place Wiz above $1B ARR before the Google acquisition closed, while older milestones show $100M ARR in roughly 18 months. That is a very strong revenue-quality signal for a private security company, even though the exact operating margin data remains undisclosed.[CI001, CI002, CI003, CI008]
| stream | mechanism | unit | current value/status | quality | diligence ask |
|---|---|---|---|---|---|
| Core cloud security | Subscription SaaS | Protected workload | Enterprise priced | Strong | Confirm gross-margin path |
| AI security expansion | Add-on modules | Feature bundle | Emerging | Medium | Validate attach rate |
| Startup entry | Discounted credits / startup program | Program access | Observed | Low | Check conversion to paid |
| Enterprise expansion | Land-and-expand | Account / workload | Observed | Strong | Obtain NRR / renewal data |
| Partner sales | Marketplace / alliance routes | Channel deal | Observed | Medium | Check channel take rate |
| Cross-cloud usage | Billed by protected footprint | Workload | Observed | Strong | Confirm mix by cloud |
| Acquisition premium | Exit value | Enterprise value | $32B | Strong | Assess multiple at exit |
| ARR milestone | Reported / estimated ARR | USD M | >$1B | Medium | Use latest public milestone only |
| Funding base | Primary rounds | Capital raised | $1B round at $12B | Strong | Reconcile lifetime proceeds |
| Disclosure gap | No public margins/burn | N/A | Still opaque | Weak | Request operating financials |
Revenue and pricing are synthesized from public company, analyst, and partner sources; exact margins and burn are not publicly disclosed.
[CI001, CI002, CI003, CI004, CI005, CI006, CI007, CI008, CI009, CI011]Wiz monetized cloud footprint growth by pricing against protected workloads and expanding across cloud, runtime, and AI security.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Customer cloud footprint [cloud] | AWS, Azure, GCP, and other environments create protected workloads. | |
| Node 2 | Agentless scan and graph [scan] | Read-only access builds context and surfaces critical risk. | |
| Node 3 | Workload pricing [license] | Revenue scales with the amount of cloud footprint protected. | |
| Node 4 | Module expansion [expand] | Runtime, AI, and response features raise ACV. | |
| Node 5 | Enterprise renewal [renew] | Land-and-expand and partner channels create larger contracts. | |
| Node 6 | Google acquisition [exit] | The standalone revenue model ended with the $32B exit. | |
| Connection 1 | Customer cloud footprint [cloud] | Agentless scan and graph [scan] | |
| Connection 2 | Agentless scan and graph [scan] | Workload pricing [license] | |
| Connection 3 | Workload pricing [license] | Module expansion [expand] | |
| Connection 4 | Module expansion [expand] | Enterprise renewal [renew] | |
| Connection 5 | Enterprise renewal [renew] | Google acquisition [exit] |
4.2 Funding and exit economics
The financing story is also unusually strong. Wiz publicly celebrated a $1B round at a $12B valuation, and the March 2026 Google acquisition closed at $32B all-cash. That is enough to show that the company moved from venture scale to exit scale without a visible funding crunch. Insight’s founder profile adds an important nuance: a preexisting team and customer network likely helped reduce go-to-market waste. In diligence terms, the most useful conclusion is that capital efficiency was good enough to support a very fast revenue ramp, but the exact margin structure still cannot be rebuilt from public documents alone.[CI004, CI005, CI010, CI011]
4.3 What still needs diligence
The remaining gap is classic private-company opacity. Public sources do not provide margin, cash-burn, CAC payback, or renewal detail with enough precision to underwrite the business the way a later-stage financial sponsor would. There are also modest conflicts in the public ARR narrative: some sources track the company differently by date, so the safest approach is to treat the latest milestone rather than any single exact estimate as canonical. That leaves the right financial conclusion in a refresh report: Wiz proved product-market fit and exit value, but public disclosure no longer supports a standalone operating model with the same precision after the acquisition.[CI006, CI007, CI012]
| diligence area | public signal | why it matters | current gap |
|---|---|---|---|
| Gross margin | Not disclosed | Shows operating leverage | No public line item |
| Burn / cash flow | Not disclosed | Indicates capital efficiency | No audited detail |
| CAC payback | Not disclosed | Measures sales efficiency | No cohort data |
| Retention / NRR | Not disclosed | Reveals expansion quality | No contract metric |
| Pricing mix | Workload-based inference | Helps model revenue scale | No public rate card |
| Geographic mix | Global enterprise hints | Affects sales efficiency | No revenue split |
| Channel economics | Partner activity visible | Influences CAC and margin | No take-rate data |
| Post-close reporting | Google-owned now | Could change disclosure access | Standalone detail unavailable |
This table is intentionally conservative because the company is no longer public and the exact operating model is opaque.
[CI006, CI007, CI012]| milestone | public anchor | implication | diligence takeaway |
|---|---|---|---|
| Early financing | $6M seed / early backing | Proved founder-market fit | Venture risk was taken early |
| Scale round | $1B at $12B | Strong growth signal | Valuation tracked revenue build |
| ARR milestone | >$1B ARR | Revenue quality mattered | Growth justified premium multiples |
| Exit | $32B all-cash | Value realized | Standalone upside ended |
| Post-close state | Google ownership | No fresh entry | Monitor integration only |
| Missing disclosures | No margins/burn | Hard to rebuild model | Underwrite conservatively |
| Secondary interest | Pre-IPO pages | Some private-market demand | Not a substitute for operating data |
| Risk overhang | Public scrutiny persists | Reputational noise can matter | Security headlines still affect trust |
A bridge table is more useful than a point estimate after the acquisition closes.
[CI001, CI002, CI004, CI005, CI008, CI010, CI011]05Product & Technology
5.1 What Wiz actually ships
Wiz’s own positioning is unusually consistent across sources: it wants to connect code, cloud, and runtime into a single context layer. That makes the product less like a point scanner and more like a risk graph that can be used by security, engineering, and platform teams. The Google acquisition blog reinforces that reading by describing the platform as a system for rapid mapping of architecture, permissions, data flows, and runtime behavior. The practical product implication is that the platform should be understood as workflow infrastructure. It is not just a dashboard. It is a way to normalize cloud context so that security teams can prioritize what matters before it reaches production.[CE001, CE002, CE011]
| module / layer | customer job | maturity | differentiation | risk |
|---|---|---|---|---|
| Cloud context graph | Map assets and exposures | Core | Single context layer | Graph quality must stay current |
| Agentless scanning | Inspect cloud without heavy deployment | Core | Low-friction rollout | Cloud access trust |
| Runtime visibility | See live behavior | Growing | Context across runtime | Coverage can lag edge cases |
| CI/CD security | Shift left before deployment | Growing | Developer alignment | Tool sprawl |
| AI security | Protect AI apps and agents | Emerging | Current-era relevance | Category still maturing |
| Response / triage | Prioritize and remediate | Core | Business-impact ranking | Workflow integration |
| Integrations | Connect to cloud and security stack | Core | Ecosystem depth | Maintenance load |
| Trust controls | Security, privacy, compliance | Core | Enterprise readiness | Acquisition roadmap uncertainty |
| Developer surface | GitHub / code workflow visibility | Emerging | Builder credibility | Adoption breadth |
| Marketplace exposure | Partner distribution | Core | Broader reach | Channel complexity |
This table synthesizes the product and operating model from company, technical, and third-party coverage; maturity labels are qualitative.
[CE001, CE002, CE003, CE004, CE005, CE009, CE010, CE011, CE012]Wiz stacks cloud context, workflow integrations, and trust controls, but the remaining question is how AI and Google-owned roadmap choices affect that stack.
- Experience
- Security teams and developers work from the same surface
- Modules
- Console
- Dashboards
- Outputs
- Workflow view
- Code and CI/CD
- Shift-left checks and developer tooling
- Modules
- CI/CD tools
- GitHub presence
- Outputs
- Pre-deploy findings
- Cloud context
- Agentless cloud graph and asset inventory
- Modules
- Scanner
- Graph
- Outputs
- Risk map
- Runtime
- Live workload and exposure context
- Modules
- Runtime visibility
- Outputs
- Attack paths
- AI security
- Visibility into AI apps, agents, and risks
- Modules
- AI security
- Outputs
- AI safeguards
- Trust and operations
- Compliance, privacy, and response controls
- Modules
- Security controls
- Support
- Outputs
- Enterprise readiness
Layering is an evidence-based synthesis of public platform descriptions and third-party reconstructions.
[CE006, CE007, CE008]5.2 How it deploys and differentiates
The technical differentiator is deployment friction. Wiz repeatedly emphasizes agentless scanning and read-only cloud access, which reduces rollout burden relative to heavyweight agents or sidecars. That helps explain why public references frame the product as both fast to deploy and enterprise-friendly. GitHub activity and CI/CD material show the company also wants credibility with developers, not just security operators. The second differentiator is context depth. Third-party reconstructions describe Wiz as a security graph, which is consistent with the company’s own language about shared context and with Google’s statement that Wiz strengthens code-to-cloud security. In other words, the moat is not a single feature. It is the amount of context the system can safely assemble and operationalize.[CE003, CE004, CE005, CE009, CE010]
5.3 Trust, AI, and remaining roadmap risk
The product has also expanded into AI security. Google says Wiz now covers AI applications and agents, which keeps the platform relevant as cloud buyers move into model-based workflows. That matters because AI security is becoming a budget line in its own right, not just an add-on to classic cloud posture. Still, the product story is not free of risk. External coverage of a Wiz-found security hole and the existence of alternative-code-security pages show that the market expects continuous proof. After the Google acquisition, the remaining open question is roadmap priority: the public evidence supports strength today, but it is less clear how quickly Wiz’s platform will evolve inside Google’s broader security stack.[CE006, CE007, CE008, CE012]
| approach | rollout burden | trust requirement | typical buyer concern | Wiz implication |
|---|---|---|---|---|
| Agentless read-only | Low | Medium | Cloud access permissions | Easier enterprise rollout |
| Heavy agent / sidecar | High | High | Operational overhead | Less attractive for fast adoption |
| Native cloud controls | Low | Medium | Coverage gaps | Easier to buy but narrower |
| DIY graphing | High | High | Maintenance burden | Wiz should win on simplicity |
| SIEM add-on | Medium | Medium | Context depth | Needs deeper cloud semantics |
| AI module | Medium | High | New risk class | Expands the platform story |
| Partner-assisted rollout | Medium | Medium | Services dependency | Helps large accounts deploy |
| Read-only benchmark | Low | Medium | Proof of value | Supports trial and adoption |
Deployment friction is the practical differentiator behind the product story.
[CE003, CE004, CE005, CE009, CE010]| risk area | current signal | severity | diligence question | implication |
|---|---|---|---|---|
| AI security | Category is emerging | Medium | Does the platform meaningfully protect AI apps and agents? | Budget opportunity but still maturing |
| Acquisition roadmap | Google controls priority | High | Will multi-cloud remain first-class? | Integration could slow pace |
| External scrutiny | Security headlines persist | Medium | Can Wiz preserve trust under Google? | Reputation risk remains live |
| Developer adoption | GitHub and CI/CD surface exists | Medium | Is there enough developer pull? | Broader use can improve stickiness |
| Platform integration | Context layer spans code to cloud | Medium | Does the stack stay coherent? | Cross-product value matters |
| Product depth | Runtime and cloud graph are core | High | Are edge cases covered? | Depth supports premium positioning |
| Trust controls | Enterprise readiness emphasized | Medium | Are controls still current post-close? | Must keep enterprise buyers comfortable |
| Roadmap focus | More surface area after acquisition | High | What gets deprioritized? | Execution risk rises |
This matrix is intended to separate product risk from pure market risk.
[CE006, CE007, CE008, CE012]06Customers
6.1 Customer scale and segment mix
The public customer story is one of the strongest parts of the Wiz record. Wiz says 65% of the Fortune 100 are customers, and its public about page also points to 5 million workloads protected and 230 billion files scanned daily. That is enough to conclude that the company reached enterprise-scale adoption before the Google deal. The customer mix looks broad rather than narrow. Named proof appears in enterprise, research, cloud, and partner contexts, which suggests that the product can land with both security and platform teams. That breadth matters because it supports the idea that Wiz is not a one-segment tool; it is a cloud-security platform with multiple adoption surfaces.[CU001, CU002, CU003, CU005]
| segment | buyer/user/payer | use case | scale | value | gap |
|---|---|---|---|---|---|
| Fortune 100 enterprise | CISO / cloud security | Cloud risk visibility | Very large | High | No retention disclosure |
| Research university | Security / platform team | Cloud exposure reduction | Large | High | No contract length disclosed |
| Partner-led enterprise | MSP / alliance channel | Deployment and expansion | Variable | High | Channel economics opaque |
| Identity / AI partner | Security operations | Non-human identity and AI security | Emerging | Medium | Attach-rate unknown |
| Cloud-native buyer | Cloud engineering | Read-only posture and runtime risk | Large | High | No cohort data |
| Public-sector / regulated | Compliance and security | Audit and remediation | Large | High | No vertical concentration data |
| Mid-market entrant | Security lead | Startup program / entry offer | Smaller | Medium | Conversion to paid unclear |
| Google Cloud customer | Cloud security | Case-study deployment | Large | High | No revenue split disclosed |
| Adoption proof | All of the above | Large-scale rollout | Broad | High | Top-account concentration unknown |
| Expansion proof | Existing customers | Cross-cloud and partner add-ons | Broad | Medium | NRR not public |
This table mixes public logos, partner proof, and case studies; it is intentionally conservative on retention and concentration because those metrics are not public.
[CU001, CU002, CU003, CU004, CU005, CU006, CU007, CU010, CU011, CU012]Wiz adoption appears to move from cloud-security awareness into enterprise rollout, then into partner-led expansion.
The journey is a synthesis of customer case studies, partner pages, and public scale claims rather than a measured funnel.
[CU001, CU002, CU003, CU004, CU005, CU006, CU007, CU010, CU011]6.2 How adoption expands
The public record points to a classic land-and-expand motion. Google Cloud, Drata, Saviynt, and WWT all frame Wiz as something that can sit inside a broader security ecosystem, which is a clue that partner-led distribution is important. The same ecosystem also hints that the most valuable account expansion probably comes from adding adjacent identity, workflow, and cloud-security modules rather than from a single one-off deployment. Public writeups such as Software Analyst’s are less authoritative than the case studies, but they still support the idea that Wiz scaled quickly inside larger accounts. The main gap is that none of the public materials disclose retention curves, contract duration, or top-account concentration, so expansion is visible while durability is not fully measured.[CU004, CU007, CU008, CU011, CU012]
6.3 What remains opaque
The customer evidence is broad, but it is not complete. The company does not publicly disclose NRR, churn, contract length, or customer concentration. That means the reader can see demand and adoption but not fully measure durability. ScaleVP’s more skeptical framing helps keep that gap visible: even very strong logo and usage claims do not eliminate concentration risk. For a refresh report, the right conclusion is therefore balanced. Wiz has enough customer evidence to support enterprise relevance and partner-driven expansion, but not enough disclosure to eliminate retention and concentration questions. Those questions now matter even more because the company is inside Google Cloud.[CU006, CU009, CU010, CU012]
| expansion path | trigger | buyer | value | proof level |
|---|---|---|---|---|
| Cloud footprint expansion | New workloads or clouds | CISO / cloud security | Broader risk coverage | High |
| Partner-led deployment | Need for rollout help | MSP / alliance team | Faster adoption | Medium |
| Identity adjacency | Non-human identity focus | Security operations | Broader platform value | Medium |
| AI security adjacency | AI launch or agent risk | AI platform lead | New budget surface | Emerging |
| Public sector hardening | Compliance pressure | Security officer | Control and auditability | High |
| Developer workflow pull | GitHub / CI-CD integration | DevSecOps | Broader developer adoption | Medium |
| Mid-market entry | Startup program / credits | Security manager | Easier first purchase | Low |
| Google Cloud customer cross-sell | Vendor consolidation | Cloud security buyer | Platform alignment | High |
The table frames adoption as a set of expansion motions rather than a single funnel.
[CU004, CU007, CU008, CU011]| diligence item | public evidence | why it matters | remaining gap |
|---|---|---|---|
| Retention | None public | Measures stickiness | No NRR data |
| Concentration | Named logos only | Shows exposure to one or two accounts | No top-account mix |
| Contract length | Case-study references | Tells how durable revenue is | No term disclosures |
| Channel mix | Partner ecosystem visible | Helps model CAC and expansion | No take-rate detail |
| Expansion attach | Multiple cloud and AI narratives | Indicates depth in accounts | No attach-rate metric |
| Vertical durability | Enterprise and regulated examples | Shows recurring demand | No cohort retention by vertical |
| Buyer diversity | Security, platform, and cloud teams | Reduces dependence on one persona | No persona mix disclosed |
| Post-close continuity | Google ownership | Changes the renewal environment | Integration impact unknown |
Public proof is strong on logos and usage but weak on retention and concentration.
[CU001, CU002, CU003, CU005, CU006, CU009, CU010, CU012]07Risks
7.1 Operational and reliability risks
Wiz now has a visible status page, and third-party trackers show incident-style monitoring around the product. That is normal for a cloud platform, but it means uptime, login reliability, and service communication remain diligence items. The existence of status pages does not imply poor reliability; it simply makes reliability observable. The bigger takeaway is that operational risk did not vanish with the acquisition. Cloud security systems sit in the path of critical infrastructure, so even short incidents can create trust friction. Buyers will continue to ask about incident response, status transparency, and how quickly support resolves platform issues.[CR001, CR002, CR008, CR011]
| risk | likelihood | severity | mitigation | residual exposure |
|---|---|---|---|---|
| Roadmap uncertainty after Google | Medium | High | Brand retention and continued multi-cloud support | Product priority drift |
| Service outage / auth degradation | Medium | Medium | Status transparency and incident response | Buyer trust friction |
| Security scrutiny / disclosure | Medium | Medium | Bug bounty and disclosure discipline | Public reputation noise |
| Partner dependency | Medium | High | Marketplace and partner ecosystem | Channel concentration |
| Cloud migration complexity | High | High | Automation and graph context | Buyer implementation burden |
| AI-era attack surface | High | High | AI security modules | New attack vectors evolve quickly |
| Support continuity | Medium | Medium | Google operational depth | Service expectations rise |
| Customer concentration opacity | Medium | Medium | Broader adoption footprint | No top-account disclosure |
| Legal / compliance exposure | Medium | Medium | Policy and controls | Security claims invite scrutiny |
| Competitive bundling | High | Medium | Differentiated graph and context | Suite vendors can undercut |
This register combines direct status/incident evidence with broader strategic risks implied by the acquisition and cloud-security category.
[CR001, CR002, CR003, CR004, CR005, CR007, CR008, CR009, CR010, CR012]Operational and roadmap risks sit highest, while acquisition-specific legal risk is mostly reputational rather than existential.
The heatmap is qualitative and intentionally conservative; it summarizes severity rather than scoring exact probabilities.
[CR001, CR002, CR004, CR005, CR007, CR012]7.2 Security, legal, and reputation risk
Reuters coverage of a Wiz-reported security hole is important because it shows the company is both a security vendor and a public security actor. That cuts two ways: it helps credibility when the company finds problems, but it also invites scrutiny when it is itself part of a security narrative. Public security claims therefore need ongoing proof. The legal risk is broader than any one headline. Security companies invite scrutiny over the quality of their detection, disclosure, and response processes. Wiz’s public posture looks competent, but the diligence lens should still treat security reputation as a live risk category rather than a solved issue.[CR003, CR005, CR009]
7.3 Acquisition and dependency risk
The Google acquisition changes the risk profile more than any single incident page. Wiz remains a multi-cloud brand, but it now depends on Google’s internal product priority, roadmap sequencing, and support model. Google says Wiz will continue to support multiple clouds, which is reassuring, but the buyer should still assume some level of roadmap and distribution dependence on Google Cloud. That makes the key thesis-break trigger straightforward: if multi-cloud support, support continuity, or security depth were to weaken materially inside Google, the strategic case would change. Public sources do not show that weakness today, but they do show why it must be monitored closely.[CR004, CR006, CR007, CR010, CR012]
| risk | early warning | mitigation | residual concern |
|---|---|---|---|
| Outage / auth | Status page or tracker movement | Faster incident comms | Trust friction |
| Support continuity | Slower response times | Google operational depth | Buyer expectations rise |
| Migration complexity | Longer deployment cycles | Automation and graph context | Implementation burden |
| AI attack surface | More AI launches | AI security modules | Category evolves quickly |
| Partner dependency | Heavy channel concentration | Broader ecosystem reach | Margin pressure |
| Competitive bundling | Suite discounting | Differentiated graph | Price pressure persists |
| Customer concentration opacity | Lack of disclosure | Broader adoption footprint | Unknown account mix |
| Security scrutiny | New media coverage | Disclosure discipline | Reputation noise |
This table turns the register into an operational checklist.
[CR001, CR002, CR004, CR005, CR007, CR008, CR012]| thesis-break condition | why it matters | public signal today | severity |
|---|---|---|---|
| Multi-cloud support weakens | Would erode product differentiation | Google says support continues | High |
| Support continuity degrades | Would hurt trust and renewals | Status pages remain active | Medium |
| Security credibility slips | Would affect buyer trust | Public scrutiny still exists | Medium |
| Acquisition priority drifts | Would slow roadmap execution | No public evidence yet | High |
| Partner ecosystem thins | Would reduce reach | Partners remain visible | Medium |
| Cloud migration complexity overwhelms users | Would make adoption harder | Implementation burden persists | High |
| AI roadmap stalls | Would limit growth adjacency | AI security is still emerging | Medium |
| Top-account concentration emerges | Would increase revenue fragility | No disclosure either way | Medium |
The matrix helps separate manageable noise from genuine thesis failure.
[CR004, CR006, CR007, CR010, CR012]08Valuation
8.1 Thesis and antithesis
The thesis is simple: Wiz proved product-market fit, scaled quickly, and realized an enormous exit. The antithesis is equally simple: the standalone asset is gone. That means valuation analysis now has to distinguish between the historical security outcome and any live investment opportunity. The company already produced the exit that many venture-backed security companies hope for; the question is whether anything remains to underwrite. Public sources say no, at least for a fresh standalone investment. The only sensible current posture is to treat Wiz as an acquisition outcome and to monitor Google’s integration quality rather than to project a fresh private valuation path.[CV001, CV007, CV011, CV012]
| item | thesis | what changes the view |
|---|---|---|
| Recommendation | Avoid / no standalone entry after acquisition | Only a new carve-out or spinout would reopen an entry case |
| Confidence | Medium | Higher if post-close disclosure remains sparse |
| Risk rating | High | Falls if integration proves clean and public disclosure improves |
| Valuation stance | Unknown / no fresh standalone mark | Would need a new independent asset or spinout |
| Bull case | Massive enterprise value realized pre-close | Requires a distributable security asset again |
| Base case | Google retains Wiz brand and product value | Product continuity and cloud support remain good |
| Bear case | Roadmap integration dilutes the multi-cloud edge | Any reduced multi-cloud focus or support continuity |
| Key diligence ask | Post-close operating economics | Need actual margin, burn, and product-plan disclosure |
| Exit readiness | Already realized | Only relevant if a spinout or secondary market emerges |
| Decision implication | Do not underwrite as a fresh standalone startup | Reframe as a Google Cloud product line |
The table is intentionally decision-oriented because the asset has already been acquired; valuation should be treated as a historical outcome, not a live entry price.
[CV001, CV002, CV003, CV004, CV005, CV007, CV010, CV011, CV012]Wiz moved from venture scale to a realized Google exit, so the right conclusion is no longer a valuation target but an ownership-status check.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Scale proof [scale] | $1B ARR and broad enterprise adoption | |
| Node 2 | Venture premium [funding] | $1B round at $12B backed the trajectory | |
| Node 3 | Google close [exit] | $32B all-cash acquisition realized value | |
| Node 4 | Value realized [liquidity] | Early backers saw paper and realized gains | |
| Node 5 | Standalone entry ends [standalone] | No fresh private-market entry remains | |
| Node 6 | Monitor integration [monitor] | Post-close continuity becomes the diligence focus | |
| Connection 1 | Scale proof [scale] | Venture premium [funding] | |
| Connection 2 | Venture premium [funding] | Google close [exit] | |
| Connection 3 | Google close [exit] | Value realized [liquidity] | |
| Connection 4 | Value realized [liquidity] | Standalone entry ends [standalone] | |
| Connection 5 | Standalone entry ends [standalone] | Monitor integration [monitor] |
8.2 Scenario framing
The bull case is already realized: the market paid a very large price for a company with real revenue scale and a strong category position. The base case is that Google preserves the Wiz brand and product value inside Google Cloud. The bear case is that integration blurs the multi-cloud edge or slows roadmap momentum. Those are the only meaningful scenarios left now that the acquisition has closed. That is why the report recommendation is not a classic buy-versus-sell call. It is an ownership-status call. If Wiz were still independent, the ARR and funding path would support a premium valuation discussion. After the close, the right question is simply whether the product value survives intact inside Google.[CV002, CV003, CV004, CV005, CV008, CV009]
8.3 Final stance
The final stance is therefore conservative. Wiz is a success story, but not a fresh entry opportunity. Secondary market pages and investor-profile pages show that outside interest existed, yet those pages do not change the fact that the company is no longer a standalone private startup. Public disclosure also remains thin on post-close operating economics, so there is no new underwriting case to make. For a diligence team, the most useful output is a post-close monitoring brief: keep an eye on product continuity, Google Cloud integration, and any evidence that Wiz’s multi-cloud posture weakens. The old valuation debate has ended; the new diligence question is integration quality.[CV006, CV010, CV011, CV012]
| scenario | what has to stay true | what breaks the case | watch item |
|---|---|---|---|
| Bull | Google preserves product depth and multi-cloud support | Roadmap narrows or brand disappears | Continuity of product surface |
| Base | Wiz remains a strong Google Cloud security line | Integration blurs the differentiation | Multi-cloud support and packaging |
| Bear | Acquisition value remains the end state | Product usefulness erodes | Support continuity and trust |
| Secondary | Some private-market demand persists | No operating disclosure exists | Operating economics |
| Spinout | A new independent asset appears | Google keeps it embedded | Legal / structural change |
| Exit premium | Legacy venture gains remain exceptional | New valuation is unsupported | Historical return framing |
| Monitoring only | Public signals remain sparse | Fresh disclosure appears | New economics data |
| Caution | Security reputation stays intact | Adverse headlines intensify | Trust and scrutiny |
Scenario framing is more useful than a single-point valuation after a completed acquisition.
[CV001, CV002, CV003, CV007, CV010, CV012]| diligence item | why it matters | current public signal | open question |
|---|---|---|---|
| Product continuity | Preserves buyer trust | Google says support continues | Will the surface stay distinct? |
| Multi-cloud posture | Core differentiation | Still publicly supported | How long does it remain first-class? |
| Pricing / packaging | Affects monetization | No public detail | How is it sold inside Google? |
| Operating economics | Needed for underwriting | Sparse disclosure | Margin and burn remain opaque |
| Reputation management | Affects enterprise adoption | Security headlines persist | Can public scrutiny be contained? |
| Channel continuity | Supports reach | Partner proof still visible | Do partner economics change? |
| AI roadmap | Growth adjacency | AI security is present | How quickly does it ship? |
| Ownership status | Determines investability | Already acquired | Only a spinout would reopen entry |
The checklist reflects what a diligence team should monitor after close.
[CV004, CV005, CV006, CV008, CV009, CV010, CV011]Disclaimer
This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | Wiz is now part of Google Cloud, but the Wiz brand continues to be used publicly. | High | SO002, SO003 |
| CO002 | Wiz launched in January 2020 with four cofounders who had already worked together at Adallom and Microsoft. | High | SO001, SO004 |
| CO003 | The public product description centers on a single context layer that connects code, cloud, and runtime. | High | SO002, SO003 |
| CO004 | The company publicly says it protects 5 million cloud workloads and scans 230 billion files per day. | Medium | SO002 |
| CO005 | Wiz says 65% of the Fortune 100 are customers. | Medium | SO002 |
| CO006 | Google says Wiz will keep supporting multiple clouds after the acquisition closes. | Medium | SO003 |
| CO007 | Public profiles place Wiz in New York and describe the company as roughly a 1,001-5,000 employee business. | Medium | SO006 |
| CO008 | Insight Partners says the Series A was $100M and that the original investor group included Index, Sequoia, Insight, and Cyberstarts. | High | SO001, SO004 |
| CO009 | Clinkbill’s public revenue timeline places Wiz above $1B ARR before the March 2026 exit. | Medium | SO008 |
| CO010 | Wiz’s public materials emphasize agentless scanning and rapid time-to-value rather than heavy deployment friction. | Medium | SO001, SO002 |
| CO011 | Reuters coverage shows Wiz still surfaces security issues and participates in external security discourse. | Medium | SO005 |
| CO012 | The public record is much stronger on product scale and acquisition than on post-close standalone financial detail. | Medium | SO002, SO003, SO008 |
| CM001 | The market boundary is best described as CNAPP plus cloud and AI security, not a single narrow scanner category. | High | SM001, SM003, SM007 |
| CM002 | Wiz’s own framing stresses a normalizing layer that reduces cloud visibility and policy fragmentation. | High | SM007, SM001 |
| CM003 | AWS publicized Wiz around cloud resilience for academic medical centers, which shows the buyer set is large-enterprise and regulated-workload oriented. | Medium | SM002 |
| CM004 | Omdia describes Wiz as a proactive and reactive CNAPP platform, signaling that analysts see it as a broader lifecycle tool. | Medium | SM003 |
| CM005 | The public market story includes agentless deployment, which lowers adoption friction but still requires cloud-context access and trust. | Medium | SM001, SM004, SM005 |
| CM006 | SecurityScientist’s Q&A format shows buyers still ask for basic implementation and value clarification, which implies market education is ongoing. | Medium | SM005 |
| CM007 | Reuters coverage of a Wiz-reported security hole shows the company is still part of active threat-research and incident discourse. | Medium | SM006 |
| CM008 | Google says Wiz will continue to support multiple clouds after the acquisition, which keeps the multi-cloud market boundary intact. | Medium | SM008 |
| CM009 | The relevant buyer map spans security operations, cloud engineering, application security, and AI-security teams. | Medium | SM001, SM003, SM004, SM007, SM008 |
| CM010 | Cloud and AI growth expand attack surface faster than traditional point products can comfortably cover. | Medium | SM001, SM008 |
| CM011 | The market’s main adoption constraint is not product awareness alone but procurement, cloud access, and trust calibration. | Medium | SM004, SM005, SM007 |
| CM012 | The strongest public evidence points to market consolidation around integrated platform security rather than isolated posture checks. | Medium | SM003, SM008 |
| CP001 | The clearest competitive shift is that Wiz is now inside Google Cloud, so hyperscaler bundling is part of the story. | Medium | SP001 |
| CP002 | Public commentary around Wiz still compares it to incumbent suite vendors such as Palo Alto Networks and CrowdStrike, which implies the market is crowded and budget-driven. | Medium | SP002 |
| CP003 | Google says it will keep supporting other security providers in Marketplace, which means Wiz coexists with competing ecosystems rather than fully displacing them. | Medium | SP001 |
| CP004 | Independent profile pages show that valuation and growth narrative are now central to how the market discusses Wiz. | Medium | SP003, SP004, SP005 |
| CP005 | The company’s core moat is still the product graph and cross-cloud context, not a proprietary cloud lock-in. | Medium | SP001, SP006 |
| CP006 | Google’s acquisition increased the strategic stakes for hyperscaler-native security, because bundling and integration now matter more. | Medium | SP001, SP007 |
| CP007 | Open-weight and self-host options remain a practical substitute class for some buyers even when Wiz is the strongest all-in-one option. | Low | SP007, SP006 |
| CP008 | Reuters coverage of a Wiz-reported security hole shows the brand still participates in public security discourse, which can cut both ways in competition. | Medium | SP008 |
| CP009 | Public sources do not show a clean one-to-one replacement for Wiz; the real competitive set is a mix of hyperscalers, suite vendors, and niche CNAPP firms. | Medium | SP001, SP002, SP007 |
| CP010 | Because Google retained the Wiz brand, the market is likely to treat Wiz as a product line inside a broader platform rather than a standalone startup. | Medium | SP001, SP006 |
| CP011 | The market narrative around a $32B exit and rapid ARR growth makes Wiz itself a reference competitor benchmark for future CNAPP entrants. | Medium | SP003, SP005 |
| CP012 | A standalone valuation is less relevant now than product integration depth and Google Cloud distribution leverage. | Medium | SP001, SP007 |
| CI001 | Wiz sold enterprise cloud security by pricing per protected cloud workload rather than by seat. | Medium | SI002, SI003 |
| CI002 | Wiz reached $100M ARR in about 18 months, which supports a land-and-expand enterprise motion. | Medium | SI002, SI006 |
| CI003 | Third-party trackers place Wiz above $1B ARR before the Google acquisition closed. | Medium | SI002, SI004 |
| CI004 | Wiz raised a $1B funding round at a $12B valuation before the acquisition. | Medium | SI001 |
| CI005 | Google’s March 2026 acquisition closed at $32B all-cash, ending the standalone financing story. | Medium | SI008 |
| CI006 | PerkBook’s startup program page implies Wiz still used discounting or startup-style entry programs to seed adoption. | Low | SI005 |
| CI007 | Public sources still do not disclose margins, CAC payback, or cash-burn detail in a way that would support full underwriting. | Medium | SI003, SI007, SI008 |
| CI008 | The business model is best described as subscription SaaS with usage-linked enterprise pricing rather than pure headcount pricing. | Medium | SI002, SI003 |
| CI009 | The acquisition price and ARR trajectory together imply a very rich revenue multiple at exit. | Medium | SI002, SI008 |
| CI010 | Insight’s founder story supports the idea that capital efficiency was aided by a preexisting team and customer network. | Medium | SI006 |
| CI011 | The public financing story remains exceptionally strong even though the post-close operating economics are opaque. | Medium | SI001, SI004, SI008 |
| CI012 | Public revenue estimates diverge, which means the safest underwriting input is the latest publicly documented milestone, not a single exact number. | Medium | SI002, SI003, SI004 |
| CE001 | Wiz describes the platform as connecting code, cloud, and runtime into a single context layer. | High | SE001, SE002 |
| CE002 | The public architecture story emphasizes rapid visibility into architecture, permissions, data flows, and runtime behavior. | Medium | SE002 |
| CE003 | Wiz says the platform can work without agents or sidecars, which lowers deployment friction. | High | SE001, SE005 |
| CE004 | The GitHub org and developer-facing content indicate that Wiz also wants credibility with builders, not just security buyers. | Medium | SE003, SE005 |
| CE005 | PuppyGraph’s reconstruction work suggests the market understands Wiz as a graph and context engine, not just a dashboard. | Medium | SE004 |
| CE006 | The Register’s coverage of an AI-aided GitHub bug report shows Wiz is active in modern AI-security workflows. | Medium | SE006 |
| CE007 | Aikido’s alternatives page confirms that buyers compare Wiz against adjacent code-security tools as well as cloud-security platforms. | Medium | SE007 |
| CE008 | Reuters reporting on a Wiz-found security hole shows the company is part of active vulnerability discovery and disclosure discourse. | Medium | SE008 |
| CE009 | Google says Wiz expands threat prevention, detection, and response while keeping multi-cloud support. | Medium | SE002 |
| CE010 | CI/CD guidance on the Wiz site shows the product extends upstream into application security workflows. | Medium | SE005 |
| CE011 | The technical story is strongest where cloud context, runtime data, and application workflows meet. | Medium | SE001, SE002, SE004, SE005 |
| CE012 | Public sources still leave some questions about roadmap prioritization after the Google acquisition. | Medium | SE002, SE007, SE008 |
| CU001 | Wiz publicly claims 65% of the Fortune 100 as customers. | Medium | SU001 |
| CU002 | Wiz says it protects 5 million cloud workloads and scans 230 billion files daily. | Medium | SU001 |
| CU003 | The research-university case study shows Wiz deployed in a real production environment, not just a pilot. | Medium | SU002 |
| CU004 | WWT, Drata, and Saviynt all frame Wiz as a partner ecosystem product, which supports channel-led adoption. | Medium | SU003, SU004, SU005 |
| CU005 | The Google Cloud case study reinforces that Wiz has been used by enterprise cloud customers. | Medium | SU006 |
| CU006 | Public customer evidence is strong on logos and use cases, but weaker on renewal, concentration, and contract length. | Medium | SU001, SU002, SU006 |
| CU007 | The partner pages suggest land-and-expand motion through adjacent identity and workflow products. | Medium | SU004, SU005 |
| CU008 | Software Analyst’s write-up argues Wiz became a very fast-growth enterprise software company, which is consistent with large-account adoption. | Low | SU007 |
| CU009 | Reuters coverage keeps security scrutiny visible even after obvious adoption success. | Low | SU008 |
| CU010 | The public record does not disclose top-customer concentration or NRR, so retention quality remains partly opaque. | Medium | SU001, SU006 |
| CU011 | Wiz’s customer story is strongest where the buyer is a cloud security team with partner support around it. | Medium | SU003, SU004, SU005, SU006 |
| CU012 | The company’s customer proof is broad enough to support scale but not detailed enough to eliminate concentration concerns. | Medium | SU001, SU002, SU006 |
| CR001 | Wiz operates a public status page, which signals operational transparency and makes outages observable to buyers. | Medium | SR001 |
| CR002 | Third-party trackers show service incidents and authentication monitoring, indicating that uptime and login reliability are real diligence items. | Medium | SR002, SR003, SR004 |
| CR003 | Reuters coverage of a Wiz-reported security hole shows the company is still exposed to public security scrutiny. | Medium | SR005 |
| CR004 | Google says Wiz will continue to support multiple clouds, but ownership inside Google still creates roadmap and priority uncertainty. | Medium | SR008 |
| CR005 | Cloud migration security remains a complex problem, so operational and integration risk does not disappear after acquisition. | High | SR007, SR008 |
| CR006 | A continued hiring signal suggests execution is ongoing, but it does not prove a clean post-acquisition operating structure. | Low | SR006 |
| CR007 | Partner and marketplace dependency remain a risk because Wiz still needs cloud ecosystem cooperation to reach customers. | Medium | SR008, SR007 |
| CR008 | Incident and status pages imply that buyers will keep asking about SLA, incident response, and support maturity. | Medium | SR001, SR003, SR004 |
| CR009 | The most important legal risk in the public record is not a single lawsuit, but the broader exposure that comes with security claims. | Medium | SR005, SR001 |
| CR010 | The acquisition reduces standalone business risk but increases dependence on Google Cloud strategy. | Medium | SR008 |
| CR011 | Public outage trackers are noisy, so the right diligence move is to treat them as directional indicators rather than hard incident logs. | Medium | SR002, SR003, SR004 |
| CR012 | The strongest residual risk is roadmap and support continuity after the acquisition, not product-category demand. | Medium | SR001, SR008 |
| CV001 | The best public anchor for the company’s value is Google’s $32B all-cash acquisition close in March 2026. | High | SV001, SV008 |
| CV002 | Wiz’s funding arc moved from an early $6M bet to a $1B round at $12B before the exit. | High | SV001, SV002, SV003 |
| CV003 | Public trackers put Wiz above $1B ARR before the Google acquisition, which is why the exit multiple mattered so much. | Medium | SV008, SV003 |
| CV004 | TechCrunch’s 200x-return framing shows that early backers already treated Wiz as a generational security outcome. | Medium | SV002 |
| CV005 | Insight’s portfolio page confirms the company was already considered a core portfolio asset by a top-tier investor. | Medium | SV007 |
| CV006 | Secondary-market pages for Wiz indicate that private-market demand existed, but they are not substitutes for operating valuation disclosure. | Low | SV005 |
| CV007 | The strongest bear case is not product quality but the fact that the standalone asset no longer exists after the acquisition. | High | SV001, SV008 |
| CV008 | The valuation story is exceptional even by late-stage standards, but the entry opportunity for a new investor is now gone. | Medium | SV001, SV002, SV004 |
| CV009 | Calcalistech’s framing makes clear that the acquisition created major paper gains for early investors. | Medium | SV004 |
| CV010 | Wiz’s public disclosure still does not answer what current run-rate economics look like after Google absorbed the business. | Medium | SV001, SV008 |
| CV011 | The right valuation stance after the close is not a pricing debate but a decision about whether the asset is still investable as a standalone company. | High | SV001, SV002, SV007 |
| CV012 | Given the acquisition, the recommendation shifts from valuation upside to post-close monitoring of integration quality and product continuity. | High | SV001, SV008 |