Skip to main content
BlobRouter v0.1 · Last updated: September 2026 · Architecture version: 2.0
BlobRouter finds wasted cloud spend starting with storage. The product center of gravity is the Storage Decision Engine: a structured view of what to change, what to leave alone, and when to re-check — not a migration factory. The SDK and smart router keep optimizing new uploads after you choose to connect providers. They are optional next steps, not the entry point.

​
Two entry points

​
1. Free — AWS S3 storage audit

Connect a read-only IAM role → BlobRouter scans your buckets → you see waste, ranked recommendations, and (when available) a decision report from the Storage Decision Engine. Nothing changes until you approve it.

​
2. Paid — Continuous analysis (+ optional migrate / route)

Paid plans buy continuous analysis and re-evaluation of your storage estate — including monitor-style “do nothing until X” outcomes. Approving migrations and installing the smart router remain optional. See Plans & billing and Storage Decision Engine.

​
Two credential models

Never confuse these: Scanner credentials are never long-lived AWS access keys. Router credentials are decrypted only in Worker memory when generating presigned URLs.

​
Product flow

​
Invariants

  • No byte proxying — files go client → provider via presigned URLs
  • Client-owned storage — we never host object bytes
  • Scanner is read-only — zero write permissions on the audit role
  • No auto-remediation — migrations require explicit approval
  • Deterministic decisions in v1 — cost formula + decision engine rules, not opaque ML for dollars

​
Architecture sketch

See Architecture for upload, scan, and migration flows in detail, and Storage Decision Engine for what the audit report means.