Oasis Security

1.1 Identity, product scope, and founding context

Oasis Security is best understood as a post-stealth infrastructure-security company selling governance for non-human identities rather than a narrow secrets utility. Across its homepage, about page, product page, and founding blog, the company describes a platform that discovers machine identities, maps ownership and usage context, and orchestrates lifecycle controls such as monitoring, certification, remediation, and decommissioning. The product language is deliberately broad: Oasis says it spans IaaS, SaaS, PaaS, and on-prem environments and names endpoints as diverse as AWS, Azure, BigQuery, GitHub, ChatGPT, Salesforce, Office 365, and Copilot. That breadth matters because it implies the company wants to sit above fragmented vaults and point tools as an identity-governance layer. The official origin story also gives Oasis a distinct narrative: Danny Brickman says the company began in a modest room in Tel Aviv with teammates from Israeli cyber operations, while independent reporting identifies Brickman and Amit Zimerman as the founding pair. The result is a company with visibly Israeli technical roots but a commercial narrative now anchored in U.S. enterprise identity security.[CO001, CO002, CO003, CO004, CO005, CO006]

1.2 Funding history, investor map, and governance signals

Oasis has moved unusually fast through private financing milestones. It emerged publicly in January 2024 with a previously closed $35 million Series A and $40 million total funding, then returned in May 2024 with a $35 million extension that management and press sources said doubled the prior valuation and lifted cumulative funding to $75 million. The most important financing event is the March 2026 Series B: Oasis announced $120 million led by Craft Ventures with existing backers Cyberstarts, Sequoia Capital, and Accel, bringing total funding to $195 million. Independent reporting from Globes and Tech Company News places the post-money valuation around $700 million, which is materially below the $1.2 billion figure in the user-supplied background and therefore the better-supported current value anchor. Governance disclosure remains thinner than funding disclosure. Public sources clearly identify the founders and the April 2026 addition of Michael DeCesare as president, but they do not surface a full board roster, committee structure, or cap-table detail. That makes investor pedigree a strength, but governance transparency an unresolved diligence item.[CO001, CO002, CO007, CO008, CO009, CO010]

1.3 Traction signals, partner validation, and category timing

Traction evidence is real but still selective. The strongest company claim is that a majority of Oasis's client base comes from the Fortune 500 and that new ARR grew fivefold year over year heading into the Series B. That is directionally impressive, especially when paired with management's claim that most new ARR is driven by multi-year enterprise agreements. Independent public customer proof is shallower: TechCrunch named Chipotle, JLL, and Mercury Financial as early users, while Gartner Peer Insights showed a 5.0 rating from a single banking review in early 2026. Partner surfaces strengthen the adoption story. CrowdStrike's marketplace listing and Wiz's integration page both describe Oasis as an active ecosystem participant rather than a conceptual integration. Just as important, third-party category signals show that the market window is real. NIST launched an AI Agent Standards Initiative in 2026, Palo Alto Networks said machine identities hit 109-to-1 versus humans, and CyberArk framed the machine-identity problem as a breach and outage vector. Oasis is therefore not selling into a synthetic category; it is selling into a problem that large security vendors and standards bodies also describe as urgent.[CO013, CO014, CO015, CO016, CO020, CO021]

1.4 Milestones, disclosure gaps, and adverse context

The milestone record from public sources is coherent enough to support an overview chapter, but it still leaves obvious gaps. The company moved from a stealth exit in January 2024 to a Series A extension in May 2024, formal channel-program launch in April 2025, Series B in March 2026, and executive expansion in April 2026. Those are the milestones of a company trying to turn an early product wedge into a scaled enterprise platform. The missing pieces are just as important. No reviewed source published a precise customer count, exact ARR dollars, board roster, or audited financials. Even the most discussed valuation figure is only a market estimate, not a disclosed board-sanctioned number. The clearest adverse-context item is a July 2026 Globes report that Cyera was in advanced talks to acquire Oasis for up to $1 billion, but without a formal announcement. That does not disprove the $700 million financing benchmark; it does indicate that strategic- option narratives around Oasis were already shifting by the run date. Investors should therefore treat the company as well-funded and clearly relevant, but still materially under-disclosed on the metrics that would let later chapters underwrite a price-sensitive view.[CO011, CO012, CO017, CO018, CO020, CO021]

1.5 Exhibits

2.1 Market boundary, included spend, and status-quo substitutes

The fastest way to misunderstand Oasis's market is to treat it as a rebranded secrets manager. Public sources instead define a broader problem set: NHIs now include application and service identities, API and OAuth tokens, machine and device identities, cryptographic identities, bots, workloads, and increasingly AI agents. That means the relevant spend boundary includes discovery, posture, ownership assignment, lifecycle governance, and runtime authorization for automated actors. It also means the status quo is fragmented. Some buyers try to solve parts of the problem with vaults or identity stores such as HashiCorp Vault; others lean on cloud-native IAM, SPIFFE-style workload identity, or manual CMDB ownership processes. Those substitutes can address credential issuance or low-level workload identity, but they do not by themselves create enterprise- wide governance over every machine identity and delegated AI action. The NHI market is therefore best viewed as a convergence layer sitting between traditional IAM/PAM, secrets management, platform engineering, and AI- governance workflows.[CM001, CM002, CM003, CM021, CM023, CM027]

