Dreeze funding, valuation and investors

Product & use cases

Illustrative buyer: a platform engineer running a customer-order app with an API hosted in EKS, Postgres/RDS, messaging, networking, IAM and secrets. (1) After security review, connect an AWS account using read-only discovery permissions; Dreeze maps dependencies from live cloud resources (the company advertises 265+ relationship types and scans every 24 hours or on demand, which is a vendor claim). (2) Review the discovered grouping and manually correct any mistaken app dependency or shared resource. (3) Define protection/retention and replicate data, infrastructure configuration and recovery plans to a customer-controlled isolated, immutable vault, with encryption/operational costs to validate. (4) Configure app-level recovery ordering, cross-account target and special procedures for external DNS, secrets, SaaS dependencies, IAM and third-party APIs. (5) Run a scheduled restore test in an isolated account, record real application availability and elapsed recovery time, then compare these against required RTO/RPO and compliance needs. (6) For incidents, invoke the restoration plan under incident-management approval. This is a representative workflow supported by product documentation; VCT did not personally deploy Dreeze. Cloud resource costs, egress and recovery-test operations can affect total cost. No public vendor price was verified. Important: Azure early access only at announcement; production multi-cloud support should be tested individually.

• Enterprise SRE and platform teams need application-level disaster-recovery runbooks when multi-service cloud workloads fail.
• Security and risk teams want isolated, immutable backup copies and repeatable recovery testing after ransomware or infrastructure compromise.
• Cloud operations teams want to recover a complete service that includes databases, IAM permissions, networking, cluster resources and configuration after a faulty deployment or an automated agent's destructive changes.

Key facts

• $33M Seed announced November 10, 2026, co-led by Norwest and Bessemer Venture Partners; Claltech participated, legal close date and valuation undisclosed.
• 'Application Revival' maps cloud app dependencies, backs up data and surrounding infrastructure/configuration, orchestrates ordered recovery, and validates in isolated test environments.
• AWS product was generally available at announcement; Microsoft Azure early access with target GA early 2027, not yet independently confirmed as delivered.
• Public pricing, customer counts, renewal rates and audited recovery performance are undisclosed; Coravant endorsement in company release is a selected vendor-supplied example.

Competitive landscape

Edge: Company-positioned advantage: actual live dependency graphs and tested, ordered application restoration, compared with storage-oriented backup or point-in-time database restores. Experience of Zerto/Kashya founding team may help distribution and engineering execution but does not independently verify the promised outcomes. The value is measured by time-to-working-application rather than 'backup succeeded'. Requires careful shared-resource mapping and permission boundaries. Vendor-specific recovery data, economics and price comparison are unavailable.

Buyer diligence: request a full-price quote and a scoped proof of concept restoring one production-like app with its DB, EKS manifests/config, identities, secrets, networking, queueing and external dependencies. Measure recovery point objective (maximum acceptable data loss), recovery time objective (time to usable application), actual cross-account restore time, test-compute and vault storage charges, data-residency/custody and administrator privilege access. Isolation does not itself prove the recovered workload is uncompromised; retained malicious configurations or credentials and off-cloud dependencies still need inspection. Norwest and Bessemer's early-stage backing signals investor conviction, not independently demonstrated SLA compliance, product retention or ARR. Do not attribute Norwest and Norwest Venture Partners as two distinct lead investors.

• AWS Backup incumbent

  AWS-native protected resources and restore capabilities; buyer must assess consistency and coordinated recovery of a cross-service application, not merely individual backups.

• Veeam Kasten direct

  Kubernetes application-aware backup and restore, with different coverage scope around external cloud infrastructure and identities; technical feature-by-feature test required.

• Rubrik direct

  Enterprise cyber-resilience and backup/restore platform; compare immutability, cross-service dependency handling and recovery-test automation.

• Druva direct

  SaaS/cloud data resilience, protection and recovery; different workload coverage and packaging.

• Commvault incumbent

  Broad enterprise backup and recovery offerings; compare full application rebuild versus protected-resource restoration and enterprise spend.

Market / IPO context