Every Endpoint. Every Protocol.
HTTP, TCP, DNS, ICMP, MCP — monitor any endpoint from 5 continents with 30-second checks. Define monitors in code or the dashboard. When something breaks, you'll know the root cause — not just that it's down.
Your Monitors Miss More Than You Think.
Single-region checks can't tell you if a failure is real or a network blip. Status codes alone don't explain why your API is slow. And when five services fail because one dependency is down, you get five alerts with zero context.
A single probe in us-east-1 reports your API is down. It's not — a transit provider had a 30-second blip. Your team wakes up for nothing.
"HTTP 503" tells you nothing. Is it the load balancer? The database? An expired certificate? A status code alone doesn't help you fix the problem.
Stripe goes down and suddenly your checkout, billing, and webhook monitors all fire independently. 12 alerts, one root cause, zero correlation.
Five Continents. One Truth.
Every check runs from multiple isolated probes simultaneously. A failure is only confirmed when multiple regions agree — eliminating false positives from network blips, routing issues, and transient errors.
Know What Failed. Not Just That It Failed.
Go beyond status codes. Assert on response time, headers, body content, SSL expiry, DNS records, and more. Each check result shows exactly which assertions passed and which didn't.
HTTP / HTTPS
Status codes, response time, SSL expiry, header assertions, body content matching, redirect following. The complete API monitoring toolkit.
TCP / ICMP
Port availability, connection time, and ping latency. Monitor databases, message queues, and infrastructure endpoints directly.
DNS / MCP
Record resolution, propagation checks, and AI model endpoint health. Cover every layer of your stack.
✓ status == 200passed✓ latency < 500ms218ms — passed✗ body contains "healthy"not found✓ ssl_expiry > 30d87d — passed✓ header x-cache == "HIT"passed 1 of 5 assertions failedCheck triggered from US-East, EU-West, AP-SoutheastOne Root Cause. One Alert.
Group related monitors into resource groups. When your API, database, and CDN all degrade because a shared dependency is down, you get one meaningful alert with full context — not a flood of noise.
Stripe API is reporting elevated latency. 4 monitors in your Payments Stack resource group are affected.
Deploy Your Monitoring With Your Code.
Define monitors in YAML, Terraform, or Pulumi — checked into your repo, applied on every deploy. Your monitoring configuration is always in sync with your services.
devhelm.yml in Your Repo
Check it into source control. CI/CD applies your monitoring config on every deploy — monitors are always in sync with your services.
Terraform & Pulumi Providers
Native providers for Terraform and Pulumi. Define monitors next to your infrastructure — same workflow, same state management.
CLI & TypeScript SDK
devhelm CLI for scripting and automation. TypeScript SDK for programmatic monitor management. Both included on every tier.
monitors:- name: "Production API" url: "https://api.example.com/health" interval: 30s regions: [us-east, eu-west, ap-south] assertions: - "status == 200" - "latency < 500ms" - "body contains healthy" group: "payments-stack" - name: "Database TCP" type: tcp host: "db.example.com:5432" group: "payments-stack"Also Included. Every Tier.
Start Monitoring in 60 Seconds.
50 free monitors. 5 protocols. 5 continents. CLI and Terraform included. No credit card required.
Start Monitoring Free