# Cloud Storage

This page groups real-world Cloud Storage architecture patterns you can implement with Flashback.

All scenarios assume you already created buckets, repositories, and API keys in the platform, then consume storage through a Flashback endpoint.

## Available use cases

* [**Credit-aware multi-cloud storage behind one endpoint**](https://docs.flashback.tech/guides/explore-use-cases/explore-use-cases/credit-aware-multi-cloud-storage-behind-one-endpoint)\
  Route writes based on provider credits/budget to avoid overages while keeping one client integration.
* [**Cross-cloud migration and vendor-lock-in escape**](https://docs.flashback.tech/guides/explore-use-cases/explore-use-cases/cross-cloud-migration-and-vendor-lock-in-escape)\
  Migrate workloads incrementally between providers with minimal application changes.
* [**Disaster recovery (DR) / cold-tier backup to DePIN**](https://docs.flashback.tech/guides/explore-use-cases/explore-use-cases/disaster-recovery-dr-cold-tier-backup-to-depin)\
  Build resilient backup patterns across traditional clouds and decentralized storage tiers.
* [**Latency-aware routing for edge and AI pipelines**](https://docs.flashback.tech/guides/explore-use-cases/explore-use-cases/latency-aware-routing-for-edge-and-ai-pipelines)\
  Select the best endpoint/node based on live performance metrics to reduce tail latency.

## Expected outcome

After these guides, you should be able to design storage routing and resilience strategies with measurable operational controls (cost, latency, failover).