The selling point of Dropbox/Google Drive isn't the storage itself, but that there's app for mobile and desktop operating systems which deeply integrates it in the OS so it's just like a local folder that's magically synced.
So it's a cool project, but not really what I'd say is a Dropbox replacement.
The critical part of Dropbox is not just the storage layer but a combination of their client and server. Even small things like how do you handle conflicting writes to the same file from multiple threads, matter a great deal for data consistency and durability.
Features I'm guessing this is missing (in no particular order): Recycle bin, Sharing with permissions, Editor, Versioning, Search, Partial sync, zone redundancy/backup, Windows, Android, Mac, and iOS clients
I bought 35$/mo 16TB server from OVH. I am running 2 replicas of Garage, one on this server. I am using this for backup for now but probably I will also move my Nextcloud files there and websites. This is fine for now and less pricey than any S3 provider I was able to find.
If you are not ready to trust a vibe-coded app with all your digital life, I recommend Filestash[1], easy to install self-hosted frontend for virtually any type of storage. Written in Go, it can be enhanced with plugins. Uses local SQLite database.
I am using it with Hetzner Storage Box[2], which is insane value for money at 11 euro per 5 terabytes per month.
It's pretty magical. It nails the "online" vs "cloud only" paradigm via the SeaDrive client. I have it running on my file server, and now all my machines have access to terabytes of storage with local performance, since it can cache a subset of your content locally.
And since I can run the server on my LAN, the throughput is way better than Dropbox would be too.
Looks like a good light weight solution to front object storage with a front end and auth. One suggestion is to add the license to the repo. The readme says License: MIT, but there’s no license file.
I used to be excited by these kind of tools, I love to self-host stuff. When I clicked on the link, I had this hesitation, suspecting "maybe it's LLM generated". And sure enough, coming back to HN, description says it is.
File sync can't be that hard! Enters the first 3 way conflict and everything explodes.
Dont misunderstand me, this is a cool idea. But if your rotation time between ideating a project and pushing it to HN is a week, you don't understand the problem space. You didn't go through the pain of realizing its complexity. You didn't test things properly with your own data, lost a bunch of it and fixed the issues, or realized it was a bad idea and abandoned it. I have no guarantee you'll still be there in a month to patch any vulnerabilities.
Not that any open-source project had these kind of guarantees until now, but the effort invested in them to get to that point was at least a secondary indicator about who built it, their dedication, and their understanding of the space.
I use archive storage class on google cloud, to store old movies and wedding videos, pictures of old vacations.
For everything else I use paid onedrive subscription.
The biggest problem is user interface with s3 like storage and predictable pricing because remember you also pay for data retrieval and other storage apis, with dropbox etc you pay a fixed amount. Every year or so I roll over data into the bucket.
Dropbox is a lot more than file storage. The syncing itself has been through serious tests to characterise its behaviour. Sure, some may not like the decisions taken to direct its sync behaviour one way or another but at least all these are known through formal testing.
But you have to pay for your own S3 bucket as well... and it's generally several times more expensive per terabyte, though this depends on different factors. (Not to mention you might still have to pay for Google if your e.g. Gmail doesn't fit into the free tier anymore.)
If this is supposed to be financially motivated, the creator seems to have it somewhat backwards.
For all the people pooh-poohing this, I'm very interested in this business model (bring your own provider token) and this looks to be nicely done. I'm going to try it out. In particular I want to see if it supports payload encryption for the data in S3. I'd need that to be comfortable stashing all my personal data in AWS or Wasabi.
There was a similar program I used when I was working at a smaller company and built an automated backup system for their call center recordings. It basically mapped the S3 bucket to a Windows drive letter, since the PBX call recording software was running on a Windows server. It was a while ago so I can't recall the name of the program
Funny I kept getting this "you are using 98% of your storage space" message with my 15GB so I'd be finding/deleting old attachments then eventually I was like fine I'll pay, it's like 48 cents a month or something
The thing I find interesting about apps made by Claude et. al. is that they always fallback to using dotenv for configuration. I thought dotenv was on its way out! Personally, I've been using sOPs for this purpose.
I love it! How would you position yourself relative to existing OSS products in the space like Filestash or Seafile? I'm trying to pick a solution at the moment, and the mobile experience matters a lot to me.
Feels like this is missing some of the key points of using generic bucket storage for me:
1. Archive pricing for really large old documents.
2. Cross-provider backups; especially for critical documents.
Ok, I'll see it later but please use the 'Release' feature of GitHub. It is the easiest way to tell for your customers that a new release is out. Even GH can send notifications. Thanks.
That is the feature that gives your drive as a mounted file system that stream files as you need them.
It gives me the ease of having access to a giant amount of files stored in my gdrive without having to worry about the space they take up locally nor moving files up and down.
Actually, what solutions to that might already exist? I don't really use the web UI of gdrive as much as use it as a cloud disk drive.
208 comments
So it's a cool project, but not really what I'd say is a Dropbox replacement.
1 TB is roughly 20-30 USD per month at AWS/GCP only in storage, plus traffic and operations. R2 is slightly cheaper and includes traffic.
Compared to e.g a Google AI plan where you get 5 TB storage for the same price (25 USD/month) + Gemini Pro thrown in.
https://news.ycombinator.com/item?id=9224
I'd rather control the whole stack, even if it means deploying my own hardware to one or more redundant, off-site locations.
Edit: Are there robust, open source, self-hosted, S3-compliant engines out there reliable and performant enough to be the backend for this?
How much on S3? A LOT more.
I am using it with Hetzner Storage Box[2], which is insane value for money at 11 euro per 5 terabytes per month.
[1]: https://github.com/mickael-kerjean/filestash [2]: https://www.hetzner.com/storage/storage-box/
https://www.seafile.com/en/home/
It's pretty magical. It nails the "online" vs "cloud only" paradigm via the SeaDrive client. I have it running on my file server, and now all my machines have access to terabytes of storage with local performance, since it can cache a subset of your content locally.
And since I can run the server on my LAN, the throughput is way better than Dropbox would be too.
Sure, ChatGPT can help, but to use it reliably, you still need enough medical knowledge to ask good questions and evaluate the answers.
File sync can't be that hard! Enters the first 3 way conflict and everything explodes.
Dont misunderstand me, this is a cool idea. But if your rotation time between ideating a project and pushing it to HN is a week, you don't understand the problem space. You didn't go through the pain of realizing its complexity. You didn't test things properly with your own data, lost a bunch of it and fixed the issues, or realized it was a bad idea and abandoned it. I have no guarantee you'll still be there in a month to patch any vulnerabilities.
Not that any open-source project had these kind of guarantees until now, but the effort invested in them to get to that point was at least a secondary indicator about who built it, their dedication, and their understanding of the space.
I'm a kid in a candy store playing around with this stuff.
For everything else I use paid onedrive subscription. The biggest problem is user interface with s3 like storage and predictable pricing because remember you also pay for data retrieval and other storage apis, with dropbox etc you pay a fixed amount. Every year or so I roll over data into the bucket.
But for infrequently accessed data its fine.
Dropbox is a lot more than file storage. The syncing itself has been through serious tests to characterise its behaviour. Sure, some may not like the decisions taken to direct its sync behaviour one way or another but at least all these are known through formal testing.
But you have to pay for your own S3 bucket as well... and it's generally several times more expensive per terabyte, though this depends on different factors. (Not to mention you might still have to pay for Google if your e.g. Gmail doesn't fit into the free tier anymore.)
If this is supposed to be financially motivated, the creator seems to have it somewhat backwards.
> Languages JavaScript 55.2%, TypeScript 44.4%, Other 0.4%
Isn't that compromises the whole purpose of the project immediatly?
Moreover, any reasonably adequate dev would work on expansion of syncthing ecosystem, not inventing a rasclet instead of a wheel
Example 2TB:
Google $10/mo vs S3 ~&45/mo?
You could get cheaper that Google Drive with glacier tiers but that’s a different level of restrictions and still has retrieval fees.
Feature request: Google Drive for desktop.
That is the feature that gives your drive as a mounted file system that stream files as you need them.
It gives me the ease of having access to a giant amount of files stored in my gdrive without having to worry about the space they take up locally nor moving files up and down.
Actually, what solutions to that might already exist? I don't really use the web UI of gdrive as much as use it as a cloud disk drive.