Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS (by signalapp)


Basic Signal-Server repo stats
about 9 hours ago

signalapp/Signal-Server is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.

Signal-Server Alternatives

Similar projects and alternatives to Signal-Server

  • GitHub repo TextSecure

    A private messenger for Android.

  • GitHub repo Synapse

    Synapse: Matrix reference homeserver

  • GitHub repo session-desktop

    Session Desktop - Onion routing based messenger

  • GitHub repo LibreSignal

    LibreSignal • The truly private and Google-Free messenger for Android.

  • GitHub repo Signal-iOS

    A private messenger for iOS.

  • GitHub repo fog

    Private payments for mobile devices. (by mobilecoinfoundation)

  • GitHub repo Signal-Desktop

    Signal — Private Messenger for Windows, Mac, and Linux

  • GitHub repo mobilecoin

    Private payments for mobile devices.

  • GitHub repo Mechanics-of-MobileCoin

    Technical exploration of the MobileCoin cryptocurrency

  • GitHub repo tdesktop

    Telegram Desktop messaging app

  • GitHub repo bbs

    Forum for discussing Internet censorship circumvention

  • GitHub repo Signal-TLS-Proxy

  • GitHub repo Vector

    A glossy Matrix collaboration client for the web.

  • GitHub repo td

    Cross-platform library for building Telegram clients

  • GitHub repo status-react

    a free (libre) open source, mobile OS for Ethereum

  • GitHub repo matrix-doc

    Matrix Documentation (including The Spec)

  • GitHub repo Signal-Android

    Patches to Signal for Android removing dependencies on closed-source Google Mobile Services and Firebase libraries. In branches whose names include "-FOSS". Uses new "foss" or "gms" flavor dimension: build with "./gradlew assemblePlayFossProdRelease". (by tw-hx)

  • GitHub repo jami-cli

    Jami client for terminal

  • GitHub repo zre_raft

    Experiment with ZRE and Raft

NOTE: The number of mentions on this list indicates mentions on common posts. Hence, a higher number means a better Signal-Server alternative or higher similarity.


Posts where Signal-Server has been mentioned. We have used some of these posts to build our list of alternatives and similar projects - the last one was on 2021-04-15.
  • The Evil Business Model of Facebook's WhatsApp (10 mins comedy deep dive)
    Funnily enough, when they got all the criticism after announcing this new "feature" they immediately updated the Signal-Server source code on GitHub, something they hadn't done in months:
  • Is Element/Riot ( a suitable replacement for Whatsapp ?
    There's no way to verify published server code is actually running unless you're an admin and can go see it for yourself, but they're finally back to updating it on GitHub - And their servers don't have full access to your contact list either. Your device basically sends truncated hashed phone numbers to the server to check if a certain contact is registered on Signal. All the server actually has on you is a phone number and when you registered that on the platform, really -
  • Will there ever be an option to use signal without a phone number? | 2021-04-14
    Side note: Commit for message abuse (I went to look through the last few commits myself before looking for the community forums and found this)
  • Thoughts on DropWizard? | 2021-04-14
    Signal's server project works on top of Dropwizard, if you want to have a look:
  • Update on beta testing payments in Signal | 2021-04-13
    > I am 99% sure they did.


    > I can't say affirmatively that anyone is running anything exactly

    Signal provides a means for reproducing Android builds so you can affirmatively determine what you're running.

    > but they now claim they did.

    Signal claims they shipped server updates without releasing code? Do you have a link to that?

    When others were complaining about the lack of an update to server, they're complaining about the client and server APIs being out of sync. Reading through these comments, I don't get the impression that the server code published is what's actually running. In fact the following comment even refers to it as a reference implementation:

    At the end of the day, it doesn't really matter much what server code is running since the Clients manage encryption and the Server has no insight into the messages being exchanged. | 2021-04-13
    I noted this in another comment, but if they _did not_ update the code in production, they ran with known vulnerabilities in the server side for many months:

    There's no good option here. | 2021-04-13
    Yes, they were. There has been multiple "releases" too, with version numbers, which I assume went into production.

    When you're using a product for which you can't get the source code, the product is not open source.

    Commits: No push between: April 20, 2020 and April 6, 2021.

  • Signal Server code on GitHub up-to-date again | 2021-04-08
  • Signal Server code on GitHub is up-to-date again | 2021-04-08
  • Signal-Server: Bump version to 5.48 | 2021-04-08
  • Moxie has responded on the delayed push of the Server source | 2021-04-08
    As much as I would like to trust Moxie, I have to ask, how come that exactly the first commit after the de-publication in april 2020 is signalapp/[email protected] which introduces parts of the crypto payment feature? (spotted by bwildenhain on GitHub) Also Signal is gonna get a big donation after integrating the crypto from MobileCoin. And they kept quite about all of that for a year...
  • Bought MOBILECOIN? You might have been SCAMMED - 37.5 MILLION coins were PRIVATELY sold at 80 CENT per coin | 2021-04-07
    In general you seem right though: This seems like a more obviously major milestone for the feature (so clients can start implementing): | 2021-04-07
    Oldest commit:
  • Signal Server code on GitHub is up to date again