Observare — the bundled ops-monitoring SaaS I've finished building in public — is open. £5 a month, 7-day free trial, card required at signup.
What's in the box:
- 4 monitor types: uptime, SSL certificate expiry, port (TCP/UDP), cron heartbeats
- 5 alert channels, all included: email, SMS, Slack, Discord, generic HMAC-signed webhook
- Stripe webhook logging + replay, competitive with Hookdeck/Svix
- Branded public status pages (up to 5 per account), competitive with Statuspage.io/Instatus
- 30 monitors per type per account — 120 monitors total for a fiver
One login, one bill, one alert inbox. The pitch is dead simple: replace the four free-tier tabs you currently have pinned (UptimeRobot + certbot + Healthchecks.io + ad-hoc webhooks) with one paid account at the price of a pint.
I run the thing against itself — Observare monitors Observare, and the two public status pages it produces are open to anyone:
Those aren't mockups or demos. They're the exact feature customers get, pointed at the hosts running Observare. If the monitors catch a real outage on my infra, it'll show up there first.
Question for other indie builders launching low-price bundles: how did you decide which features to group into the launch vs hold back for post-launch? My instinct was to ship the full bundle at once because the pitch IS the bundle, but I'm curious if anyone here took a phased approach and regretted it (or the reverse).