Djinn Relay · Push for self-hosted servers · Beta
Phone notifications from a server you run yourself.
The official DjinnChat apps can only be woken up with our push identity, so a self-hosted server cannot reach them on its own. Relay forwards your server's notifications to the apps. Your server, database and conversations stay where they are.
01
You keep the server
DjinnChat, its database, keys, files and conversations remain on your infrastructure. Relay never runs your workspace.
02
Only notifications cross us
Your server sends each notification to Relay, which hands it to the app store push service. Chat traffic never passes through Relay.
03
Remote access is yours to choose
To reach your server from outside your network, use a VPS, Tailscale Funnel or Cloudflare Tunnel. The server setup guide walks through each one.
A narrow trust boundary
We deliver the notification. We do not keep it.
Delivering a notification means we handle the device token and, unless you turn on IDs-only mode, its title and body. Neither is logged or stored; to count push users we keep only a keyed hash of each token for about two months. In IDs-only mode the notification carries only identifiers, never message text.
Beta status: forwarding is tested with the Android app. The mobile apps are not in the stores yet, and iOS delivery follows the App Store release. Billing is not switched on, so no payment is collected.
What we store
Running the service and the plan needs a little data. We list it plainly instead of calling the service anonymous.
- Account email, password hash and billing details
- Your installation name and its relay credential
- Daily delivery counts per installation
- A keyed hash of each person who got a notification this month, to count people without knowing who they are
Self-hosting stays free. Relay is only for push.
You do not need Relay to run DjinnChat. You need it when your team wants notifications on the official mobile apps.
Set up your server