head to head · open source

Peergos vs rememory

Peergos has 2,524 GitHub stars, 199 forks, 103 open issues and last shipped yesterday. rememory has 1,452 stars, 79 forks, 20 open issues and last shipped yesterday. Peergos leads on adoption by 74% (2,524 vs 1,452 stars). Peergos is written in Java under AGPL-3.0; rememory is written in Go under Apache-2.0. Peergos has attracted 8% as many forks as stars, rememory 5%. Peergos was the more recently maintained of the two, and both are self-hostable with no licence fee.

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

Peergos ★ 2.5K rememory ★ 1.5K category Security & Privacy

← all 20902 open source comparisons

Side by side

Peergos rememory
GitHub stars ★ 2.5K ★ 1.5K
License AGPL-3.0 Apache-2.0
Written in Java Go
Last push 2026-09-19 2026-09-19
Forks ⑂ 199 ⑂ 79
Self-hosting Yes Yes
Data ownership Your server Your server

pick Peergos if

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

full Peergos profile →

pick rememory if

  • You want the rememory feature set and don't need the biggest community
  • You prefer the Apache-2.0 license terms
  • Your stack matches Go
  • You evaluated both and rememory fits your workflow better

full rememory profile →

About Peergos

Peergos is a peer to peer secure file storage system, social network, and application protocol built in Java under AGPL 3.0. It lives in the IPFS, IPLD, and libp2p ecosystem and supports a private web where users control their data, decide where it is stored, and determine who can see it. The project addresses centralized services that can track users, expose personal data, and observe relationships or file contents without cryptographic access control.

read the full Peergos overview →

About rememory

ReMemory is an Apache 2.0 licensed encryption tool written in Go that seals your files with age encryption, splits the decryption key into separate pieces held by people you trust, and lets a threshold of those people unlock the archive together without any server being involved.

read the full rememory overview →

More in Security & Privacy

PayloadsAllTheThings ★ 81K Puter ★ 44K Mattermost ★ 39K Keycloak ★ 37K Tailscale ★ 37K HashiCorp Vault ★ 36K

Related comparisons

puter vs mattermost mattermost vs nextcloud puter vs signal puter vs ente mattermost vs signal mattermost vs ente mattermost vs zulip signal vs ente supabase vs better-auth keycloak vs jumpserver keycloak vs better-auth keycloak vs authelia keycloak vs authentik jumpserver vs better-auth jumpserver vs authelia better-auth vs authelia payloadsallthethings vs vault vaultwarden vs vault payloadsallthethings vs unkey payloadsallthethings vs phase payloadsallthethings vs keyshade puter vs vault mattermost vs vault keycloak vs vault

More Data Security & Privacy projects

Compare either of these against the rest of the Data Security & Privacy field.

Peergos vs Puter Peergos vs Mattermost Peergos vs Signal Peergos vs Ente Peergos vs Element Peergos vs Fluxer Peergos vs certificates Peergos vs Tuta Peergos vs Zen Peergos vs Cinny Peergos vs Certipy Peergos vs Stoat

Frequently asked questions

Is Peergos or rememory more popular?

Peergos has 2,524 GitHub stars and rememory has 1,452. Peergos has the larger community by that measure.

Are Peergos and rememory free?

Both are open source. Peergos is licensed under AGPL-3.0 and rememory under Apache-2.0. Neither carries a licence fee.

What is the difference between Peergos and rememory?

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

Which should I choose, Peergos or rememory?

Choose Peergos if you want the larger community (2,524 stars) or its AGPL-3.0 licence terms. Choose rememory if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.