2.2 Sizing lenses, identity segmentation, and regional shape

Public market sizing for NHI governance is directionally strong but not numerically clean. Mordor Intelligence sizes the narrower NHI security segment at $8.22 billion in 2026 and $22.94 billion by 2031, while Research and Markets and its Yahoo Finance distribution partner place the broader NHI access-management category at $12.2 billion in 2026 and $38.8 billion by 2036. The spread is not noise; it reflects different boundaries. The broader estimate includes solution and services layers across identity types, deployment modes, organization sizes, and verticals, while the narrower estimate is closer to the security-control subset. Regional shape is clearer than precise SAM: North America currently leads, Asia-Pacific is forecast to grow fastest, and large enterprises dominate present demand. Identity-type segmentation is also explicit in the broader forecast: application and service identities, API and OAuth token identities, machine and device identities, cryptographic identities, and AI-agent identities are already first-class subsegments. The correct takeaway is that the market is real, large, and expanding quickly, but a clean Oasis-specific SOM is not public.[CM004, CM005, CM006, CM007, CM008, CM009]

2.3 Buyers, vertical use cases, and how adoption actually starts

Buyer structure matters because this category rarely belongs to one team. The product narratives of Oasis, Saviynt, Delinea, GitGuardian, Aembit, and HashiCorp all imply a shared-control model: IAM/PAM leaders care about identity governance, cloud and platform teams care about workload access patterns, and regulated business owners care about auditability and resilience. Oasis's own solution pages make the point concrete. The AI page emphasizes restricting AI agents to approved model suppliers and enforcing least privilege; the finance page ties the pain to PCI DSS 4.0, SOC 2, and digital-operations continuity; the healthcare page ties it to patient privacy, HIPAA/GDPR-style obligations, and uninterrupted care. Across the market, adoption typically begins with discovery and inventory, then moves into owner attribution and risk labeling, then lifecycle policy, and only later into runtime authorization or secretless enforcement. That sequence is a useful reminder that many buyers will first land on visibility and posture before they trust a vendor with inline access control.[CM015, CM021, CM022, CM025, CM026, CM029]

2.4 Growth drivers, adoption constraints, and the standards gap

The strongest growth driver is simple arithmetic: machine identities and AI agents are proliferating faster than human IAM systems were built to handle. Palo Alto says the machine-to-human ratio reached 109-to-1 in 2026 and continues to rise, while Axis Intelligence highlights both secrets sprawl and long-lived credential exposure. On top of that, NIST has now launched an AI Agent Standards Initiative, and vendors across the market are translating that into product narratives around open protocols, least privilege, and governance. But the same sources also reveal why market conversion will not be frictionless. OWASP-style maturity work shows a large adoption-to-protection gap; Cloud Security Alliance says enforceable controls do not yet exist; ITECS argues shadow AI is already outpacing visibility; and Delinea warns that AI agents often carry persistent, broadly privileged access. In practice, buyers are pulled forward by urgency and compliance, but held back by fragmented tooling, unclear ownership, and the operational burden of replacing entrenched vault or cloud-IAM patterns. That combination supports a fast-growing market with real friction rather than a straight-line land grab.[CM011, CM012, CM013, CM014, CM016, CM017]

2.5 Exhibits

3.1 Landscape: direct peers, suite incumbents, adjacents, and substitutes

The competitive map around Oasis is crowded, but not flat. One cluster is the direct NHI and agentic-identity pure plays: Oasis itself, Entro, Aembit, and until its June 2026 Cisco absorption, Astrix. A second cluster is the suite incumbents: CyberArk, Saviynt, and Delinea, all of which approach the problem from broader identity- security or machine-identity platforms. A third cluster is runtime and infrastructure control: HashiCorp Vault, SPIFFE/SPIRE, and newer developer-first identity entrants such as WorkOS. These are not always direct displacement threats, but they are legitimate substitutes for specific buyer use cases. The key implication is that Oasis is rarely fighting a single category. In some deals it will be compared with lifecycle-governance peers; in others it will be asked why a buyer cannot extend an incumbent vault, PAM, or workload identity framework instead. That multi-category competition increases both buyer education burden and the importance of clear category ownership.[CP001, CP010, CP018, CP020, CP027, CP028]

3.2 Profiles: who owns lifecycle breadth versus runtime depth

The strongest profile contrast is between lifecycle-breadth vendors and runtime-depth vendors. Oasis, Entro, and Saviynt all emphasize discovery, contextual ownership, posture, and remediation. CyberArk competes with scale and lifecycle breadth for machine identities, but from a broader enterprise identity base and with certificate and secrets heritage. Delinea also pushes continuous discovery and privileged-access hygiene. By contrast, Aembit and HashiCorp are more explicit about short-lived or dynamic access patterns: Aembit sells secretless, policy-based runtime access for agentic AI and workloads, while HashiCorp validates OAuth-based AI-agent authentication and dynamic secrets. SPIFFE is even more infrastructure-native, offering a cryptographic workload identity control plane without the business-governance wrapper. These differences matter because buyers do not all value the same layer. A security leader worried about overprivileged orphaned identities may favor lifecycle governance; a platform team focused on eliminating static secrets may prefer runtime plumbing first.[CP002, CP003, CP004, CP005, CP007, CP009]

