$ cd ../services

Object storage

Pixel Bucket

Buckets in one API call.

Create a bucket, drop objects in, and flip it between public and private without redeploying anything. Pixel Bucket gives developers and designers a plain HTTP API for files of any shape, with instant mode switching and per-bucket access keys.

$ cloudeee bucket create assets --private

~/services/pixel-bucket
PUBLIC

$ cloudeee pixel-bucket --features

What you get.

  • F-01

    Instant public or private

    Toggle a bucket between public and private in one request. The change is live right away, with no cache to wait out and no redeploy.

  • F-02

    A small, predictable API

    PUT, GET, DELETE and LIST over plain HTTP. If you can call curl, you can store files, and the same calls work from any language.

  • F-03

    Scoped access keys

    Mint read-only, write-only or full-access keys for a single bucket, so a build script never holds more power than it needs.

  • F-04

    Multipart uploads

    Large files are split into parts, uploaded in parallel and resumed from the last good part if the connection drops.

  • F-05

    Metadata and tags

    Attach key-value metadata to any object and query by prefix, so a bucket stays organized as it grows.

  • F-06

    Lifecycle rules

    Expire temporary uploads or move old objects to cheaper storage on a schedule you define once and forget.

$ cloudeee pixel-bucket --how

Four steps, zero fuss.

  1. Step 01

    Create a bucket

    Name it, pick a primary region and choose private or public. Your bucket gets its own endpoint immediately.

  2. Step 02

    Upload objects

    Send files with the API, the CLI or the dashboard. Each object is encrypted in transit and at rest on arrival.

  3. Step 03

    Set the mode

    Keep it private behind keys, hand out signed URLs for a single file, or switch the whole bucket to public.

  4. Step 04

    Serve or share

    Link files from your site and apps, or pair the bucket with Edge Cache Drop to deliver it worldwide.

$ cat specs.txt

The specs.

~/services/pixel-bucket/specs.txt
Pixel Bucket specifications
Max object size1 TB per object (multipart)
Access modesPrivate, public, signed URL
AuthenticationScoped bucket keys
EncryptionIn transit and at rest
ListingPrefix and delimiter queries
PlacementPrimary region chosen per bucket

$ man pixel-bucket

Quick answers.

Q01Can I change a bucket from private to public later?
> Yes. The mode is a single setting you can change at any time, and the change applies immediately. Switch it back just as quickly if you published something by mistake.
Q02How do I give a contractor temporary access?
> Create a scoped key limited to one bucket and one permission, or generate a signed URL for a single file. Delete the key or let the URL expire when the work is done.
Q03Do I need the CLI to use Pixel Bucket?
> No. Everything is available over the HTTP API, the dashboard and the CLI, so use whichever fits your workflow.

$ cloudeee signup --free

Start with Pixel Bucket.

Create a free account, get 20 GB of encrypted storage and try it in minutes.