CLOUD FILES: HOW IT WORKS

The technologies behind Cloud Files

OpenStack®
Cloud Files runs on OpenStack technology. We have developers from all around the globe contributing to our feature list, helping us fix bugs, and making the product the perfect object storage solution. 

Global Presence
Rackspace Cloud Files has infrastructure located in several data centres worldwide, including Dallas, Chicago, and London. 

Uptime
With 24x7x365 monitoring and operations teams, you don't have to stay up all night worrying about uptime. We're already doing it for you! 

Replication
All data stored in Cloud Files is instantly written to three storage disks, all on separate nodes or locations that have dual power supplies. 

Private Containers
With private containers, all traffic between your application and Cloud Files uses SSL to establish a secure, encrypted channel. This ensures that any data (usernames, passwords, and content) cannot be intercepted and read by a third party. 

Public Containers
In public containers, your media files receive a web-ready URL that can be shared with anyone. Public files are served blazingly fast too, thanks to Cloud Files integration with the Akamai Content Delivery Network. 

Large File Support (API only)
If you need to store very large files (e.g. videos, HD movies, or backups), Cloud Files accomplishes this by allowing customers to upload multiple file segments and a manifest file to map those segments together.  Large files will be downloaded as a single file.

Temporary URLs (API only)
If you are looking to share documents or data without serving it publicly, Cloud Files allows users to create temporary URLs that give direct access to your Cloud Files objects for a specified period of time.  

Expiring Objects (API only)
If you don't need or want to keep Cloud Files objects indefinitely (e.g. log files or recurring full backups), simply add a header while uploading the object to set when it will be automatically removed from your Cloud Files account.