I/O Mesh

Heartbeat after a signed event

Production agents need a heartbeat.Not another chat window.

Production agents need a heartbeat. Not another chat window.

Tess’s Friday thread is the record — SHA pasted, scroll lost, note still on one laptop.

Chat is not memory.

One signed event on a named stream is the heartbeat she cites.

A name in the directory isn't a live connection yet. The board stays empty until a signed event is pulled.

The board stays empty until a signed event is pulled.

The first signed pull paints the pulse. A name in the directory isn't a live connection yet. Slack looks finished because someone pasted the SHA. The digest cites the live event and the private note on her machine. Cite both sides, or say which one is missing.

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.

Get a first heartbeat
Talk to us Explore the mesh

Sit down, run the install, and consume the first signed pull.

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.

See it for

Platform teams connect tools they already run. First session needs someone who can add the PagerDuty webhook and a GitHub repo admin. Heartbeat after the first signed event.

context://mesh · eng.ops · policy-gated MCP

Demo

Heartbeat

18 / min

  • 14:02:11
    opssre.incidents

    P2 opened — checkout p95 1.8s

    Signed from pager. Team tenancy: sre.oncall

  • 14:02:18
    opseng.ops

    Deploy v2.14.3 → prod-eu

    Heartbeat linked to runbook RB-441

  • 14:02:24
    opscs.tickets

    Enterprise ticket · latency on checkout

    Scoped to cs.enterprise — not a global index

  • 14:02:31
    knowledgesre.incidents

    Recall: similar p95 in Mar

    Institutional memory of last quarter

  • 14:02:39
    analyticsgtm.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.

Built for teams shipping production agents

  • Platform
  • SRE

The gap

Memory products store chat history and user facts. I/O Mesh stores the work: a signed event on a department stream, and the RCA or runbook already on disk. Cite both sides, or say which one is missing. The board stays empty until a signed event is pulled. You pick the model. Private notes stay on your machine.

Signed event on one side. Local notes on the other. Cite both sides, or say which one is missing. The board stays empty until a signed event is pulled.

Free MIT memory kernel and TUI on your machine. Buyer-facing examples stay free of live staging endpoints.

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. The board stays empty until a signed event is pulled. Local MIT memory on your machine stays free.

How it works

How you get a first heartbeat

Connect a source, open a stream, land one signed event. Cite both sides, or say which one is missing. Agents attach via MCP after that heartbeat.

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.

  1. 01

    Connect a source

    PagerDuty first. GitHub second. First signed event is the heartbeat.

    Connect PagerDuty first when your team owns incidents. GitHub second for the change that usually caused the page. Slack waits. Heartbeat after a source, a stream, and a first signed event.

  2. 02

    Create a mesh stream

    A named inbox such as OPERATIONAL_EVENTS.

  3. 03

    First signed event is the heartbeat

    The console shows events after a signed message lands on that stream. The board stays empty until a signed event is pulled.

  4. 04

    Cite both sides, or say which one is missing.

    Cite both sides, or say which one is missing.

  5. 05

    Agents attach via MCP after heartbeat

    Copy the Agent / MCP connection after the first signed event. Attach is not the product definition.

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.

One heartbeat. Three signals.

The full organizational pulse.

Department-scoped streams — not a company-wide vector dump. Agents get the real-time pulse of work, the memory of what it meant, and the patterns that emerge.

Live operations

Tickets, incidents, deploys, and customer updates, organized by team. The primary heartbeat a reviewer can see after a source, a stream, and a signed event.

Knowledge

Docs, runbooks, and memory of past heartbeats. What previous activity meant. Reviewers can open this layer in the product; do not chip it as a readiness label.

Analytics

Patterns and trends across heartbeats so agents see beyond the moment. Same rule: describe the layer, do not chip a status.

Now

Signed events you can consume from a mesh stream.

Hours–days

Recent activity and rolling operational context.

Weeks–years

Analytical history plus free local MIT memory on your machine.

Why teams choose I/O Mesh

The pulse they attach to

Tickets, incidents, and deploys as department-scoped signed events.

The record they cite

Live pulse plus private notes on your disk. If a side is missing, the digest says so.

The model stays yours

I/O Mesh is not the brain. Local, or the cloud model you already pay for.

Solutions

Platform & SRE and Incident RCA first.

Primary

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.

Explore →

Primary

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.

Explore →

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

New sign-ups for hosted plans are paused.

Most teams start here. New sign-ups for hosted plans are paused. Local memory on your machine is the MIT kernel. Heartbeat after source, stream, and first signed event.

Hosted plans

Sign-ups paused

  • New sign-ups for hosted plans are paused.
  • Talk to us at hello@iome.sh.

Local memory · exists

On your machine

Free

  • MIT memory kernel + TUI
  • Private notes stay on disk
  • Not a paid add-on · cite-both needs this side

Cloud Memory · optional

Hosted add-on beside time-to-first-heartbeat

  • Cloud Memory is a hosted add-on. New sign-ups for hosted plans are paused.
  • A name in the directory isn't a live connection yet.
  • Separate paths. The board stays empty until a signed event is pulled.

optional · catalog

Local memory and Cloud Memory are not substitutes. Local memory stays free on your machine (MIT kernel). 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. The board stays empty until a signed event is pulled.

Talk to us Pricing

Evaluation

How teams evaluate I/O Mesh

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 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.

Platform SREIncident RCALater recipes on the same heartbeat:Account healthFinance analytics

See evaluation templates

Questions

Straight answers. No chat UI, no model lock-in.

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 io@iome.sh.

Talk to us
See pricing