Top 10 Reasons why Cloud Files + Limelight offers a better experience than S3 + CloudFront

EDITOR’S NOTE June 12, 2012: Some of the details contained in this post are no longer accurate, as Rackspace no longer uses Limelight.

1.  World-class technical support is only one click away.

Live support, with real humans based right here in our offices, is available 24/7.  And they are really, really good!

2. World-class technical support is free.

Yes, free.  As in you don’t pay for it.  And it is really, really good support!

3. You can get started in as little as one minute.

Not a programmer?  Not a problem!  You do not have to know how to code to use Cloud Files + CDN!  Our simple web-based interface makes it a snap to share your content!

4. Limelight is a tier one CDN provider.

Really, Limelight is VERY cool, and one of the foremost CDN provider’s in the industry.  That’s why we chose to partner with them!

5. No API is required to share files.

Did we mention this already?  If so, it is worth mentioning again!

6. Language-specific APIs are available, if you need them.

Not everyone knows ReST and SOAP, so we’ve created and provide support for the following language APIs – PHP, Python, Java and .NET. We do this to allow you to work in the language you feel most comfortable with.

7. Pricing for data transfer does not vary depending on edge locations.

Data transfer starts at $0.22/GB, no matter what edge location is used to share your content. This should make it easier on you when you are trying to estimate your monthly bill.

8. There are no per requests fees for CDN.

Just another way we simplify your life, and your billing.

9. There is no limit to the number of CDN-enabled containers you can create.

As far as we can tell, you can only have up to 100 distributions in Amazon’s Cloud Front system. At Mosso, we try to keep these types of arbitrary limitations to a bare minimum, not just for Cloud Files, but for all of the services we offer.

10. The Cloud Files GUI is easy to use and navigate.

Our browser based GUI let’s you easily upload a file and share it on CDN without writing a single line of code.  Heck, you don’t even need to know a programmer to share content via Cloud Files!

Father of two, mother of none. Rob has lived across the globe. He has moved back to San Antonio more times than most people move. Now he's here to stay (so he says!) Rob loves fixing things which explains his backgrounds in medicine, software quality assurance and customer care.


  1. Number 11 would be: You support SSL – if only you did!

    This would be the single killer feature for us. Support SSL & soon. We’d be here, using it, tomorrow.

  2. i want to use your service. i want to start using it today. sadly my top two reasons s3 + cloudfront offers a better experience than cloud files + limelight are:

    1. cloudfront provides cname support, necessary for that professional appearance.

    2. s3 supports folders (or at least allows files to be organised hierarchically), necessary for managing large quantities of files.

    i’m already hosting with slicehost, i’d love to use mosso too. but not so bothered about your top 10 until you’ve nailed those two.

  3. @zonknz – depends on what you mean about SSL – we sent you email.

    @sidepodcast – on your #1 – yep. Agreed. Will happen – not giving dates. On #2 – not so sure about this one. can you send email to with details on how this differs from unlimited containers?

    @fitzrev. See above. It’ll come. No date offered yet.

    Thanks for the great comments!

  4. I’m a happy Mosso customer and a user of Slicehost for our Startup.

    * CNAME option is needed not just for the professional looking URL but also for the fact that I’ve the freedom to move my content anywhere and not worry about the URLs across my website.
    * When one grows really big (let’s hope so), it is perfectly OK to use two or more CDN providers and thus S3+CF and Mosso+Limewire being used together is also an alternative.

    @sidepodcast Folders on S3 are not actually folders (you just see them as it is, courtesy your client that views your files). They’re treated as a single string corresponding to a file. I would not really care about folders as long as my script and API are able to communicate with the provider in manners understandable and sortable at our client’s end.

  5. @brajeshwar. am aware of this, but, cyberduck gives me the option of chucking a standard filesystem directory structure onto s3 and it figures everything out so that href links work as expected. e.g:


    that way i can point my cname at either an ftp folder or s3 and all the code works without change.

    @rob, shall do cheers. although the above explanation may have helped too.

  6. Hi. I’m just getting started with using a CDN/external storage solution and I was wondering how people generally keep their files in sync? I was reading a blog post (, and in the final paragraph, it said that one technique was to setup your static media on a subdomain and then point it to the CDN. If the CDN has the file, it serves it up, otherwise it requests it from your server and then serves the file.

    Is this possible?

  7. I was just coming back here to look at this article, and no offense to RackSpace, but it looks like it is invalid.

    3, 5, 6, 7*, 10 all need to be looked at now …

    *yes, Amazon charges based on edge location, and the also are 7 cents/GB cheaper (on avg.) … I’d rather get charged for each little thing, then to get one big bill. I know where I can cut down then.



Please enter your comment!
Please enter your name here