First Deployment
From quick start to production, first get the service running, then handle HTTPS, data directories, health checks, and the first validation pass.
Built with Rust + React. Start with single-node deployment, then add team spaces, S3, WebDAV, WOPI, and follower nodes as needed.
AsterDrive is a lightweight self-hosted cloud drive built with Rust and React. You can start with the default single-node deployment using SQLite and local storage, then connect PostgreSQL / MySQL, S3-compatible object storage, team spaces, WebDAV, WOPI online preview and editing, and follower node storage as needed.
It is not a full collaboration suite or a multi-primary cluster system. The current focus is making file management, sharing, uploads, previews, storage policies, and routine operations clear for individuals and small teams.
Start with Quick Start. It walks you through starting the service, creating the first administrator, uploading a file, trying sharing, checking WebDAV, and running a basic acceptance pass.
If you have already decided to deploy formally, go straight to Deployment Overview. That documentation set explains Docker, systemd, reverse proxy, launch checks, upgrades, and backup along one path.
Start from User Guides. Regular users should first read the User Manual and Common Workflows, then jump to team permissions, sharing, editing, online preview, uploads, or WebDAV for specific questions.
Read Admin Console first, then Configuration Overview. AsterDrive configuration is split into startup configuration, admin-console runtime settings, storage policies, policy groups, storage policy backends, and the external network environment. It is much clearer when viewed by layer.
If you are connecting S3 / MinIO / R2, see Storage Policy Backends.
Before going live, choose a deployment method from Deployment Overview, then add Reverse Proxy, First-Start Checklist, Production Launch Checklist, and Backup and Restore. If something is already broken, go directly to Troubleshooting, then combine it with Error Code Handling when you see an error code.
Start with the Glossary and FAQ Quick Reference. These two pages are not meant to be read from beginning to end; they are there to keep you from taking unnecessary detours.
In one sentence
Do not add mental burden to your own data - that is why we build AsterDrive.