InsightForge Now Supports SendGrid

SendGrid joins Postmark and Azure Communication Services (ACS) as a connected InsightForge provider. A lot of teams already watching Postmark or ACS delivery through InsightForge also have a SendGrid account somewhere — a legacy sender that never got migrated, a product line that standardized on it independently, or simply the account that came with whatever platform they signed up for first. Until now, that traffic sat outside InsightForge entirely. It doesn't anymore.

What's actually connected

InsightForge ingests SendGrid's delivery, bounce, complaint, and open events through SendGrid's Event Webhook, with signature verification turned on — the same signed-event handling used to confirm this integration works end-to-end, not just against sample payloads. Once connected, those events land in the same unified dashboard as Postmark and ACS: one bounce-rate trend, one complaint-rate trend, one delivery-latency view, regardless of which provider actually sent the message.

Setup is self-serve from the dashboard's Setup screen — add a SendGrid API key and, once Signed Event Webhook is enabled on the SendGrid side, its verification key. No redeploy, no ARM update, no waiting on a new release to pick up a new credential.

One step SendGrid doesn't automate

Connecting ACS is close to zero-touch: give InsightForge the resource's ARM ID and it provisions the Event Grid subscription for you. SendGrid doesn't have an equivalent handoff. After adding the API key and verification key in the dashboard, the ingest URL shown on that same screen still has to be pasted into SendGrid's own Event Webhook settings by hand. It's a two-minute step, but it's a real one — worth knowing going in rather than assuming SendGrid wires itself up the same way ACS does.

What this doesn't include yet

SendGrid support in InsightForge is scoped to delivery and engagement events, and it's worth being precise about where that scope ends:

• No suppression-list sync — InsightForge surfaces bounce and complaint events as they arrive, but doesn't read or reconcile SendGrid's suppression lists
• No domain authentication or sender-identity management — that stays inside SendGrid's own dashboard
• Header Detective and Flight Tracker — InsightForge's per-message SMTP header chain and full delivery timeline tools — remain Postmark-only. SendGrid-sourced messages show up in the unified dashboard and trend charts, not in those two diagnostic views

None of that is a roadmap complaint so much as an honest boundary: SendGrid joins the unified delivery, bounce, complaint, and latency picture on day one. The deeper per-message diagnostics that currently exist only for Postmark are a different, separate piece of work.

Where SendGrid fits in the plans

Standard ($49/month) covers a single connected provider — up to 3 Postmark servers, 1 ACS resource, or 1 SendGrid credential. Pro ($99/month) connects up to 3 providers in any mix of Postmark, ACS, and SendGrid, with unlimited sending identities. A team running Postmark and SendGrid side by side during a migration, or just permanently split across both, doesn't need two separate tools to watch them — Pro connects both under one dashboard.