Skip to main content
BlobRouter v0.1 · Last updated: August 2026 · Architecture version: 2.0
BlobRouter talks to providers through one S3-compatible adapter (AWS SDK v3). Only endpoint and credentials differ.

Supported providers (v1)

You can connect up to three providers (one bucket per provider per customer in v1).

Two ways credentials appear

Scanner (AWS only)

Read-only IAM role assumption for the free audit. See Connect AWS.

Router (S3 / R2 / B2)

Long-lived access keys you paste in the dashboard. Encrypted with AES-256-GCM before storage. Used only to mint presigned URLs — uploads and downloads go client ↔ provider.

Connecting for routing

Object access

All objects are private. Access is only via time-limited presigned URLs from:
  • storage.get(fileId) / GET /v1/file/:id
  • Upload init returns a short-lived PUT URL (~1 hour)

What BlobRouter stores about files

Metadata only: file id, name, size, content type, chosen provider, routing decision, savings estimate, status. Never object bytes.