RelayStack pricing

RelayStack is usage-based with a stated platform price. Each plan has an annual platform fee that includes a block of executions, and additional executions are billed at the rate shown for that plan.

An execution is one run of one workflow step. Retries of the same step are not billed, so a flaky downstream API does not raise your bill.

Plans

Builder

$6,000 per year

For a small engineering team running its first production workflows.

  • 5 million executions included each year
  • Overage at $0.60 per 1,000 executions
  • Full API, CLI, and SDK access
  • Community support

Platform

$42,000 per year

For organizations that run orchestration as shared infrastructure.

  • 150 million executions included each year
  • Overage at $0.30 per 1,000 executions
  • Replay and event history for 90 days
  • Private networking options
  • Priority support with an assigned engineer

How usage billing works

Your annual platform fee is billed up front and includes the executions listed for your plan. If you use more, the overage is billed monthly at your plan's rate, and you can see running totals in the usage view at any time.

Usage alerts can be sent to an email address or a webhook when you reach set percentages of your included executions, so overage never comes as a surprise.

Frequently asked questions

What counts as an execution?

One run of one workflow step counts as one execution. A workflow with five steps that runs once uses five executions, and retries of a failed step are not counted again.

Can we use the API without the dashboard?

Yes. Everything in the dashboard is available through the API, the CLI, and the SDKs, and many teams never open the dashboard except to read traces.

Which systems can workflows call?

Any system with an HTTP API. Customers commonly orchestrate Salesforce, HubSpot, Slack, Microsoft Teams, Zendesk, Snowflake, NetSuite, SAP, and Oracle alongside their own services.

How do we test a workflow before deploying it?

Run it locally with the CLI against recorded events, then deploy it to a staging environment. Replay lets you run a real production event against a new version before you promote it.