The tools you already run, read as each viewer.
Ten connectors live at launch — the tools your team already runs. Each reads as each viewer's own account and ships with a maintained recipe a real team has run, so your agent starts from a working readout, not a blank page.
Jira
LiveSprint dashboard
Status, ownership, and the one issue that still needs an owner, ready before standup.
Open Jira →GitHub
LiveDelivery review
PR velocity, review load, and what shipped this week across your repos, without exporting a thing.
Open GitHub →Google Sheets
LiveWeekly status readout
Delivery from your repos, goals from a sheet, and the ownership gaps worth naming.
Open Google Sheets →Salesforce
LivePipeline review
Stage movement, slipping deals, and the number the team actually opens on Monday.
Open Salesforce →Linear
LiveCycle dashboard
Issue status, ownership, and the work that still needs a name before planning.
Open Linear →Zendesk
LiveSupport queue
Backlog, SLA risk, and the tickets aging past their promise.
Open Zendesk →PagerDuty
LiveOn-call & incident
Who's on, what paged, and the follow-up work that trails a launch.
Open PagerDuty →Confluence
LiveStatus readout
The current state of a space, gathered from the pages your team already keeps.
Open Confluence →Notion
LiveStatus readout
Project state and ownership pulled from the docs your team already keeps.
Open Notion →HubSpot
LivePipeline review
Stage movement, campaign impact, and the number the team opens on Monday.
Open HubSpot →Read as each viewer, never as a shared login.
Every live connector read runs against the person opening the readout — through the data proxy's access checks, against their own connected account. A shared link only ever shows each viewer what the source system already lets them see. There is no standing shared credential under the hood and no shared login behind the page.
When the whole team needs one view, a named person publishes an edition — a stable, dated copy the whole team opens, carrying a byline: whose access it went out on, and as of when. Every shared view is authored; none is anonymous.
“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
