AList vs Unison
| Tagline | File list program supporting multiple storages, with WebDAV and web UI | Bidirectional file synchronisation tool for Linux, macOS, and Windows |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Google Drive, Dropbox | Dropbox, Google Drive |
| GitHub stars | 50k | 5.4k |
| Language | Go | deb |
| License | AGPL-3.0 | GPL-3.0 |
| Self-host difficulty | 2/5 Easy | 4/5 Involved |
| Deploy options | Docker Manual | Manual |
| Managed hosting | ||
| Last updated | 13 days ago | 10 days ago |
| 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
Unison
- No web UI; requires CLI or basic GTK client, not suitable for non-technical users
- No mobile clients for iOS or Android
- Conflict resolution is interactive and not automated; requires user intervention
- No file versioning or history; deleted files cannot be recovered from the tool itself
Bottom line
Choose AList if you want the lower-effort setup; choose AList for the larger community and ecosystem. Unison has seen more recent development. Open each guide below for deploy steps and the full feature gap.