Hey Product Hunt 👋 I'm Vatan, solo builder of BYOS. The idea started from something dumb and specific: I was building yet another side project that needed file storage, and I was about to add another line item to my AWS bill for something my Google Drive was already sitting there for, mostly empty, doing nothing. So I built BYOS — connect your Google Drive, get back an S3-compatible bucket. Upload, download, delete, list, signed URLs, versioning — all through a clean REST API and an SDK that feels like the AWS SDK, except the storage is yours and it's already paid for. Why this isn't just "Drive with extra steps": We only ever request the drive.file scope — we literally cannot see any other file in your Drive. Not a privacy policy promise, a technical constraint. It's S3-shaped on purpose. If you've used @aws-sdk/client-s3, the BYOS SDK should feel like nothing changed except your bill. Google Drive is not built to be object storage, so most of my last few weeks went into making it behave like one — handling nested "folders" as flat keys, resumable uploads for big files, and a background job that reconciles my database against Drive's real state in case you go move files around in the Drive UI directly (you will, and it needs to not lie to you when you do). Who this is actually for: indie hackers, student builders, AI side-projects, internal tools — anyone shipping something small who doesn't want a cloud storage bill before they even have users. What's next: Google Drive is live today. OneDrive, Dropbox, and eventually plain S3/R2/B2 passthrough are next — same SDK, same API, you just pick where your files actually live. I built this solo end to end — API, SDK, dashboard, all of it — so I'd genuinely love your feedback, especially if you try connecting your Drive and something feels off. Tear it apart in the comments, I'm here all day 🙏

BYOS

Turn Your Google Drive Into an S3-Compatible Storage Engine.

Turn Your Google Drive Into an S3-Compatible Storage Engine.