Cloud storageCAN I VIBECODE
pCloud?
BUILD FIRST
- A non-sensitive or read-only version of the core experience
- A manual review step wherever correctness or trust matters
- A narrow companion tool that removes a real piece of work
LEAVE FOR LATER
- Regulated decisions, payments, or irreversible actions
- Claims of correctness, compliance, or uptime that the MVP cannot support
- Sensitive integrations until security, support, and auditability are ready
RESEARCH NOTES
What this tool actually does.
pCloud is a Swiss-headquartered (pCloud AG) cloud storage service offering file hosting, sync, sharing, and backup. It has a free tier (up to 10 GB) and paid plans—Premium (500 GB), Premium Plus (2 TB), and Ultra (10 TB)—sold as subscriptions and as one-time-payment lifetime plans. Data is protected with TLS/SSL in transit; the optional pCloud Crypto add-on provides zero-knowledge client-side encryption. Key features include pCloud Drive (cloud mapped as a local virtual drive), 30-day versioning/rewind (extendable history), share links with password, expiry, and download limits, folder sharing, remote upload, social-media backup (Facebook, Google Photos, Dropbox, OneDrive, Google Drive), a built-in media player, and a photo editor. Apps cover Windows, macOS, Linux, iOS, Android, and web; data centers are in the US and the EU.
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused web MVP that recreates the core pCloud-style workflow: upload files, organize them in folders, preview and play media, share items via controlled links, keep version history, and store files in an optional client-side-encrypted vault.
Core workflow: a user signs up/logs in, uploads files via drag-and-drop or file picker (support large files via chunked, resumable upload), browses a folder tree, renames/moves/deletes, sees thumbnails and previews, plays audio/video in-browser, views and restores past versions, creates share links with optional password, expiry, and download limits, and can toggle a zero-knowledge 'vault' folder where files are encrypted in the browser before upload and decrypted only client-side.
User-facing requirements: a clean file-manager UI (list/grid, breadcrumbs, right-click context menu), upload progress, search, a share-link management screen, a per-file version timeline, a vault lock/unlock flow, and a settings page for profile and storage quota.
Technical requirements: backend in Node.js/Express or Python/FastAPI; local disk or S3-compatible object storage (e.g., MinIO) with signed URLs and Range-request streaming; SQLite or Postgres metadata DB; JWT auth; chunked upload endpoint with SHA-256 verification; versioning on write with retention; share links as signed tokens with constraints; Web Crypto API (AES-256-GCM + PBKDF2) for vault encryption; HTTPS/TLS everywhere.
Sensible choices: single-page front end (React or plain TypeScript); use presigned object-store URLs for upload/download instead of proxying bytes; store encrypted vault metadata only client-side and never send keys to the server.
Do not copy pCloud's brand, logo, marketing copy, proprietary assets, or UI design; build an original interface.
Out of scope: native desktop/mobile apps, virtual-drive mounting, social-media backup connectors, billing/subscriptions, multi-datacenter features, and team/enterprise admin consoles.
Deliver a README covering setup, architecture, and important limitations (e.g., browser-only vault decryption, no offline sync, single-server deployment).