I built NthLayer because I was tired of the manual effort every time a new service onboards - copying dashboard JSON, writing alert rules, setting up PagerDuty, defining SLOs. 20 hours of work per service.

Define your service once:

    name: payment-api
    tier: critical
    type: api
    dependencies:
      - postgresql
      - redis
    slos:
      availability: 99.95
      latency_p99_ms: 200

Get automatically: - Grafana dashboards (12-28 panels based on dependencies) - Prometheus alerts (400+ battle-tested rules) - SLO definitions with error budgets - PagerDuty teams, escalation policies, services - Recording rules for performance

Plus: See reliability health across all your services:

    $ nthlayer portfolio
    Overall Health: 78% (14/18 SLOs meeting target)
    Critical: 5/6 healthy
    ! payment-api needs reliability investment

Works with your existing tools - generates configs for Grafana, Prometheus, PagerDuty. No vendor lock-in.

Live demo: https://rsionnach.github.io/nthlayer GitHub: https://github.com/rsionnach/nthlayer Install: pipx install nthlayer

It's early alpha - looking for SRE teams to try it. What reliability toil would you automate first?