The much-anticipated launch of Linode Object Storage is finally here! We built Linode Object Storage to make it easier and more affordable for developers to manage unstructured data such as content assets, as well as sophisticated and data-intensive storage challenges around artificial intelligence and machine learning.
To see additional ways developers might use object storage, check out our documentation:
- Linode Object Storage Use Cases
- How to Use Linode Object Storage
- Host a Static Site Using Linode Object Storage
Linode Object Storage is S3-compatible, highly available, and easily scalable storage for any of your backup, big data and data archiving needs. With Object Storage you do not need to have or use a Linode virtual machine to benefit from storing your files or expanding your capacity. Linode Object Storage is immediately available in our Newark data center and will roll out to our remaining regions starting in the months to come.
Linode Object Storage starts at $5/mo includes 250GB and 1TB outbound transfer, and then storage and transfer above that are $0.02/GB. Buckets scale up to 10TB per customer, per cluster.
Get Started Now!
For existing customers, you can begin provisioning and managing your unstructured data and static website right from your Linode Cloud Manager. It really is as easy as clicking a button.
Leslie from our Documentation team created a video tutorial showing just how simple it is:
Those of you who aren’t already customers can sign up here and apply a $20 credit towards your first few months of Linode service when you use the code OBJECT20.
To learn more about Linode’s storage options, visit our product page.
Good news thanks for the wonderful staff. Greetings
Greetings, Mohammed – Thanks for the kind words!
Bad pricing? Spaces only costs half this for bandwidth including CDN.
Thanks for the feedback, and I’ve shared it with the team.
I hate to saying it but this is disappointing pricing for the storage y’all.
I was really hoping for good pricing and unmetered/uncharged ingress/egress from the object storage if used entirely within the Linode network.
Backblaze B2, for example, is $.005 (half a penny) per GB per month.
The included 1TB of bandwidth is nice, but the storage pricing really needs to be tweaked to be competitive. This just makes it “more of the same” when compared with other providers.
Strive to be better than S3 pricing! You can do it!
We appreciate you taking the time to share this feedback with us, and I’ve passed it along to our team to review. The outbound traffic will work against your transfer pool first, before being charged the $0.02/GB, and 250GB of storage is included in the $5/month.
Bandwidth pricing isn’t everything. You have to compare latency, reliability, etc. Linodes have always been very low latency compared to Amazon so Linode’s offering may be better for things like static site hosting, small files, etc. and other services may work out cheaper for large binary downloads where latency isn’t an issue. It depends on your use case.
Good news. When it will be available on Singapore Region and is there any plan to build a new data center in Indonesia 🙂
We don’t currently have anything to share, but we’ve taken note of your interest! Make sure to keep an eye on the blog for our latest updates.
Let’s say I have a use that requires distributing large files to users, who expect to download them with reasonable bandwidth, but latency does not matter at all. What would you recommend to use instead?
John If you’d prefer to use something other than Object Storage, then you could set up a Linode with FTP (or your alternative of choice) and use an attached Block Storage Volume to store the data. There’s more info on Block Storage here:
For AWS, from some documentation: “An Amazon S3 bucket has no directory hierarchy such as you would find in a typical computer file system. You can, however, create a logical hierarchy by using object key names that imply a folder structure. For example, instead of naming an object sample.jpg, you can name it photos/2006/February/sample.jpg.”
Is this the same with Linode’s object storage? The video indicates that you can upload folders, and they will actually show up in the web interface as being a folder. When doing this, is the folder virtual in nature, or does it actually exist in the bucket?
Hey Kirby – the short answer here is yes! You can do this with Linode Object Storage as well. Technically, the file structure is still flat, but you can still emulate folders/folder hierarchy when uploading objects.
As in the video, if you’re using the Cloud Manager, this can be achieved by uploading a folder with object in it already or by dragging objects directly into an already-established folder.
For more tips/tricks/tools, check out our How to Use Linode Object Storage guide.
When you’ll add CDN to your spaces, like DigitalOcean does? For even better latency for people/users from the same local area/state