Uploaded November 2026 | Updated November 2026, 6 days ago
Avi Raichel, COO and co-founder of Dreeze, outlined three early strategic decisions that shaped their product, each with a credible alternative. The first decision addressed the common question of why Dreeze is needed if infrastructure as code (IaC) is already in use. Raichel explained that IaC is excellent for forward deployment and defining intent, but it differs fundamentally from backup, which captures the actual state at a specific point in time. He highlighted several limitations of IaC as a recovery mechanism, including undeclared estate, constant drift, lack of sequencing across multiple IaC files, commits not being true restore points, and the potential for IaC repositories or pipelines to be compromised within a blast radius. Despite these distinctions, Dreeze leverages IaC as an input for classification and application mapping and reconciles with IaC post-recovery to ensure a functional deployment pipeline.
The second key decision was for Dreeze to own the data backup process rather than simply orchestrating on top of a customer's existing data backup solution. This choice was made to prevent integration complexities and pain points during critical recovery events. Raichel, drawing on his experience as a former CIO, emphasized that running recovery across two separate products, one for infrastructure and application, and another for data, would create an integration gap that customers would face under immense pressure, leading to confusion about which product was causing issues. By taking ownership of data backup, Dreeze aims to deliver improvements like granular data restore, cost optimization through colder storage, and tag-free operations, addressing common customer challenges with cloud backup.
Finally, Dreeze decided to place the backup vault within the customer's cloud account instead of Dreeze's own accounts. This decision was based on two important customer considerations: data sovereignty and storage billing. Keeping the data in the customer's account ensures that it never leaves their control, providing clear data sovereignty. Furthermore, this approach allows the significant storage bill, which is often the largest part of cloud backup costs, to count towards the customer's existing cloud commitments and Enterprise Discount Programs (EDPs). These three decisions collectively reflect Dreeze's commitment to building an end-to-end solution that provides a single, unified recovery motion, avoiding dependencies on customer IaC, other backup vendors, or Dreeze holding customer data.
Recorded live in San Jose, California, on September 24, 2026, as part of Cloud Field Day 26. Watch the full presentation at techfieldday.com/appearance/dreeze-presents-at-cloud-field-day-26 or visit dreeze.com or techfieldday.com/event/cfd26 for more information.
Avi Raichel, COO and co-founder of Dreeze, outlined three early strategic decisions that shaped their product, each with a credible alternative. The first decision addressed the common question of why Dreeze is needed if infrastructure as code (IaC) is already in use. Raichel explained that IaC is excellent for forward deployment and defining intent, but it differs fundamentally from backup, which captures the actual state at a specific point in time. He highlighted several limitations of IaC as a recovery mechanism, including undeclared estate, constant drift, lack of sequencing across multiple IaC files, commits not being true restore points, and the potential for IaC repositories or pipelines to be compromised within a blast radius. Despite these distinctions, Dreeze leverages IaC as an input for classification and application mapping and reconciles with IaC post-recovery to ensure a functional deployment pipeline.
The second key decision was for Dreeze to own the data backup process rather than simply orchestrating on top of a customer's existing data backup solution. This choice was made to prevent integration complexities and pain points during critical recovery events. Raichel, drawing on his experience as a former CIO, emphasized that running recovery across two separate products, one for infrastructure and application, and another for data, would create an integration gap that customers would face under immense pressure, leading to confusion about which product was causing issues. By taking ownership of data backup, Dreeze aims to deliver improvements like granular data restore, cost optimization through colder storage, and tag-free operations, addressing common customer challenges with cloud backup.
Finally, Dreeze decided to place the backup vault within the customer's cloud account instead of Dreeze's own accounts. This decision was based on two important customer considerations: data sovereignty and storage billing. Keeping the data in the customer's account ensures that it never leaves their control, providing clear data sovereignty. Furthermore, this approach allows the significant storage bill, which is often the largest part of cloud backup costs, to count towards the customer's existing cloud commitments and Enterprise Discount Programs (EDPs). These three decisions collectively reflect Dreeze's commitment to building an end-to-end solution that provides a single, unified recovery motion, avoiding dependencies on customer IaC, other backup vendors, or Dreeze holding customer data.
Recorded live in San Jose, California, on September 24, 2026, as part of Cloud Field Day 26. Watch the full presentation at techfieldday.com/appearance/dreeze-presents-at-cloud-field-day-26 or visit dreeze.com or techfieldday.com/event/cfd26 for more information.










