How to forecast what an integration platform will cost as you grow

An integration platform bill grows with whatever the vendor meters. Per-user and per-connection pricing grows as more people and systems join. Per-task, per-credit, and per-execution pricing grows with every run, including loops over large record sets and, now, AI agents calling tools. The unit matters less than three things you can check before you sign: what counts, what your own workflows use, and what happens when you go over. On Tray.ai, usage is measured in Tasks, adding users or connections doesn’t change the price, retries aren’t charged, and an annual commitment fixes your cost, with any growth settled at a true-up.

The worry behind the question is usually a specific one. A tool that looked affordable in year one came back at renewal priced against a footprint nobody had forecast. Or a usage-priced bill jumped after a second team started using the platform, and the first anyone heard of it was the invoice. Integration platforms are prone to both, because the work they meter grows in ways that are hard to see from outside: more records, more frequent runs, more teams, and now agents deciding for themselves how many calls a request needs.

What integration platforms charge for

Every platform meters something, and the unit decides what makes the bill move.

Pricing units as each vendor publishes them.¹

No unit is predictable or unpredictable on its own. Per-user pricing is easy to forecast until a second department adopts the tool. Per-execution pricing rewards long workflows and still counts every run of a polling trigger that fires every minute. Per-task pricing tracks the work done closely, which makes it fair, and it also means the bill moves whenever the work does. If predictability is why you’re leaving Workato, here are the alternatives compared by how they bill.

Where the surprises come from

A loop meets a bigger data set. A workflow tested against 200 records runs against 20,000 in production. On any per-step, per-task, or per-credit model, each pass through the loop counts, so the cost of that workflow scales with the data rather than with how often it runs.

A schedule nobody revisited. A workflow that polls every minute runs 43,200 times in a 30-day month, whether or not anything changed. Switching to a webhook, or narrowing the schedule to business hours, is often the cheapest fix available. Tips for using fewer Tasks in Tray works through several patterns like this.

A second team adopts the platform. The first contract was sized for one department’s integrations. A year later, three teams are building on it, which is a good outcome and a different bill.

Agents start calling tools. An agent decides at runtime how many tool calls a request needs, so the same question can cost different amounts on different days. Packaging a multi-step job into one tool makes the number of calls more predictable, and it cuts the token cost of each conversation too.

The renewal is priced against the original scope. By the time the renewal arrives, the estate has changed, and the quote may still reflect what you estimated before you had any usage data. Three questions to ask before anyone quotes a figure covers how to rescope it.

The common thread is visibility. The costly version is the one nobody saw coming: usage grew for months, nothing flagged it, and the first anyone heard was a true-up invoice.

How to forecast any platform before you sign

1. Run your own workflows in a trial, rather than the vendor’s demo workflows.
2. Read usage per run for each workflow from the platform’s own usage reporting, then multiply by how often each one runs.
3. Model two and three times today’s volume, and add the workflows already on next year’s roadmap.
4. Ask what happens when you go over: an overage rate, throttling, an automatic upgrade, or a true-up at the end of the term.
5. Ask what isn’t charged, such as retries, failed runs, and test runs during development.
6. Ask how you’ll see growth coming: usage dashboards, alerts, and limits you can set yourself.
7. Get the cost for years one, two, and three in writing against your projected volumes, from every vendor on the shortlist.

How predictable is Tray.ai pricing as usage grows?

You know your annual Tray cost when you sign. You commit to an annual volume for a fixed annual cost, and larger volumes get preferential pricing. If your usage grows past your plan, the difference is settled at a true-up.²

What you’re measured on. Integrations, automations, MCP tools, and agents are measured in Tasks. Apps built on Tray Helix are measured in Helix Compute Units (HCUs), a single unit covering deploy, compute, database, storage, data delivery, and requests.²

What a Task is. A Task is one operation Tray performs on a piece of your data. The trigger firing is one Task, and so is each connector or service step and each pass through a loop or boolean. A Task is not an API call, so a connector step that makes several API calls still counts as one Task.²

What doesn’t change the price. There are no per-user or per-connection fees, and no runtimes to buy and install, so adding people or systems doesn’t change what you pay. Retries aren’t charged.²

How you see it coming. Usage dashboards show your Task and HCU usage, and you can set monthly limits.²

How you size it. The free trial runs for 30 days with no card and no sales call. Run your own workflows during the trial to see how many Tasks they use, so the plan is sized on real usage rather than an estimate.²

What Tray doesn’t publish is a list price for each iPaaS plan. Pro, Team, and Enterprise are quoted, so you’ll still need a conversation to get a number for your volume. Tray Helix Builder Edition, for taking AI-built apps and integrations to production, starts at $50 a month.^1,2

Where plan choice changes cost

Usage is one lever. The plan and its add-ons are the other.

On Team, add-ons include HIPAA, SSO, regional hosting, 30-day log retention, log streaming, and on-premise connectivity. HIPAA, SSO, regional hosting, and on-premise connectivity are included in Enterprise. Agent Development, which brings Agent Gateway for MCP and Agent Builder together, is an add-on.² Support is the last lever: Tray Advantage comes with every plan, and Tray Advantage Plus is an upgrade, so it’s worth knowing what support each plan includes before you size the contract.

If you’re comparing Tray with Workato specifically, the Tray.ai and Workato comparison sets out how each prices, and how Workato pricing works covers Workato’s side in detail.

Sources

1. Tray.ai blog, The best Workato alternatives (pricing units and Tray Helix Builder Edition entry price, with vendor sources and check dates): https://tray.ai/blog/workato-alternatives/
2. Tray.ai, pricing: https://tray.ai/pricing/