AList vs Yopass
| Tagline | File list program supporting multiple storages, with WebDAV and web UI | Secure one-time sharing of secrets, passwords, and small files |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Google Drive, Dropbox | Dropbox, Google Drive |
| GitHub stars | 50k | 2.8k |
| Language | Go | Go |
| License | AGPL-3.0 | Apache-2.0 |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | Docker Manual | Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 13 days ago | today |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
AList
- Primarily a read/list and aggregation layer; not a true two-way sync engine like Dropbox
- No native desktop/mobile sync clients (relies on WebDAV)
- Limited collaboration, versioning, and team permission features
- Documentation is partly Chinese-first and can lag for some backends
Yopass
- Not a general-purpose file storage tool; limited to small secret payloads
- No persistent file storage; every secret auto-deletes after first access or TTL
- No user accounts, history, or file browsing capabilities
- Requires Memcached or Redis as an external dependency
Bottom line
Choose AList if you want the lower-effort setup; choose AList for the larger community and ecosystem. Yopass has seen more recent development. Open each guide below for deploy steps and the full feature gap.