StatusPageBuddy: A Free, YAML‑Free Status Page Builder
Patch your status page by replacing Supabase's default SMTP with a custom Resend SMTP to avoid rate limits and spam.
Create a Resend account, verify SPF/DKIM, paste credentials into Supabase Auth SMTP settings, toggle to custom, and test signup flow to ensure emails land in inbox.
Summary
StatusPageBuddy was built to avoid the $29/month cost of Statuspage.io and the YAML/CI complexity of Upptime. It offers a one‑line landing page: "Skip the YAML, the GitHub Actions, and the $29/month bill." The scope decision is that SPB is a public‑facing status page, not a prober; it lacks built‑in HTTP checks, alerting rules, and integrations. The stack uses Next.js 16.2.1, Supabase for Auth, Postgres, and RLS, and Resend for transactional email. The author discovered that Supabase’s default SMTP is rate‑limited and uses a shared domain, causing sign‑up emails to be throttled or spammed. The fix involved creating a Resend account, verifying SPF/DKIM, pasting credentials into Supabase Auth, and toggling to custom SMTP. The multi‑tenant architecture uses an org_members join table and a RLS policy that restricts status_pages rows to orgs the user belongs to.
Key changes
- Eliminates YAML and GitHub Actions for status page setup
- Public page only, no monitoring or alerting features
- Built on Next.js 16.2.1, Supabase Auth, Postgres, RLS, and Resend
- Supabase default SMTP is rate‑limited and uses a shared domain
- Fix: create Resend account, verify SPF/DKIM, paste credentials into Supabase Auth
- Toggle Supabase Auth to custom SMTP to restore email flow
- Multi‑tenant via org_members join table
- RLS policy restricts status_pages rows to orgs the user belongs to