Dreeze

Application Revival platform for restoring complete cloud applications after outages or cyberattacks.

Cover Block

From the public record

Field	Value
Name	Dreeze
Tagline	Application Revival platform for restoring complete cloud applications after outages or cyberattacks [Dreeze, November 2026]
Headquarters	Dover, DE [Dreeze, November 2026]
Founded	2025 [SecurityWeek, November 2026]
Stage	Seed [Dreeze, November 2026]
Business Model	B2B
Industry	Security
Technology	Software (Non-AI)
Geography	Middle East / North Africa
Growth Profile	Venture Scale
Founding Team	Co-Founders (3+), Ziv Kedem, Oded Kedem, and Avi Raichel [SecurityWeek, November 2026]
Funding Label	Seed (total disclosed ~$33,000,000) [Dreeze, November 2026]

The Short Version

PUBLIC Dreeze is building a cloud-application recovery platform that aims to restore whole applications, not just backed-up data, after outages or cyberattacks, and it merits attention now because it launched out of stealth with a $33 million seed round and a generally available product on day one [Dreeze, November 2026] [SecurityWeek, November 2026] [Citybiz, November 2026]. The company was founded in 2025 by Ziv Kedem, Oded Kedem, and Avi Raichel, a team drawn from prior data protection and disaster recovery companies Kashya and Zerto, with Zerto later acquired by Hewlett Packard Enterprise in 2021 and Kashya acquired by EMC [Blocks & Files, November 2026] [Israel Defense, November 2026] [TechCrunch, June 2014].

The product thesis is straightforward: conventional backup may recover data without reconstructing the application environment around it, while Dreeze says its Application Revival platform continuously maps dependencies, generates an automated recovery plan as the environment changes, stores application dependencies in an immutable isolated vault, and rebuilds applications in dependency order with pre-validation support [Blocks & Files, November 2026] [Israel Defense, November 2026] [Ynet News, November 2026]. That framing gives the company a clear wedge with enterprise infrastructure, IT, security, and business continuity teams operating in public cloud environments, although public launch materials do not yet establish customer adoption, revenue, or production scale [Calcalist/CTech, November 2026] [SecurityWeek, November 2026].

The founding team is the main reason investors will take an early meeting. Ziv Kedem previously co-founded Kashya and Zerto and served as Zerto's CEO, Oded Kedem previously co-founded Kashya and Zerto and has been identified as Zerto's CTO, and Avi Raichel previously held CIO and COO roles at Zerto after earlier information systems leadership at Amdocs [Blocks & Files, November 2026] [Bloomberg Markets] [Businesswire, June 2021] [Finsmes, November 2026].

Dreeze sells a B2B software product and disclosed a $33 million seed round led by Norwest and Bessemer Venture Partners, with Claltech participating, which is a large opening financing relative to a first public launch and suggests investor confidence in the team and category timing [Dreeze, November 2026] [Finsmes, November 2026] [SiliconANGLE, November 2026]. Over the next 12 to 18 months, the key questions are whether Dreeze can convert founder-market fit into referenceable enterprise deployments, demonstrate that application-level recovery is budgeted separately from traditional backup, and reconcile early signals on organizational scale, since Israel Defense reported 70 employees across Israel and the United States at launch while Startup Nation Finder lists a smaller 1 to 10 employee range [Israel Defense, November 2026] [Startup Nation Finder, retrieved 2026].

Inferred, not confirmed -- Core launch, funding, product scope, and founder histories are supported by multiple public sources, but the section includes a material headcount discrepancy across public records.

Taxonomy Snapshot

Axis	Value
Stage	Seed
Business Model	B2B
Industry / Vertical	Security
Technology Type	Software (Non-AI)
Geography	Middle East / North Africa
Growth Profile	Venture Scale
Founding Team	Co-Founders (3+)
Funding	Seed, total disclosed ~$33,000,000

The Company in Brief

PUBLIC

Dreeze presents as a newly formed cloud-application recovery company, with publicly available company materials describing an "Application Revival" platform for restoring complete cloud applications after outages or cyberattacks [Dreeze, November 2026]. The company is headquartered in Dover, Delaware, according to the structured company record provided for this report, and was founded in 2025 [Crunchbase, retrieved 2026].

The public timeline is still short, which matters for interpretation. Crunchbase places the company’s founding in 2025 [Crunchbase, retrieved 2026], and the company emerged from stealth in November 2026 alongside the public launch of its platform and disclosure of a $33 million seed round led by Norwest and Bessemer Venture Partners, with Claltech participating [Dreeze, November 2026]. On the evidence available here, that November 2026 launch is the first clear public milestone for the business rather than a late-stage financing update [Dreeze, November 2026].

