Buckets

A bucket is a named container for your objects. You create one in the dashboard, and the platform provisions it, assigns its credentials, and books its capacity from the regional pool.

Naming

You choose a short name; the platform prefixes it with your tenant id, so the full bucket name looks like t1a2b3c4-<name> (for example t1a2b3c4-media). The prefix keeps your buckets isolated from every other tenant's.

The name portion you pick follows standard S3 rules: 3 to 63 characters, lowercase letters, numbers, and hyphens, starting and ending with a letter or number. No uppercase, underscores, or spaces.

Capacity and quota

You set a capacity in GB when you create the bucket. That capacity is both:

• your quota: writes that would push stored data past it are rejected (see limits and errors), and
• your billing basis: you pay $0.04 per GB-month on the capacity you booked, whether or not it is full (see billing).

Pick a capacity that fits your data plus some headroom. If you need more room later, resize the bucket via the Buckets API or open a support ticket.

Versioning

Versioning is an optional toggle, set when you create the bucket and changeable later via the Buckets API. When it ships:

• On: overwriting or deleting an object keeps the previous versions, so you can recover an earlier copy. Every retained version counts toward your booked capacity.
• Off (the default): an overwrite replaces the object, and a delete removes it, with no earlier copy kept.

Usage

The bucket's page in the dashboard shows how many objects it holds and how much of your booked capacity is used, so you can see when to free space or ask for more.

Deleting a bucket

Before you delete a bucket, make sure you no longer need anything in it, or copy the objects elsewhere first (for example with rclone copy or aws s3 sync to another bucket). Deleting the bucket also retires its credentials.