RaiDrive connects cloud storage, a NAS, or a remote file protocol to the operating system as a mounted drive. Files then appear in File Explorer or the Linux file manager, so an ordinary desktop program can open a remote document without a separate download screen. RaiDrive works with personal cloud accounts, business storage, object stores, WebDAV, SFTP, and FTP. The mounted drive remains a view of remote data. It does not create a complete synchronized folder or a backup merely because it has a drive letter.
Mount, do not sync
A sync client normally keeps a selected folder on the computer and reconciles it with the cloud. RaiDrive reads remote paths on demand and writes changes back through the connection. This saves local space when a storage account contains far more data than the computer can hold. It also makes network quality part of ordinary file work.
Opening a large video, searching a folder, or generating thumbnails can trigger remote reads. A slow connection can make a familiar desktop program appear frozen. If the service disconnects during a save, the local application may report an error or leave a temporary copy. RaiDrive cannot complete a remote write after the account, network, or server has stopped accepting it.
Sign in by browser
RaiDrive sends supported account authentication through the chosen web browser. The storage service handles the sign-in and permission screen, then returns authority to the mounted connection. This avoids entering a cloud password directly into every file action. It also means a blocked popup, the wrong browser profile, or an expired account session can prevent the drive from mounting.
Check the account name and requested scope before approval. A personal and a work account can share similar addresses while exposing completely different drives. Revoking access at the storage provider breaks the mount even when RaiDrive still retains its saved connection entry.
Cache is temporary
RaiDrive keeps local cache data so repeated reads and pending writes do not always start from zero. Read and write retention use separate timing controls, and the cache directory can live on a chosen local disk. Cache encryption protects those temporary files at rest.
The cache is working storage, not an archive. Clearing it, uninstalling RaiDrive, or losing the local disk does not delete the cloud original. The reverse matters too: a cached copy does not guarantee that the newest remote revision is safely preserved. Important material still needs an independent backup with a tested restore path.
Locks need support
RaiDrive can coordinate file locks with compatible office programs and storage behavior. A lock helps stop two editors from saving over the same remote document. It cannot force every protocol, server, or application to honor the same convention. An editor that writes by replacing the entire file may behave differently from one that updates it in place.
Before several people edit a shared folder, test a disposable document from two machines. Watch what happens when both users save, when one connection drops, and when the remote service creates conflict copies. RaiDrive carries the operations; the storage backend decides many naming, locking, and revision rules.
Public or private
A public local-disk mount can participate in Windows sharing and may be accessible from another account or computer after sharing permissions are set. A private mount blocks that route. RaiDrive documents an important tradeoff: some Windows applications cannot see a private local-disk mount at all.
The local-disk and network-drive choices also affect how programs recognize the path. Media libraries, backup programs, or catalog tools may accept one type and ignore the other. Choose privacy first for a single-user connection, then change the mount type only after testing the exact application that needs access. Making a drive public for compatibility widens its local exposure, so Windows share permissions must match the intended users.
