Object storage migration and backup

Move data to Quake AI from another provider, use Quake AI as a backup target alongside your primary storage, or keep multiple clouds in sync. Quake AI's S3-compatible API means your existing tools and SDKs work with minimal configuration changes.

Find your guide#

I want to move all my data to Quake AI#

Full migration: copy everything, then switch your application to use Quake AI as the primary storage provider.

1. Plan your migration: S3 compatibility matrix, data inventory, egress cost estimation, and validation checklist
2. Pick the guide matching your current provider:
3. Update your application endpoint: swap SDK configuration to point at Quake AI

I want to use Quake AI as a backup target#

Backup and archival: keep your primary storage where it is and replicate data to Quake AI for disaster recovery or long-term retention.

I want to keep data synced across multiple clouds#

Multi-cloud sync: run continuous or scheduled replication between Quake AI and another provider for redundancy, failover, or compliance.

What makes Quake AI different#

• S3-compatible API: standard S3 SDKs and tools (rclone, AWS CLI, boto3) work with an endpoint change
• No egress fees: transfer data out at no cost
• No minimum storage commitments: pay for what you use, delete when you want
• OpenStack Swift backend: some S3 features (lifecycle policies, event notifications, bucket policies) are not available. See the compatibility matrix for details and workarounds