PushPortPush Notification Relay for self-hosted apps

One relay holds the transport credentials, so every self-hosted backend can deliver.

What is PushPort?

Run the server

GitHub

One Binary, Every Transport

One Go binary, embedded SQLite, one send API for APNs, FCM, and WebPush.

Encrypted and Sealed

End-to-end encrypted, so the relay never reads your payloads. Each device gets its own unguessable endpoint.

Multi-Tenant with Guardrails

Many isolated apps on one relay, each with its own rate limits and quotas.

Get started

# write the two required secrets to .env (bare KEY=value, no quotes)
cat > .env <<EOF
PUSHPORT_ADMIN_TOKEN=$(openssl rand -hex 32)
PUSHPORT_SECRET=$(openssl rand -base64 32)
EOF

# run the relay (SQLite lives in ./pushport/data on the host)
mkdir -p pushport/data
docker run -d --name pushport \
  -p 8080:8080 -v "$(pwd)/pushport/data:/app/data" \
  --env-file .env \
  muniftanjim/pushport:latest

The full walkthrough is in Installation.

How a push travels

1 · Register

The admin creates an app and sets the transport credentials: APNs .p8, FCM service account, VAPID private key.

2 · Connect

Self-hosted backends register as instances and get a token. Devices subscribe and receive a sealed push endpoint.

3 · Push

The backend POSTs an encrypted payload to the push endpoint. PushPort relays to APNs, FCM, or WebPush service.