Answers to the rollout, architecture, and pricing questions technical buyers ask first
What changes in our app to use Meshes?
Usually one thing: emit a single event to Meshes instead of wiring each destination directly. Your product keeps the business logic; Meshes handles outbound routing, retries, and delivery behavior after the event leaves your app.
How does Meshes handle multi-tenant SaaS?
Workspaces isolate connections, credentials, rules, limits, and event history. Use them per customer, environment, or region so tenant boundaries stay clean without scattering integration logic across your app.
What happens when a destination is down or rate-limiting?
Meshes retries with backoff, records failure details per destination, captures dead letters when needed, and gives you a replay path once the destination is healthy again.
Can we start with one integration and expand later?
Yes. Many teams start with one event type and one destination, prove the flow, then add more tools and rules without changing the ingestion pattern in their app.
Which destinations do you support today?
Meshes supports the destinations shown across the site and docs today, including HubSpot, Salesforce, Intercom, Mailchimp, Zoom, Resend, and generic webhooks for custom endpoints.
When should we book a technical demo?
Book a demo if you are planning a production rollout, need help sizing events and workspaces, or want to pressure-test the design for customer-specific integrations. If you want to validate the flow yourself first, start on the Developer plan.
Do we have to host any infrastructure?
No. Meshes is fully managed. You send events over HTTPS, and Meshes handles queues, retries, fan-out, dead letters, and delivery state.
How do we send events to Meshes?
You can send events over HTTPS from any language, or use a lightweight SDK. The event ingestion flow is intentionally small so you can drop Meshes into an existing app, job runner, or webhook pipeline quickly.
Can we separate development, staging, and production?
Yes. Create separate workspaces for dev, staging, and production so each environment has its own connections, rules, limits, and event history.
How do you handle data security?
Credentials are encrypted at rest, scoped per workspace, and never shared across tenants. Data is encrypted in transit, and audit history helps teams inspect what was sent and where.
What happens if we exceed our included events or limits?
Usage is enforced by plan. If you are approaching a limit, move up to a larger plan before it interrupts traffic. For sustained higher volume or pooled usage needs, talk to us about Scale or Enterprise.
Do you offer a free trial?
The Developer plan is free and is the best way to validate your event flow before rolling Meshes into production.