Introduction

MyDrive is an open source, self-hosted cloud storage platform. It behaves like Dropbox or Google Drive from a user’s point of view, but you run it on your own server and configure every setting those platforms keep fixed:

• Storage quotas — set per plan or per individual user, and change them at any time.
• Payment methods — turn on Stripe, PayPal, crypto, or manual bank transfer, in any combination.
• Everything else — upload limits, allowed file types, trash retention, encryption, and backup targets are all environment-driven.

MyDrive is released under the AGPLv3 license. The source lives at github.com/iiaanloopez/MyDrive.

Who this is for

You should reach for MyDrive if you are a developer, sysadmin, or small team that wants:

• Full ownership of where files are stored, with no vendor lock-in.
• The option to charge your own users for storage, using payment methods you choose.
• A multi-tenant setup: one instance serving several organizations with isolated users and plans.

If you just want personal file sync with no interest in self-hosting, a managed provider is probably a better fit — MyDrive assumes you’re comfortable running a server.

How this documentation is organized

• Installation walks through deploying MyDrive with Docker Compose.
• Configuration covers every environment variable, including quotas and payment providers.
• Administration and end-user guide cover day-to-day usage.
• Security & backups covers encryption and disaster recovery.
• FAQ & troubleshooting answers the questions that come up most.

Minimum requirements

• A server or VPS with at least 1 vCPU and 1GB RAM for a small instance.
• Docker Engine 24+ and the Docker Compose plugin.
• A domain name if you want to expose MyDrive over HTTPS (recommended for production).