One inbox for your homelab's notifications: the noise bundled, only what matters on your phone.
434
The filter for your homelab's notifications. Every service wants to tell you something: Proxmox about its backups, Watchtower about every container update, Uptime Kuma about every hiccup, the NAS about its disks. Sooner or later the phone buzzes so often that you stop looking. That is notification fatigue, and it is how the one alert that matters gets missed.
nexsift collects the alerts of all your services in one inbox, sorts them, bundles the noise and passes on only what matters: to your phone, or wherever you want it.
It is not another push server. ntfy and Gotify deliver every message they are given. nexsift sits in front of them: your services report to nexsift, and nexsift decides what is worth a push. That push then goes out through the ntfy, Gotify, Telegram, Pushover or Apprise you already use, or straight to the phone as a Web Push notification without any extra app.
| Without nexsift | With nexsift |
|---|---|
| 30 container updates, 30 pushes | one line "Watchtower: 30 containers updated", no push |
| a failed backup, somewhere in the noise | a red line on top, one push at once, an all-clear when it works again |
| every service with its own push setup | every service reports to nexsift, the phone is set up once |
Senders need no plugin and no change. To make that possible, nexsift answers like the services they already know: a Gotify server, an ntfy server, a Discord webhook, a mail server, a syslog server, or a plain webhook.

The inbox. Problems on top, each with where it came from, why it is critical and whether it reached the phone.

Routine from one source in one line, whatever the titles. Nothing of it rang the phone.

Adding a source: pick the sender, and nexsift shows exactly what to enter there, with values to copy.

