Abstract violet and amber illustration representing a self-hosted personal cloud drive with multiple storage backends

Cloudreve

Cloudreve

Cloudreve is a self-hosted alternative to Dropbox or Google Drive, written in Go, with a browser interface that actually looks and behaves like a drive: folders, thumbnails, drag-and-drop uploads, and share links, instead of a bare file listing. What sets it apart from something like Nextcloud is storage flexibility. Point it at local disk, an S3-compatible bucket, or OneDrive, and Cloudreve treats all of them the same way from the user’s side.

What Cloudreve actually does

Cloudreve is built with a Go backend (Gin plus the ent ORM) and a React frontend, and it deliberately avoids trying to be a full groupware suite the way Nextcloud does. There’s no calendar, no contacts, no chat app bolted on. It focuses on one job: giving files, wherever they physically live, a fast, modern web interface with real multi-user support.

License: this one needs more than a one-line answer. The backend (github.com/cloudreve/cloudreve) is GPL-3.0, confirmed directly from the LICENSE file in the repository, same as it’s always been. Since Cloudreve V4, though, that only covers the backend. The frontend’s source code is handed out exclusively to paying Pro subscribers through Cloudreve’s license management dashboard, according to the project’s own documentation on custom frontend builds. Community Edition users still get a fully working, free interface, it’s baked into the binary and the Docker image as pre-built static files, but you can’t get at or modify that frontend’s source without paying. That’s a real step back from V3, when the whole stack, frontend included, shipped under an open license.

The good news: the Community Edition itself needs no license key, no time bomb, and no artificial cap on users or storage. Only the Pro edition requires the --license-key startup flag. What Pro actually buys, beyond frontend source access, includes a desktop sync client for Mac and Linux (the free tier’s native sync client is Windows-only), removal of Cloudreve branding on the login page, and monetization and advanced storage-policy features aimed more at people running Cloudreve for other users than a single homelab admin.

Core features

  • Multi-backend storage: local disk, remote nodes, OneDrive/SharePoint, and S3-compatible services including Cloudflare R2, Google Cloud Storage, MinIO, and Backblaze B2, plus several China-region providers (Aliyun OSS, Tencent COS, Huawei OBS).
  • Direct client-to-storage transfer: uploads and downloads move straight between the browser and the storage backend rather than round-tripping through the Cloudreve server, which matters once files get large.
  • WebDAV support across every storage backend, so any WebDAV client can mount a Cloudreve share like a network drive.
  • Remote download via Aria2 or qBittorrent integration, letting Cloudreve fetch files in the background instead of through the browser.
  • Online preview and editing for video, images, audio, ePub, text, Markdown, diagrams, and Office documents, plus archive compression, extraction, and browsing.

Installing Cloudreve with Docker Compose

Cloudreve’s own documentation points to a dedicated Compose repository rather than a single self-contained image. Clone it and copy the example environment file:

git clone https://github.com/cloudreve/docker-compose.git ~/cloudreve
cd ~/cloudreve
cp .env.example .env

The repository’s base docker-compose.yml runs Cloudreve alongside PostgreSQL and Redis (a separate docker-compose.pro.yml overlay switches to the Pro image and adds the license key, and a docker-compose.fts.yml overlay adds full-text search). Bring the base stack up with:

docker compose up -d

Cloudreve listens on port 5212 by default; open http://localhost:5212, register an account, and that first account becomes the administrator. The backend image itself is published as cloudreve/cloudreve on Docker Hub.

Hardware: Cloudreve’s Go backend is lightweight on its own, but the officially documented stack adds PostgreSQL and Redis alongside it, so budget accordingly: 2 vCPUs and 2GB of RAM is a reasonable starting point for personal use, more if the full-text search addon (which pulls in Apache Tika and Meilisearch) gets added later. As with any internet-facing file service, put it behind a reverse proxy with real TLS rather than forwarding the raw port.

Prerequisites

Docker and Docker Compose on a Linux host, plus a domain or subdomain if a proper TLS certificate matters (it should). Nothing Cloudreve-specific beyond that; it’s the same baseline as any self-hosted web app on this site.

Cloudreve vs. the alternatives

Cloudreve, Nextcloud, and Seafile all answer the same basic question, where do my files live and how do I get to them, but differently enough that picking between them usually comes down to what else is wanted alongside file storage.

  • Genuinely broad storage-backend support; S3-compatible object storage and OneDrive both work natively, which neither Nextcloud nor Seafile’s Community Edition handle as directly
  • A modern, drive-like interface with fast browsing, thumbnails, and inline previews, closer to what commercial cloud storage feels like
  • Lighter server footprint than Nextcloud, since it skips the groupware features entirely
  • The frontend source is Pro-only since V4; anyone who cares about the entire stack being modifiable, not just the backend, should know that going in
  • No calendar, contacts, or chat; if a full collaboration suite is the goal, that’s what Nextcloud is for
  • Desktop sync outside Windows requires WebDAV plus a tool like rclone or davfs2, since the native sync client is gated to Pro on Mac and Linux

Against Nextcloud, Cloudreve trades groupware features for a lighter, more drive-focused tool with better multi-backend storage support. Against Seafile, the comparison is closer: both are sync-and-share-focused rather than full platforms, though Seafile’s block-level differential sync and client-side encryption are things Cloudreve doesn’t really match, and Cloudreve counters with far more storage-backend flexibility and a more modern-feeling web UI.

Official resources

FAQ

Is Cloudreve free?

The Community Edition is, with no license key and no time limit. What’s not fully free since V4 is the frontend source code, which is only handed out to paying Pro subscribers. The backend stays GPL-3.0 and openly available.

What’s actually different about Cloudreve V4’s licensing?

In V3, the whole project, backend and frontend, shipped under an open license. Since V4, the backend stays GPL-3.0, but the frontend’s source is Pro-only. Free users get a fully functional, pre-built interface baked into the binary; they just can’t access or modify its source without paying.

Cloudreve or Nextcloud, which one should I run?

Nextcloud if calendar, contacts, chat, and office editing alongside file storage matter. Cloudreve if the priority is a fast, drive-like interface with flexible storage backend support, S3, OneDrive, and beyond, and the groupware features aren’t needed.

Does the free edition have real limitations?

A few, worth knowing upfront: the native desktop sync client is Windows-only outside Pro (Mac and Linux fall back to WebDAV), and Cloudreve branding shows on the login page. Core file management, sharing, and storage-backend support all work fully in the free edition.