3.3 Distribution power, proof points, and switching dynamics

Distribution power is emerging as a decisive differentiator. Oasis has visible partner surfaces with CrowdStrike and Wiz, and both integrations tell a helpful story: the platform is not only finding identities, but also pulling in endpoint or cloud context and tying that to governed remediation. That is a more mature commercial signal than a standalone homepage claim. At the same time, Oasis's public proof remains thinner than its partner story. Gartner shows only one visible review, while SourceForge and Slashdot provide product- directory summaries rather than enterprise-grade reference depth. That asymmetry matters in head-to-head sales cycles. Switching costs also appear additive rather than fully replacement-oriented. Buyers can keep Vault, SPIFFE, cloud IAM, or other workload primitives and still add a governance layer on top. This makes the market structurally multi-home, which lowers outright rip-and-replace friction but raises the bar for proving why Oasis should become the unifying control plane rather than just another dashboard.[CP017, CP021, CP022, CP023, CP024, CP025]

3.4 Moat durability, consolidation, and commoditization risk

Oasis's moat is credible but not yet unassailable. The best version of the case is that it unifies inventory, contextual ownership, lifecycle action, and an agentic-access narrative in one market-facing platform. The weaker version is that many of those pieces are being added across the ecosystem: Saviynt and Delinea are deepening discovery and posture; CyberArk already owns a large machine-identity budget anchor; HashiCorp and Aembit attack static credentials through runtime patterns; and Astrix's absorption into Cisco shows that larger platforms want this capability set. The category may therefore commoditize from both ends — discovery and posture from suites, runtime access from infrastructure vendors. Public pricing opacity makes it harder to see who is cheapest, but that probably increases, rather than decreases, the role of distribution, deployment model, and reference depth in buying decisions. The result is a market where Oasis can still win, but only if it keeps moving from point capabilities to a visibly integrated control plane.[CP006, CP008, CP013, CP019, CP031, CP033]

3.5 Exhibits

4.1 Revenue Model, Procurement, and Contract Stack

The best public evidence says Oasis sells recurring enterprise software, not project-based consulting. Its July 2025 SaaS subscription agreement is tied to an order and then layered with a public DPA and SLA, while AWS Marketplace routes buyers to custom private offers instead of fixed catalog pricing. That combination is the classic posture of an enterprise SaaS vendor that negotiates terms per customer and expects ongoing service delivery. The contract stack also shows that Oasis is already operating in procurement environments where privacy, uptime, and support commitments matter, which tends to correlate with annual or multi-year subscription selling rather than discretionary tooling purchases. The product surface behind that revenue model is broad enough to support expansion. Oasis does not only inventory non-human identities; it packages provisioning, ownership assignment, attestation, rotation, posture management, and decommissioning as lifecycle capabilities. The provisioning launch is especially relevant financially because it extends the product into workflow triggers such as Terraform, ServiceNow, and generic APIs, and into cloud and vault ecosystems including AWS, Azure, GCP, HashiCorp, CyberArk, and Azure Key Vault. That makes revenue quality more likely to come from platform embedment than from isolated point-feature adoption. Pricing transparency, however, remains weak. AWS Marketplace confirms buyers can request a private offer, but there is no public list price, seat metric, or asset-based tiering schedule that would let an outsider infer ACV. The result is that Oasis can be described as a custom-priced, enterprise-subscription software business with partner- assisted procurement, but not yet as a business whose realized price architecture is publicly visible.[CI001, CI002, CI003, CI004, CI007, CI008]

4.2 Delivery Model, Cost Structure, and Unit-Economics Signals

Oasis has not published unit economics, but its public architecture points to where the cost base likely sits. The Outpost pattern keeps sensitive identity operations inside the customer perimeter while the central platform handles control logic, metadata, lifecycle automation, and analysis. That setup suggests a software- heavy model whose marginal delivery burden should be dominated by engineering, cloud analytics, customer support, and partner enablement rather than by hardware, inventory, or large working-capital swings. The secret-rotation and governance pages reinforce that reading because they frame risk remediation as an automated recurring control, not as a manually staffed professional service. The strongest public production proof in this chapter is the financial-services case study. Oasis describes fast Azure AD deployment, auto- discovery, risk posture analysis, stale-account cleanup, and automated identity rotation for a private-credit customer. Even though the case study is company-authored and does not disclose contract value, it is still useful because it shows the platform can enter regulated customer workflows where compliance and credential hygiene are economically important. The finance-solution page further links the buyer case to PCI DSS 4.0, SOC 2, and GDPR-sensitive environments, which implies that the company is targeting use cases where budget owners often care about risk reduction, auditability, and operational resilience rather than only developer convenience. Still, the public record stops short of underwriting metrics. There is no disclosed ACV, gross margin, CAC, NRR, or services mix. The only defensible conclusion is qualitative: Oasis appears structurally capable of software-like margins, but no outsider can yet measure how much support, services, or channel discounting compresses those margins in practice.[CI005, CI006, CI012, CI014, CI015, CI018]

4.3 Capital Adequacy, Funding Context, and Missing Runway Inputs

