DomainDash

DomainDash is a multi-region monitoring SaaS for SSL certificates, uptime, and DNS. Probes run from up to five AWS regions in parallel, so what you see reflects what your users actually see — not just what one synthetic check happened to find.

The problem ​

Most monitoring tools fall into two camps. The cheap ones run a single check from a single region, so your "uptime" is really uptime as observed from us-east-1. The expensive ones do multi-region properly but charge accordingly — pricing tiers that only make sense for companies running global infrastructure.

In between is everyone else: people running a handful of services, with customers in more than one country, who'd like to know when SSL is breaking in Sydney even if Frankfurt is fine.

What DomainDash does differently ​

Each check runs in parallel from multiple AWS regions. SSL certificates are validated end-to-end — issuer chain, expiry, hostname match. Uptime probes report per-region latency and status. DNS checks verify resolution from each vantage point.

When something fails, the alert tells you where it failed. "SSL expired" is useful. "SSL expired in ap-southeast-2 but valid elsewhere" is actionable.

How it's built ​

The control plane is a Laravel + Horizon application running on ECS, dispatching jobs to Rust Lambda functions in up to five AWS regions. Each Lambda probes its target and POSTs the result back to a signed webhook on the Laravel side. There are no cross-region database connections, no complex VPC peering — just a stateless data plane and a stateful control plane talking over HTTPS.

I wrote about the architecture in PHP is dead. Long live PHP. Microservices are dead. Long live microservices..

Why I'm building it ​

I needed it. I run a handful of small services and the existing tools were either too thin or too expensive. The "multi-region" tier of every commercial monitoring product I evaluated was priced for enterprise budgets, not solo founders.

It's also the kind of project that's enjoyable to build on the side: a clean separation of concerns, a polyglot stack with each tool playing to its strengths, and a problem space where boring engineering wins.