All help articles

Object storage

Object storage keeps files in buckets, reached with the S3 API. Use it for backups, media and anything else you'd keep in Amazon S3. Any S3 tool or library works with it: the AWS CLI, rclone, restic, s3cmd and the AWS SDKs.

Getting it

An organization subscribes to object storage on your account page. Pick a plan under Object storage → Get object storage. You need to be an owner of the organization, or handle its billing.

Each plan sets how much you can keep and how many buckets you can have:

PlanStorageBuckets
Starter250 GB10
Standard1 TB100
Large5 TB1,000

The space counts every object and every part of an upload not finished yet.

Buckets and access keys

On your account page, Object storage shows each of your organizations' storage accounts. The organization's owners manage them. On plans with team access (Standard and Large), its admins can too.

Connecting

The Object storage section shows the endpoint and region. Use path-style addressing: the bucket goes in the path, https://ENDPOINT/BUCKET/KEY, not in the host name.

The AWS CLI, with the endpoint shown on your page:

aws configure set aws_access_key_id ZK...
aws configure set aws_secret_access_key ...
aws --endpoint-url https://s3.example.com s3 ls
aws --endpoint-url https://s3.example.com s3 cp backup.tar.gz s3://my-bucket/

rclone (rclone config, or in rclone.conf):

[zappocity]
type = s3
provider = Other
access_key_id = ZK...
secret_access_key = ...
endpoint = https://s3.example.com
force_path_style = true

In the AWS SDKs, set the endpoint and turn on path style (for example UsePathStyle: true in Go, forcePathStyle: true in JavaScript, addressing_style: path in boto3).

What works

The largest object is 5 GiB, whether in one upload or in parts. Every request is signed: there are no public buckets yet, so share objects with presigned URLs. Versioning, bucket policies, lifecycle rules and CORS are not offered yet. Tools that ask for them get a "not implemented" answer.

Objects are served so a browser can't run them as a page on our host. An HTML file is shown sandboxed, without its scripts.

Where objects are kept

Objects are kept on our servers. Those not written for a while may move to a storage provider we use (Backblaze B2). Each is encrypted on our servers before it goes, with a key of its own that only we hold, so the provider keeps only scrambled bytes it can't read or change unseen. Nothing changes for you: they're read, listed, copied and removed the same way, and only the first byte may take a moment longer.

If something goes wrong

See also the FAQ.