Beszel vs Mast Pager

Meet Beszel Companion – Your ultimate server management app for iOS! Note: A Beszel instance (https://beszel.dev) is required to use this app. Multi-Instance Support: Securely connect to and seamlessly switch between multiple Beszel hub instances. Perfect for managing work, home, and personal projects all in one place. Real-Time System Stats: Monitor your server's CPU usage, memory load, and system temperatures with beautiful, interactive charts. Docker Container Monitoring: Keep a close eye on the resource usage of all your running containers. Drill down into individual container performance with detailed graphs. Customizable Dashboard: Pin your most important system or container charts to a personalized "Home" screen for at-a-glance visibility of what matters most to you. Home Screen Widgets: Configure widgets to display key system metrics from any of your instances directly on your home screen. Native iOS Experience: Enjoy a fast, clean, and intuitive interface that supports Dark Mode and feels right at home on your device. Flexible Time Ranges: Analyze data from the last hour up to the last 30 days to track trends and diagnose issues. 100% Private, No Telemetry: Beszel Companion is designed with your privacy as the top priority. The app connects directly to your hub instances and collects absolutely no data, analytics, or telemetry. All your credentials and server information stay securely on your device.

Mast turns your iPhone into a pager, for one person who is the whole on-call rotation or a team with one. Pages re-alert until you acknowledge them, and silent cron jobs page you when they stop. Create a channel in the app and it hands you a URL; from then on, anything that can make an HTTP request can page you: a deploy script, a backup job, the error handler in your API. curl -d "disk 92% on db1" https://mast.tissue.dev/mk_9f2a41c8b7 No account, no sign-up: install the app and that is the whole setup. The phone itself is the credential, and the channel address is the only secret. That first rung, Try it out, is two channels, one vital and a thousand messages a month on this phone. An email address gets you Free: five channels, five vitals, five probes and ten thousand messages a month, with a week of history. Solo, Team and Company add more phones, an on-call rotation, escalation to the next person and longer history. They come with a Tissue Mast account on tissue.systems, and the app joins that account. HOW LOUD, CHANNEL BY CHANNEL Every message carries a priority, and the priority is what the notification does to the phone. The default comes from the channel, and so does the ceiling: a sender can name a priority per message but never one above it. - quiet: no sound, no banner. The feed records it and the phone stays dark. - normal: a banner and a sound. The ringer switch, Focus, and the channel's quiet hours all still apply. - loud: time-sensitive, so it breaks through Focus. One alert, no repeat, for problems that need eyes soon but should not wake anyone. - page: the pager tier. It re-alerts every two minutes until you acknowledge it, sounds through the ringer switch on a phone with critical alerts turned on, and a page you have not acknowledged moves on to the one other phone the channel names. THE WATCH BELL A channel can also be a vital: it alerts when the posts stop. Your cron job or backup script checks in on a schedule, and silence past the schedule plus a grace window is what raises the alarm. The next check-in closes the page the silence opened. The feed and a home-screen widget both draw every vital as a dot, late ones marked. WHEN A PAGE GOES UNANSWERED A page breaks through Focus, Sleep included, and sounds through the ringer switch once critical alerts are turned on — one switch in the app, off until you turn it on. It stays on the lock screen and in the Dynamic Island until it is acknowledged. Acknowledge it from the notification, from the app, by asking Siri, from the Action button or a Shortcut. Resolve and Mute channel 1h sit beside Acknowledge on the notification, and none asks for Face ID. Pair with one other person's Mast — a QR code scanned by the other phone — and an unacknowledged page moves on to them. A pause is the only thing that holds a page: name a length, and pages land silently until the window ends and everything unanswered rings at full volume. A STORM IS ONE LINE Send a message with a key and a repeat of that key inside the channel's dedupe window lands once; a channel that floods collapses into one row that counts up in place. A page is never the one folded away, and it ignores mute and quiet hours, so a flapping check cannot bury a real one. EVERY PAGE KEEPS ITS RECORD Each message carries its own log: fired, repeated and how many times, escalated, acknowledged and by which device, resolved. A script holding only the channel address can read back what became of its message, so a deploy can page you and wait for the tap. A monitor that knows the outage is over can close the page it opened. RUNS APART FROM WHAT IT WATCHES A downtime alert that runs on the machine having the downtime dies with it. Mast's server side runs on tissue.systems, in a different failure domain from whatever it is watching. Home Assistant pages you through the hass-mast integration. Mast is for iPhone; pages reach a paired Apple Watch through notification forwarding.