Oasis clearly has capital to keep investing, but public sources do not reveal enough to convert that fact into a runway model. The March 2026 Series B brought in $120 million, and contemporaneous reporting from Newswire, Globes, and SiliconANGLE framed the round around the security problem created by enterprise AI agents and non- human identities. Globes additionally reported total capital raised of $195 million, a roughly $700 million valuation according to market sources, a fivefold ARR increase, and a customer base composed mostly of Fortune 500 companies. Even if those traction figures are company-supplied rather than audited, they are directionally important: Oasis is not financing itself from a position of obscurity. What remains hidden is the balance- sheet side of the story. Public materials reviewed here do not disclose cash on hand after the Series B, monthly burn, gross margin, or net revenue retention, and no debt facility or credit line surfaced in the chapter evidence. GuidePoint’s OASIS+ positioning shows federal go-to-market intent, and the channel program plus marketplace listings show an expanding partner motion, but none of that translates into a quantified revenue split between direct, federal, or partner-led business. The right conclusion is therefore asymmetric. Oasis looks well funded for near-term product and go-to-market expansion, especially relative to the early age of the company, but the evidence is still too incomplete to estimate remaining runway or the next-round trigger with confidence. A diligence team would need monthly financial statements, ARR history, and concentration data before taking a hard view on capital adequacy.[CI016, CI017, CI021, CI022, CI023, CI024]

4.4 Peer Benchmarks for Revenue Quality and Capital Intensity

Because Oasis is private, public identity and security vendors provide the only clean recurring-revenue benchmarks. Okta, SailPoint, Rubrik, and CyberArk all reported billion-dollar subscription or ARR scale in 2026-period disclosures, and both Okta and SailPoint also have current SEC filing trails that confirm the market treats identity security as a recurring software category. These companies are not direct product matches for Oasis, but they do establish the economic language that investors and acquirers use for identity businesses: subscription revenue, ARR, SaaS ARR, RPO, and large-customer recurring cohorts. Those peers also show why Oasis’s missing disclosures matter. If management can substantiate strong ARR growth, healthy retention, and software-like gross margin, then the company can plausibly be framed against a premium identity-security revenue model rather than against services or infrastructure resellers. If not, the same lack of transparency can become a discount factor. In that sense, the comparable set is helpful not because it yields a precise multiple for Oasis today, but because it defines the proof burden Oasis would need to satisfy in a financing or acquisition process. Analyst valuation research sharpens the point. Windsor Drake’s Q2 2026 IAM report places mainstream public IAM near 6.0x NTM revenue while non-human and AI-agent identity platforms can clear a 15x-30x range. Finro’s warning that mature public cyber comps can mislead on AI-native private companies is directionally fair, but it also cuts both ways: without hard ARR and margin evidence from Oasis, the premium part of that range is aspirational rather than underwritten.[CI028, CI029, CI030, CI031, CI032, CI033]

4.5 Financial Verdict and Diligence Blockers

The financially attractive interpretation of Oasis is straightforward. It appears to be a contract-backed, custom-priced enterprise SaaS company selling into a painful and expanding identity problem, with enough product depth to support expansion and enough fresh capital to keep pressing the market. The public peer set shows that identity-security winners can become very large recurring-revenue businesses, and Oasis’s partner footprint suggests it is trying to scale through both direct enterprise relationships and distribution channels. The problem is that the public evidence stops at narrative quality and fundraising quality. There is no auditable public view of ARR, revenue mix, gross margin, burn, NRR, CAC, or concentration. Even pricing is opaque beyond the fact that it is quote-based. As a result, Oasis’s financial chapter should be read as structurally favorable but not yet underwritable from public information alone. For diligence, that means the gating items are specific and unavoidable: a quarterly ARR bridge, segment and channel mix, gross margin by component, burn and runway materials, and concentration data for top customers and partners. If management can produce those quickly and the numbers are consistent with the growth narrative, the financial posture strengthens materially. If not, the absence of disclosure itself becomes a risk factor because valuation expectations are already being influenced by premium-category narratives around non-human identity and agentic access.[CI026, CI033, CI034, CI035, CI036, CI038]

4.6 Exhibits

5.1 Product Definition and Module Map

Oasis no longer presents itself as only a non-human identity inventory vendor. The public product story now has two connected layers. First is the legacy NHI management platform covering governance, posture, and secret rotation across service accounts, applications, roles, keys, and other machine identities. Second is Agentic Access Management, which extends those controls to AI agents that reason and act across enterprise systems. The core product promise is not merely “discover the identities” but “convert every machine or agent action into a governed identity workflow” through provisioning, ownership, approval, policy enforcement, rotation, and decommissioning. That module map is unusually coherent for a young category. Oasis’s governance page concentrates on secure provisioning, ownership assignment, privilege control, rotation, attestation, and decommissioning. The posture-management page adds analytics for compromise attempts, toxic combinations, policy violations, and anomalies. The secret-rotation page then translates those insights into operational action by structuring discovery, observation, policy management, safe rotation, and lifecycle cleanup. For AI agents, AAM adds intent analysis, short-lived session identities, and chain-of-custody logs tying prompts to actions. Taken together, Oasis is building a control plane for who or what can act, why they can act, how long that access lasts, and how the action is audited after the fact.[CE001, CE002, CE003, CE004, CE005, CE015]

