The archive · Developer & Business Tools · Product decision · 2026
Locker: open-source 'Dropbox' on your own S3, built in a week — Show HN 252 pts
Nerd-sniped on X, Zach Meyer shipped Locker in about a week: MIT, self-hosted file storage over your own S3/R2/local backend; Show HN drew 252 points.
Locker
What the business is
Locker is an MIT-licensed, self-hosted file storage platform: a Dockerized Next.js 16 app on PostgreSQL (tRPC, Drizzle, BetterAuth, Tailwind, Turborepo) with file/folder management, share links with password/expiry/download limits, upload links, per-user quotas, workspace teams, API keys, an optional virtual bash shell, and semantic or full-text search plugins. Storage is provider-agnostic — local disk, AWS S3, Cloudflare R2 or Vercel Blob — chosen with one BLOB_STORAGE_PROVIDER environment variable, and Locker also speaks the S3 protocol so other apps can write to it. A hosted version runs at locker.dev.
How it started
Days before the 2026-04-07 launch, @swyx nerd-sniped @zachmeyer on X into building an open-source Dropbox; Meyer took the dare seriously and shipped Locker in about a week, posting 'Stop paying for Dropbox/Google Drive, use your own S3 bucket instead' to Hacker News.
What happened
The Show HN drew 252 points and 208 comments, with pushback that Dropbox's real value is OS-level sync, not storage; the dev.to write-up (2026-04-20) walked through a Railway deployment, praised the single-environment-variable storage switch, and published a one-click template. The project covers share and upload links, quotas, workspace teams, search plugins and S3-compatible API keys.
How it ended up
Still live as of 2026-09-04 as an open-source project with a hosted demo at locker.dev; the dev.to review judged it ready for personal use and small teams, but said large organizations should wait for more production mileage before trusting it as primary infrastructure.
Background
Locker is an MIT-licensed, self-hosted file storage platform: a Dockerized Next.js 16 application on PostgreSQL (tRPC, Drizzle, BetterAuth, Tailwind, Turborepo) offering file management, password/expiry-protected share links, upload links, per-user quotas, workspace teams, API keys, an optional virtual bash shell, and semantic or full-text search plugins.
Its key design move is provider-agnostic storage: local disk, AWS S3, Cloudflare R2 or Vercel Blob, selected by one BLOB_STORAGE_PROVIDER environment variable — and Locker itself speaks the S3 protocol, so other applications can write into it via generated API keys.
Days before the 2026-04-07 launch, @swyx nerd-sniped @zachmeyer on X into building an open-source Dropbox; Meyer shipped it in about a week. The Show HN drew 252 points and 208 comments, and dev.to's alphasec published a self-hosting write-up on 2026-04-20 with a one-click Railway template.
As of 2026-09-04 the project is live with a hosted demo at locker.dev; reviewers judge it ready for personal use and small teams, with more production mileage needed before large organizations rely on it as primary infrastructure.
What has to be true
- The one-week, dare-driven origin is itself notable: a sharp wedge can be shipped fast instead of waiting for feature parity with Dropbox.
- Provider-agnostic storage via a single env var directly answers the main objection to self-hosted tools — lock-in to one backend.
- The S3-compatible endpoint turns Locker from a Dropbox clone into infrastructure that other apps can write to.
- The 208-comment debate over OS-level sync marks the honest boundary of the bet: it wins control-minded users, not everyone.
What can be applied
A dare-built MVP found traction on an architectural wedge: separating storage from the app turned every developer with an S3 bucket into a potential user, with no lock-in argument to lose.
Aftermath
As of 2026-09-04 Locker is live as an open-source project with a hosted demo at locker.dev. dev.to's 2026-04-20 write-up judged it reasonable for personal use and small teams but advised large organizations to wait for more production mileage before trusting it as primary infrastructure. The Show HN thread's main pushback — that Dropbox and Google Drive sell OS-level sync integration, not raw storage — marks the boundary of the bet: Locker appeals to developers who already own buckets and want control, not mainstream sync users.
Sources
- Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead
- A Developer Built an Open-Source Dropbox on a Dare. Here's How to Self-Host It.
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card