Show HN: USD 0.99/TB/month cloud storage
earthcompute.com
earthcompute.com
* Where is the data stored, and what's done to keep it safe * How / why is it so cheap, and how can I be assured the business will keep going once I've loaded data into it * What is my upload and access method? Is this S3 compatible, maybe something else? * What sort of terms are we entering into, what's the companies support obligation to me if I need my data tomorrow and there's a problem? * Do you have any existing customers, and if not why should I trust you with my data over AWS et al?
I'm sure there's some great thoughts about the business model, and probably a lot of hard work on the technical side. As a prospect customer though, I'm just seeing a price and a sign up button. It doesn't inspire any confidence to give over my email address, if anything it feels quite shady. This sort of information needs to be at my finger tips to form some level of trust.
I hope they're able to expand the information if it is a long term business venture. For all I know it could be amazing, unfortunately they're just not telling us why.
> Please make it easy for users to try your thing out, ideally without barriers such as signups or emails. You'll get more feedback that way.
This seems more like an ad to get customers than anything else, doesn't it?
The website looks and feels like it was made by some undergrad that's following django+bootstrap class and has to deliver an entirely made-by-hand project the next day. Not that it would matter much normally, but there's really nothing inspiring confidence on it.
I see you're using Next+Tailwind+Supabase and the main Next instance is being diretly hosted on a bare metal server from Scaleway, https and all, which is a somewhat weird choice for a framework like Next that works very well with standard hosted/serverless options from your usual big providers.
Considering there's not much logic going on, since the DB and auth logic are being handled by a hosted version of supabase, the homepage links redirect to github and the storage request flow is akin to sending an email, this could explain the HN hug of death, since no proxy/cache/scalable option was used.
Furthermore, the email verification link was sent from a simple gmail alias, with no confirmation on the website part.
I wouldn't dox you publicly, but your full name, surname and YOB are visible in the email sender information (along with your private gmail address). This confirms my undergrad project hunch.
All of the above makes me even more concerned about what could happen with any data uploaded here.
Ultimately I don't trust this, and I would advise anyone else not to.
There's nothing wrong with experimenting, learning and building cool stuff, especially while young, but I would have considered a whole lot more things before posting in a community such as HN
Also, website's hung. I can't signup or move ahead.
My university gives everyone some storage and hosting for whatever. As long as it’s legal and tolerates the built in rate limiter, go nuts.
What if governments did that? Just a bit of free hosting and a bit of compute for anyone to do whatever with as long as it’s legal and tolerates the rate limiter. Heck this feels like a public library type thing. Give people the raw workshop space for their ideas.
I know there’s a lot of “yeah but…” issues, but I’m feeling optimistic about the idea.
There are far better services a government could offer, like a nation-wide login system. Imagine asking for a passport by clicking a couple of buttons and taking a selfie.
The visual inconsistency of this webpage suggests it was not written "by hand".
> Failed to load resource: the server responded with a status of 404 () _buildManifest.js:1
> Failed to load resource: the server responded with a status of 404 () _ssgManifest.js:1
> Failed to load resource: the server responded with a status of 404 ()
I wouldn't trust it with my data, but I like the entrepreneurial spirit from OP.
Start by not using an unknown provider with questionable reliability or stability where the only contact is an email address.
Eg if your service vendor costs you 1000/month and they have a 10-day outage and you lose 10000000, they will credit you 1000 best-case, or maybe 1/3 of that (since it was up most of the month).
Umm, most providers' standard T&Cs exclude liability for indirect or consequential loss following unavailability of their service.
https://www.backblaze.com/cloud-storage/pricing
I'm surprised the don't come up more in a discussion about backup storage.
https://www.backblaze.com/blog/hard-drive-cost-per-gigabyte/
I know the link is LTO based for some of it. Is LTO really cheaper than hard drives? Or is it just that LTO has automation equipment behind it?
It's interesting to me that hard drives have dropped 56% in cost since 2017, and yet I don't think storage prices have dropped anything like that. Per the article, it's because demand allows them to keep it high.
I welcome a price war! And thanks for the honesty Backblaze.
My long held suspicion is they designed the product slos/apis to allow for the underlying storage technology to change without customers being aware, hence its clearly inspired by tape access patterns.
Possibly some of the very largest aws regions use tape libraries.
But I suspect aws co-mingles the data with S3 and just wears the cost. They've been known to price below cost (eg lambda implementation before firecracker) to corner the market.
Just a quick question, do you know if you will be charged 2TB / $12 per month if you have 1.1TB of Data?
If that’s within your use case it’s fantastic. I use B2 to store my backup repositories, and S3 Deep Archive to mirror “master” stuff like my optical media backups, family photo archives, etc.
Microsoft has an almost identical product in Azure at a similar price point.
Which means that the break even time for this product is at least 3 years. Assuming personnel and infrastructure costs are near zero.
I can't see how this is a genuine product.
A 10-pack of LTO-9 tape cartridges, so 180TB, can be found for ~$400. Glacier storage is used for petabyte-scale datasets you might only add chunks to years then read sequentially one time to train your next LLM. It's not for random access like a hard drive.
(Apologies for promoting this advertisement thread unintentionally; the real question is for S3, Backblaze and the like.)
https://www.tomshardware.com/news/new-freeware-detects-fake-...
A physicist generally should use the metric system. SI units convert to s⁻¹ from month⁻¹. Usually put the metric prefix first so T⁻¹ becomes pico. 2.6298e+6 seconds per month so pico becomes atto. Can't use B because that is magnetic feild in Tesla in SI units. $ is perhaps not as clear as USD, but feels like a better symbol to me (ideally with USD subscript but hard you write that here). I'm not a physicist, but generally I expect a physicist to use whatever is least ambiguous: which in this case is what was given (not my terrible attempt to convert to SI units!!!)