Vibecode Google Drive
track this build5 steps, step by step0%NOT REALLY · don't bother
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.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Google Drive. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Google Drive indie build ## Goal Build the smallest trustworthy replacement for the core Google Drive workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Google Drive instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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 ## Required capabilities - 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 ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Google Drive. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Google Drive indie build ## Goal Build the smallest trustworthy replacement for the core Google Drive workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Google Drive instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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 ## Required capabilities - 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 ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Google Drive. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Google Drive product brief ## Problem 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. ## Product outcome 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. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief 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 ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Google Drive capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Google Drive indie build ## Goal Build the smallest trustworthy replacement for the core Google Drive workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 those capabilities are essential, use Google Drive instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief 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 ## Required capabilities - 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 ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Google Drive product brief ## Problem 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. ## Product outcome 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. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief 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 ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Google Drive capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
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.
share on X ↗"I just replaced Google Drive ($1.99/mo) with one prompt"
Vibecode 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/month (Google One Basic 100 GB, checked 2026-08-18), 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.