message-server

Signal Server is the official open-source backend for the Signal secure messaging protocol, providing the server-side infrastructure that routes messages and…

  • Communication
  • Tools & Utilities
Signal Server is the official open-source backend for the Signal secure messaging protocol, providing the server-side infrastructure that routes messages and synchronises state for Signal clients. It runs the core services that let users exchange end-to-end encrypted messages, and is intended for people who want to operate their own Signal server stack. FoundationDB is a required dependency for building and running it.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
100last commit 16 days ago
Popular
8110,769 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
201 serious finding, 3 minor, CI, tests
GitHub stars
10,769
Open issues
4
Last commit
2026-11-04
License
AGPL-3.0
Activity
declining

Checked 16 days ago - source: GitHub (signalapp/Signal-Server)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the message package Run npm install sveltekit-flash-message before writing code; npm is the tool that downloads the helper files the app needs. Without it, the flash-message imports will be missing and the app won't start. source
  • Wire up flash messages In the app's shared layout files, wrap the server-side page data function with loadFlash and display getFlash. If you skip this, one-time success or error notices won't show up after a page reloads. source
  • Add messages on redirects Use the flash-message redirect helper when finishing a form or server action. This attaches the one-time message to the next page, while a normal redirect would send the user there without the note. source
  • Required dependency Signal Server uses FoundationDB and requires the FoundationDB client library to be installed on the host system before building or running the server. source

Fetched 42 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which port should I check if the Samba POS message service appears unavailable?

Check the messaging service tool and verify the service on port 9000.

What symptom can appear after a failed Samba POS message server connection test?

The Samba Market store may not show the activation button.

What must I install before using sveltekit-flash-message imports?

Run npm install sveltekit-flash-message before writing code; otherwise the imports are missing and the app won't start.

Where do I wire up sveltekit-flash-message so one-time notices appear after a reload?

In the shared layout files, wrap the server-side page data function with loadFlash and display getFlash.

How do I attach a one-time message to the next page after a form submission?

Use the flash-message redirect helper when finishing a form or server action.

Answers sourced from forum.sambapos.com, forum.sambapos.com, github.com, github.com, github.com

Community

Collected 48 days ago - public community threads