ArchiveBox vs Floccus
A side-by-side comparison of two self-hosted bookmarks & read-it-later options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
ArchiveBox
Self-hosted web archiving from bookmarks and feeds
VS
Floccus
Sync your browser bookmarks across browsers and devices
| Feature | ArchiveBox | Floccus |
|---|---|---|
| Category | Bookmarks & Read-It-Later | Bookmarks & Read-It-Later |
| License | MIT | MPL-2.0 |
| Language | Python | JavaScript |
| Setup difficulty | Medium | Easy |
| Min. RAM | 1,024 MB | 64 MB |
| Deployment | docker, bare-metal | source |
| GitHub stars | ★ 28,079 | ★ 8,322 |
| First released | 2017 | 2015 |
| Replaces | Raindrop.io, Chrome Sync |
Why pick each one
Choose ArchiveBox if…
- Thorough page preservation
- Imports from many sources
- Open formats
Choose Floccus if…
- Released under the MPL-2.0 license
- Easy to set up — beginner-friendly
- Mature project with 8.3k GitHub stars
- Written in JavaScript
Frequently asked questions
Is ArchiveBox or Floccus better?
Neither is universally better. ArchiveBox has the larger community, while Floccus is simpler to set up (easy difficulty). Choose based on the comparison table above and your own setup.
Are ArchiveBox and Floccus free and open-source?
Yes. ArchiveBox is licensed under MIT and Floccus under MPL-2.0. Both can be self-hosted at no software cost.
Can I run ArchiveBox and Floccus with Docker?
ArchiveBox: yes. Floccus: check the project docs for container support.