FAQ

We have a free developer account you can use to test out the service.

You can cancel your subscription at any time. You can do this from your account settings.

You can find your invoices in your account settings.

We accept all major credit cards.

Yes, you can upgrade or downgrade your plan at any time. You can do this from your account settings.

Not at this time.

No. Meshes is fully managed. You send events over HTTPS, and we handle queues, retries, fan-out, and storage.

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.

You segment tenants into workspaces. Each workspace has its own connections, rules, limits, and audit history. Credentials are never shared across workspaces.

On Developer, Starter, Pro, and Scale, usage is enforced with hard caps: if you hit your limit, new events may be throttled or rejected until your usage resets or you upgrade. For sustained higher volume, we recommend Scale or Enterprise so we can size a plan around your traffic. Enterprise plans can be configured with pooled usage and soft overages so you can absorb spikes without interrupting traffic.

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.

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.

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.

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.

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.

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.