Do I have to host any infrastructure?
No. Meshes is fully managed. You send events over HTTPS, and we handle queues, retries, fan-out, and storage.
What happens if a downstream service is down or rate-limiting?
Meshes automatically retries with backoff, respects rate limits, and records dead letters when a destination is persistently unavailable. You can see failures in the UI and replay when things are healthy again.
How does multi-tenancy work?
You segment tenants into workspaces. Each workspace has its own connections, rules, limits, and audit history. Credentials are never shared across workspaces.
How do I send events to Meshes?
You can send events over HTTPS using our REST API from any language. We also provide lightweight SDKs and examples so you can drop Meshes into your existing job queues, webhooks, or background workers in a few lines of code.
Which integrations do you support?
Meshes works with popular CRMs and messaging tools (like HubSpot, Salesforce, Mailchimp, and Intercom) plus generic webhooks for custom destinations. New integrations are added based on customer demand - if you need something specific, reach out and we can prioritize it.
How fast are events delivered?
Most events are dispatched to downstream services within seconds, subject to the latency and rate limits of each provider. Meshes queues, retries, and backs off automatically so you get fast delivery when providers are healthy and graceful degradation when they’re not.
How do you handle data security?
Credentials are encrypted at rest, scoped per workspace, and never shared across tenants. We minimize the payloads we store, encrypt data in transit and at rest, and provide audit logs so you can see exactly what was sent and where.
Can I separate development, staging, and production?
Yes. You can create separate workspaces for dev, staging, and production, each with its own connections, rules, and limits. That lets you test changes safely before promoting them to production.
Do I need to expose my own webhooks?
You send events to Meshes over HTTPS. For downstream systems, Meshes can call their APIs or webhooks directly—no extra public endpoints or custom queueing layer required on your side.