BucketPilot Cloud
Storage we run for you: create a bucket in a minute, in the US, Europe or Asia Pacific, with no download, request or transfer fees, and use it like any other bucket.
What it is
Most of what BucketPilot does happens in storage you already own. BucketPilot Cloud is for when you would rather not own the bucket: object storage we run, created from the console, billed on your BucketPilot invoice, with nothing to set up and no keys to keep.
A Cloud bucket behaves like any other bucket in your workspace — browse it, search it, back up to it, migrate into it, point BucketPilot Drop at it, share drop links to it — and it keeps every version of a file when versioning is on.
Creating one
- 1.Open Buckets & Servers and press Create Bucket.
- 2.Choose BucketPilot Cloud, pick a region — US East (N. Virginia), US West (Oregon), EU (Amsterdam), EU (Frankfurt), EU (London) or Asia Pacific (Singapore) — and a name.
- 3.The price per GB-month is shown before you confirm. Press Create; the bucket is ready in about a minute.
A bucket can also be created from inside a backup job's form, so a new backup and its destination are set up in one go. A card on file is needed before the first Cloud bucket is created; the Billing page is where it goes.
How it is billed
- •Storage is billed per GB-month, measured every few hours from what the bucket holds, and appears as a line on your BucketPilot invoice.
- •There are no download, request or transfer fees: restoring, downloading or serving from a Cloud bucket costs nothing extra.
- •Every file counts as at least 4 KiB, so an archive of very small files is billed a little above its byte count. The Create panel says so.
- •Storage is billed for at least 90 days from the day a bucket is created. Deleting a bucket stops your billing at removal and keeps the bucket restorable until its term ends, in case the delete was a mistake.
The Billing page shows the current month's Cloud usage and what it will cost.
Where your data lives
A Cloud bucket lives in the region you chose and nowhere else; regions are not replicated to each other. For a second copy in a second region, create a bucket there and set up a backup job between the two — it runs on a schedule like any other backup. Your data is yours: it is never read for any purpose other than the operations you ask for.