5 ms·
Disclaimer: I am the author of the blog post and work at Backblaze. > surprised that AWS, GCP, or Azure haven't acquired Backblaze by now Sometimes press/cust
by brianwski 8y ago
Disclaimer: I am the author of the blog post and work at Backblaze.
> surprised that AWS, GCP, or Azure haven't acquired Backblaze by now
Sometimes press/customers/people ask us how many customers has Backblaze "converted over from" S3 to B2. To be honest, I think the answer is approximately zero. If a customer already has a Petabyte uploaded into S3, it is simply not practical or cost effective to download that from S3 and import it into B2. The S3 download costs are extremely expensive (9 cents per GByte to download out of S3, vs 1 cent per GByte to download out of B2).
Most of Backblaze's B2 customers fall into one of two camps:
1) New customers starting out that have just started to look at cloud storage and need to decide where to put their data. They look at S3, compare with B2, and make a decision and Backblaze B2 gets some of those customers. Realistically we don't even get half of these new customers either because B2 is missing a feature the potential customer needs, or because the customer has not even heard of Backblaze. So Backblaze is probably not causing Amazon too much lost revenue yet.
2) Multi-cloud customers. Any one "cloud provider" can have outages, including Backblaze and including Amazon. So if you store an entire copy of your data in Amazon S3, and also store an entire copy in Backblaze B2, you will (by definition) have both more durable data and higher availability data than a single copy in either one alone. By definition this doesn't actually cost Amazon S3 any sales, because you STILL need a complete copy in S3!! For multi-cloud, Backblaze B2 doesn't harm Amazon one bit.
> Seems like an obvious move (for Amazon to acquire Backblaze).
Amazon has never offered to buy Backblaze, but also we are not for sale. Or at very least not at the prices Amazon would probably want to spend (or could justify to their board). I don't know if this is common knowledge but Backblaze is employee owned. We never took any significant VC funding, so the only people with voting rights on the board of directors are the original 5 Backblaze founders (including myself). We like what we are doing and we COMPLETELY control our own destiny and work environment. Literally nobody (except customers) can tell us what to do, how to price our products, or what features to build. Backblaze is a fun company to work at, and we all make a good living. So it would be inordinately expensive to buy us out just to put us out of business and dissolve our tight-knit group here and ruin all our fun. Our plan is to stay independent forever.
- deleted 8y ago[deleted]
- atYevP 8y agoControlling our own destiny is nice!
- nicoburns 8y ago> Amazon has never offered to buy Backblaze, but also we are not for sale. Or at very least not at the prices Amazon would probably want to spend (or could justify to their board). I don't know if this is common knowledge but Backblaze is employee owned. We never took any significant VC funding, so the only people with voting rights on the board of directors are the original 5 Backblaze founders (including myself). We like what we are doing and we COMPLETELY control our own destiny and work environment. Literally nobody (except customers) can tell us what to do, how to price our products, or what features to build. Backblaze is a fun company to work at, and we all make a good living. So it would be inordinately expensive to buy us out just to put us out of business and dissolve our tight-knit group here and ruin all our fun. Our plan is to stay independent forever. This as much as anything encourages me to trust and invest in Backblaze. Long may you live. Maybe I'll get around to writing that Rust SDK I've been meaning to write for a while...