Governed operational data mesh for AI agents — department-scoped streams, MCP tools, optional institutional memory, and usage-based billing on fabric you control. Connect ops and knowledge systems once; route department-owned products with policy; expose governed MCP tools to copilots and workers; meter usage so finance and platform can see what agents actually consume. LoopCompound™ (Build · Steer · Compound) maps each capability to a loop beat you can staff and measure.
I/O Mesh is the governed operational data mesh for production AI agents. Live SaaS, docs, and metrics land as department-scoped dept.* data products — not a company-wide vector dump. Agents consume them through policy-gated MCP tools on fabric you control, with optional Agentic Memory Palace for institutional recall. LoopCompound™ (Build · Steer · Compound) maps those surfaces so you prove workflow lift on your ops facts before you scale inference spend.
Ops connectors and fail-open publish are GA; knowledge and analytical mesh layers expand under Beta.
Methodology: LoopCompound™ · Build · Steer · Compound
Five modules on one dept.* fabric — mesh routing console, GTM suite, CRM connectors, and automation studio on governed dept.* streams.
Domain-owned dept.* streams from ops, docs, and warehouse connectors — link enrich, catalog contracts, and MCP compose on one fabric.
Integrations · Data products catalog
Broker admins configure streams, processors, subject scopes, and policy preview from settings — no separate admin console required.
Settings → Mesh routing
Self-serve marketing ingress and pipeline tooling — custom webhooks, first-class Mautic/Matomo, campaigns, attribution, and CRM API.
Integrations · Settings → Marketing
YAML DAG workflows with visual canvas, n8n handoff, and mesh publish nodes — governed batch paths without retiring your existing automations.
Settings → Automation studio
Sovereign learning loops for regulated evaluators — SSO, SCIM, IdP scope sync, and HIPAA marketing pack mapping.
Settings → Security · Marketing HIPAA
Connectors group by mesh layer and bill as usage meters. GA = production-ready path; Beta = shipped with expanding coverage. Custom webhooks cover n8n and any HMAC-capable client.
GA path: live SaaS workflow events — incidents, tickets, CRM, and engineering signals.
Beta: wiki and drive changes as dept.* products with governed recall.
Beta: dbt metrics, warehouse CDC, and embeddings as agent-ready live views.
Webhook fabric and growth ingress — n8n completion path GA; suite connectors Beta.
Self-serve broker configuration from Settings → Mesh routing. Core streams, processors, and scopes are included with your workspace; advanced federation and policy tooling unlock via the Governance add-on, IdP scope sync via Compliance.
Create and delete dept.* streams and enrich processors from the portal with broker audit trails.
Department subject ACL bindings with inline Rego/OPA policy preview before save.
Bridge NATS dept.* subjects to Kafka topics for downstream analytics pipelines.
Cross-org field masks with multi-region preferred+fallback routes tied to federation grants.
Load bundle modules, draft Rego AST, evaluate, and preview mesh policy without persisting bundles.
Broker-side sampling and route traffic analytics for SRE and platform operators.
Customer mesh write audit timeline and federated mesh audit JSON export for evaluators.
Map SSO group claims to dept.* subject patterns automatically on membership change.
Starburst- and Denodo-class platforms excel at analytical federation; Confluent moves events at scale. CTOs still stitch memory, tool policy, and department ownership themselves. Agents need dual-use products at event time — with contracts and governance — not another batch lake copy.
I/O Mesh starts where agents need freshness — operational facts from SaaS tools on dept.* streams — then extends the same tenancy to documents and analytical live views without a company-wide vector dump. Compare us for agent production readiness, not warehouse SQL alone.
Business domains own their data products — context, meaning, and quality live with the team that produces the work.
On I/O Mesh today: dept.* streams per department (engineering, sales, CS, support, finance, legal) with tenant isolation — not a shared memory bucket.
Publish addressable, trustworthy assets with clear consumers — event streams, live views, and agent output ports instead of ad-hoc exports.
On I/O Mesh today: Connector-normalized events on dept.{domain}.events.{source}, link-enrich advisories, and MCP tools as governed output ports.
Central plumbing (tenancy, audit, metering) so domain teams ship without rebuilding pipelines per project.
On I/O Mesh today: Customer portal signup, integrations UI, usage-metered ingress, and memory billed by ingest volume.
Automated guardrails and policy — not committee gates — so risk scales with product velocity.
On I/O Mesh today: Visual Rego policy editor with mesh preview, field-level ABAC federation grants, traffic tap and analytics, federation routing, and write/federation audit exports — advanced mesh via Governance add-on, enforced at ingress and MCP invoke.
Core path for production agents: live events from how work runs — incidents, tickets, CRM, PRs, chat — with link enrichment and fail-open publish so hot-path ingest is not blocked by memory.
Docs and wiki as dept.* products with the same tenancy as ops events — so agents cite runbooks that match the live incident, not a stale shared chunk index. Connector coverage is expanding under Beta.
Dual-use live views: metrics and warehouse context as governed output ports for agents — freshness SLOs and catalog discovery without per-agent SQL sprawl. Warehouse drivers expand under Beta.
Same dept.* tenancy across ops, docs, analytics, catalog, and governance. GA = production-ready path; Beta = shipped with expanding connector/driver coverage. Not every checkbox is GA yet. Browse the data product catalog or FAIR dashboard for evaluator detail.
GA path for production agents: domain-owned dept.* streams, ops connectors, enrich, MCP, and optional memory.
Wiki and drive platforms as dept.* products — same tenancy as ops. Connector coverage expands under Beta.
Self-serve discovery, versioned schemas, lineage, and quality signals — contract enforcement opt-in.
Live views and semantic layers as agent output ports — dbt, warehouse CDC, embeddings. Drivers expand under Beta.
Policy at ingress and MCP invoke; advanced mesh via Governance add-on. FAIR/DOI evaluator features optional.
operational mesh
On-call and engineering domains publish linked incident → PR → Slack products agents trace for RCA.
operational mesh
Sales and support domains merge CRM + ticketing events into renewal-ready context without spreadsheet exports.
knowledge mesh
Product and engineering docs versioned on dept.* — agents cite the runbook that matches the live incident.
knowledge mesh
Legal domain owns vendor contracts and policies linked to finance transactions and support escalations.
knowledge mesh
Sales playbooks and battlecards stay in sync with CRM opportunity events — not a stale doc index.
analytical mesh
Semantic metrics and dbt models published as governed products — agents read pre-computed truth, not warehouse SQL.
analytical mesh
Snowflake and BigQuery table CDC on dept.* views — federated upstream to dbt metrics lineage without warehouse SQL in agent prompts.
Step 1 · connectors
Ops, docs, warehouse, and GTM connectors → dept.* events with signed webhook audit — workflow and marketing facts that feed your learning loop.
Step 2 · broker
Governed publish/pull on dept-scoped streams with plan gates and metering — token capital routed by department, not one shared bucket.
Step 3 · enrich
Cross-table advisories (incident → PR → Slack) without blocking hot-path ingest — evidence chains that compound across workflows.
Step 4 · memory
Governed institutional recall — agents remember what your firm learned from live workflows, scoped by department, and yours when models change.
Step 5 · mcp
Department-scoped tools for copilots — summarize health, trace incidents, recall context your firm has already encoded.
Agentic Memory Palace is I/O Mesh's institutional recall layer — how copilots remember what your firm learned from live work, across sessions and model swaps, without one company-wide search dump.
Connectors → dept.* broker → link enrich → agent memory → MCP / HTTP context APIs Fail-open: memory never blocks publish · Plan gates at ingress · Metered SaaS
LoopCompound™ names three nested loops on operational facts. Read the loop engineering guide and take the readiness assessment before you activate a kickoff workspace.
Industry research argues that AI put data back at the center of strategy — but tools alone don't guarantee better decisions. Learn how context liquidity on the operational data mesh closes the agent pilot gap.
Start with GTM scale context — pay for usage meters as workflow volume grows and add governance packs when private evals need advanced controls.