A Messy Starting Point
When Daniel Drucker joined McLean Hospital in 2019, he did not inherit a clean environment. He inherited what he calls “a gigantic mess.” Nothing was documented. Teams were doing their own thing. And at the center of it all was a mostly working Dell Compellent system that was reliable enough to stay in place, but painful enough to hold the team back.
“It was extremely reliable,” Daniel says. “But actually working with it was just a nightmare.” The interface felt outdated, there was no API access, and even basic tasks were slow and manual. “Everything you wanted to do, you had to do by hand,” he says. “Every click took 30 seconds.”
The bigger problem was not just operational friction. It was loss of control.
When Replacement Costs Become the Real Problem
As McLean evaluated what came next, the replacement path pointed straight into a familiar enterprise trap: high switching costs, limited flexibility, and pricing the team could not justify. Daniel remembers being quoted “a million dollars to replace the system” for about half a petabyte, a number that was simply out of reach. The issue was no longer just storage performance. It was whether the hospital could control its roadmap, its budget, and its options going forward.
Why TrueNAS Stood Out
So Daniel looked elsewhere. He evaluated multiple options, including Dell Isilon, NetApp, and even building something from scratch. What pulled him toward TrueNAS was not a flashy pitch. It was familiarity, usability, and the sense that the platform would let him work the way he wanted to work.
He had already run it himself and liked what he saw. “I still run it at home and found that the interface was fast and easy to use,” he says. More importantly, it gave him something the incumbent platform never had: API access, operational flexibility, and visibility into what the system was actually doing.
Turning Manual Work into Automation
That control showed up immediately in day-to-day work. Under the old system, provisioning a new user was a multi-step manual process spread across interfaces and runbooks. With TrueNAS, Daniel automated it.
“Now I have this one shell script,” he says. It takes a username and single sign-on information, then uses the TrueNAS API to create the dataset, build the NFS mount, and set permissions. “From my point of view, it’s just magic in the background. Once I wrote that script, I never have to touch it again.”
Supporting Real Production Workloads
That same simplicity now supports real production workloads. McLean’s main TrueNAS system is about a petabyte and a half, serving both SMB file shares for users and labs and NFS storage for a high-performance computing environment used for neuroimaging analysis.
Daniel is direct about why it works: the environment does not need unnecessary complexity. “For our use, having a single NFS server, it works. It’s simple,” he says. “It’s incredibly simple to manage.”
Built for Recovery and Continuity
Just as important, the environment is built for recovery. McLean runs a second TrueNAS system in a Mass General data center about 20 miles away and sends ZFS replication updates every four hours. If the primary system failed, Daniel says the team could switch mounts and be “literally up and running in minutes.” In the worst case, “the most people could possibly lose is four hours of work.”
A third system backs up workstations and OS images, extending protection beyond shared storage alone.
Control Without the Black Box
For Daniel, the value of TrueNAS is not that it hides complexity. It is that it gives him control over it.
“It doesn’t hide stuff,” he says. And in an environment where he is responsible for keeping things moving, that matters. He does not have to wait on a vendor ticket queue to understand his own infrastructure. “When anything goes wrong, I know how everything works,” he says. “I don’t have to wait weeks for somebody to pick up a ticket.”
The Outcome: More Than Cost Savings
That is the real outcome of this story. McLean Hospital did not just replace aging storage. It regained leverage.
Instead of following a vendor-controlled upgrade path, the team built around its own requirements. Instead of accepting a million-dollar replacement quote, it chose a platform that matched storage economics to workload reality. Instead of relying on a black box, it gained API-driven automation, portable data workflows, and recovery options it could understand and manage firsthand. Even Daniel’s view of support reflects that shift: TrueNAS gives him expert help when needed, but he is not structurally dependent on the vendor to understand his own environment.
At McLean, that has meant more than lower cost. It has meant control over operations, control over economics, and control over what comes next.

It’s incredibly simple to manage…It doesn’t hide stuff. When anything goes wrong, I know how everything works. I don’t have to wait weeks for somebody to pick up a ticket.

