Purpose-built outbound delivery instead of a normalized data-access layer.
The Meshes advantage
A unified data API does not replace the customer-facing delivery layer. Meshes gives outbound events the fan-out, retry isolation, mappings, recovery, and embedded control they need.
Focused delivery
Your app emits lifecycle events that need to reach customer-owned CRMs, email tools, messaging platforms, and webhooks with fan-out, retries, replay, and destination-level history.
Delivery reliability
A failed destination does not hide or block successful siblings. Meshes records each matched delivery independently and lets operators recover eligible failures from the event history.
Customer operations
Each customer manages destinations, mappings, and routing rules in an isolated workspace while your product keeps ownership of the source event model.
Meshes delivery advantages
| Capability | Meshes | Merge |
|---|---|---|
| Data direction | ||
| Primary direction | Outbound: your app to customers' tools | Inbound: customers' tools to your app |
| Core job | Deliver product events to destinations | Normalize third-party data into your app |
| What it covers | ||
| Outbound event delivery | Yes: fan-out, retries, dead letters, replay | Not the primary use case |
| Write operations to third parties | Destination actions are triggered by customer-scoped routing rules | Application code calls write endpoints through the Unified API |
| Delivery and reliability | ||
| Fan-out routing | One event to many destinations in parallel | N/A: API request and sync model |
| Automatic retries | Exponential backoff with jitter, per destination | API-level retry handling and sync or webhook patterns |
| Dead letter capture | Yes | N/A |
| Event replay | Yes: replay failed or all deliveries per destination | N/A |
| Developer experience | ||
| Embeddable UI | White-label workspaces for connections, rules, mappings, and delivery history | Merge Link connects end users for unified API access |
| Multi-tenant | ||
| Tenant model | One workspace per customer with isolated connections, rules, credentials, and event history | Linked Accounts per end-user or customer connection |
Data direction
Meshes
Outbound: your app to customers' toolsMerge
Inbound: customers' tools to your appMeshes
Deliver product events to destinationsMerge
Normalize third-party data into your appWhat it covers
Meshes
Yes: fan-out, retries, dead letters, replayMerge
Not the primary use caseMeshes
Destination actions are triggered by customer-scoped routing rulesMerge
Application code calls write endpoints through the Unified APIDelivery and reliability
Meshes
One event to many destinations in parallelMerge
N/A: API request and sync modelMeshes
Exponential backoff with jitter, per destinationMerge
API-level retry handling and sync or webhook patternsMeshes
YesMerge
N/AMeshes
Yes: replay failed or all deliveries per destinationMerge
N/ADeveloper experience
Meshes
White-label workspaces for connections, rules, mappings, and delivery historyMerge
Merge Link connects end users for unified API accessMulti-tenant
Meshes
One workspace per customer with isolated connections, rules, credentials, and event historyMerge
Linked Accounts per end-user or customer connectionWhy engineering teams choose Meshes
Meshes is purpose-built for delivering your product events to downstream tools. If your problem is 'how do I get my events into my customers' CRMs,' Meshes is the answer.
One event reaches every configured destination in parallel. A signup can update HubSpot, Mailchimp, Intercom, Slack, and more from a single API call with isolated retry handling per destination.
Exponential backoff, dead letter capture, and replay come standard. When a destination is down, Meshes retries without losing the event and without blocking delivery to other destinations.
Your customers manage their own connections, routing rules, field mappings, and event history inside white-label workspaces embedded in your product.
Configure how event payload fields map to destination fields per connection, with transforms and error handling. No manual data reshaping in your app code for every downstream system.
Connections, rules, mappings, retries, and delivery history stay together instead of splitting outbound product traffic across sync state and application-managed API writes.
Common questions