head to head · open source

cloudreve vs cryfs

cloudreve has 28,737 GitHub stars, 3,896 forks, 147 open issues and last shipped 2 days ago. cryfs has 2,304 stars, 170 forks, 154 open issues and last shipped yesterday. cloudreve leads on adoption by 1,147% (28,737 vs 2,304 stars). cloudreve is written in Go under GPL-3.0; cryfs is written in Rust under LGPL-3.0. cloudreve has attracted 14% as many forks as stars, cryfs 7%. cryfs was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 2 topic tags (cloud, cloud-storage), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

cloudreve ★ 29K cryfs ★ 2.3K category Productivity & Utilities

← all 20902 open source comparisons

Side by side

cloudreve cryfs
GitHub stars ★ 29K ★ 2.3K
License GPL-3.0 LGPL-3.0
Written in Go Rust
Last push 2026-09-18 2026-09-19
Forks ⑂ 3.9K ⑂ 170
Self-hosting Yes Yes
Data ownership Your server Your server

pick cloudreve if

  • You weight community size — 29K stars and counting
  • You want the GPL-3.0 license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full cloudreve profile →

pick cryfs if

  • You want the cryfs feature set and don't need the biggest community
  • You prefer the LGPL-3.0 license terms
  • Your stack matches Rust
  • You evaluated both and cryfs fits your workflow better

full cryfs profile →

About cloudreve

Cloudreve is a self hosted file management and sharing system written in Go that gives an organisation its own web file manager, sharing layer, and multi cloud storage gateway running on infrastructure it controls.

read the full cloudreve overview →

About cryfs

CryFS is a FUSE based cryptographic filesystem written in Rust that encrypts a vault directory so it can be stored safely in cloud services such as Dropbox, iCloud, or OneDrive, and it is intended for Linux users who want their file contents, file sizes, directory structure, and metadata hidden from the storage provider rather than encrypted one file at a time.

read the full cryfs overview →

More in Productivity & Utilities

n8n ★ 205K Excalidraw ★ 132K RustDesk ★ 124K LocalSend ★ 92K AppFlowy ★ 77K OBS Studio ★ 76K

Related comparisons

localsend vs cloudreve localsend vs rclone localsend vs copyparty localsend vs files localsend vs yazi localsend vs spacedrive localsend vs nextcloud localsend vs uppy openclaw vs khoj open-webui vs open-notebook open-webui vs khoj appflowy vs affine appflowy vs memos appflowy vs plane appflowy vs joplin mem0 vs memos n8n vs langchain n8n vs browser-use firecrawl vs browser-use n8n vs langgraph n8n vs frigate n8n vs lightpanda n8n vs proxmoxve n8n vs activepieces

More File Management & Sync projects

Compare either of these against the rest of the File Management & Sync field.

cloudreve vs LocalSend cloudreve vs rclone cloudreve vs copyparty cloudreve vs Files cloudreve vs yazi cloudreve vs Spacedrive cloudreve vs Nextcloud cloudreve vs uppy cloudreve vs superfile cloudreve vs ranger cloudreve vs Seafile cloudreve vs PairDrop

Frequently asked questions

Is cloudreve or cryfs more popular?

cloudreve has 28,737 GitHub stars and cryfs has 2,304. cloudreve has the larger community by that measure.

Are cloudreve and cryfs free?

Both are open source. cloudreve is licensed under GPL-3.0 and cryfs under LGPL-3.0. Neither carries a licence fee.

What is the difference between cloudreve and cryfs?

cloudreve is written in Go and cryfs in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, cloudreve or cryfs?

Choose cloudreve if you want the larger community (28,737 stars) or its GPL-3.0 licence terms. Choose cryfs if its feature set, stack or LGPL-3.0 licence fits better. Both are self-hostable.