Real-time
Signed events you can consume from department-owned mesh streams after the first event lands.
Product
A heartbeat Platform and SRE can consume.
Not a copilot skin. The governed operational data mesh is how those signed events stay department-scoped.
Wire the tools you already run. Every Catalog connector uses the same path: create a stream, pull a signed event, get a heartbeat. Agents attach to signed events through policy-gated MCP under team tenancy.
Any connector in the Catalog uses the same path: create a stream, pull a signed event, get a heartbeat. GitHub and PagerDuty are common demo examples — not the only sources.
I/O Mesh is the context plane — the heartbeat after a source, a stream, and a signed event. It is not a replacement for observability (Datadog, Grafana), incident command (PagerDuty, incident.io), issue tracking (Linear), or a workspace (Notion). It is not an MCP gateway or agent control plane product. Still not another chat window, and not a company-wide vector dump.
Time-to-first-heartbeat is the install that proves a consume-clock. The board stays empty until a signed event is pulled. Cite both sides, or say which one is missing.
- Ready now: live operations mesh, signed events, policy-gated tools, paid workspace.
- Next: longer patterns across heartbeats. Analytics is Beta.
- On your machine: free MIT memory kernel and TUI.
Cloud Memory is a hosted add-on beside time-to-first-heartbeat. New sign-ups for hosted plans are paused. A name in the directory isn't a live connection yet. Local MIT memory stays free on your machine.
context://mesh · sre.incidents · policy-gated MCP
Heartbeat
18 / min
- 14:02:11opssre.incidents
P2 opened — checkout p95 1.8s
Signed from pager. Team tenancy: sre.oncall
- 14:02:18opseng.ops
Deploy v2.14.3 → prod-eu
Heartbeat linked to runbook RB-441
- 14:02:24opscs.tickets
Enterprise ticket · latency on checkout
Scoped to cs.enterprise — not a global index
- 14:02:31knowledgesre.incidents
Recall: similar p95 in Mar
Institutional memory of last quarter
- 14:02:39analyticsgtm.pipeline
Renewal pattern on the same heartbeat
Pattern across heartbeats
This is a demo of the console heartbeat. Your org shows this after the first signed event on a mesh stream.
Multi-horizon intelligence
Short-term
Hours to days of stream history and rolling operational context.
Long-term
Analytical history and institutional patterns over weeks to years, under team tenancy.
How I/O Mesh works
These five sentences walk from a heartbeat to a workspace. The mesh is the governed plane under that consume-clock — not the first line.
Time-to-first-heartbeat is the install that proves a consume-clock. The board stays empty until a signed event is pulled. Cite both sides, or say which one is missing.
Heartbeat, not a chat window
Agents keep time from signed events, not from a chat window.
The agent cites the record, not the chat.
When the mesh took the event in, that is what the agent cites, not the chat.
Department keys
Your team shares one mesh, keyed by department and policy, not a private computer per bot.
The tools you already run
Connect the sources your team already owns. Any Catalog connector uses the same path — source, stream, first signed event, then heartbeat. GitHub and PagerDuty show up often in demos because they are common on Platform/SRE teams, not because other connectors wait.
First event, then a workspace
Connect a source, open a stream, and land one event. New sign-ups for hosted plans are paused.
Workflow maps
Platform & SRE and Incident RCA first. Later recipes on the same heartbeat: Account health, Finance analytics. Prove it on your own facts under department tenancy. No public lift %. No logos.
Platform SREIncident RCALater recipes on the same heartbeat:Account healthFinance analytics
Platform SRE
Deploy and incident narratives on one record. Connect the service that pages you and the repo that shipped the change. Prove on your facts: time to a linked pull request and how complete the root-cause write-up is. Not a Datadog replacement.
Incident RCA
When the page fires, the incident, the change, and the notes often live in different tools. Wire the pager pulse and the change pulse, then drop RCA notes you already wrote. If the digest cannot name all three, it says so. Prove it on your own facts. Not a PagerDuty replacement.
Later recipes on the same heartbeat
Account health
When CRM and support streams exist, agents read health and support burden under the same tenancy rules as ops. A name in the directory isn't a live connection yet. Prove it on your own facts. No renewal lift percent. No logos.
Finance analytics
Governed metric views with freshness and lineage when that path is allowed. Not unconstrained warehouse SQL inside prompts. Prove it on your own facts. No board ROI claim.
Hosted plans
Prove lift before you scale inference.
New sign-ups for hosted plans are paused. Heartbeat after source, stream, and first event.
Existing customers with billing or support questions write to support@iome.sh.