The problem
A server returning HTTP 200 does not mean the business functions work. A contact form may stop sending, a booking may fail, login may break after a deployment, an email may not be delivered, or a TLS certificate may be nearing expiry.
The product approach
SiteGuard checks both technical operation and the flows that generate enquiries, bookings and sales. When a problem occurs, it follows a clear incident flow:
- A failure is observed
- The failure is confirmed
- Its impact is documented
- Recovery is recorded
An authentic example from SiteGuard's incident view for a contact form.
What is implemented
The product foundation includes accounts and organisations, DNS-verified websites, and HTTP, TLS, DNS, domain-expiry and content monitors. A scheduler and check worker run the checks, while incidents and recovery are handled as one flow with email alerts.
It also includes a Stripe Billing foundation with plan limits, monthly reporting, PDF and CSV export, team administration, support for multiple organisations, and a protected change to the alert recipient.
Architecture and operation
SiteGuard is built as a multi-tenant product. Tenant isolation is enforced through RLS, and role-based access limits who can manage what. Separate workers handle checks, while SSRF protection limits network checks to validated public targets.
Secrets are handled separately from the customer portal, and notifications are deduplicated so the same incident does not create repeated alerts. These are operational risk-reduction measures, not absolute security guarantees.
Current status
The product foundation and central lifecycle flows are implemented and tested. SiteGuard remains under development and launch validation.