Your PagerDuty readout, built once and never rebuilt.
You already rebuild the incident wrap-up from PagerDuty by hand — pull the incident log, reshape it, screenshot, paste. Your agent can build the readout once, starting from a maintained PagerDuty recipe a real team has run. Aptarium publishes it behind sign-in, reads PagerDuty as each viewer's own account, and keeps it current on the schedule you set — publishing a fresh edition each time, a stable, dated copy the whole team opens, carrying a byline: whose access it went out on, and as of when.
The shipped PagerDuty recipe: On-call & incident.
Who's on, what paged, and the follow-up work that trails a launch. It ships complete — loading and empty states, pagination, stale-cache messaging, and provenance already in the box — so the agent starts from a working readout, not a blank page.
No shared login, no standing credential.
Live PagerDuty reads run against each person's own connected PagerDuty account, through the data proxy's access checks — so a shared link only ever shows each viewer the services and schedules PagerDuty already puts them on. There is no shared login behind the page and no standing credential anywhere. Anything the whole team opens is an explicit edition with a byline — the on-call owner's name and the moment it went out.
From Google sign-in to the on-call owner's first shared readout.
From Google sign-in to your first shared, connected readout, starting from the PagerDuty recipe — the incident wrap-up, now a link you send once. No API keys to mint, copy, or paste; one command pairs the agent you already use, and any mistake rolls back with one click.
PagerDuty is one of ten connectors live at launch — Jira, GitHub, Google Sheets, Salesforce, Linear, Zendesk, PagerDuty, Confluence, Notion, and HubSpot. Readouts often read two at once — pair PagerDuty with GitHub for its delivery review beside your on-call & incident.
See all ten connectors →“Why these ten — and not the tool I use?”
We only ship connectors that can read as each viewer — the invariant the whole lineup is chosen by. If your tool isn't here, it's usually for one honest reason: it can't make that promise. Slack and Datadog-class tools are admin-gated, so they can't resolve one viewer's own access — Slack is a notification target, not a per-viewer source. Microsoft 365 and Excel arrive the moment Microsoft's identity path allows per-viewer reads — it's the top of the list, not a maybe.
Bring the tools you already run.
Join with a work email and you're in a wave with a real invite coming, not dropped at a wall. Nothing is public by default; viewers are always free.
Cohorts invited weekly
