| Core |
|---|
| End-to-end encryption | File names and contents are stored encrypted; the keys stay on your devices. | Available |
|---|
| Verified reads | Every read is checked: correct content or an explicit error, never damaged data. | Available |
|---|
| History and trash | Every save is a version, deleted files wait in the trash, and concurrent edits keep both versions. | Available |
|---|
| Fetch on demand | A device can keep only what it uses and fetch the rest when opened; pinned folders work offline. | Available |
|---|
| Large and small files | Only changed blocks are uploaded, small files are bundled, and interrupted transfers resume. | Available |
|---|
| Copy locations | See which devices and storage hold a copy of each file before retiring a disk. | Available |
|---|
| Protected deletion | No single device can delete from storage, so a mistake or ransomware cannot remove your copies. | Available |
|---|
| Access record | Who touched which file, when, on which device; stored encrypted and never editable. | Available |
|---|
| Device management | Add a device by confirming on an old one, revoke a lost one, recover with the recovery key. | Available |
|---|
| Shared libraries | Family or team devices join one library and work on the same files. | Available |
|---|
| Export any time | Every library carries a format description and a stand-alone recovery script, and exports to a plain folder. | Available |
|---|
| People and roles | Each person joins with their own devices as read-write, read-only or admin; removing a person revokes all their devices. | Planned |
|---|
| Scale acceptance | A million files, 1 TB, a 100 GB file and ten devices, measured against the published budget. | Planned |
|---|
| File-system metadata | Permissions, owners, xattrs, ACLs and hard links are not preserved. | Not planned |
|---|
| Sync and storage |
|---|
| Automatic sync | Devices keep each other up to date through storage, and need not be online at the same time. | Available |
|---|
| Direct device-to-device sync | Two devices on the same network, or through a relay, sync directly with no storage in between. | Available |
|---|
| Local disk, NAS and cloud-drive folders as storage | Any folder can be a store: a local disk, a NAS share or the sync folder of a cloud drive. | Available |
|---|
| S3 storage | Any S3-compatible object storage works as a store. | Available |
|---|
| WebDAV storage | A WebDAV server works as a store. | Available |
|---|
| Cloud drives by API | OneDrive, Dropbox and Google Drive without their desktop clients. | Planned |
|---|
| Storage across several disks | One store spread over several disks, each file whole on as many of them as you choose. | Planned |
|---|
| A trusted server | Stores and relays only ever see ciphertext. | Not planned |
|---|
| Command line and mount |
|---|
| Command line | Everything is available from the cipherfs command: vaults, files, stores, devices, history, trash, export and mount. | Available |
|---|
| Mounted disk on macOS and Linux | The library appears as a disk in Finder or the file manager, with content fetched when opened. | Available |
|---|
| Windows | The command line and libraries work; there is no mounted disk, and transparent access will come through Windows Cloud Files. | In progress |
|---|
| A Windows file-system driver | No WinFsp driver and no WebDAV service; Windows transparent access is Cloud Files only. | Not planned |
|---|
| Desktop app |
|---|
| Desktop app | The desktop app runs; its management panels, native uploads and downloads and vault selection are being completed. | In progress |
|---|
| Desktop integration | System file providers, tray, autostart, biometric unlock, installers and updates. | Planned |
|---|
| Phones |
|---|
| Phone apps | Android and iOS apps that hold part of the library and fetch on demand. | Planned |
|---|
| Servers and applications |
|---|
| Server service | One process holds a vault on a server, unlocks without a person present and puts the keys away when idle. | Available |
|---|
| HTTP API | A local HTTP/JSON API with exact write receipts and streaming reads and writes. | Available |
|---|
| S3 endpoint for applications | An application that already speaks S3 reads and writes through CipherFS without touching the keys. | Available |
|---|
| Libraries and bindings |
|---|
| Rust library | Rust applications use the vault directly, with streaming reads and writes and background sync. | Available |
|---|
| C, Python and Go bindings | The same operations from C, Python and Go: files, byte ranges, streaming, recovery keys, pins, stores, devices and sync. | Available |
|---|