Taildrive

What Taildrive Is and How It Works

Taildrive is a policy-controlled shared folder feature that exposes a selected folder over a Tailnet using WebDAV. The key idea is not public file hosting, but controlled cross-device access inside a private network, so users can work with the same folder from different devices without opening storage directly to the internet.

Because the service behaves like a small file server, it sits at the intersection of file sharing, network access control, and user convenience. That makes it useful for personal or team workflows where a synced or centrally reachable folder is preferable to ad hoc file transfer, but it also means access decisions matter as much as the storage location itself.

Taildrive’s Access Model and Trust Boundary

Taildrive’s security value comes from the fact that the folder is reachable only to devices and users already inside the Tailnet’s trust boundary. In practice, that means the share is governed by network membership and policy rather than by publishing a service endpoint to the public internet.

This changes the exposure profile. The folder is not inherently private because it is on a local machine or internal server, it is private because access is mediated through the Tailnet and the WebDAV share is scoped to selected users or devices. That makes the trust boundary explicit and easier to reason about than a broadly exposed file share.

For readers comparing control models, Taildrive is closer to a managed internal file service than to a general-purpose cloud drive. The operational question is therefore not only where the data lives, but who can reach it, from which device, and under what policy conditions.

Where Taildrive Fits in Shared File Workflows

Taildrive is most useful when teams or individuals need a folder that feels local on each device but remains consistently accessible across endpoints. That can reduce friction compared with manually copying files, mounting disparate shares, or relying on a public download link for every exchange.

Because the feature is folder-based, its practical value is tied to the contents of that folder and the discipline around what is placed there. A shared folder may be convenient for working documents, project files, or other collaboration data, but it can also become an accidental aggregation point if users place more sensitive material there than the access policy was designed to support.

The WebDAV design also means behaviour depends on the client side as well as the network side. Different operating systems and file managers may present a mounted share differently, so user experience, caching, and offline handling can affect how reliably people perceive the folder as “the same” across devices.

Security Implications of a Policy-Controlled Folder Share

Even though Taildrive avoids internet exposure, the share still depends on correct policy, device trust, and folder scoping. A shared folder is only as safe as the permissions attached to it, and a narrow internal boundary can still be too broad if too many users or devices are allowed to mount the same data.

The most important security implication is that file access becomes an access-control problem, not merely a storage problem. If a device or user is compromised inside the Tailnet, the share can become a convenient path to read, alter, or exfiltrate whatever is exposed through WebDAV.

That is why the folder should be treated as a governed resource. Content sensitivity, permitted collaborators, and the practical blast radius of a compromised endpoint all matter more here than the fact that the service is not openly published.

Operational Trade-offs and Good Fit

Taildrive is a good fit when the goal is simple, private, cross-device file access with minimal infrastructure overhead. It is less suitable when the organisation needs advanced document governance, rich collaboration controls, or a full content-management platform with detailed audit and workflow features.

The trade-off is convenience versus granularity. A lightweight folder share is easy to adopt, but that simplicity means the surrounding governance has to carry more weight, especially for naming conventions, folder ownership, and deciding which data belongs in the shared location at all.

As a result, Taildrive is best understood as a pragmatic access layer for files inside a controlled network, not as a substitute for broader records management or enterprise content governance.

Related resources from NHI Mgmt Group

• What is the difference between Taildrop and Taildrive for Chromebook file sharing?