Rules decide level, bundling and push. Try a message against them before it arrives.
title, message and priority work, and so do the field names most
senders already use (text, body, severity, level, status, …)POST /message), for Watchtower and everything else built on shoutrrrPOST /<topic>), including the subscription Home Assistant's ntfy integration opensIcon header) wins.? shows them).common and organizations), Keycloak, Authelia, Pocket ID and the like, several side by
side, each with its own button. For authentik there is a one-button setup (or a blueprint to import). The account
is linked to a provider once, signed in, under Settings, Account; from then on exactly that identity gets in, and
the password can be switched off. If the provider fails, python -m app.reset_password in the container switches
it back on.GET /api/v1/status (unread, open critical, messages today, …) and GET /api/v1/threads (newest lines, titles
only), with Authorization: Bearer nxs_….services:
nexsift:
image: ghcr.io/derkezorm/nexsift:latest
container_name: nexsift
restart: unless-stopped
ports:
- "8490:8000" # interface, webhooks, Discord-style webhooks
- "8491:8001" # Gotify API
- "8492:8002" # ntfy API
- "25:2525" # SMTP, no sign-in
- "514:5514/udp" # syslog
- "514:5514/tcp"
volumes:
- ./data:/data
environment:
PUID: 1000
PGID: 1000
TZ: Europe/Berlin
NEXSIFT_PUBLIC_PORTS: "web=8490,gotify=8491,ntfy=8492,smtp=25,syslog=514"
docker compose up -d
Open http://<your-host>:8490 and create the operator account (a password of at least 12 characters). Then add
the first source; the dialog shows what to enter in the sender. The docker-compose.yml in
this repository explains every line.
Remove a port line to close that door. If a host port is taken, use another one on the left and say so in
NEXSIFT_PUBLIC_PORTS, so the setup hints show the right numbers.
Put the interface (port 8490) behind a reverse proxy with TLS if you open it beyond your own network. The other doors are meant for the devices in your network.
id over SSH and put them into PUID and PGID. The first administrator is
often 1026, later users are not.sudo synoacltool -del /volume1/docker/nexsift/data, then sudo chown -R <uid>:<gid> on the same folder.NEXSIFT_PUBLIC_PORTS.Set two addresses under Settings: the public address you type in the browser (https://nexsift.example.com),
and the address for senders at home (192.168.1.10). Syslog, email and the Gotify and ntfy doors do not go
through a proxy, so the setup hints have to send the devices to nexsift directly.
If the proxy ends TLS, nexsift itself only sees http. It believes the proxy's X-Forwarded-For and
X-Forwarded-Proto only from the addresses you list in NEXSIFT_TRUSTED_PROXIES, never from anybody else. Out of
the box the list is empty and nobody is believed, not even 127.0.0.1. Put the proxy's address or network there: a
proxy in another container shows up with its address in the Docker network, one on the same host with host
networking as 127.0.0.1. Otherwise the authentik card under Settings, Sign-in warns that the address nexsift sees
differs from the one in your browser, the sign-in cookie has no Secure flag, and every visitor counts as the proxy
for the sign-in brake. The authentik button
never registers a guessed address: without a public address it offers the one your browser uses and registers
exactly that.
Everything lives in /data. Mount it from a local disk, never from an SMB or NFS share; SQLite's locking does not
hold up over network filesystems.
| Path | What |
|---|---|
nexsift.db | The SQLite database: sources, rules, targets, messages, settings |
secret.key | Protects the stored secrets: source tokens, push target credentials, the OIDC client secret, the Web Push key pair |
backups/ | Copies of the database with a small .json next to each (version, kind, note, counts) |
backups/restore-pending/ | Only for a moment: a checked archive waiting for the next start |
logs/nexsift.log | The log; rolls over at 5 MB, three older files, gone after 14 days |
The copies in backups/ lie on the same disk as the database. A real backup is the archive you download under
Settings, Backup, kept somewhere else; it holds nexsift.db and secret.key. Without its password nobody opens it.
A restore happens at the next start: nexsift ends itself after the upload and comes back through
restart: unless-stopped. It also ends with exit code 3, so restart: on-failure brings it back too. All browsers
are signed out afterwards.
Forgot the password? In the container: python -m app.reset_password.
| Variable | Default | Meaning |
|---|---|---|
NEXSIFT_DATA_DIR | /data | Data directory |
NEXSIFT_SECRET_KEY | created on first start | Protects the stored secrets; when set, it wins over secret.key |
NEXSIFT_PUBLIC_URL | from the request | The address people and senders use to reach nexsift; for the setup hints and the redirect address of the sign-in providers (/api/oidc/<short name>/callback; a provider set up in 0.11 or before keeps /api/oidc/callback). The setting under Settings wins when set |
NEXSIFT_PUBLIC_PORTS | the inner ports | The ports as seen from outside, for the setup hints: web=8490,gotify=8491,ntfy=8492,smtp=25,syslog=514 |
NEXSIFT_TRUSTED_PROXIES | none | Addresses or networks of reverse proxies whose X-Forwarded-For and X-Forwarded-Proto are believed, comma separated. Only they can tell nexsift that a request came in over https. Empty trusts nobody, 127.0.0.1 included; a proxy on the same host with host networking needs 127.0.0.1 here |
NEXSIFT_SESSION_DAYS | 30 | A browser session ends after this many days |
NEXSIFT_COOKIE_SECURE | auto | on, off or auto (from the request; X-Forwarded-Proto only from a trusted proxy) |
NEXSIFT_LOG_LEVEL | empty | Usually left out: the level is set under Settings, Log. When set (quiet, normal, detailed, trace, or WARNING, INFO, DEBUG) it wins and the interface cannot change it; the way out when nexsift does not even start |
NEXSIFT_API_DOCS | false | Serves /api/docs and /api/openapi.json |
NEXSIFT_GOTIFY_PORT, NEXSIFT_NTFY_PORT, NEXSIFT_SMTP_PORT, NEXSIFT_SYSLOG_PORT | 8001, 8002, 2525, 5514 | Ports inside the container; 0 turns that door off |
PUID, PGID | 1000 | Owner of the files in the data directory |
X-Requested-By: nexsift.X-Frame-Options: DENY and friends.http and https./api/v1, and only while the switch under Settings, API keys is on. Only their
hash is stored. A signed-in browser does not get into /api/v1.cd backend && python -m venv .venv && .venv/Scripts/pip install -r requirements-dev.txt
NEXSIFT_WEB_PORT=8490 .venv/Scripts/python -m app.serve
cd frontend && npm ci && npm run dev
The frontend on port 5480 proxies /api to http://127.0.0.1:8490 (another address with NEXSIFT_API).
Tests: pytest in backend, npm test in frontend.
AGPL-3.0.
Content type
Image
Digest
sha256:b265dd3d9…
Size
78.1 MB
Last updated
about 22 hours ago
docker pull derkezorm/nexsift