Druva's 2013 SaaS Pivot
Druva
The 2013 shift mattered because Druva stopped selling backup software that customers had to run, size, and maintain themselves, and started selling backup as an always on cloud service. That changed the product from something bought like infrastructure into something consumed like utility software. It also let Druva price by subscription and usage, ship updates centrally, and protect newer workloads like laptops, SaaS apps, and cloud data from one web console instead of through customer managed backup servers.
-
Before and during 2013, Druva still supported on premises and private cloud deployment, including an OpenStack based inSync edition for enterprises that wanted backup behind the firewall. The pivot was not just a hosting change. It was a decision to leave the legacy appliance and software path and rebuild around a SaaS control plane and cloud storage model.
-
That move gave Druva a cleaner break from incumbents like Veritas, Commvault, and Veeam, which were rooted in customer operated backup stacks, and even from newer players like Rubrik that first won with appliances before shifting toward cloud subscriptions. Druva could sell zero infrastructure backup from the start, which made global rollout and ongoing operations simpler for customers.
-
The business model changed with the architecture. Druva now makes money through recurring subscriptions and consumption based storage, rather than large upfront license and hardware style purchases. In backup, that matters because buyers increasingly want costs to scale with protected data, not with big capacity bets made years in advance.
Going forward, this 2013 decision is what allows Druva to keep moving up from backup into broader data security. Once backup, recovery, compliance, and threat signals all run through one SaaS platform, the company can add more security workflows without asking customers to deploy another box, storage tier, or management plane.