Single-source, plausible -- This section relies on company materials and a single company database record, with only partial corroboration in the allowed source set.

What They Have Built

MIXED

Dreeze is making a narrower claim than most backup vendors at launch: that restoring data is not the same as restoring the application that depends on it. Public launch coverage describes its Application Revival platform as software that continuously maps a customer’s cloud environment, identifies application dependencies, and keeps an automated recovery plan current as the live environment changes [Blocks & Files, November 2026] [Israel Defense, November 2026]. That framing matters because the product is being positioned around whole-application recovery for enterprise teams running in public-cloud environments, rather than point recovery of datasets alone [SiliconANGLE, November 2026] [Calcalist/CTech, November 2026].

The recovery workflow described in press coverage is reasonably specific for a company just out of stealth. According to Ynet News, Dreeze backs up application dependencies, including data, configuration, encryption keys, and infrastructure, into an immutable, isolated vault [Ynet News, November 2026]. Blocks & Files reports that the platform then rebuilds the application in dependency order and supports pre-validation of the recovery plan, which suggests the company is trying to reduce uncertainty before an outage or cyber event forces a live restore [Blocks & Files, November 2026]. Citybiz reported the platform as generally available at launch, which is a useful distinction even if public material does not yet disclose reference customers or deployment scale [Citybiz, November 2026].

The technical stack is less visible than the recovery logic, and the public record should be read carefully here. A verified careers page shows at least one open Backend Engineer role, but the source set provided for this section does not establish programming languages, cloud providers, databases, or infrastructure design, so any deeper stack claim would be overstated [Dreeze Careers]. What is visible is a product thesis shaped by founders who previously built in data protection and disaster recovery, with Dreeze now extending that history toward cloud-application reconstruction rather than backup alone [Blocks & Files, November 2026] [Israel Defense, November 2026] [Finsmes, November 2026].

Single-source, plausible -- Product capabilities are corroborated across Blocks & Files, Israel Defense, Ynet News, and Citybiz, but the technical stack itself is not publicly described beyond a verified job posting.

Market Size and Demand

PUBLIC The market matters because Dreeze is entering cloud recovery at a point when enterprises increasingly run business-critical workloads in public cloud, but outage and cyber recovery still tends to restore data before it restores the full application stack [SecurityWeek, November 2026] [Ynet News, November 2026]. The available public record does not provide a named third-party TAM, SAM, or SOM for Dreeze specifically, so the market case has to be built from adjacent demand signals rather than from a clean sizing model. That is a limitation worth keeping in view, especially for a company that launched with a large seed round and a broad product claim set [Dreeze, November 2026] [Finsmes, November 2026].

The demand thesis in public sources is straightforward. Multiple launch reports describe the core problem as the gap between recovering backed-up data and restoring a working cloud application, including infrastructure, configuration, dependencies, identities, secrets, keys, and network connections [Calcalist/CTech, November 2026] [Finsmes, November 2026] [Ynet News, November 2026]. That framing suggests Dreeze is not selling into backup spend alone. It is aiming at a broader recovery and resilience budget owned across infrastructure, security, IT operations, and business continuity teams [SiliconANGLE, November 2026] [SecurityWeek, November 2026].

The more interesting point is where the product sits relative to adjacent markets. Public coverage consistently places Dreeze between cloud backup, disaster recovery, cyber recovery, and application dependency management, with its wedge being orchestration of complete application restoration rather than file- or volume-level recovery [Blocks & Files, November 2026] [CFO Tech Outlook, November 2026]. In practical terms, that means the nearest budget lines may come from data protection and business continuity, while the substitute behavior is still internal scripting and process-heavy runbooks that try to recreate applications after an outage or attack [Israel Defense, November 2026] [Ynet News, November 2026].

Regulatory and macro forces are present in the background, even if the sourced coverage does not tie Dreeze to any one rule set. The company is being introduced into a market shaped by higher executive attention to cyber resilience and operational continuity after ransomware and cloud-service disruptions, and the reporting repeatedly anchors the use case in cyberattacks and outages rather than ordinary backup administration [SecurityWeek, November 2026] [SiliconANGLE, November 2026]. That framing supports real urgency, but it also means category education may still be required, since buyers often procure backup, DR, and security tooling through different teams with different success metrics.

Market lens	What the sources support	Relevance to Dreeze
Core category	Cloud application recovery after outages or cyberattacks [SecurityWeek, November 2026] [Citybiz, November 2026]	Direct category framing at launch
Adjacent budget	Backup and data protection spend [Blocks & Files, November 2026] [Finsmes, November 2026]	Likely entry point, but Dreeze argues backup alone is insufficient
Substitute workflow	Manual or semi-manual recovery planning and application rebuild steps [Ynet News, November 2026] [Israel Defense, November 2026]	Helps explain wedge if buyers currently rely on internal runbooks
Buyer set	Infrastructure, IT, security, and business continuity teams [SiliconANGLE, November 2026] [SecurityWeek, November 2026]	Cross-functional sale may expand budget access, but can lengthen procurement

