Transparent, auditable, and open.
OpenPrivateDrive is designed to be open source so developers, companies, and privacy-focused users can inspect the code, deploy it independently, and adapt it to their needs.
Why Open Source?
Transparency builds trust
With open source, you don't have to guess what happens with your data. The code is available for anyone to audit.
Service-Oriented Architecture
The project follows a robust Flask-based SOA, ensuring shared logic between the web interface and the dedicated REST API for Android integration.
Security by Design
Centralized permission engine gates every single request. Files are stored outside the web root, preventing direct physical path access and ID enumeration.
Full Data Ownership
No vendor lock-in. You own your deployment, your storage physical location, and your backup strategy. Move your instance at any time.
License
OpenPrivateDrive is licensed under the AGPLv3 for the community edition. This ensures the project remains open and that improvements are shared back with the community while allowing for private self-hosting.
View Source Code on GitHubContribute to the project
Report issues, suggest features, or improve documentation. We welcome contributions from the self-hosting community.
Get InvolvedEngineering-led project
Built for maintainable private deployments.
OpenPrivateDrive is designed by Christophe CREMIEUX, with a focus on secure web platforms, clean API design, DevOps-ready deployment, and privacy-first file workflows.
Secure Flask and API architecture
Private-server deployment experience
DevOps, CI/CD, and infrastructure hardening
Mobile-ready API and encrypted file workflows