Your Hardware, Your Data

Storage is a place. The drives that hold your photographs, your customer records, your engineering archives, your patient files, your legal correspondence, and your family videos exist somewhere. There is a building, a rack, a circuit board, a controller, a magnetic platter or a NAND die. Bits do not float. When you put your data “in the cloud,” you have not put it nowhere. You have put it in someone else’s building, on someone else’s hardware, under someone else’s law, subject to someone else’s business decisions. That is sometimes the right choice. It should always be a deliberate one.

This is not only a consumer question. Law firms with privileged communications, clinics with patient data, research labs with experimental data they cannot afford to leak or lose, small businesses with customer records under data-protection regimes, broadcasters with archives, departments inside larger organizations that need storage they can audit end-to-end. All of them have the same structural question to answer. RealNAS exists for all of them. The closet, the office server room, and the data-center cage are all the same problem.

“The cloud” is a marketing term for a fact of physics: a computer you do not own, run by people you have never met, in a place you cannot enter.

The structural costs of hosted storage

Hosted storage services are convenient, often well-engineered, and sometimes appropriate. They are not free of structural risk. Every one of the following has happened, repeatedly, to real customers of real services:

• The host can read your data. Encryption at rest, where it exists, often uses keys the host holds. End-to-end encryption with operator-held keys is the exception, not the default.
• The host can scan your data. Many service agreements reserve the right to inspect content for “policy violations,” defined by the host.
• The host can lose your data. Reliability marketing notwithstanding, data loss from configuration error, software bug, hardware failure, or operator mistake at scale is a real and recurring occurrence.
• The host can change pricing. The marginal cost of storing your data is approximately zero; the price you pay for it is whatever the host can charge. Free tiers vanish. Paid tiers grow.
• The host can change ownership. The terms you signed up under apply only until the acquirer rewrites them.
• The host can shut the service down. Sometimes with notice. Sometimes without.
• The host can be legally compelled to hand your data over. To a government that you trust, or to a government that you do not, depending on the host’s jurisdiction and yours.
• The host can be breached. The host’s incentive to disclose the breach quickly, accurately, and to you, is regulated; it is not the same as your incentive.

None of these are paranoid hypotheticals. They are categories of news story.

Surveillance is the business model

The largest providers of consumer cloud storage do not, in any meaningful sense, charge their users for storage. They subsidize it, and they earn the subsidy back by mining what they hold: for advertising, for ML training data, for vertical product integration, or to justify ever-larger purchases of inference compute. This is not a moral failing of any particular company; it is the economic logic of free or near-free hosted services. A photograph that is also a training example is more profitable than a photograph that is only a photograph.

The relationship between you and a NAS sitting on your own network is structurally different, because there is no second party. The hardware does not have a reason to mine your data. It does not have a reason to upsell you. It does not have a quarter to make. When you stop running it, it stops running. When you keep running it, it keeps running. There is no funnel, no engagement metric, no growth-team initiative aimed at the contents of your drives.

Lock-in is corrosive

A storage system that you can leave is a storage system you have chosen to stay with. RealNAS uses formats and protocols whose specifications are written down and implemented by multiple independent codebases:

ZFS

The filesystem itself. A pool created by RealNAS can be imported by any other ZFS implementation that supports the same feature flags.

SMB

The file-sharing protocol the rest of the network speaks. Samba is open source; the protocol is documented; clients exist for every platform.

NFS

The Unix-side file-sharing protocol. RFC-specified; multiple independent implementations.

FreeBSD

The operating system. BSD-licensed, openly developed, third-party packagable.

None of these depend on RealNAS continuing to exist. If the project disappeared tomorrow, the data would remain readable by widely-deployed tools that you do not need anyone’s permission to run.

The right to keep running

Devices you own should be devices you can keep running. The hardware you bought should remain useful for as long as it physically functions, regardless of whether the vendor that originally sold it still exists, still cares, or still wants to sell you something new. This is the basic claim of the right-to-repair movement, and storage hardware is one of its most legitimate domains: a NAS is a long-lived asset, often outliving the warranty, often outliving the operating system version that originally came on it.

RealNAS’s contribution to that claim is modest but real:

• There is no license server. There is nothing to revoke.
• There is no signed-boot chain that requires vendor cooperation to update.
• There is no “end-of-life” that bricks the device. End-of-life means “the project stops shipping new packages.” The system continues to boot, the pools continue to import, and the shares continue to serve.
• The source is available. If you do not like a decision the project makes, you can make different decisions on your own copy.
• The operating system underneath is general-purpose FreeBSD. When RealNAS is gone, you have FreeBSD. That is not nothing.

No phone home

RealNAS does not contact any server that the RealNAS project controls. There is no telemetry, no anonymous usage report, no “diagnostic upload,” no opt-out checkbox for these things because there is nothing to opt out of. The project does not know you exist. The project does not know how many systems are running. The project does not have a count of pools, datasets, snapshots, share types, or any other detail of your installation. We consider that the correct relationship.

The only outbound network traffic a default RealNAS installation initiates is what you ask it to initiate: SMTP to the relay you configured, replication to the destination you set, package updates from the mirror you point at. Each of these is an explicit operator decision.

The honest case for self-hosting

Self-hosting is more work than not self-hosting. A NAS is a thing in your closet that occasionally wants attention. Disks fail. Software has bugs. Power supplies wear out. Updates require thought. Backups require discipline. The total cost of ownership of a competently-run home or small-business NAS, measured in hours, is non-trivial.

In exchange, you get a relationship with your data that hosted services structurally cannot offer. The data does not move without your knowledge. The data is not subject to a terms-of-service change that you must accept or lose access. The data is not part of someone else’s training corpus. The data is not someone else’s business asset. The hardware does not have a contract date attached. The software does not require an account.

RealNAS exists to lower the cost of running that arrangement competently. It does not exist to make self-hosting effortless (effortless self-hosting is a contradiction in terms), but it exists to make the work tractable, repeatable, and durable.