Backblaze B2 vs DigitalOcean Spaces

Backblaze B2

$6.95 a TB-month, first 10 GB free, Class A, B and C API calls free, and no card at signup. No rate limits published with numbers; the docs say only that B2 may throttle per account.

DigitalOcean Spaces

Per-bucket access keys with read or read-write-delete grants, an 800 operations a second limit per bucket and a 99.9 per cent SLA are all published. The MCP server manages keys and CDN endpoints only, not objects, and the S3 reference documents no error codes. A payment method is required before any bucket is created.

Backblaze B2

1. Take the region from the key's S3 endpoint (the second label of s3.<region>.backblazeb2.com) and pass it as the SDK region
2. Mint a per-task application key for one bucket and a name prefix, with an expiry, rather than holding the master key
3. Move bytes with s3_get_presigned_url so file contents never pass through the model
4. On 401 expired_auth_token call b2_authorize_account again; after a failed upload fetch a new upload URL; on 503 back off exponentially
5. Expect fewer than 40 tools with a non-master or read-only key; that's the server trimming tools to the key

DigitalOcean Spaces

1. Set the endpoint to https://<region>.digitaloceanspaces.com and, in AWS SDKs other than Python's, set region to us-east-1 when creating a bucket
2. Ask for a limited access key with a Read or Read/Write/Delete grant on one bucket. A full access key can create, configure and delete every bucket
3. Do the object work through the S3 API. The MCP server and doctl cannot upload, list, move or delete files
4. Retry with exponential backoff on 503 Slow Down, and keep below 800 operations a second per bucket
5. Fetch presigned links from the origin host, not the CDN. The docs say presigned requests through the CDN are not cached and can double the bandwidth charge
6. Avoid many tiny objects. Each bills as at least 4 KiB on Standard and 128 KiB on Cold Storage, which also has a 30-day minimum