UptimeCAN I VIBECODE
Instatus?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Instatus is a SaaS platform that combines uptime monitoring, incident response, and status pages into one product, positioning itself as a replacement for three separate DevOps tools. It monitors websites, APIs, cron/heartbeat jobs, SSL certificates, DNS, TCP/UDP, and ping, with checks as frequent as every 30 seconds from multiple global locations and assertions on status codes, response time, keywords, JSON body, and headers, plus response logs and screenshots for debugging. Alerts go out via email, SMS, phone, Slack, Microsoft Teams, Discord, Google Chat, WhatsApp, push, and webhooks, with on-call scheduling and escalation policies. Status pages can be public, private (magic links, IP allowlisting, passwords, Google or SAML SSO), or audience-selected, with custom domains, custom code injection, multi-language support, subscriber notifications, component-level subscriptions, scheduled m
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a self-hosted replacement for Instatus, the all-in-one uptime monitoring, incident response, and status page platform. Workflow: an admin configures monitors (HTTP/HTTPS website and API checks, ping, TCP/UDP, DNS, SSL certificate expiry, cron heartbeat), each with a check interval (down to 30s), a check location, and pass/fail assertions (status code, response time, keyword, JSON body, response header). A scheduler runs checks and records availability and response-time history. On failure the system creates an incident, notifies subscribers and on-call team via email, Slack, Discord, and webhooks, and auto-resolves when the monitor recovers. A public status page shows component uptime, incident timeline, scheduled maintenance windows, and general notices, with email subscriber signup and per-component subscriptions. Requirements — user-facing: admin dashboard for monitors, incidents, and subscribers; customizable public status page with custom-domain support; embeddable status widget; RSS and JSON status API. Technical: Node.js or Go backend, Postgres for state, Redis-backed job queue, worker processes running checks, an alerting module with retries and escalation, server-side-rendered status page. Use a clean, accessible design; do not copy Instatus branding, logo, copy, or UI. Out of scope: SAML SSO, SMS/phone alerts, true multi-region check infrastructure (simulate locations via config), billing, and multi-tenant SaaS features. Include a README with setup steps, environment configuration, and known limitations (single-region checks, no SLA analytics).