SitePulse

Launched SitePulse 8 days ago. Here's an honest week-1 debrief.

Numbers

• 32 unique visitors, 81 page views (last 7 days via Vercel Analytics)

• - Traffic from US, Taiwan, France, Netherlands

• - Referrers: chatgpt.com, github.com, direct

• - Paying users: 0

• - Free signups: 3 (all my own test accounts)

No external customers yet. But the SEO content is getting early crawls and the comparison pages (/vs/uptimerobot, /vs/betterstack) are indexed.

What I shipped for launch

• Uptime monitoring with 1-min checks (Pro) and 5-min checks (Free)

• - SSL certificate monitoring with 14-day expiry alerts

• - Free public status page on every plan (sitepulse.satosushi.co/status/your-slug)

• - 30-day uptime history calculated automatically

• - Email alerts on down/recovery

What I tried this week

• Posted to r/SideProject and r/devops today

• - Product Hunt draft ready (scheduling for May 6)

• - Show HN prepared but blocked by karma restriction

• - Reached out to 3 newsletters (console.dev, DevOps Weekly, Changelog)

What I'm doing next

The 0-customer problem is a distribution problem, not a product problem (I think). My plan:

1. Reddit + communities — posting in r/SideProject, r/devops, r/webdev (Saturday) today

2. 2. Product Hunt launch — May 6

3. 3. Direct outreach — DM indie hackers who complain about UptimeRobot on Twitter

4. 4. SEO content — already have 4 blog posts indexed, adding more /vs/ pages

The product works. Now I need to find the 10 people who'll actually use it.

Would love feedback — especially from anyone who's been through early distribution on a devtools/infrastructure product. What worked for you?

https://sitepulse.satosushi.co — free tier, 5 monitors, no credit card.

After spending too long staring at UptimeRobot's 2014 UI and bouncing off BetterStack's per-seat pricing, I shipped my own uptime monitor: SitePulse.

🌐 https://sitepulse.satosushi.co

## The problem

Every uptime tool I tried felt wrong for an indie SaaS:

- UptimeRobot — solid, but the dashboard hasn't been redesigned in a decade.

- BetterStack — gorgeous, but $30/mo per seat scales fast.

- Pingdom — $15/mo for 10 monitors. No thanks.

I wanted Vercel-style polish + flat pricing + a status page that doesn't look like 2014.

## What I built

- Free: 5 monitors, 5-min checks, email alerts, public status page

- Pro $9/mo: 25 monitors, 1-min checks, 90-day history

- Business $29/mo: 150 monitors, 1-yr history

- Flat pricing. No per-seat. No surprise add-ons.

## What's different

- 60-second setup — paste URL, click save, you're done.

- Public status page on every plan (BetterStack charges for this).

- `/status/<your-slug>` — auto-generated, with 24h uptime bars and 30-day incident history.

- I dogfood it — every page on SitePulse is monitored by SitePulse: https://sitepulse.satosushi.co/status/sitepulse

## Tech stack

- Next.js 16 (App Router) + React 19

- Supabase (Tokyo region) for auth + DB

- Vercel (Tokyo region — colocated, drops TTFB by ~700ms vs default iad1)

- Stripe for billing

- Resend for transactional email

- cron-job.org for the probe scheduler (so a Vercel hiccup can't silence the whole queue)

## Honest gaps

I'm a solo maker shipping the v1, so:

- Email alerts only (Slack/Discord webhooks coming)

- Single-region probes (Tokyo) — multi-region voting on roadmap

- No SMS yet

If those are dealbreakers, UptimeRobot is the right call today. Otherwise, you might like SitePulse better.

## What's next

- This week: Twitter launch + Show HN

- Next 2 weeks: Slack + Discord webhooks

- Month 2: Multi-region probes

Try it: https://sitepulse.satosushi.co — 5 monitors free, no credit card.

Building in public from Tokyo 🇯🇵 — feedback very welcome.