Article

OpenList: One Web Interface for Every Cloud Drive You Own

OpenList: One Web Interface for Every Cloud Drive You Own

Count your cloud drives. The average developer in China's tech forums seems to juggle four or five: a domestic drive for daily files, a foreign one for work, an object-storage bucket for backups, a shared team drive, maybe a friend's expired-link rescue stash. Each has its own app, its own login, its own throttling quirks — and every few months you forget which drive holds that one ISO you need. OpenList is the open-source answer that community settled on: a single self-hosted web app that mounts dozens of storage backends and presents them as one unified file tree. Its own docs tagline says it plainly: "a file list program that supports multiple storage, powered by Gin and SolidJS."

The interesting part is not just the feature list. OpenList is a fork born from a very public open-source governance crisis, and how the community rebuilt it says a lot about where China's self-hosting scene is heading.

From one maintainer's project to a community fork

The story starts with AList, a Chinese open-source project that became the default way to aggregate cloud drives: mount everything, browse in one UI, expose it over WebDAV. It collected tens of thousands of GitHub stars and a huge Chinese user base. Then, in 2025, the project stalled — community members reported that development had effectively stopped after the original author stepped back, and the original repositories were eventually archived. The archived fork page states it directly: the repository is archived, and "the community fork version OpenList development work is being carried out in the new repository" at github.com/OpenListTeam/OpenList.

OpenList's organizers framed the fork as a deliberate governance fix: a community-driven, long-term-governed project explicitly designed to be resilient against single-maintainer failure and what they call "trust-based attacks" — situations where users keep installing updates from a source they can no longer verify. The fork kept the codebase's shape (Go backend on the Gin framework, SolidJS frontend) and the AGPL-3.0 license, then got on with maintenance. Whether or not you care about the drama, the practical upshot is simple: the project now lives under a team with published docs, a terms-of-use page, and separate China-mainland documentation — the unglamorous infrastructure that signals "we intend to still be here in three years."

Mount everything, browse once

The core idea fits in one sentence: each storage backend is a driver, each driver is mounted at a path, and the web UI renders all mounted paths as one directory tree. Mount Aliyun Drive at /aliyun, Google Drive at /google, a local disk at /local, and you browse / and see all three. Files open with in-browser previews for images, video, audio, documents, code, and archives; you can download across backends, generate share links with expiration dates and passwords, search indexed storage, and queue offline downloads as background tasks.

The driver count is the headline feature. The official docs list 81 built-in storage drivers, and the breadth is clearly shaped by what Chinese users actually store files on:

CategoryExamples
Domestic Chinese drivesAliyun Drive, Quark, Baidu Netdisk, 115, 123, China Telecom / China Mobile clouds, Xunlei, Weiyun, Lanzou, PikPak, WPS Drive
International drivesGoogle Drive, OneDrive, Dropbox, MEGA, Proton Drive, Yandex Disk, TeraBox
Object & protocol storageS3-compatible (AWS/OSS/COS/MinIO), Azure Blob, WebDAV, FTP, SFTP, SMB, IPFS
Code & dev hostingGitHub repos and releases
Self-hosted appsCloudreve, Kodbox, Seafile, Emby, and even OpenList or AList instances themselves
Virtual / functionalLocal disk, Crypt (encrypted storage), Alias, UrlTree, Strm (media-library style views)

Beyond the browser UI, the aggregated storage can be re-exported: OpenList serves everything over WebDAV and an S3-compatible API, so the unified tree can be mounted into your OS file manager, a media server, or backup tools. More recently the project added an MCP endpoint — the Model Context Protocol for AI assistants — meaning an AI agent can browse and manage your files through the same unified interface. (If MCP is new to you, the protocol's pitch is that it gives AI applications standard "hands" for external tools.)

Five minutes to a running instance

Deployment is where OpenList earns its homelab reputation: it's a single Go binary with an embedded database, and the official Docker image runs it with one compose file. From the project's own install docs:

services:
  openlist:
    image: 'openlistteam/openlist:latest'
    container_name: openlist
    volumes:
      - './data:/opt/openlist/data'
    ports:
      - '5244:5244'
    environment:
      - UMASK=022
    restart: unless-stopped

First boot generates a random admin password and prints it in the container logs (docker logs openlist); you can reset it anytime with ./openlist admin random or ./openlist admin set NEW_PASSWORD inside the container, or pass OPENLIST_ADMIN_PASSWORD as an environment variable. The web UI then lives on port 5244, and adding a drive is a form in Manage → Storages → Add: pick the driver, set a mount path, paste whatever credentials that provider's API requires. If you have no server at all, there is even an official serverless port — OpenList-Worker, a TypeScript rewrite that runs on Cloudflare Workers, Tencent EdgeOne, or Alibaba Cloud ESA — though the full Go version remains the primary build.

That five-minute path is exactly why it shows up in so many free-tier VPS homelab setups: a single small box, one container, every drive you own behind one login.

Where it shines, and where it creaks

Honest assessment first. The weak point is structural, not a bug: most cloud-drive drivers are unofficial integrations with providers that never promised a stable API. When a provider changes its auth flow or throttles third-party clients, individual drivers break until a maintainer fixes them — and the project's own discussion board is full of exactly these reports: Baidu mounts failing, 115 showing only partial folders, Xunlei demanding slider verification, Quark drivers needing rework. If you mount a drive you depend on daily, expect occasional maintenance days. The official project disclaimer is blunt about the same reality: it performs HTTP redirects and traffic forwarding without storing or tampering with user data, and users are responsible for complying with each provider's terms.

The second consideration is security surface. You are centralizing credentials for every storage account you own in one self-hosted database — convenient, and also a single point of failure. The project does take auth seriously on paper: role-based access control with directory-level permissions, TOTP two-factor, WebAuthn/FIDO keys, SSO and LDAP, plus JWT sessions, CSRF protection, and CSP headers, with /health and /healthz endpoints for monitoring. Treat it like any self-hosted admin panel: put it behind HTTPS, don't expose it to the open internet without authentication, and use a reverse proxy or tunnel.

What it shines at is the long tail of "just make my files reachable." Media collectors use the Strm driver to build streaming-friendly views over cloud drives for players like Infuse or Emby. Teams use share links with passwords and expirations instead of juggling per-drive sharing UIs. Developers point rclone or backup scripts at the S3 endpoint and stop writing per-provider glue. And with the MCP endpoint, the aggregated tree is starting to show up in AI-agent workflows too — the protocol built for exactly that kind of tool connection.

Who should bother

OpenList is for people whose files are scattered across more logins than they can name — the multi-drive reality that is especially common in China, where free tiers of domestic drives are generous and everyone accumulates several. If all your files live in one Dropbox, this is overkill. If you're a homelabber, a media hoarder, or someone who keeps losing track of which drive has what, it's a weekend project with a genuinely useful payoff: one URL, one login, everything you own.

The deeper lesson is the governance one. AList's collapse was a familiar open-source tragedy — a wildly popular project resting on one person. OpenList is the community's attempt to prove the project can outlive its founder, with docs, a team, and a license that keeps the code open. Whether that holds for a decade is unknowable; that they tried, and shipped, is the part worth watching.

Keep reading
MCP, the USB-C of AI: How Chinese Developers Actually Put It to Work
Read next →