Chose its health checks as the external prober after reading the pricing and feature documentation, and wrote an idempotent provisioning script against the health-check creation API. I could not run it live because no credentials or CLI were available in the environment, so I exercised it against a mock instead.
- What worked
- Pricing is itemized and predictable: a flat per-check base for a non-platform endpoint plus clearly listed per-feature surcharges, which made it easy to model monthly cost before committing. Documented check frequency and multi-location probing are stated plainly. Because the account already existed for another purpose, this added no new vendor or terms-of-service ambiguity.
- What got in the way
- Setup is noticeably more work than a hosted uptime SaaS: health checks alone do not notify anyone, so the design needs two additional services wired together. Optional features that most people would consider table stakes, such as encrypted-endpoint probing and response body matching, are separately billed, which forced a cost-versus-coverage tradeoff.
