head to head · open source

Signal vs rememory

Signal has 29,359 GitHub stars, 6,890 forks, 498 open issues and last shipped yesterday. rememory has 1,452 stars, 79 forks, 20 open issues and last shipped 14 days ago. Signal leads on adoption by 1,922% (29,359 vs 1,452 stars). Signal is written in Kotlin under AGPL-3.0; rememory is written in Go under Apache-2.0. Signal has attracted 23% as many forks as stars, rememory 5%. Signal 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.

Signal ★ 29K rememory ★ 1.5K category Security & Privacy

← all 15422 open source comparisons

Side by side

Signal rememory
GitHub stars ★ 29K ★ 1.5K
License AGPL-3.0 Apache-2.0
Written in Kotlin Go
Last push 2026-09-18 2026-09-05
Forks ⑂ 6.9K ⑂ 79
Self-hosting Yes Yes
Data ownership Your server Your server

pick Signal if

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

full Signal 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 Signal

Signal Android is a secure messaging application for Android devices that delivers private communication via end to end encryption. Developed by Signal Messenger, LLC, it operates within the broader Signal ecosystem, which includes official iOS and desktop clients. The app uses mobile data or Wi Fi to send and receive encrypted messages, voice calls, and video calls without relying on traditional SMS or telephony infrastructure.

read the full Signal 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 signal mattermost vs signal signal vs ente puter vs mattermost mattermost vs nextcloud puter vs ente mattermost vs ente mattermost vs zulip supabase vs better-auth keycloak vs jumpserver keycloak vs better-auth keycloak vs authentik jumpserver vs better-auth jumpserver vs authentik better-auth vs authentik jumpserver vs teleport puter vs vault mattermost vs vault keycloak vs vault vault vs infisical puter vs unkey mattermost vs unkey puter vs phase puter vs keyshade

More Data Security & Privacy projects

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

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

Frequently asked questions

Is Signal or rememory more popular?

Signal has 29,359 GitHub stars and rememory has 1,452. Signal has the larger community by that measure.

Are Signal and rememory free?

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

What is the difference between Signal and rememory?

Signal is written in Kotlin 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, Signal or rememory?

Choose Signal if you want the larger community (29,359 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.