When you’ve got questions, we’ve got answers.
Cloud Files is a cost-effective, internet-based, redundant, object-based storage offering from Rackspace. Cloud Files allows users to store/retrieve files via a simple Web Service (REST: Representational State Transfer) API, The Rackspace Cloud Control Panel or the MyRackspace® customer portal. Files can range in size from a few bytes up to extremely large and your storage grows or shrinks based on your usage. Add as much or as little as you want without worrying about over-buying/under-utilizing or running out of space. With Cloud Files, you pay for what you use and how much you use is up to you.
Cloud Files infrastructure is located in the US and the UK. Our global footprint means that you can put your cloud where your customers are—and serve them at top speeds. For information on our UK products and pricing, please visit our UK site.
Developers/users can access Cloud Files via The Rackspace Cloud Control Panel, the MyRackspace customer portal, third party tools, or with any of the following: RESTful web-services, Python, PHP, Java, Ruby, or C#/.NET. Our customers come from a variety of industries, including (but not limited to): Web development/design, IT services, e-Commerce, Consulting, and Software. Common solutions that use Cloud Files include rich media sites, social media sites, and test/development sites.
Cloud Files can be an excellent storage solution for a number of reasons and is well suited for a number of applications:
Users can have virtually unlimited file sizes in Cloud Files by using our Large File Support. This allows customers to upload as many file chunks as they wish, and map them together using a manifest file. Each file chunk can be up to 5 GB.
Yes. Rackspace founded OpenStack with NASA, and we're one of the project's lead contributors. The Rackspace Cloud Files development team created and contributed the underlying source code that has become OpenStack Object Storage software, which currently powers Cloud Files.
We believe that Rackspace Cloud Files is currently one of the largest, if not the largest, production deployment of OpenStack Object Storage.
Pricing for Cloud Files is broken down to storage usage, data transfer, and requests.
Storage: Starting at $0.10/GB
Data Transfer In: No Charge
Data Transfer Out: $0.12/GB
Requests: No Charge
Other CDN Costs: No request/operation charges; No bandwidth charge from Cloud Files to CDN
For more information, visit Cloud Files Pricing.
Yes, there is a Cloud Files SLA which guarantees that the service will be available 99.9% of the time in a given billing cycle. Read the Cloud Files SLA.
Bulk Import to Cloud Files enables you to send Rackspace physical media to be uploaded directly at the datacenters. Avoid the time and bandwidth charges that go along with uploading large amounts of data from a standard connection. To get started, contact Support. For additional information, visit our Knowledge Center Bulk Import FAQs.
You don't have to choose between dedicated hardware and cloud-based servers at Rackspace. RackConnect lets you run both on the same network. So, if you need Dedicated Servers for performance or compliance requirements and the flexibility to quickly scale with Cloud Files, Rackspace makes it all work together seamlessly. View sample configurations.
Cloud Files has incorporated Akamai's Dynamic Site Delivery, HTTP Streaming Delivery and SSL Delivery services to bring our customers speedy delivery of their cloud storage objects.
Yes! Rackspace Cloud Files supports CNAMEs. Simply manage your CNAME records from your DNS tool, and we'll take care of the rest. No need for an API, control panel, or phone call. Your records are under your control. Find more details in our Knowledge Center.
If you want to CDN-enable files and media, there are no additional fees. The bandwidth (out) charges for CDN-enabled files
($0.12 per GB) are the same as files that are not CDN-enabled ($0.12 per GB). See more detailed
Cloud Files pricing.
In contrast, many CDN providers collect a number of usage points for billing including ingress, midgress, and egress. Ingress is the traffic from your origin server to the CDN. Midgress is the traffic within your CDN's network. Egress is the traffic from the edge locations to the end user. Rackspace only charges Cloud Files customers for egress—the traffic from the edge to the user.
Akamai claims one of the largest networks in the industry, with more than 105,000 servers in 78 countries within over 1000 networks. Rackspace uses 213 of Akamai's edge locations, selected especially for our customers' typical usage patterns, and designed to cover all major areas of the globe. More points of presence, or edge node locations, help you get your content closer to your users.
Rackspace lets customers utilize a feature called Edge Purge. Edge Purge enables users to update their content at the edge before the TTL has expired. Read more in the Cloud Files Developer Guide.
Yes, Rackspace supports SSL delivery (or https) which encrypts your data in transit as it goes through the CDN. Your content remains encrypted all the way from the origin servers out to the browser. You can choose to serve your content over SSL on a per object basis simply by using your SSL URL instead of your traditional CDN URL. Click here for more information.
In most cases, CDN-enabled content is delivered much faster than non-CDN enabled content. Of course, there are a number of variables (e.g. region, file size, etc.) that impact overall response times. In tests that Rackspace completed, we observed that response times were up to 38% faster with CDN-enabled content.
Rackspace Cloud Files and CDN require no long-term contracts or minimum usage. Just sign up, pay as you go, and use the services you need when you need them. It's that simple.
Try Cloud Files for yourself. Create a Rackspace Cloud account to get started.Sign Up Now