5.2 Architecture and Deployment Model

The public architecture pattern is that of a governance control plane layered across heterogeneous identity environments. Oasis documents provisioning workflows that can start in Terraform, ServiceNow, a generic API trigger, or the Oasis UI. It also supports both credential-based and federated identities, which matters because it allows buyers to choose between directly managed secrets and trust-based access patterns such as managed identities, IAM roles, and OIDC. This is not the footprint of a narrow secrets vault; it is a product trying to sit above multiple identity primitives and orchestrate lifecycle controls around them. Oasis Outpost is the most important architectural clue. Outpost is described as a collector container that lives inside the customer’s cloud perimeter so that privileged identity operations, secret generation, and secret storage stay local. Oasis itself exchanges control messages and metadata rather than becoming a backdoor into the customer environment. That design supports enterprise acceptance because it reduces the trust leap customers must take when automating sensitive machine credentials. It also suggests Oasis is optimizing for governance and orchestration rather than for owning every enforcement point directly. The case study in financial services adds practical deployment evidence. Oasis describes rapid Azure AD integration, auto-discovery, posture analysis, stale-account cleanup, and automated identity rotation. Even though the case study is company- authored, it demonstrates that the product is meant to be installed into live enterprise identity estates rather than offered as a conceptual roadmap-only platform.[CE006, CE007, CE008, CE011, CE012, CE013]

5.3 Integration Ecosystem and Operator Workflow

Oasis’s operator workflow depends heavily on integrations rather than on a closed-stack assumption. The Wiz integration enriches Oasis with issues and data-security posture findings so identity actions can be prioritized by blast radius. The Zscaler partnership pairs identity governance with inline enforcement for machine-to-machine and agentic traffic. The Cursor partnership shows how the model extends up-stack into the agentic IDE, where agents run commands, call MCP tools, and interact with internal systems. Finally, the CrowdStrike marketplace motion and AI Access Partnership Program show that Oasis wants to be embedded inside broader enterprise AI and security buying journeys, not merely sold as a standalone dashboard. This ecosystem posture is strategically important. It allows Oasis to capture context from cloud exposure platforms, influence execution in zero-trust enforcement layers, and plug directly into developer and AI-agent workflows. That breadth may expand distribution and stickiness, but it also means the product’s value is partly dependent on maintaining interoperability across third-party systems whose own APIs and product strategies will evolve. In technical terms, Oasis appears to be building the identity-governance layer that normalizes signals from many systems and turns them into bounded, auditable access decisions.[CE009, CE010, CE019, CE020, CE021, CE033]

5.4 Trust, Standards, and Technical Maturity

Oasis’s trust story has three pillars: auditability, standards alignment, and technical credibility. Auditability comes from the AAM claim that each agent action is logged from prompt to action through a chain- of-custody record. Standards alignment comes from the AAM Framework launch and the broader NIST AI Agent Standards Initiative, which together show that the company is trying to anchor its narrative in a maturing external governance conversation rather than in product marketing alone. Technical credibility is reinforced by the OpenClaw disclosure, where Oasis researchers publicly detailed an agent-takeover chain and said the upstream team shipped a fix within 24 hours. At the same time, the standards environment is still early. NIST’s initiative is oriented around secure interoperability and open protocols, not a mature checklist buyers can simply adopt today. That creates an opening for Oasis to shape best practices, but it also means many of its governance claims are ahead of stable third-party certification norms. Public materials further highlight developer-signal through recruiting and engineering culture, yet they do not surface the kind of deep public API or package ecosystem that would make technical adoption easy to independently inspect. So the current technical-maturity signal is strong on narrative coherence and growing ecosystem relevance, but lighter on public benchmarks and open implementation proof.[CE022, CE023, CE024, CE025, CE026, CE027]

5.5 Roadmap Direction and Product Risks

The public roadmap is visible in the release chronology even without a formal product roadmap file. Oasis began with NHI lifecycle management, then added more explicit provisioning and governance workflows, and by late 2025 to mid-2026 had clearly pivoted into agentic access management, ecosystem partnerships, and a practitioner-built governance framework. That is a credible expansion path because AI agents inherit the same underlying identity problems as service accounts and workload identities, only with higher autonomy and faster decision loops. The main technical risks are equally clear. First, the company is making high-value claims about intent analysis, policy enforcement, and lifecycle automation without publicly released benchmark data, throughput metrics, or efficacy comparisons. Second, the architecture depends on continued cooperation from cloud, vault, IDE, and security-platform partners. Third, developer-signal is present mostly through recruiting and thought leadership rather than a visible open-source or SDK footprint. None of these risks breaks the product thesis, but they do mean that buyer diligence should move quickly from “the story sounds right” to “show the implementation detail, deployment evidence, and performance data.”[CE029, CE030, CE031, CE032, CE033, CE034]

5.6 Exhibits

6.1 Customer Base Segmentation and Vertical Mix

