Create and mount virtual drives from cloud data in code.
Create and mount virtual drives in code from cloud storage, remote servers, and network file systems.
USE CASES
What you can build with CBFS Cloud
Mount SFTP, Amazon S3, S3-compatible, WebDAV, OneDrive, Google Drive, Azure, SharePoint, or NFS storage as a local drive, defined in code.
Cloud storage access without a sync client
Give an app direct file access to Amazon S3, Azure, OneDrive, Google Drive, SharePoint, and more. No separate sync utility needed on the user's machine.
SFTP, WebDAV, and NFS as local drives
Mount SFTP, WebDAV, and NFS servers as ordinary drives so existing file-based tools can read and write remote data with zero protocol-specific code.
HOW IT WORKS
Mount remote storage as a drive. All in code.
CBFS Cloud connects to SFTP, Amazon S3 and S3-compatible storage, WebDAV, OneDrive, Google Drive, Azure, SharePoint, or NFS using a connection string defined in your app. No mounting tool, no end-user setup.
Once connected, the remote storage shows up as a normal local drive. Apps and scripts read and write it through standard file APIs. CBFS Cloud handles the protocol work underneath.
Built-in caching cuts down repeat network calls, so common file operations stay fast even though the data lives remotely.
START BUILDING
Documentation & Resources
Online Documentation
Full API reference for all components and languages, with code examples for every method and event.
Read now
Knowledge Base
Troubleshooting guides, how-tos, and answers to common implementation questions.
Read nowGetting Started With CBFS Cloud
A step-by-step guide for mounting cloud storage services and remote file servers as virtual local drives.
Read nowSample Applications
Demonstrates how to use the CBCloudDrive component to connect to an Azure Blob Storage account.
Demonstrates how to use the CBCloudDrive component to connect to an Azure Files storage service.
Demonstrates how to use the CBCloudDrive component to connect to a Google Drive account.
Demonstrates how to use the CBCloudDrive component to connect to an NFS server.
Demonstrates how to use the CBCloudDrive component to connect to a Microsoft OneDrive account.
Demonstrates how to use the CBCloudDrive component to connect to an S3-compatible storage service.
Demonstrates how to use the CBCloudDrive component to connect to an SFTP server.
FEATURES
Comprehensive Features for Full Control
Mount Remote Storage as a Local Drive
Mount Remote Storage as a Local Drive
Expose remote storage systems such as SFTP servers, Amazon S3 and S3-compatible services, WebDAV endpoints, OneDrive, Google Drive, Azure Storage (Files and Blobs), SharePoint, and NFS as local drives or mounted folders. Interact with remote files just like working with files on disk.
Intelligent Caching for Efficiency
Optimize performance with built-in caching mechanisms that reduce redundant network operations and improve responsiveness. Configure caching behavior to balance performance, consistency, and resource usage based on application requirements.
Eliminate Upload and Download Workflows
Access, edit, and manage remote files directly without creating local copies. File operations are handled transparently, reducing friction and simplifying application logic.
Create and Mount Drives in Code
Define connections and mount virtual drives directly within your application. No external tools or user configuration required.
Expose Remote Data Through Standard File APIs
Access remote storage using standard file operations. Applications and scripts can work with external data without requiring custom integration logic.
Automate Mounting and Lifecycle Management
Control when and how drives are mounted within your application. Automatically initialize connections, manage sessions, and cleanly unmount resources without relying on end-user configuration.
Support for Secure Remote Protocols
Connect to secure back-end systems including SFTP and cloud storage providers. Leverage existing authentication methods and secure transport mechanisms for safe data access.
Intuitive Component API
Abstract away the complexity of remote protocols and filesystem behavior behind a simple component interface. Focus on your application logic instead of low-level implementation details.
PLATFORMS
Supported Languages & Operating Systems
Every edition ships with a pre-built driver, sample applications, and full documentation. 30-day fully functional trial for all editions.
CBFS Cloud supports .NET Framework 4.0+ and .NET 5 through .NET 10, with full Visual Studio integration and C# sample applications.
DocumentationFAQ
Frequently Asked Questions
Common questions about licensing, integration, and deployment.
What is CBFS Cloud?
CBFS Cloud is a developer library for mounting remote storage, SFTP, Amazon S3, WebDAV, OneDrive, Google Drive, Azure Blob Storage, Azure Files, SharePoint, or NFS, as a local drive. Everything is set up in application code: no kernel driver work, no manual setup for end users. Drives mount through a connection string your app defines.
Once mounted, remote data works like any local file through standard file system APIs. Built-in caching cuts down on network round-trips to keep things responsive.
How do I mount cloud storage like Amazon S3 or SharePoint as a local drive without writing a kernel driver?
CBFS Cloud handles the driver layer for you. Define a connection to the backend: SFTP, Amazon S3, S3-compatible storage, WebDAV, OneDrive, Google Drive, Azure, SharePoint, or NFS, with a connection string, and CBFS Cloud mounts the drive. No mounting utility, no manual configuration, no kernel code.
Available in .NET, C++, Java, Python, Go, Delphi, Rust, and Qt. Your app controls when drives mount and unmount, and the protocol details stay out of your way.
Which cloud and remote storage platforms does CBFS Cloud support?
SFTP servers, Amazon S3 and S3-compatible storage, WebDAV servers, Microsoft OneDrive, Google Drive, Azure Blob Storage, Azure Files, Microsoft SharePoint, and NFS servers. Every backend mounts through the same API.
How does CBFS Cloud differ from CBFS Connect?
CBFS Connect is general-purpose: you write callback handlers that define the filesystem yourself, backed by anything your app can reach, including custom or proprietary backends. CBFS Cloud is narrower. It ships pre-built connections to a specific set of cloud and remote storage platforms, mounted with a connection string instead of custom callback code.
Use CBFS Connect for custom or proprietary backends, or when you need fine-grained control over filesystem behavior. Use CBFS Cloud when your backend is already on the supported list and a connection-string mount is enough.
How does CBFS Cloud differ from CBFS Sync?
CBFS Cloud mounts remote storage as a drive. Files don't need to exist locally; CBFS Cloud serves content on demand, like a network drive. CBFS Sync keeps a real local copy synced with a remote source, using OS-native sync APIs (Cloud Filter API, File Provider, FUSE) and native sync icons.
Use CBFS Cloud for on-demand access with no full local copy. Use CBFS Sync when you need offline access and two-way sync.
What languages and platforms does CBFS Cloud support?
CBFS Cloud currently ships as a .NET edition. Support for additional languages and platforms are planned for upcoming releases.
Start with a free 30-day trial
Fully functional, no feature restrictions. Free technical support from day one. No credit card required.
TRUSTED BY DEVELOPERS WORLDWIDE
Built for production. Proven at scale.
Components and drivers from Callback Technologies have been shipping in commercial products for over two decades, from single-developer tools to enterprise software deployed at Fortune 500 companies.
I bought your components because of convenient, easy to learn API, plus there is really no match (literally!) on the market. It provides neat functional capabilities. I will recommend it to all my peers working on complex storage solutions.
Kudos to you for such a great product! My programmers like it enormously. We were able to plan and develop a complex storage and data management application within the allocated timeframe. Thank you for giving us individual support from the beginning.