The table highlights a market that is legible in workflow terms but not yet well bounded in public numeric terms. For now, the case rests less on a published market size and more on whether Dreeze can convert a familiar pain point, incomplete recovery after disruption, into a distinct enterprise software budget.

Single-source, plausible -- Section is grounded in multiple public launch reports, but no named third-party market sizing report was available, so the market analysis relies on adjacent-category evidence rather than directly corroborated TAM data.

Who Else Is Fighting for This

MIXED Dreeze is positioning itself less against point backup tools than against the broader gap between data recovery and full application recovery in public-cloud environments, a distinction repeated across launch coverage but not yet pressure-tested against named competitors in the public record [Blocks & Files, November 2026] [Ynet News, November 2026] [SecurityWeek, November 2026].

Public reporting gives only a partial map of the field, but the segment lines are still visible. The incumbent set appears to be the enterprise backup and disaster-recovery vendors that restore data and virtual machines, while the adjacent substitute set is made up of internal cloud-platform teams stitching together cloud-native snapshots, infrastructure-as-code, secrets management, and runbooks to rebuild services after an outage or cyberattack [Calcalist/CTech, November 2026] [Ynet News, November 2026]. Dreeze's pitch is that those approaches often leave application dependencies, configuration state, encryption keys, and recovery ordering outside the core recovery workflow, which is why the company frames its product around restoring the application as an operating system rather than restoring a dataset alone [Blocks & Files, November 2026] [Finsmes, November 2026].

That leaves the challenger set harder to name from the available sources, because the company did not publicly benchmark itself against specific startups at launch [SecurityWeek, November 2026] [SiliconANGLE, November 2026]. In practical terms, the most credible early competitors are likely to be vendors already selling cyber recovery, cloud backup, and business continuity into the same enterprise buyers, namely infrastructure, IT, security, and resilience teams [SiliconANGLE, November 2026] [Calcalist/CTech, November 2026]. The absence of named rivals in public materials is itself informative: Dreeze is trying to define a product category around application revival before the market settles on a standard feature set.

Dreeze's clearest edge today is team credibility. Ziv Kedem and Oded Kedem previously co-founded Kashya and Zerto, and Avi Raichel held senior operating roles at Zerto, with Kashya later acquired by EMC and Zerto acquired by Hewlett Packard Enterprise in 2021 [Blocks & Files, November 2026] [Israel Defense, November 2026] [Businesswire, June 2021] [Help Net Security, June 2021]. That founder-market fit matters here because the product claim, continuous dependency mapping, automated recovery planning, isolated backup of application dependencies, and ordered rebuild, asks customers to trust a new vendor with one of the highest-consequence workflows in enterprise infrastructure [Blocks & Files, November 2026] [Israel Defense, November 2026] [Ynet News, November 2026]. The durability of that edge is mixed: reputational access to enterprise design partners and investors can persist, but product credibility in resilience software usually decays quickly if real-world recoveries, integrations, and proof-of-recovery exercises do not match the thesis.

The company is still exposed on distribution and proof points. Norwest and Bessemer Venture Partners co-led the $33 million seed round, with Claltech participating, which should help with recruiting and enterprise introductions, but capital does not substitute for named references, renewal evidence, or a published ecosystem position with major cloud platforms [Dreeze, November 2026] [Finsmes, November 2026]. Dreeze also announced general availability at launch, yet the public record cited here does not identify customers, production deployments, or commercial partners, which leaves an opening for larger incumbents and adjacent platform vendors to respond by bundling parts of the workflow into existing backup, security, or cloud-management suites [Citybiz, November 2026] [SecurityWeek, November 2026].

The most plausible 18-month scenario is a land-grab around enterprise accounts that already understand the limits of data-only recovery after ransomware and cloud outages. If Dreeze can turn founder access and its seed financing into referenceable deployments, Dreeze is the most plausible winner if buyers decide that application-level recovery deserves its own control plane rather than a feature extension inside backup software [SiliconANGLE, November 2026] [CFO Tech Outlook, November 2026]. The loser if that assumption fails is Dreeze itself: if incumbent recovery vendors close enough of the dependency-mapping and orchestration gap, a standalone platform could face a narrower wedge than launch coverage currently implies.

Opportunity

Upside case