Oasis’s public customer story is clearly enterprise-first and heavily skewed toward regulated or operationally complex environments. The broadest signal comes from its own about page, which says leading organizations across many industries use the product. More specific signals come from Newswire and Globes, which say Oasis serves dozens of Fortune 500 companies and that a majority of the client base comes from the Fortune 500. The vertical pages and case-study surfaces point most strongly to healthcare, financial services, logistics, insurance, manufacturing, and large consumer brands. Those are precisely the environments where machine identities proliferate fastest, operational downtime is expensive, and audit pressure is real. The interesting nuance is that Oasis sells into both end-user enterprises and partner-facing ecosystems. The AI Access Partnership page pitches enterprise AI vendors who want governance out of the box, not only the final enterprise buyer. GuidePoint, CrowdStrike Marketplace, and Wiz extend the route to market further, showing that customer access may come through procurement vehicles and partner workflows as much as through direct sales. This broadens acquisition paths but makes it harder to see the exact composition of the installed base from public evidence alone. The end result is a customer map with strong top-end enterprise bias, decent vertical richness, and weak denominator transparency. Public materials make it plausible that Oasis is landing with large complex buyers, but they do not disclose how many customers exist in each segment or which segments dominate recurring revenue.[CU001, CU008, CU009, CU010, CU018, CU027]

6.2 Named Customer Proofs and Case-Study Depth

The richest public customer evidence is mostly company-authored, but it is not empty marketing fluff. Oasis has surfaced detailed deployment narratives in multiple sectors. A private-credit firm in financial services is described using Oasis in Azure AD for visibility, tailored security policies, stale-account cleanup, and automated identity rotation. A healthcare-provider case study is more data-rich still: the environment reportedly had 8,500 human identities, more than 100,000 NHIs, over 50,000 certificates, and around 10,000 service accounts, all being managed by an 18-person security team and roughly 50-person IT-operations team. An industrial-company webinar adds an Azure remediation and compliance narrative. Two named public references stand out. Mars appears in a dedicated April 2026 case-study resource focused on hyper-fragmented cloud identity visibility. Antares appears in the financial-services whitepaper as a user that streamlined lifecycle management and reduced manual work. These named references are stronger procurement-grade proof than anonymous vertical cases, though they still lack contract details, deployment length, or expansion history. By contrast, the Bank of America account page should be treated as account-based marketing, not as evidence of a live deployment. The core diligence takeaway is that Oasis has real use-case depth and at least some named public proof, but the public evidence remains unevenly distributed. Named customer proof exists, yet many of the most operationally informative case studies still remain anonymous.[CU002, CU011, CU012, CU013, CU014, CU015]

6.3 Adoption Signals, Review Surfaces, and Independent Customer Voice

Public adoption signals are strongest when Oasis speaks about enterprise outcomes and weakest when outside review platforms are examined. On the positive side, the home page lists multiple enterprise results: a Fortune-50 healthcare provider avoiding an estimated HIPAA fine, a Fortune-500 logistics buyer cutting secret- rotation effort by 35%, an insurance customer containing an outage impacting half of production workloads, and a manufacturing customer enforcing M&A compliance on newly acquired environments. The product page adds a Fortune 1000 quote about discovering 17,000-plus non-human identities in a cloud environment. Those signals are meaningful because they imply the product has been used inside live operational settings. The independent- customer-voice layer is much thinner. Gartner Peer Insights shows a 4.6 out of 5 rating from 20 ratings on the captured page, which is directionally positive. But that is still a relatively small sample for a company claiming dozens or more large-enterprise deployments. SourceForge and Slashdot provide product listings, yet the captured SourceForge page shows an overall 0.0/5 and both long-tail review sites offer very limited review substance. That does not prove customer dissatisfaction, but it does mean the public review surface is shallow outside Gartner. Investors should therefore separate two truths. First, Oasis likely has real enterprise adoption. Second, independent public voice remains too sparse to say much about broad satisfaction, ease of deployment, or renewal behavior at scale.[CU003, CU004, CU005, CU006, CU007, CU020]

6.4 Retention, Expansion, and Concentration Risks

The public record provides only one direct durability signal: Newswire said most new ARR is driven by multi- year enterprise agreements. That is a useful clue because multi-year contracts generally indicate some stickiness and customer commitment. The case studies also describe ongoing governance work rather than one- time assessments, which supports a recurring-usage interpretation. But the public evidence stops there. No NRR, GRR, churn, cohort, renewal-rate, or contract-length distribution is available, and no public customer count makes it possible to turn named proof into a credible penetration or concentration model. Concentration risk is the largest unresolved customer question. If Oasis truly serves dozens of Fortune 500 companies yet remains early in total count, then a small number of very large accounts could influence revenue heavily. The public record also does not reveal how much business arrives through GuidePoint, CrowdStrike Marketplace, Wiz- driven workflows, or the broader partner channel. Those routes are clearly important for acquisition and procurement access, but they could also concentrate bargaining power or distort deployment ownership if overused. The right diligence posture is cautious optimism. Oasis’s public customer evidence is strong on workflow relevance and deployment anecdotes, but weak on retention math and concentration visibility. That means customer quality cannot be fully underwritten without internal cohort and segment data.[CU024, CU025, CU026, CU027, CU028, CU036]

6.5 Exhibits

7.1 Risk Stack Overview and Severity Ranking

