1stLine - Route any alert payload without responder limits

Hi hunters! I started building 1stLine because I was struggling with finding the good fit for Opsgenie replacement. Being in charge of monitoring, I firsthand experienced that these systems have many complex underlying components. However, what surprised me was that incidents, schedules, and on-call rotations weren't the hardest part unlike I expected. Integrations were. Every monitoring system sends different payloads. Every destination expects different payloads. Grafana, Alertmanager, Pingdom, Slack, Discord, Teams, custom webhooks - everything speaks a different language. Instead of trying to force integrations into a single format, I built a routing engine that accepts arbitrary payloads, extracts fields, routes alerts, starts escalations, and optionally transforms payloads before forwarding them. Along the way I noticed another pattern: Many teams use shared users, service accounts, or other workarounds to avoid responder-seat pricing. So 1stLine doesn't charge per responder. Today we're opening Public Preview and I'd love feedback from anyone dealing with alert routing, on-call workflows, or Opsgenie migration. Happy to answer any questions.