Open source · Rust · Python

One URL for every object store.

Copy, move, stream and sign objects across AWS S3, Google Cloud Storage, Azure Blob Storage and local disks. Turn on encryption and the provider stores only ciphertext.

Scheme decides the backend
s3://bucket/key→AWS S3 and S3-compatible stores
gs://bucket/key→Google Cloud Storage
az://container/key→Azure Blob Storage
https://host/path→HTTP and HTTPS
~/path/file→Local filesystem
Works with AWS S3GarageSeaweedFSGoogle Cloud StorageAzure Blob StorageHTTP(S)Local Filesystem
osc-gui with two panels side by side, each with a connection selector, an address bar and a file list
Two panels, any two connections. Copy from a bucket to a laptop folder, or across clouds, with the key and TLS state of each panel in view. Archived objects are greyed out until they are restored.
Routes

Move data between clouds without changing tools.

One client reads and writes every backend. The same calls work whichever store sits behind the URL, so a migration is a loop, not a rewrite.

URLBackendNotes
s3://bucket/keyAWS S3 and S3-compatible storesAWS profiles and SSO, plus Garage or SeaweedFS endpoints
gs:// or gcs://Google Cloud StorageApplication default credentials and service accounts
az://, wasb(s)://, abfs(s)://Azure Blob StorageContainer and key in the path
http:// and https://HTTP and HTTPSAny web endpoint, addressed by URL
file:///path, /path, ~/pathLocal filesystemThe same API for a working copy on disk
Three ways in

Point and click, script it, or build on it.

Pick the surface that fits your work. Each one reaches the same stores with the same encryption.

osc-gui · desktop

Browse and copy in two panels.

  • Two panels, any pair of connectionsCopy, move, rename and delete objects and whole folders within a panel or between clouds.
  • Your connections are already thereAWS profiles and SSO sessions, Google credentials and Azure CLI logins are found at startup.
  • Security at a glanceA key icon for encryption, and a shield, warning or dot for each panel's TLS state.
  • Storage class in viewArchived objects are greyed out and restoring ones are marked.
  • Installs like an appA macOS disk image, a .deb for Debian and Ubuntu, an .rpm for Fedora and RHEL.
osc · command line

The same commands on every provider.

  • One command set everywhereput, get, ls, cp, mv, rm, exists and mb on s3://, gs://, az://, HTTP and local paths.
  • Copy between clouds in one stepSource and destination can be different providers.
  • Large files through a pipeget-stream writes to stdout in bounded memory.
  • Pre-signed linksosc sign makes download and upload URLs, with length and type checks on S3 uploads.
  • Encryption and profiles on the flag--keyring encrypts and decrypts; --profile picks an AWS profile.
Rust · Python

One API in your code.

  • One API, many backendsThe URL scheme picks the backend. put, get and list work everywhere.
  • Streams without holding the fileget_stream feeds put_stream, so large objects never sit in memory whole.
  • Cross-provider copy and moveOne client moves an object from S3 to GCS to Azure.
  • Encryption you can auditAuthenticated encryption, self-reloading keyrings and key rotation. Python never sees the key bytes.
  • Install from the registrypip for Python wheels, or a Cargo dependency. Leave out the CLI with default-features = false.
Encryption

Encrypted before it leaves your machine.

Keys stay with you, and the provider stores only ciphertext. Rotation adds the new key first, then moves objects over.

  • Authenticated encryptionEvery object is checked before it is returned. A tampered object fails.
  • Keyrings that reload themselvesAdd or retire a key without restarting the app or the service.
  • Refuse plaintext--require-encryption makes put, get and sign fail when no keyring is set.
  • Keys from a file or a commandA keyring can come from a command, so it never touches disk.
FAQ

Questions before you install.

Is encryption on by default?

No. Encryption needs a keyring. Create one with osc keyring new, or point the client at a keyring file or command. Without one, objects are stored as sent.

Which platforms are supported?

The CLI and Python wheels cover Linux on x86_64 and aarch64, macOS on Apple silicon, and Windows on x86_64. The GUI runs on macOS (Apple silicon) and on Linux with a Wayland session; X11 is not supported.

Does it work with S3-compatible stores?

Yes. Any S3-compatible endpoint works through the s3:// scheme, including Garage and SeaweedFS.

Do pre-signed links keep working after my SSO session ends?

No. A link signed with temporary credentials stops working when that session ends, whatever expiry was requested.

Is the macOS app signed?

Not with an Apple Developer ID. On first launch, open System Settings, go to Privacy & Security, and choose Open Anyway.