Oasis is addressing a real problem, but it is doing so in a threat environment moving faster than standards, buyer education, and public proof. The external context is unusually harsh. NIST’s AI Agent Standards Initiative is still at the stage of industry-led protocols and gap analysis rather than enforceable controls, while the Cloud Security Alliance says enterprises already need practical governance now. At the same time, machine identities vastly outnumber humans, AI agents are proliferating, and multiple recent incidents show how fragile the surrounding toolchain can be when trust boundaries are weak. That creates a distinctive risk profile. Oasis is not primarily exposed to a single catastrophic regulatory ban or a single hardware dependency. Instead, its biggest risks stack on top of each other: selling ahead of settled standards, relying on multiple partner ecosystems, proving control quality without much public benchmark evidence, and serving demanding regulated buyers whose procurement cycles are long and security-review burden is high. The product thesis may be right while the execution bar keeps rising. The implication for investors is that the most important risks are not abstract. They are monitorable: whether enterprise security reviews shorten, whether integrations remain stable, whether public proof matures beyond research and narrative, and whether management can turn category urgency into trusted large-scale deployment without strategic distraction.[CR001, CR002, CR022, CR024, CR037, CR039]

7.2 Regulatory, Legal, and Trust Risk

Oasis is selling into environments where compliance and trust burden are high, but the external standards layer is not yet mature. NIST is building agentic-AI standards around secure interoperability and open protocols, while CSA explicitly argues that enterprises are operating before agent-specific controls are settled. This mismatch is risky: Oasis can benefit from urgency, but it can also find itself repeatedly educating buyers and defending category assumptions that standards bodies have not fully codified. The company’s own public contract stack partly mitigates this and partly shifts risk back to customers. The DPA references GDPR, UK GDPR, and Israeli privacy law, while the SaaS agreement makes customers responsible for legal bases and permissions around their data. The SLA gives a 99.9 percent uptime commitment, but remedies are constrained to service credits capped at 20 percent of subscription value. In other words, Oasis has baseline enterprise paperwork, yet customers still shoulder meaningful compliance and outage risk in practice. This means legal and regulatory risk is less about immediate enforcement against Oasis and more about trust conversion. Buyers in healthcare, finance, and AI governance will expect a rapidly improving proof stack: clearer standards alignment, better external validation, and evidence that public legal language maps to reliable operational control.[CR003, CR004, CR005, CR006, CR007, CR033]

7.3 Operational, Technical, and Security Risk

The strongest evidence in the file is that the underlying problem space is dangerous. Oasis’s own research and incident analyses document a string of agentic and NHI failures: OpenClaw takeover from a visited website, Claude prompt-injection data exfiltration, shared agent-identity ambiguity in Claude Tag, localhost hijack in Cline, silent folder-open execution in Cursor, one-click VS Code MCP compromise, malicious MCP package exfiltration, weak-default-credential failure in McHire, and older but still highly relevant breaches at Change Healthcare, Cloudflare, and Cisco. Taken together, these are not edge cases. They show a pattern of repeated access-boundary failure across AI and machine-identity systems. That pattern is a commercial opportunity for Oasis but also a product risk. If buyers conclude that agentic systems are too unsafe to deploy broadly, demand can pause. If buyers do deploy aggressively, the burden shifts to vendors like Oasis to prove their controls actually reduce the risk. External threat summaries from OWASP, CyberArk, Palo Alto, Delinea, and related sources reinforce that governance gaps, over-privilege, weak offboarding, secret leakage, and immature AI controls are all common. Public evidence does not yet show Oasis publishing the kind of third- party efficacy benchmarks that would decisively answer that challenge. Operationally, the deployment model is safer than pure central custody because customer-side execution and local control boundaries matter. But that also means implementation quality, connector resilience, and customer-operational maturity become part of the product-risk equation, not something Oasis can abstract away entirely.[CR008, CR009, CR010, CR011, CR012, CR013]

7.4 Partner, Customer, and Model Risk

Oasis’s route to market is part of its moat and part of its risk stack. The AI Access Partnership Program openly pitches buyers and partners on bypassing lengthy security reviews. The public ecosystem also spans GuidePoint’s OASIS+ route, the channel program, Wiz, Zscaler, and other surrounding platforms. These dependencies help Oasis reach customers and integrate into enterprise security workflows, but they also mean platform stability, distribution leverage, and even some buyer trust are partially borrowed from partners. Customer risk is similarly double-edged. Large regulated enterprises can be sticky once won, yet they are slow to procure, expensive to support, and often concentrated. Public materials suggest Fortune-500-oriented traction and meaningful customer outcomes, but they still do not quantify retention, concentration, or partner-attributed ARR. That missing visibility matters because it becomes much harder to tell whether large logos represent a durable base or a small set of demanding accounts with outsized leverage. Financial-model risk is therefore mostly an information risk today. The March 2026 Series B reduced immediate funding anxiety, and multi-year-agreement language is helpful, but burn, runway, and concentration remain undisclosed. Finro’s warning about valuation-compression risk under weak public comps is a useful reminder that great category narratives do not eliminate financing discipline.[CR026, CR027, CR028, CR030, CR031, CR038]

7.5 Mitigations, Monitoring, and Kill Criteria

