Home › AeroCrypt

AeroCrypt

Profile-bound encryption with explicit format and metadata boundaries.

Zero-knowledge, on any cloud

AeroCrypt encrypts file content and names locally before a bound profile uploads them. The remote still sees ciphertext sizes, object counts and access timing; encryption does not hide all metadata or make the underlying transport irrelevant.

Bind once, decrypt everywhere

Bind a supported encrypted store to a saved profile so supported GUI, CLI, MCP and background operations use the overlay. Unlocking requirements depend on the credential/vault mode. Connections made without the binding are ordinary connections; verify the active profile before writing.

Names and structure, hidden too

The native overlay encrypts content and filenames with its documented store layout. Providers can still observe encrypted sizes, counts and access patterns. Headed and headerless stores manage metadata differently; keep required local metadata when backing up or migrating a store.

A crypt overlay listing decrypted names locally while the remote shows encrypted filenames

AeroCrypt writing files in rclone crypt format and opening a Cryptomator vault

Distinct Interoperability Formats

AeroFTP has a distinct rclone crypt interoperability mode. Existing Cryptomator vaults use their own access workflow. AeroCrypt native stores, rclone crypt remotes and Cryptomator vaults are not interchangeable formats. Follow the format-specific import, export and compatibility guidance.

Verify the Encryption Binding

An active profile binding routes supported operations through the provider overlay. This protection applies to that binding, not to every client with access to the same server. Review the profile, unlock state and compatibility limits before writing.

The crypt overlay enforced across CLI, GUI, MCP and sync surfaces

Free & open source

Own your keys, use any cloud

Download AeroFTP and turn your first remote into zero-knowledge storage.

Download Now View on GitHub

AeroFTP

Theme