“Is it down?” has a URL now.
A hosted status page with real monitoring behind it — HTTP checks, SSL certificates, heartbeats from cron jobs — plus incidents, maintenance windows and subscriber emails. Same system as your roadmap. No bolt-on status product.
Checks that cover real systems.
Not just “is the homepage up”. Watch the things that break on a Tuesday night: API endpoints, certificate expiry, and the background jobs that fail silently.
- HTTP checks — method, headers, expected status range and timeout; intervals from 5 minutes on Free down to 30 seconds on Team.
- SSL monitoring — get warned before the certificate does its dramatic midnight exit.
- Heartbeats — cron jobs and workers check in; silence after a grace window is an incident.
- Groups — organize checks by system, with public toggles per group and per check.
- Phone alerts — on Pro and Team, downtime calls your on-call people and keeps calling until someone explicitly acknowledges.
Bad days, communicated well.
Open an incident, post updates as you learn, close it with a resolution. Plan maintenance before it plans itself. Subscribers get an email at every step — before they find out in your support inbox.
- Incident updates — investigating → identified → monitoring → resolved, with timestamps.
- Maintenance windows — planned work announced in advance, shown on the page.
- Confirmed subscribers — double opt-in emails, so incident comms stay wanted.
Zero infrastructure. Zero status-product subscription.
The public page comes with uptime summaries, daily history bars and your branding. Start on a managed subdomain — no DNS changes for your customers — and it sits right next to the roadmap and releases that show the upside.
- Managed subdomain — yourproduct.status.usedamper.com, live in minutes. Paid plans can bring their own domain.
- Uptime history — daily bars and summaries customers can actually read.
- One vendor for trust — what you're building and whether it's healthy, on the same platform.
Reliability, published.
Set up your checks, publish the page, and let subscribers hear it from you first.
Where this fits in the loop.
Collect
Catch feedback where it happens — in your app, in Slack, on a call — and land it in one clean inbox.
Prioritize
Rank requests by who is asking. Votes are weighted by plan, so paying customers move the roadmap.
Build
Hand the top task to your AI coding agent with the rules that govern it — and get proof when it is done.
Ship
Shipped work becomes a changelog entry, and everyone who asked for it hears first.
Around the loop
Docs, uptime, errors and team access — the product ops that sit next to the loop.