The encouraging part of the Oasis risk stack is that most of it can be tested early. Several of the top risks are not binary unknowables. Management can show evidence that enterprise security reviews are speeding up, that customer retention is healthy, that partner concentration is moderate, that public proof is expanding, and that vulnerability-response discipline is rigorous. If Oasis can move those needles, the risk case weakens materially because the company’s market relevance is already credible. The kill criteria are equally concrete. If public incidents keep showing the ecosystem is fragile while Oasis cannot provide benchmark evidence of control efficacy, buyer trust may stall. If partner dependence rises without fallback options, distribution resilience weakens. If strategic noise around potential M&A begins to distract teams or customers, execution risk rises. And if financial disclosure stays thin even as valuation expectations rise, investors should assume model risk is being carried forward rather than solved. In short, Oasis’s risk profile is best understood as manageable but front-loaded. The company must prove discipline, trust, and resilience faster than the agentic-access threat surface expands around it.[CR029, CR032, CR037, CR038, CR039, CR042]

7.6 Exhibits

8.1 Investment Thesis and Anti-Thesis

The public bull case for Oasis is compelling. The company sits in a category whose importance is rising quickly as AI agents and non-human identities proliferate across enterprise systems. Oasis has a visible Series B, recognizable investors, enterprise-oriented customer references, and a product story that positions it as the access-governance layer for the agentic enterprise. Strategic scarcity is real: category peers are being funded, large security vendors are consolidating adjacent machine-identity assets, and industry research now treats non-human and AI-agent identity as a first-order security control problem. The anti-thesis is equally important. Oasis has not publicly disclosed the operating metrics needed to justify a premium valuation. ARR, gross margin, retention, burn, and concentration are missing. Public category excitement therefore does not translate directly into underwriting confidence. Investors can believe the problem is real and still conclude that the price cannot be judged with enough precision yet. That tension matters because valuation here is narrative-sensitive. Oasis may in fact deserve a premium mark if growth quality is as strong as the company and reporters imply. But until the denominator is disclosed, the public file is best read as strategically promising rather than valuation-complete.[CV004, CV005, CV006, CV007, CV009, CV024]

8.2 Financing Context and Entry Discipline

The most reliable public price anchor is the March 2026 financing. Newswire, Globes, SiliconANGLE, Access Newswire, and TechCompanyNews all support the $120 million Series B. Globes adds the most useful valuation detail by reporting that market sources believed Oasis was worth about $700 million and that total capital raised reached $195 million. That is the public financing mark of record. July 2026 introduced a second but weaker valuation signal: Globes reported advanced talks to sell Oasis to Cyera for up to $1 billion, mostly cash with a small amount of stock. Investors should not treat that as a closed-market mark. It is better interpreted as evidence that larger security players or private platforms could view Oasis as strategically relevant. The rumor increases upside optionality, but it also raises the risk of over-reading an unconfirmed process. Entry discipline should therefore remain tight. The last funded mark around $700 million is credible. The rumored strategic ceiling near $1 billion is interesting. But without cap-table detail, preferences, or unit-economics disclosure, a disciplined investor should not underwrite to the high case by default.[CV001, CV002, CV003, CV008, CV026, CV027]

8.3 Comparable Framework and Market Sentiment

The right comparable framework is recurring-revenue identity security, not generic services or infrastructure software. Okta, SailPoint, Rubrik, and CyberArk all discuss their businesses through subscription revenue or ARR. Their filings and official results reinforce that investors value identity platforms on recurring-revenue quality, retention, and expansion. Those companies are much larger and not directly comparable to Oasis on product scope, but they do establish the language of the category. Analyst valuation work adds the second layer. Windsor Drake’s Q2 2026 IAM report pegs mainstream public IAM around 6.0x NTM revenue while stating that non-human and AI-agent identity platforms can clear roughly 15x to 30x in private rounds. Finro argues that using mature public cyber comps against private AI-native companies can badly mislead. Multiples.vc shows that the broader cyber tape has also improved meaningfully in 2026. Strategic consolidation reinforces the point: Astrix’s sale to Cisco and CyberArk’s machine-identity consolidation around Venafi show that large platforms are still buying into this control layer. The catch is that Oasis has not disclosed ARR. So while the comparable set says what kind of company Oasis might become, it cannot yet say what multiple Oasis truly deserves today.[CV010, CV011, CV012, CV013, CV014, CV015]

8.4 Scenario Analysis and Recommendation

The base-case decision is to anchor near the last defensible public financing mark and refuse to extrapolate too far beyond it. That means treating roughly $700 million as the current public benchmark, not because it is certainly correct but because it is the best-supported mark. The bull case can credibly approach $1.0 billion if the Cyera interest proves directionally right or if management can validate premium ARR growth and retention quality. The bear case falls to the mid-hundreds of millions if the market reverts to public-IAM discipline before Oasis supplies the metrics needed to justify premium private-category framing. Given that setup, the most defensible recommendation is research-more. Oasis looks like a company worth staying close to, not a company that can be bought confidently on public evidence alone. Confidence is medium because the category tailwinds and financing mark are real, but the operating evidence is incomplete. Risk rating remains high because disclosure, dependence, and proof questions are still material. This is a company that may be good and may even be strategically scarce. The issue is that the public file still does not show enough to know whether the current implied price is attractive, merely fair, or already stretched.[CV026, CV027, CV028, CV032, CV033, CV034]

8.5 Exhibits