Status Page for Indie SaaS
A simple hosted status page with components, incident updates, scheduled maintenance and subscriber email notices, priced for one-person SaaS.
Economics
- Pricing example
- $9/month per page (free: 1 page with a small credit link, no email notices)
- Daily math
- 67 pages x $9/month = about $600/month, or $20/day.
- Target if you hit the daily math
- Target: $600 / month at about 67 paid pages
Audience and urgency
Audience: Indie SaaS founders, API providers and small dev teams.
Urgency: When something breaks, customers flood support asking whether it's down. A status page answers that in one place, but larger tools are priced for bigger teams.
MVP scope
- ✓ Components with status (operational, degraded, partial outage, major outage)
- ✓ Incidents with timestamped updates and scheduled maintenance windows
- ✓ Subscriber emails with double opt-in for incidents and maintenance
- ✓ Optional HTTP checks every 5 minutes that suggest an incident for the owner to confirm (never auto-post)
- ✓ 90-day history bars from your own incident records; Stripe subscription
Omitted features
- - Do NOT auto-publish incidents without the owner confirming
- - Do NOT build SMS or phone alerts
- - Do NOT build custom domains in Day 1 (subdomain only)
Suggested stack
- Frontend
- Next.js + Tailwind CSS
- Backend or API
- Postgres (Supabase) + scheduled checker function + Resend for emails
- Payments
- Stripe Billing
- Hosting
- Vercel or Netlify (free tier to start)
Repository metadata
- Blueprint ID
indie-status-page- Category ID
dev_tools- Monetization ID
micro_subscription
Day-one distribution
Channels
- Indie hacker communities on X (Twitter)
- Reddit r/SaaS and r/indiehackers (follow rules)
- Hacker News 'Show HN'
Reddit strategy
Offer the free tier and a short write-up on what to say during an outage.
Cold outreach or directory hook
Set up free status pages for 10 small SaaS products and ask for feedback.
Search keywords
status page for saas, cheap status page, hosted status page
One-shot master prompt
Build a "Status Page" SaaS in Next.js with Tailwind CSS, Supabase and Resend. Core requirements: 1. Owner dashboard (magic link): page name, logo, slug, components with groups and current status. 2. Incidents: title, affected components, status (investigating, identified, monitoring, resolved) and timestamped updates; scheduled maintenance with start/end times. 3. Public page /[slug]: overall status banner, components, active incidents, upcoming maintenance, 90-day history bars computed from incident records, and an Atom feed. 4. Subscribers: email sign-up with double opt-in; emails sent on new incidents, updates and resolution via Resend; one-click unsubscribe. 5. Optional HTTP check per component every 5 minutes (scheduled function); 3 failures in a row create a draft incident and email the owner to confirm. Stripe Billing ($9/month) unlocks emails and removes the credit link.
Comparable products
Published 2026-10-08.
Related blueprints
Changelog Page from GitHub ReleasesConnect a repository and get a hosted, branded changelog page, RSS feed and a small 'What's new' widget generated from your GitHub releases.Cron Job Heartbeat MonitorGive each scheduled job a ping URL and get an email or Telegram alert when it fails or does not check in on time.Email Test Inbox for DevelopersPoint a staging app's SMTP settings at a shared test inbox, and preview every caught email's HTML, text, headers and links without any of them reaching real users.Env File Diff & Validator CLICompare .env files across local, staging and production and validate them against a schema in CI, without ever printing secret values.