Backblaze B2 through Squiid

What Backblaze B2 is

Backblaze B2 is cloud object storage sold on price. It exposes both a native API and an S3-compatible endpoint, supports object lock for immutable backups, lifecycle rules for expiry, and server-side encryption, and its bandwidth alliance means egress to partner networks such as Cloudflare and Fastly is free rather than metered per gigabyte. Large files are uploaded in parts and reassembled server side, and versioning keeps previous copies of an object until a lifecycle rule removes them.

In an AI-coded project B2 is usually the archive tier rather than the hot path. Database backups, raw uploads kept for compliance, original media before processing, model checkpoints and logs all cost real money on premium object storage and very little here. Because it is S3-compatible, moving a bucket between providers is generally a configuration change and a sync job rather than a rewrite. For a team already using Cloudflare in front of storage, the free partner egress is what makes the total cost hard to beat.

Why connect it through Squiid

Backblaze B2 is on the Squiid roadmap. When it lands, Squiid will provision the bucket, hold the application key id and secret, and route access through https://api.squiid.io/v1/backblaze-b2/... with Authorization: Bearer $SQUIID_API_KEY, with S3-compatible clients working by endpoint swap (gateway convention). Storage, downloads and transactions will bill at Backblaze's listed price on your single Squiid invoice with no markup, and the long-lived application key that can read and delete every object stays out of your environment files. Backups are also the case where a service being on a separate account from your production stack is a feature rather than an inconvenience.

• One account, one key, one bill, one dashboard. Backblaze B2 sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Backblaze B2 credentials. Your code carries SQUIID_API_KEY, so B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY, B2_BUCKET, S3_ENDPOINT never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Backblaze B2 costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned B2 bucket with keys held by Squiid
• S3-compatible API and tooling
• Free egress to partner CDNs
• Object lock and lifecycle rules for backups
• Backblaze list pricing, no markup

How to connect Backblaze B2

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces B2_APPLICATION_KEY_ID, B2_APPLICATION_KEY, B2_BUCKET, S3_ENDPOINT
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/backblaze-b2/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Backblaze charges per gigabyte stored per month plus download and transaction charges, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Backblaze B2 usage, with no markup and no per-request margin.

Backblaze B2 has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Backblaze B2 usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: files and configuration are copied into your own Backblaze B2 account; there is no account transfer. Squiid never owns your code, your schema or your domain, and the gateway speaks Backblaze B2's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Backblaze B2 through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Backblaze B2 usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.