Exaba + Rclone

Exaba object storage, ready for rclone

Exaba is S3-compatible object storage that runs on your own hardware, from a single node to clustered petabytes. It’s designed to be operated by MSPs and Data Centers, with no egress or API charges. Rclone has an Exaba provider built in, so connecting the two takes a few lines of config.

Getting started

Setting it up

Add an Exaba remote to ~/.config/rclone/rclone.conf:

[exaba]
type = s3
provider = Exaba
endpoint = https://your-exaba-endpoint
access_key_id = your-access-key
secret_access_key = your-secret-key
acl = private

Leave region blank, because Exaba doesn’t need one. Your access key and secret key come from Exaba IAM. Then rclone lsd exaba: should list your buckets.

Our documentation covers sync and mount examples, Object Lock and performance tuning. The official rclone provider options are documented at rclone.org/s3/#exaba.

Better together

Built in, not bolted on

Rclone is one of the more reliable ways to move data between storage systems, and its S3 backend ships with an Exaba provider. There’s no fork to install and no custom build. Set the provider, add your endpoint, and you’re connected.

Exaba Logo
Rclone logo
Storage you run, priced so you can actually use it
About Exaba

Storage you run, priced so you can actually use it

  • No egress or API charges

    Under $2 per TB stored, flat. Rclone’s API calls and re-reads cost nothing, so verify as often as you like.

  • Multi-tenant from the start

    Customer isolation, per-tenant billing and white labelling, built in rather than bolted on later.

  • Immutable when it matters

    Object Lock retention and Legal Hold, with erasure coding underneath and encryption in transit and at rest.

More on how it’s built in scale-ready architecture and immutability.

Run Exaba on your own machine first
Try it locally

Run Exaba on your own machine first

There’s a Docker image if you want to see how Exaba behaves before committing any hardware to it.

docker pull exaba/exaba

One command gives you an S3 endpoint on port 9000 and a management interface on port 9006, and you can point rclone straight at it. Mount a volume at /data if you want the storage to survive the container being deleted.

This build is pre-release and the on-disk format still changes between versions, so treat it as somewhere to test against rather than somewhere to keep real backups. The full run command, along with cluster and high-availability setups, is on Docker Hub.


Nick Craig-Wood

Exaba has delivered rock solid software developed by passionate and knowledgeable people

Nick Craig-Wood

CEO, Rclone