Dreeze Emerges From Stealth With $33M Seed Round for Cloud Application Recovery

Dreeze is emerging from stealth with $33 million in seed funding and a proposition aimed at one of cloud computing’s most frustrating failures: restoring the data without restoring the business application that depends on it.

The round is led by Norwest and Bessemer Venture Partners, with participation from Claltech. Alongside the financing announcement, the Tel Aviv company is launching its Application Revival platform, designed to map, protect, rebuild, and test the resources needed to bring a complete cloud application back into operation.

Dreeze was formed in 2025 by Ziv Kedem, Oded Kedem, and Avi Raichel, veterans of the backup and recovery industry with experience at Zerto and Kashya. The company says it has 70 employees across Israel and the United States and will use the funding to accelerate product development, expand sales and marketing, and reach more enterprise customers.

When Restored Data Still Leaves an Application Offline

The problem Dreeze is targeting sits between a successful backup restore and a functioning service. A cloud application can depend on infrastructure, configuration settings, identities, secrets, encryption keys, and connections to other resources. Bringing back its database addresses only part of that system.

If the surrounding components are unavailable or restored in the wrong sequence, IT teams may still need to reconstruct dependencies manually. Dreeze calls that process the “recovery scramble”: the period when data has returned but the application remains unusable.

“Companies have spent years getting better at backing up data, but getting the data back doesn’t mean the business is back,” said Ziv Kedem, Dreeze’s co-founder and CEO, in the announcement.

That distinction changes the recovery objective. For a business, the meaningful endpoint is a service that employees or customers can use again. A restored storage volume is an important milestone, but it does not establish that authentication works, required resources are connected, or the application can complete its normal tasks.

Four Stages of Application Revival

Dreeze organizes its platform around four capabilities, combining discovery and protection with recovery execution and testing.

Know: Map Dependencies Before an Outage

The company says its autonomous dependency mapping connects resources to the applications they support and generates a recovery plan from the live environment. The intention is to keep the plan aligned with changes to the application rather than leave recovery teams dependent on an aging runbook.

This is the foundation of the approach: an automated recovery sequence is only as complete as its understanding of what must be recovered. Identifying dependencies before a disruption shifts that work away from the incident itself.

Protect: Back Up the Supporting Resources

Dreeze says its vaulted backup protects data together with configuration, keys, and other application dependencies. The announcement describes an immutable, air-gapped vault and optional replication across regions.

Orchestrate: Rebuild in Dependency Order

The platform’s Revival Automation capability executes the recovery plan, rebuilding data, infrastructure, configuration, identity, and connections in dependency order, according to Dreeze.

The value of orchestration is in coordinating the handoffs between those components. For example, restoring a service before the resources it requires are available can leave teams troubleshooting a partially rebuilt environment. A dependency-aware plan aims to reduce that manual sequencing work.

Validate: Test the Complete Recovery Plan

Dreeze describes its validation capability as an automated, end-to-end test that rebuilds a working application. The company says these tests run without production impact or manual cleanup afterward.

Testing is central to the product’s commercial argument. A documented plan describes what should happen; a successful rehearsal provides evidence about what actually happens in the tested environment. The announcement does not disclose independent benchmarks, recovery-time measurements, or a comprehensive support matrix.

AWS Availability, With Azure to Follow

Dreeze says its AWS offering is generally available. Its Microsoft Azure product is in Early Access, with general availability planned for early 2027. The distinction matters for enterprises planning deployments across both clouds: the announcement describes different availability stages.

Jeremy Miller, founder and CEO of Coravant, said in the release that customers’ concern is recovering an entire application with its dependencies in the correct order. That is the operational gap Dreeze aims to close: preparing the complete route back before an outage exposes missing pieces.

Why the Funding Matters

Dreeze is entering a market where recovery must account for more than the quantity of protected data. As applications gain services, permissions, and infrastructure dependencies, the recovery task becomes a coordination problem as well as a storage problem.

AI adds another reason for enterprises to make recovery preparation explicit. Unite.AI’s coverage of backup awareness in AI agents examines the risks of automated systems changing environments without adequate preparation for restoration. Dreeze’s announcement addresses the broader operational question of rebuilding applications after disruption; it does not establish that the platform prevents unsafe agent actions.

The seed funding gives Dreeze resources to turn that application-level recovery pitch into a wider enterprise business. Its next challenge is demonstrating that dependency discovery, protection, orchestration, and testing work together across customers’ actual environments. For buyers, the compelling outcome is straightforward: a tested route back to a usable application when a critical service goes down.