Mesh is the enterprise stream of Refract — built on the same source that powers Lens, refracted through your organization via MCP-native connectors, deterministic workflows, multi-tenant isolation, and an auditable compliance kernel. The Workato alternative for teams who already speak AI.
Mesh is composed, not bundled. Every layer is independently addressable, independently versioned, and independently auditable. Run the whole stack, run a slice, run it on prem.
No proprietary connector format. No "we built our own thing." Mesh's connector layer is MCP-native end to end — every source becomes a model-context-protocol server, addressable by every agent and every workflow under the same primitive.
// dag.compose() · trigger → parallel(mcp_calls) → agent_reason → policy_gate → emit
Mesh workflows are deterministic DAGs of MCP calls and agent inferences. Author them in code, in the visual composer, or let the source propose them — then version, replay, and govern them like any other production artifact.
The connector grid below is what's coming live first. The actual surface is bigger — anything addressable through MCP, plus the long tail accessible via the universal HTTP / GraphQL connectors.
Every action an agent considers takes a trip through the kernel before it runs. Risk gets classified, policy gets enforced, audit gets written. The kernel is what takes Mesh from "raw source" to "audit-grade orchestration."
The iPaaS category was built for deterministic data movement. Mesh is built for deterministic data movement and agentic decision-making — without bolting one onto the other.
| Capability | Refract Mesh | Workato | MuleSoft | Zapier |
|---|---|---|---|---|
| MCP-native connectors | ● first-class | ○ | ○ | ○ |
| AI agents (built-in) | ● the core | add-on | add-on | add-on |
| Deterministic workflows | ● | ● | ● | ● |
| Replayable / versioned | ● by default | enterprise tier | ● | ○ |
| Multi-tenant compliance kernel | ● 5-tier classify | policy controls | governance pkg | ○ |
| Append-only audit ledger | ● crypto-chained | log only | ● | ○ |
| Multi-provider LLM routing | ● | ○ | ○ | ○ |
| Self-host / on-prem | on roadmap | ○ | ● | ○ |
| Boutique implementation included | ● via RautingTech | via partners | via SI | ○ |
// honest competitive read · not a hit-piece · this matrix updates as Mesh ships
Mesh is the enterprise stream. Lens is the personal stream — same source, same connector layer, scoped to one human, loosely compliant by design.
See Refract Lens →Mesh is shipping in design-partner cohorts. Tell us what you run and what you're trying to orchestrate — we'll send back a reference architecture and a 30-min slot to walk through it.
// design partners get reference-architecture sessions, early SDK access, and shaping power on the roadmap