Skip to main content
Billing, Plans & Credits

Agent Runner Plans and Concurrency Slots

An Agent Runner plan is a flat monthly subscription for your whole organization. It sets how many automation runs you may have in flight at once, and it unlocks two things a connector plan does not:…

Written By Christopher Scaminaci

Last updated About 22 hours ago

An Agent Runner plan is a flat monthly subscription for your whole organization. It sets how many automation runs you may have in flight at once, and it unlocks two things a connector plan does not: bringing your own Anthropic key on any connector tier, and setting a per-automation queue wait.

This is the one StackJack subscription that is not per connector. Everywhere else StackJack bills per connector — see How billing works — but an Agent Runner plan is held by the organization and is billed separately from every connector you have activated.

The tiers and what they include

TierConcurrent runs included
Pro1
Business3

Extra concurrency slots are sold as a separate add-on subscription, in whatever quantity you buy. Prices are shown at checkout — they are not listed here and are not shown in the portal.

Negotiated plans are also possible: StackJack can arrange a flat monthly plan with a slot count set for your organization instead of a published tier.

How to get one

There is no buy button in the portal for an Agent Runner plan or for extra slots. To start one:

  • Buy BYOK Pro or BYOK Business yourself on stackjack.io/automations. The checkout is handled by Paddle, the same provider as connector upgrades, and your plan is activated automatically once payment is processed. Check out with the same email address and company name your organization signed up with, so the checkout matches your organization. If you are not sure which address that is, ask your account owner before you buy. If the plan does not appear on your organization after you buy, contact support@stackjack.io rather than buying again.
  • For extra slots, contact StackJack and use the checkout link we send you. Slots need an active base plan.
  • For a negotiated plan, contact StackJack directly — those are configured for your organization rather than bought self-serve.

How many runs you can have at once

Your ceiling is the slots your base plan includes, plus every extra-slot add-on you hold, with a floor of one run. Two things about that arithmetic are worth knowing before they surprise you:

  • Extra slots need a live base plan. If the base plan lapses, add-on slots stop counting toward your ceiling even while you are still paying for them.
  • Organizations with no Agent Runner plan are not unlimited. They run on the platform allowance, which is 25 concurrent runs.

When every slot is busy, a triggered run is saved as Queued and starts automatically as a slot frees — it is not dropped, and while it waits it holds no AI session and reserves no credits. A run that cannot be queued is refused instead, and the refusal names your organization's own slots rather than the platform.

For all of that in full — what counts against a slot, which triggers can queue, how long a queued run waits, and how to read the Concurrency card on Automations → Credits — see Concurrency, slots, and the run queue.

What the plan also unlocks

  • Bringing your own Anthropic key on any connector tier. An Enterprise connector tier is the other route to this; an Agent Runner plan grants the same eligibility whatever your connector plans are. See Bring your own Anthropic key.
  • A per-automation queue wait. The advanced builder's Queued-run patience (minutes) field lets you decide how long a queued run of that automation waits before it gives up — including waiting indefinitely. Without an active Agent Runner plan the field is not editable, and it shows the automation's current setting rather than the platform default. If your plan lapses, an existing setting is left exactly as you saved it and keeps applying; it is not reset. See Concurrency, slots, and the run queue and Create with the advanced builder.

When a plan ends or a payment fails

  • Past due or paused. Your organization keeps running automations, and a key you brought yourself keeps being used, but your purchased slots stop applying until payment recovers — you fall back to the platform allowance for concurrent runs.
  • That fallback can change your ceiling in either direction. Because the platform allowance is 25, falling back can raise your ceiling as easily as lower it, depending on how many slots you bought.
  • Canceled. Your purchased slots go away, the per-automation queue wait stops being editable, and — if your Anthropic key was enrolled on the Agent Runner route rather than an Enterprise connector tier — StackJack stops using that key and pauses automation runs rather than moving them onto credits. Your key is not deleted. See When an Agent Runner plan ends.
  • Re-subscribing restores everything, including use of a key that was left on file.

A plan still in its trial period counts as active throughout, so none of the above applies while a trial is running.

Still need help? Ask the team