Product

API observability that watches the contract, not just the server.

DevFlow Watch is built around three primitives. Each is shippable on day one; together they replace the synthetic + SLO + status-page sprawl most teams build by hand.

Synthetic checks

HTTP and gRPC monitors run from 14 global edges, with fail-quorum so a single edge does not fire false alerts.

SLO tracking

Error budgets, multi-window burn-rate alerts, and the math to back up your reliability numbers.

Response assertions

JSON-Schema, JSONPath, regex, headers, latency. Fail-fast when the contract changes — even at 200.

Boring, and on purpose.

DevFlow does not replace your APM. It does not replace your logs. It does not replace your dashboards. It does the focused job of watching what your customer’s code watches: a request, a response, a clock. Less than that and your reliability numbers lie. More than that and the tool is competing with three other tools your team already pays for.

Where it overlaps deliberately is on alerting — pages routed via Slack, PagerDuty, Opsgenie, Teams, Linear, and webhook are first-class. The agent that watches the contract should also be the agent that pages.

yaml

name: payments-api-charge
url: https://api.example.com/v1/charges
method: POST
frequency: 30s
regions: [us-east-1, eu-west-1, ap-southeast-1]
quorum:
  mode: fail-quorum
auth:
  type: bearer
  token_secret: PAYMENTS_PROD_TOKEN
retry:
  max_attempts: 3
  backoff: exponential
  jitter: full
assertions:
  - status_eq: 200
  - latency_lt_ms: 800
  - body_json_schema:
      schema_ref: workspace://schemas/charge-response-v3.json
alert_channels:
  - pagerduty:payments-oncall
tags:
  env: prod
  service: payments-api
  team: payments
  slo: payments-availability-99.9