LATEST / 18 AUG 2026
Lucidity adds Azure object-storage mapping, tiering and sprawl cleanup

COMPANY / CLOUD INFRASTRUCTURE

Lucidity wants to stop billing you for empty space

Oversized cloud disks are insurance against a very bad evening. Lucidity’s wager is that software can provide the safety without charging rent on all that empty space.

At a large global manufacturer, getting another 200 gigabytes of disk space once meant waiting three days. Someone noticed a server filling up. Someone requested capacity. Somewhere, approvals accumulated. The company bought generous amounts of storage in advance, which was sensible enough: an empty disk costs money; a full disk can stop the business. The expensive part was treating those as the only two choices.

Lucidity sells a third choice. Its software watches cloud storage and adjusts it as demand changes. The manufacturer’s operations manager described the first demonstration with a splendidly untechnical question: ‘What is this witchcraft?!’ The trick, according to Lucidity’s customer account, was replacing repeated human decisions with continuous block-storage rightsizing.

THE SHORT VERSION
  • Rightsize live disks instead of buying permanent headroom.
  • Track savings and engineering time separately.
  • Start with evidence, then allow changes within guardrails.

The insurance policy nobody cancels

Block storage is the disk capacity attached to the virtual machines running applications. Buying it is easy. Judging how much a busy application will need next month, then changing that allocation safely, is less agreeable. A database can grow; a workload can become quiet; yesterday’s emergency allocation can survive indefinitely. The cloud has made provisioning convenient without making every provisioning decision wise.

Lucidity co-founders Nitin Bhadauria and Vatsal Rastogi met in 2020 and founded the company in 2021. Rastogi had worked at Microsoft Azure and Swiggy. Their founding account describes more than 100 enterprise conversations and a recurring puzzle: organizations purchased considerable spare capacity yet still suffered storage outages. The problem was distribution and timing, as well as the total amount purchased.

The founders called their proposed destination ‘NoOps for cloud storage’. It is a useful ambition precisely because storage work is so unglamorous. Nobody receives a standing ovation for another successfully completed disk-expansion ticket. Yet someone must complete it, and the applications depending on that disk are rarely prepared to wait.

Lucidity co-founder Nitin BhadauriaLucidity co-founder Vatsal Rastogi
01 / Nitin Bhadauria, left, and Vatsal Rastogi. An alliance against the disk-expansion ticket. Company portraits.

A disk that can grow - and give space back

AutoScaler is Lucidity’s capacity engine. It expands and shrinks live volumes across AWS EBS, Azure Managed Disks and Google Cloud Persistent Disks. The company says rightsizing avoids downtime and application-code changes. Its claimed distinction is particularly practical: shrinking a live partition, so a customer can surrender unnecessary capacity rather than merely buying more.

Capacity is only part of the judgment. AutoScaler’s current product description includes IOPS, throughput, latency and historical workload behavior in its decisions. In May 2026, Lucidity added policy-based performance controls. A smaller disk is no bargain if it leaves an application waiting for data; optimization must respect the work the disk performs.

Lumen supplies visibility, disk-tier recommendations and idle-disk cleanup. It uses cloud APIs and metadata without deploying an agent. AutoScaler handles continuous capacity adjustment, while Lumen helps teams decide whether expensive performance tiers and forgotten disks deserve their continued patronage. Customers can begin with insights, approve actions individually, or permit automation within policies. Trust arrives in installments.

That graduated approach matters to the buyer. The people signing off on a storage change need to understand the evidence, the permitted action and the route back. A system that offers several levels of control can let an organization learn from a limited deployment before handing it a larger estate. The sales argument and the operating discipline meet at the same point: confidence.

Lucidity product dashboard showing storage metrics and optimization views
02 / Empty space, caught on camera. Lucidity’s dashboard makes storage waste visible. Company product image; click to enlarge.

The saving that outgrew the spreadsheet

Lucidity’s manufacturer account reports a 70% reduction in block-storage spending and utilization improving from 14% to 55%. It also reports roughly 2,000 automated provisioning tasks over several months. Those are vendor-published customer results, rather than a promise that every installation will behave identically. Still, they reveal two separate purchases: less wasted capacity and fewer chores.

A large retailer illustrates the second purchase. It initially liked the potential savings, then came to value the stability and maintenance reduction more. Its engineering director reported eight months without the disk-filling incidents that had previously demanded emergency changes and late-night calls. The team’s mind changed during rollout: the financial benefit was visible first; the operational benefit became harder to ignore.

A medical technology manufacturer provides another reported result: 52% lower block-storage spending, utilization rising from 24% to 80%, and more than 16,000 automated expansions and shrinks. Lucidity also names World Market, Dometic and ESO among its customers. The audience is enterprise infrastructure, cloud and DevOps teams, with finance enjoying the consequences.

MEDICAL MANUFACTURER / DISK UTILIZATION
Before
24%
After
80%
52%lower block-storage spending reported
03 / More of the disk earns its keep. Figures from Lucidity’s medical-manufacturer customer account; results are specific to this deployment.

From one troublesome disk to the storage estate

The company’s market position sits between broad cloud-cost management and the storage layer itself. A billing dashboard can reveal a large expense; Lucidity wants to change the resource producing it. Native cloud advisors, manual scripts and engineering teams are practical alternatives. Lucidity’s proposition combines cross-cloud visibility with execution, particularly for organizations whose existing applications make a wholesale architectural rewrite inconvenient.

The product boundary has widened. Kubernetes support arrived in September 2025, including rightsizing for EKS Persistent Volumes. In August 2026, Lucidity announced object-storage mapping, tiering and sprawl cleanup, generally available on Azure. That availability matters: support for three providers in block storage does not automatically imply identical object-storage coverage.

There is a business behind the invisible engineer. Lucidity sells enterprise software subscriptions through direct agreements, partners and marketplaces; fees and quantities sit in the customer’s order form. SoftwareOne is a documented distribution partner. A $21 million Series A led by WestBridge Capital, announced in February 2025, brought the company’s stated total funding to $31 million. Alpha Wave participated. The money funds a company trying to make its customers buy less infrastructure.

Trust arrives in installments.Observe → Approve → Automate

Measure the empty space before buying the cure

The useful thing to copy is the sequence. Measure real utilization across the estate, preserve each workload’s performance requirements, test on a bounded group, and compare the resulting bill and maintenance workload. A savings percentage alone cannot tell a buyer whether the subscription pays for itself. The sensible calculation subtracts software fees and implementation costs from avoided storage charges, then separately measures engineering time recovered.

Lucidity made the first step easier in March 2026 with a free, agentless, self-serve Assessment. The company says it produces a view of usage, waste and savings opportunities in about 15 minutes. It is an entry point for evidence before committing to operational changes.

The proposition becomes less compelling where disks already fit their workloads closely. It also depends on supported infrastructure and permission to make changes; policies that prohibit resizing will constrain the benefit. These are practical implications of the product’s mechanism. Start with one estate, one measured baseline and explicit guardrails. Empty space has an astonishing talent for looking prudent. Giving it a number makes the conversation considerably more interesting.