On-call console.On-call console.On-call console.On-call console.

Every production team has the same story: four monitoring tools, four sets of alert emails, four different notification patterns. Someone always misses the P1. This is the on-call dashboard that fixes it.

One inbox on Inbin, 4 newsletter or alert subscriptions pointed at it. Every email that lands gets parsed against your schema.

One PUT to /v1/schemas. Inbin extracts these fields from every future email. Hallucination guard drops anything the model invented.

{
  "extract": {
    "alerts": {
      "type": "array",
      "items": {
        "severity":    { "type": "string", "pattern": "^P[0-3]$", "required": true },
        "service":     { "type": "string", "required": true },
        "message":     { "type": "string", "required": true },
        "occurrences": { "type": "number", "nullable": true },
        "first_seen":  { "type": "string", "format": "date-time", "nullable": true },
        "source":      { "type": "string", "required": true }
      }
    }
  }
}

1. 01
   Create the inbox

   POST /v1/inboxes returns a permanent forwarding address like abc123@in.inbin.dev. Use it everywhere you subscribe.
2. 02
   Point the sources at it

   Sign up for each source with that address, or set a Gmail filter forwarding Sentry, StatusPage, etc. to the inbox.
3. 03
   Declare the schema

   Paste the JSON above. Inbin creates version 1, tracks all future versions, replays extractions if you change the shape.
4. 04
   Consume the events

   Every parsed email hits your webhook as HMAC-signed JSON. Or read them via GET /v1/events. Or query them from an agent via MCP.

vs. Datadog Incident Management: $10 / host / mo.

Every product listed above exists because the underlying data was hard to get. Newsletters give you that data for free. Inbin structures it.

Also worth building