PUBLIC The prize here is unusually large for a company this early: if Dreeze becomes the control plane enterprises trust to bring whole cloud applications back after an outage or cyberattack, it could sit in a budget stream that is closer to business continuity infrastructure than to point backup software [SecurityWeek, November 2026] [Ynet News, November 2026].

The headline opportunity is not simply selling faster restore times. It is owning the recovery workflow for cloud applications whose failure now carries operational and security consequences beyond lost data. Public launch coverage is directionally supportive of that outcome because Dreeze is framing the problem at the application layer, not the file or database layer: the platform continuously maps cloud environments and dependencies, generates an automated recovery plan as those environments change, stores application dependencies in an immutable isolated vault, and rebuilds systems in dependency order with pre-validation support [Blocks & Files, November 2026] [Israel Defense, November 2026] [Ynet News, November 2026]. That positioning matters. If enterprise buyers accept the founders' premise that restoring data alone does not restore the business, then Dreeze is competing for a larger and more durable role inside resiliency architecture [SiliconANGLE, November 2026] [Calcalist/CTech, November 2026]. The setup is more reachable than a typical launch-stage ambition because the founding team has prior operating history in data protection and disaster recovery, including Kashya and Zerto, with those companies later acquired by EMC and Hewlett Packard Enterprise respectively [Blocks & Files, November 2026] [Israel Defense, November 2026].

A plausible path to scale is easier to see when the upside is broken into concrete motions rather than treated as a single outcome. The table below outlines three public-evidence scenarios that could each support a venture-scale result.

Scenario	What happens	Catalyst	Why it's plausible
Cloud recovery standard	Dreeze becomes a preferred recovery layer for enterprises running business-critical applications in public clouds	A wave of cyber incidents and outage-driven buying shifts budget from backup-only tools toward full application recovery	Dreeze launched specifically around the gap between data recovery and application recovery, and its platform was generally available at launch rather than pre-product [Ynet News, November 2026] [Citybiz, November 2026]
Founder-led enterprise wedge	The company converts founder credibility into early large-account adoption, then expands from one application estate to broader cloud environments	Reference customers begin with continuity or security teams already familiar with the founders' prior work in recovery infrastructure	Ziv Kedem and Oded Kedem previously co-founded Kashya and Zerto, while Avi Raichel held CIO and COO roles at Zerto, giving Dreeze a team with category-specific operating history [Blocks & Files, November 2026] [Businesswire, June 2021] [Help Net Security, June 2021]
Recovery platform expansion	Dreeze starts with restore orchestration and vaulting, then broadens into adjacent resilience workflows such as testing, policy, and cross-team operational controls	Enterprises standardize on one product that maps dependencies, validates recovery plans, and rebuilds applications in order	Public product descriptions already span mapping, plan generation, protected backup, pre-validation, and rebuild orchestration, which is a broader surface area than backup alone [Blocks & Files, November 2026] [Israel Defense, November 2026] [Finsmes, November 2026]

The compounding dynamic, if it appears, would come from operational embed rather than consumer-style network effects. A platform that continuously maps a customer's cloud environment, identifies dependencies, and updates recovery plans as the live environment changes becomes more valuable as that environment grows more complex [Blocks & Files, November 2026] [Israel Defense, November 2026]. That creates a reasonable flywheel: one successful deployment can widen from a single application estate into more workloads because the product's value rises with interdependency count and the cost of failure. Early signs are still limited, but the ingredients for that flywheel are visible in public materials: Dreeze launched with a generally available platform, a disclosed $33 million seed round, and a team reported at 70 employees across Israel and the United States at launch, which suggests an intent to build both product depth and enterprise go-to-market capacity early [Citybiz, November 2026] [Dreeze, November 2026] [Israel Defense, November 2026].

The size of the win cannot be anchored to a confirmed market-sizing report in the available public record, so the cleanest public comparable is strategic value rather than a precise TAM. The relevant founder precedent is Zerto, which was acquired by Hewlett Packard Enterprise in 2021 after building a business around disaster recovery and data protection infrastructure [Blocks & Files, November 2026]. If Dreeze were to establish itself as a cloud-application recovery platform with broad enterprise adoption, the upside case is a strategic-infrastructure outcome measured in the high hundreds of millions or low billions of dollars in enterprise value (scenario, not a forecast), particularly if buyers treat full application restoration as a distinct control layer rather than a feature inside backup [SecurityWeek, November 2026] [Calcalist/CTech, November 2026]. That is still conditional on execution, but the public evidence supports a real shot at category relevance rather than a narrow feature company.

Single-source, plausible -- The section relies on multiple named public sources for product scope, founder background, funding, and launch status, but the valuation framing is an analytical scenario rather than a directly sourced market benchmark.

Sources