Backrest vs copyparty
| Tagline | Web UI and orchestrator for restic backups across local and cloud storage | Portable all-in-one file server with resumable uploads, WebDAV, FTP, and media indexing |
| Category | File Storage & Sync | File Storage & Sync |
| Replaces | Dropbox, Google Drive | Dropbox, Google Drive |
| GitHub stars | 7k | 46k |
| Language | Go | Python |
| License | GPL-3.0 | MIT |
| Self-host difficulty | 2/5 Easy | 2/5 Easy |
| Deploy options | Docker Docker Compose Manual | Docker Manual |
| Managed hosting | ||
| Last updated | 10 days ago | 4 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.
Backrest
- It's a backup tool, not a live sync/share platform like Dropbox
- No real-time file syncing across devices or shareable links
- No multi-user collaboration or document editing
- Restore is snapshot-based rather than continuous file availability
copyparty
- No selective sync desktop client; files must be managed via web UI, CLI, or WebDAV
- User management and access control are basic compared to Dropbox Teams or Google Drive Shared Drives
- No online document editing (Docs/Sheets equivalent)
- Mobile apps are absent; mobile access is browser or WebDAV only
Bottom line
Both are a similar lift to self-host; choose copyparty for the larger community and ecosystem. copyparty has seen more recent development. Open each guide below for deploy steps and the full feature gap.