iGotify vs SSHush

1. Receive Push Notifications: iGotify lets users receive notifications directly from a Gotify server on their iPhone or iPad. These notifications can be used for various applications and integrations like Proxmox and Uptime Kuma. 2. Biometric Security Feature: The app adds an extra layer of security by allowing access to be locked with biometric features like Face ID or Touch ID. This protects sensitive notifications from unauthorized access. 3. Custom Sounds: iGotify allows configuring custom sounds for different notification priority levels. This offers a clear distinction between important and less urgent notifications. 4. Markdown Support: Notifications formatted in Markdown are fully supported. This allows sending and displaying structured and visually appealing notifications. 5. Message Decryption: iGotify decrypts received messages using a public key generated on the iOS device. This ensures the security and confidentiality of the notifications. 6. Multi-User Support: The app supports multiple users, which is particularly useful in environments where several individuals need to receive notifications from one or more Gotify servers. 7. Docker Integration: The app seamlessly works with Docker instances and facilitates the setup of local and remote Gotify servers powered by Docker containers. Users can manage multiple servers and instances through the app. 8. Multi-Language Support: iGotify supports multiple languages, including English, German, Spanish, Italian, and Dutch, making it accessible to an international user base. Find the plugin guide for receiving messages at https://github.com/androidseb25/iGotify-Notification-Assistent

3am. Your phone is face down in a drawer, on battery, in Low Power Mode. /var crosses 95%. You get woken up. That sentence is the entire product, and it is harder to deliver than it looks. An alert computed on your phone can only fire when iOS chooses to wake your phone, and iOS makes no guarantee that it ever will. Background execution is throttled on battery, suspended in Low Power Mode, stopped completely by a force quit, and starved hardest overnight - precisely when you need it. Worse, it fails in silence. You see your thresholds configured and you assume you are covered. TWO SYSTEMS, DELIBERATELY SEPARATE Live metrics come from your phone's own SSH session. Open the app, it connects, you see the server as it is right now. Alerting is a different system entirely. A small agent runs on your server and reports outward on its own schedule, independently of your phone. It does not care whether the app is open, backgrounded, force-quit or deleted from your home screen. A threshold breach originates on the server and arrives as a real push notification. If a server card shows as offline, that describes your phone's SSH connection. It says nothing about your alerting, which is still running. Your server speaks. Your phone listens. Nothing in between. Everything a monitoring platform does about a crossed threshold. None of the platform. No dashboard to host. No port to expose. No domain, no reverse proxy, no account. No platform sitting between your servers and you. No other iOS app does this. Every alternative either computes its alerts on the phone, which iOS can throttle or stop without telling you, or asks you to stand up and secure a dashboard of your own, or routes you through a monitoring platform with an account and a seat. FREE, AND NOT A TRIAL Unlimited servers. Full metrics. No agent, no account, no signup. Per-core CPU, temperature, memory, swap, disk by mount, load average, network interfaces. A full SSH terminal. Your servers sync across your devices through iCloud. This tier is agentless and always will be. Nothing is installed on anything. ALERTING, AS A SUBSCRIPTION Enable it on a server and the app installs the agent over the SSH connection you already have. There is nothing to sign up for and nothing to go and look at afterwards. Rules are configured in the app: CPU, memory, swap, disk per mount point, load average, temperature, interface down. And silence. If the agent stops reporting, you hear about it - the failure a monitoring system exists to catch, and the one a check on your phone can never see, because a sleeping phone and a dead server look identical from the inside. Every rule fires on sustained breach, not on a momentary spike. READ EVERY LINE BEFORE YOU INSTALL IT Alerting asks something real of you: a binary, on your server. You should not agree to that on trust. The agent is open source, Apache 2.0. github.com/ultra-nick/sshush-agent It runs as an unprivileged user, never as root, under systemd restrictions that make your filesystem read-only to it apart from one directory. It never listens on a port. It never executes a remote command. It never downloads anything, ever. Its whole network footprint is two URLs you can read in a config file. Metrics are sampled and rules evaluated on your server. Only a crossed threshold is ever sent. The numbers never leave the machine. Nothing else is touched. No package manager integration, no cron entry, no existing file modified. One command removes it completely, or the app asks it to remove itself. Your SSH credentials never leave your device. They live in your iCloud Keychain. Our infrastructure has never held an SSH credential and is not built to. Monitoring is free, unlimited and agentless. Alerting is there when silence stops being acceptable. --- Requirements: iOS 26.0 or later. iCloud syncs your servers and alert history across your devices. Terms of Use: https://www.apple.com/legal/internet-services/itunes/dev/stdeula/