
BlobRouter
Optimize your AWS storage — without blindly moving it.
BlobRouter analyzes your S3 environment, finds storage waste, and shows what to change, what to keep, and why. Start with a free read-only audit.
Read-only · No application changes · No credit card
Connect your S3-compatible storage
Supported providers: AWS S3, Backblaze B2, Cloudflare R2.
The cheapest storage isn’t always the cheapest architecture.
S3 storage price is only one part of the equation. Moving data can introduce:
- Transfer costs
- Retrieval costs
- Latency
- Workload dependencies
- Operational complexity
- Compliance constraints
BlobRouter evaluates the decision, not just the storage price.
See how BlobRouter reasons about storage
Click a tab to see how the Storage Decision Engine breaks down a workload.
Storage Decision Engine
Decision Report
150 TB · AWS S3 · 120 days observed · scale band 4 · list pricing
Current / month
$8,798
Recommended / month
$3,783
Monthly opportunity
$5,015
29-day break-even · 35.9x ROI at 36 months · strategy custom-per-segment
Confidence
out of 100
Do not move
compute topologyA storage-price-only model would move this data to cheaper storage. The engine prices what happens after the move.
DO NOT MOVE — Model checkpoints (80 TB stays on aws-s3)
$4,381/ mo transfer penalty if moved
- Compute reading this data lives in aws-s3 (computeDependency: same_cloud, 95% of reads from in-cloud compute)
- Same-cloud reads are modeled as free; a cross-provider move bills every read at aws-s3 egress rates
- Data criticality high — kept on aws-s3 INTELLIGENT_TIERING rather than moved
Moving 80 TB to backblaze-b2 adds ~$4,381/mo in cross-provider transfer while compute stays in aws-s3. Current placement costs $2,186/mo in storage.
DO NOT MOVE — Training data (30 TB stays on aws-s3)
$984/ mo transfer penalty if moved
- Compute reading this data lives in aws-s3 (computeDependency: same_cloud, 80% of reads from in-cloud compute)
- Same-cloud reads are modeled as free; a cross-provider move bills every read at aws-s3 egress rates
- Data criticality critical — kept on aws-s3 GLACIER_INSTANT_RETRIEVAL rather than moved
Moving 30 TB to backblaze-b2 adds ~$984/mo in cross-provider transfer while compute stays in aws-s3. Current placement costs $342/mo in storage.
The demo uses a fully populated workload profile. Live audits currently start with observed S3 storage data and clearly label which figures are modeled assumptions rather than measured.
The real dashboard, not a mockup
This is an actual screenshot of the BlobRouter product UI, shown here with a seeded demo account so you can see it populated with real numbers instead of an empty state.

Not a $/GB calculator
Don’t optimize storage in isolation. A storage-price-only model would move everything to the cheapest tier — the Storage Decision Engine prices what happens after the move. Click a card — the report above switches tabs to show it live.
From S3 inventory to storage decisions
- 01
Connect AWS
Create a read-only IAM role. BlobRouter observes your storage without write access during the audit.
- 02
Analyze your storage
We analyze buckets, storage classes, object distributions and available usage signals to identify waste and optimization opportunities.
- 03
Evaluate what should change
BlobRouter compares storage strategies and estimates their economics, including migration and topology costs when the required signals are available.
- 04
Review and approve
See the reasoning, assumptions and expected economics. Nothing moves without your approval.
- 05
Execute when appropriate
When migration is the right decision, BlobRouter can execute the approved transfer and verify the result.
Already using BlobRouter for storage routing? Our TypeScript and Python SDKs let applications route uploads directly to supported providers.
Built for the storage problems AI workloads create
AI teams accumulate training datasets, model checkpoints, inference assets, experiment artifacts, generated data, and logs — and these workloads can have very different access patterns and compute dependencies than a typical application.
- Training datasets
- Model checkpoints
- Inference assets
- Experiment artifacts
- Generated data
- Logs
BlobRouter starts with storage because storage decisions become particularly expensive when data is coupled to compute — exactly the situation AI infrastructure creates.
AWS S3 cost optimization
BlobRouter helps engineering teams identify opportunities to reduce Amazon S3 storage costs across buckets and storage classes — from S3 Standard and Intelligent-Tiering down to Glacier, informed by lifecycle policies, cold and unused data, storage growth, and the cost of moving data across providers.
AWS already provides strong native tools for this — Intelligent-Tiering and Storage Lens both help you find and act on storage waste. We’re not replacing them. Our difference is evaluating the architecture and tradeoffs across possible actions, not simply flagging that a bucket is cold.
S3 storage cost estimator
This is a storage-only estimate using public AWS pricing. Your audit uses your actual S3 environment and available usage signals.
Estimated monthly S3 cost
$182/mo
Estimated optimized cost
$28.49/mo
Estimated monthly savings
$154/month
These estimates cover storage only. Future versions will analyze compute, databases, networking, and other cloud infrastructure.
Vision
Where we're going
Storage first—because access patterns are objective, trust required is minimal, and value shows up fast. Then route smarter. Then expand the map.
AWS S3
Source
Backblaze B2
Cold
Cloudflare R2
Hot
Waste detected → you approve → BlobRouter routes cold and hot paths intelligently
Today
AWS S3 storage intelligence
Read-only analysis, recommendations, and approved execution.
Next
Workload-aware infrastructure decisions
Understand how storage interacts with compute, networking and workload behavior.
Later
Infrastructure optimization
Apply the same decision framework beyond storage.
Long term: an AI interface for understanding and operating cloud infrastructure.
Security & trust
Connecting AWS should feel safe. Here's exactly what BlobRouter can and cannot do.
Read-only IAM Role
BlobRouter requests only the permissions required to analyze your storage. It cannot modify infrastructure during audits.
Temporary Credentials
Audits use AWS STS temporary credentials that expire after the scan. Long-lived access keys are never used for auditing.
Encryption
When you enable routing, provider credentials are encrypted at rest with AES-256-GCM before they are stored. They are decrypted in memory only when generating presigned URLs.
Your Data Stays Yours
BlobRouter never stores your object bytes. Files stay in your cloud storage providers; we only process metadata needed for audits and routing decisions.
Verified Migrations
Approved migrations copy each object individually and verify it landed before moving on. Migration execution is currently in beta while we finish hardening it.
Early access
We're looking for 5 AI/engineering teams with meaningful S3 spend
Help shape BlobRouter. We're working with our first design partners—not collecting fake logos.
- Free access during development
- Direct founder support
- Influence the roadmap
- Early access to upcoming features
Sign up and we'll reach out from the founders.
Beta pricing
You pay for continuous reasoning about your storage estate — not for how many gigabytes we move. If we charged per migration we’d have an incentive to recommend them; we want the opposite incentive.
Founding Partner pricing is being finalized with early design partners, and the audit remains free.
Free
Always free
One-time read-only storage audit
- AWS storage audit (read-only IAM)
- Waste + recommendation report
- No credit card required
Founding Partner
Beta pricing
Continuous reasoning · direct founder support
- Everything in Free
- Ongoing analysis as your estate changes
- Segment-level recommendations, including what to leave alone
- Re-evaluation triggers when the answer changes
- Approve migrations when they're the right call
- Direct founder support
Enterprise
Contact us
For larger estates
- Custom scale and compliance constraints
- Security review support
- Dedicated onboarding
- Procurement-friendly billing
FAQ
Straight answers for engineering and security teams.
No. Audits use a read-only IAM role. BlobRouter cannot change your infrastructure during a scan.
BlobRouter