Should you build your own Google Drive?
Cloud file storage with sync clients, sharing links, and the Google Docs suite bolted on.
You can absolutely build a file upload page with folders, search, and share links in an afternoon. What you cannot build is durable multi-region storage that has not lost a byte in fifteen years, a sync daemon that survives sleep, flaky wifi, and two machines editing the same folder, and native apps on every platform your family owns. The cost side is brutal too: two terabytes of redundant storage plus egress will run you more than the consumer plan, before you have written a line of code. Add that half the value is not storage at all, it is that everyone you share with already has an account and Docs opens in one click. This is infrastructure wearing a UI, and infrastructure is the part you are paying for.
ENOriginal research content in English. Original prompt preserved in English.
Build a self-hosted personal file locker called "Vault". Single Node.js service, no framework soup.
Stack, non negotiable:
- Node 20 with Fastify and TypeScript
- SQLite via better-sqlite3 for metadata
- Files stored on local disk under DATA_DIR, sharded by the first two chars of a content hash
- Server rendered HTML with Nunjucks plus a little vanilla JS, no React
- Single admin user, password hash in .env, cookie session
In scope:
- Upload via drag and drop, chunked, resumable, files up to 5 GB, using tus protocol or a simple range based chunk endpoint you write
- Content addressed storage: hash on upload, dedupe identical bytes, keep every version of a path
- Folder tree browsing, rename, move, soft delete with a 30 day trash table and a purge command
- Search on filename, extension, size range, and date, all from SQLite
- Share links: random 22 char token, optional expiry, optional download limit, optional password, served from a read only route that streams with correct Content-Type and range support
- Thumbnails for images and PDF first pages using sharp and pdftoppm if present, skipped gracefully if not
- A "vault backup" CLI command that rsyncs DATA_DIR and dumps the SQLite file, plus a "vault verify" that rehashes everything and reports drift
Out of scope, do not attempt:
- Desktop or mobile sync clients
- Multi user accounts, sharing between accounts, permissions matrices
- Document editing or previews beyond thumbnails
- Any cloud service, telemetry, or analytics
Requirements:
- All config in .env: PORT, DATA_DIR, ADMIN_PASSWORD_HASH, SESSION_SECRET, PUBLIC_BASE_URL
- docker-compose.yml with one service and one named volume
- Integration tests covering chunked upload, resume after interrupt, dedupe, share link expiry, and trash purge
- README that states plainly: this is one disk, it is not a backup, here is the restore drill, run it once a quarter
The prompt opens pre-filled in your agent. Review it before running. · this prompt is generated from the build plan · improve it via PR
What would building your own look like?
A self-hosted file locker: upload, browse folders, full text search on filenames, and generate expiring public share links from a single box you control.
What you will need
- A VPS or always-on home machine with disk you actually trust
- S3-compatible object storage or a RAID array plus a real offsite backup
- A domain and TLS cert for share links
- Willingness to test your own restore path before you need it
Because storage is a promise, not a feature. Paying a few dollars a month means you are not the person on call when a disk dies, a sync loop eats a folder, or your share links stop resolving during a family emergency. On top of that, most people's Drive is load bearing for other people: shared folders, Docs links pasted into email threads years ago, phone backups. Replacing the upload form is easy, replacing the promise and the graph of links pointing at it is not.
xReal sync clients on macOS, Windows, iOS, and Android, including offline files and conflict resolution
xGoogle Docs, Sheets, and Slides opening inline with live multiplayer editing
xDurability and availability engineering you will never match, plus versioning and trash that actually works
xSharing with people who already have accounts, plus granular permissions and audit trails
xOCR and content search inside PDFs and images, and the mobile scanner
Nothing worth pointing at. That’s why the prompt exists.
How much does Google Drive cost?
- Monthly billing
- $1.99/mo$1.99/mo
- Per year
- $23.88/yr$23.88/yr
- On a Brazilian card, with 3.5% IOF
- R$10.40/moR$125/yr
Saved to My list. You will see a notice on this site when the price changes.
You complete the purchase on Google Drive’s site. Vibe Radar does not handle payments.
Is it cheaper to build or buy Google Drive?
Adjust the numbers: hours to build, your hourly rate, running costs and the subscription price.
Over 24 months, subscribing is cheaper.
Starting hours estimated from the analysis (a weekend). Does not price what you give up (support, integrations, security).
Can I rebuild Google Drive?
Not really. Google Drive’s value is not the code: The moat is redundant global storage plus a client on every device your relatives own. See the honest breakdown above.
How much does Google Drive cost?
Google Drive costs about $1.99/mo (Google One Basic 100 GB, checked 10/20/2026), which is $23.88 per year.
What do I lose by replacing Google Drive?
Honestly: Real sync clients on macOS, Windows, iOS, and Android, including offline files and conflict resolution; Google Docs, Sheets, and Slides opening inline with live multiplayer editing; Durability and availability engineering you will never match, plus versioning and trash that actually works; Sharing with people who already have accounts, plus granular permissions and audit trails; OCR and content search inside PDFs and images, and the mobile scanner. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Google Drive?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.