AList vs Kinto
| Tagline | File list program supporting multiple storages, with WebDAV and web UI | Minimalist JSON storage service with sync, sharing, and permissions |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Google Drive, Dropbox | Dropbox, Google Drive |
| GitHub stars | 50k | 4.4k |
| Language | Go | Python |
| License | AGPL-3.0 | Apache-2.0 |
| Self-host difficulty | 2/5 Easy | 3/5 Moderate |
| Deploy options | Docker Manual | Docker 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
Kinto
- Focused on JSON data sync, not binary file storage or large media uploads
- No out-of-the-box web UI for end users; requires building a frontend or using kinto-admin
- Community activity has slowed significantly; long-term maintenance uncertain
- Less ecosystem tooling compared to more established alternatives like PocketBase
Bottom line
Choose AList if you want the lower-effort setup; choose AList for the larger community and ecosystem. Kinto has seen more recent development. Open each guide below for deploy steps and the full feature gap.