Features

• Web dashboard — add, view, and remove monitored services from a simple UI, no config file editing required for day-to-day use.
• MongoDB storage — services, check history, and app state are stored in MongoDB via Mongoose, so it scales past what a JSON file comfortably handles and plays nicely with normal backup/replica tooling.
• Discord login — sign in to the dashboard with your Discord account.
• Custom branding — set your own site name, footer text, and upload your own icon/logo from the dashboard. No code or config editing needed.
• Categories — group services (e.g. "Websites", "Game Servers") from the dashboard; both the dashboard and public page show them grouped.
• Hide target addresses — a toggle in Settings that hides each service's URL/host/IP on the public page, showing only its name and status. The dashboard (admin-only) always shows the real address.
• Full status page design — an overall "all systems operational" banner, collapsible category sections with their own operational/degraded badge, per-service uptime bars (last ~50 checks visualized as colored blocks), uptime percentages, and response-time line graphs.
• Edit services from the dashboard — click the pencil icon on any service to edit its name, type, target/IP, port, or category in place, no need to delete and re-add.
• Maintenance windows — schedule maintenance for one, several, or all services with a title, description, and start/end time. Affected services show a "Maintenance" badge instead of online/offline (on the dashboard, public page, and Discord embed) for the duration, and the public page gets a dedicated /maintenance history tab (active, scheduled, and past windows). A one-click 🔧 button on each dashboard service row also starts/ends an instant "ongoing" maintenance window without opening the full form — handy for "I'm working on this right now." You can also start a brand-new service under maintenance right from the add-service form.
• Uptime bar tooltips — hover any block in a service's uptime bar on the public page to see exactly when that check ran and whether it was online or offline.
• Console startup banner — a bordered summary printed on boot with version, Node version, memory, dashboard/status page links, online vs offline service counts, and a persistent "total starts" counter.
• Discord embed matches your dashboard — categories, per-service online/offline status with uptime %, plus an Overview (services online, average uptime) and Performance (avg response time) summary, styled like a proper status dashboard instead of a flat list.
• Discord/social link previews — the public status page includes Open Graph and Twitter Card meta tags, so pasting its link into Discord (or Twitter/Slack/etc.) shows a rich embed with your site name, logo, and live up/down summary instead of a bare link. Only accounts whose ID is listed in ownerIds are let in.
• Public status page at / — anyone with the link can see current status, no login needed.
• Two service types:
  • http — checks a URL, considers 2xx/3xx responses "up"
  • tcp — opens a TCP connection to host:port (works for game servers, databases, or anything listening on a port)
• Discord bot — posts a status embed to a channel and edits that same message on every check cycle, so it doesn't spam the channel.