MountWindows | macOS | Linux
Access nuFS as a local filesystem. Open and edit files with your existing applications, shell tools and coding agents. File content is fetched on demand.
- On-demand reads
- Versioned files
Access files on demand across apps and AI agents, without downloading or storing them locally.
Mount a drive or use the terminal. AI agents can also work directly with your files using their existing tools. Every interface works with the same files, version history and access permissions.
Access nuFS as a local filesystem. Open and edit files with your existing applications, shell tools and coding agents. File content is fetched on demand.
Work with files, version history and access controls through typed clients in your application.
Read, write, search and restore files from the terminal or an automation script.
Read byte ranges, make partial edits and manage versioned files over HTTP.
Use existing S3 clients for supported listing, upload and download operations.
Turn on file history when you want to keep earlier versions. Compare a revised document with its original. Retrieve the dataset used for an earlier run. Restore a file after an unwanted change. Retained versions remain readable even as work continues.
project-notes.mdEach committed file version has its own identity. Read or download its retained bytes even after the current file changes. Clear history whenever you need to free storage.
Guard a write with its expected version. If another client has committed a change, the stale update is rejected so you can inspect the new state.
Restoring old contents creates a new current version. Access permissions and retention still govern historical reads.
Keep your project's footage and audio on nuFS, and work from the mounted drive in your editing software. Your files are available without downloading the whole project first.
Open scene-01.mp4 in your editing software just as you would a local file. nuFS supplies the file content as the software reads it.
nuFS responds to your editing software's requests in the background. The highlighted area shows the part being read, while the complete file stays stored in nufs.
Files saved to nuFS remain available after you close your terminal, end an agent session or restart a client. Return to the same drive later, or open its files from another authorized tool.
Write notes and results, then finish your task.
Save confirmedresearch/notes.mdSavedresults.csvSavedOpen the same saved files and continue with your own tools.
Same driveBefore ending your session, wait for the save to be confirmed. Edits still waiting to upload are not yet saved to nufs.
Keep your team's files together in a shared drive. Invite people to work on the same files, and manage their access for that drive.
People in this drive
Keep project files together in a drive. Create another drive for a different team or project.
Invite teammates to your drive. Everyone works with the shared project files through their own account and tools.
Send a file link or request an upload when someone only needs to send or receive files, without adding them to the drive.
nuFS is a persistent, versioned filesystem. People can use a mounted drive; applications and agents can access the same files through the CLI, REST API, official SDKs and supported S3 operations.
Give your agent a mounted directory or a scoped nuFS credential. It can read and write using its existing filesystem tools, the CLI or an SDK. Your agent supplies the model and interpretation; nuFS supplies authorized, persistent files.
The Linux and Windows desktop apps include the command line and mounted drive. Python, TypeScript, Go and Rust SDKs and the REST and S3-compatible APIs provide access from code. See Downloads for platform availability.
No. You can use S3-compatible tools with nuFS, without an AWS account. See the S3 documentation for supported operations and connection examples.
A sync folder usually centers on copies on individual machines. An object API usually centers on replacing whole objects. nuFS provides a mounted filesystem plus file APIs, selected-byte edits, immutable versions over the same stored files. Its S3 interface supports documented object operations; the SDKs expose the richer file operations.
Mount a drive to open and edit files using your existing applications. Compatibility depends on the filesystem features an application needs; installing and running applications from the drive is not currently supported.
Python, TypeScript, Go and Rust SDKs expose files, versioned mutations, history, drive plans and access controls. The documentation includes installation steps, examples and a method reference for each language.
File content can be retrieved on demand and retained in a bounded local cache. A range read can request part of a file. An application that reads an entire file will still transfer that file.
API and SDK mutations can require an expected version. If another change has committed, a stale guarded update is rejected. The application can then inspect the newer version and decide how to proceed.
Yes. Retained committed versions can be read or downloaded. Restoration creates a new current version; it does not rewrite the earlier version. Access permissions and retention still apply.
Yes. A plan provides your own drive. You can also accept invitations to shared drives without buying a plan. Each drive’s owner manages its storage and seats; ownership stays with that account.
Yes. An expiring, revocable public link grants access to a particular saved file version. Upload requests let recipients send new files into one destination without browsing the drive.
The desktop app keeps pending changes locally so they can resume after a restart. A file is saved to nuFS once its upload is confirmed. You can follow pending saves in the transfer panel.
You need a connection to load uncached files and save changes to nufs. Downloaded data can remain in the local cache, and pending edits are kept locally until they finish uploading.
Your saved files are stored on nuFS, independently of your device. The desktop app keeps a local cache of downloaded data, which you can clear in Settings without deleting your cloud files.