Automations Your own AI, credits and limits.

/automations/pricing Available now

Run automations on your own AI: your Azure Foundry or your own Anthropic key, on one flat runner plan. Credits are there to try it, and a cap stops a run at your limit.

[ 02 // how it runs ]
[ 02 ]

Run it on your own AI.

An automation runs on your Azure Foundry or on your own Anthropic key. Your cloud bills the AI and StackJack charges no credits for it. StackJack still runs the schedule, the triggers, every tool call, the approvals and the run history.

Your Azure Foundry

StackJack sets it up in your subscription

  • Claude, or another model Azure sells that can run an automation
  • StackJack creates the Foundry resource and the model deployments for you
  • Keyless sign-in or a stored key, and a check on each deployment
  • Azure bills the model use, in your subscription. You choose the Azure region

An owner or administrator connects it under Automations, then Foundry. The builder’s AI help can run there too. No StackJack credits. Azure Foundry in the docs

Your Anthropic key

Add your API Console key

  • Every Claude model, Opus 5.5 by default
  • Runs, builder chat and AI Assist bill your Anthropic account
  • Only an owner or co-owner adds the key
  • No StackJack credits

Add your Anthropic API Console key (it starts with sk-ant-) under Automations, then Credits. BYOK in the docs

One runner plan, for either

Priced by how many automations run at the same time. Unlimited runs. You pay your own cloud for the AI, and StackJack a flat monthly rate for the runner platform. The Portal and the help center call a BYOK plan an Agent Runner plan.

BYOK Pro
$199
a month · 1 automation at a time
BYOK Business
$299
a month · 3 automations at a time
Extra slot
+$99
a slot, a month · on top of an active plan
Enterprise
Qualifies
an Enterprise connector plan needs no BYOK plan

How many runs at once

Without a plan, your organization can run up to 25 automations at the same time on credits. A BYOK plan replaces that limit with its own slots: 1 on BYOK Pro, 3 on BYOK Business, plus any slots you add. Extra runs wait in a queue and start when a slot frees. Slots need an active BYOK base plan. Slots and the run queue in the docs

Connector limits still apply

Connector tool calls still count against your connector plan’s monthly allowance. BYOK changes who pays for the AI, not your connector limits.

What you need

For Azure Foundry: an Azure subscription. To deploy Claude it must be one Azure sells Claude on, which leaves out CSP subscriptions; the other models do not need that. For your own key: an Anthropic API Console key. Buy the plan with the same email address and company name as your StackJack organization.

If a plan ends

Runs on your own AI pause instead of moving back to credits, and your key is not deleted.

[ 03 // how credits work ]
[ 03 ]

Reserve first.
Refund the difference.

Just trying it? Start on credits. Credits pay for the AI work of an automation on StackJack’s own AI account, with no plan. Credits are reserved before a run, tracked as it runs, and finalized after, and every transaction is in the ledger. 1 credit is $0.10 of usage today.

1

Estimate up front

Before any run, credits are reserved up to the agent’s per-run cap. Complexity and expected runtime inform the estimate.

2

Live as it runs

Token usage, tool calls, and duration are tracked in real time. The estimate tightens as the run progresses.

3

Refund the difference

After the run, actual consumption is finalized. Unused reservation is refunded. Every transaction is in the ledger.

Credits never expire

Stack any number of packs.

A ledger you can read

Reservation, finalize, and refund transactions are all visible.

A cap on each automation

Set Max credits per run. A run stops when it reaches the cap, so it stays near your budget.

The builder uses credits too

The wizard is credit-aware: reserved, finalized, refunded on failure.

Just trying it? Start on credits. Credit packs are a one-time purchase with no plan and no subscription. Up to 25 runs can go at once.

Buy a credit pack
[ 04 // faq ]
[ 04 ]

Questions.

How do credits relate to actual usage?

Before every run, credits are reserved based on the agent’s complexity and expected runtime, up to the automation’s Max credits per run cap. As the run executes, real token and tool-call usage is tracked. At the end the run finalizes: unused reservation is refunded, and every transaction shows in your ledger.

What happens if a run blows past its credit cap?

Runs have a Max credits per run setting and the runtime enforces it. The run stops with the status Out of credits and whatever summary was produced to that point. If actual consumption exceeds reservation within the cap, the delta is recorded in the ledger rather than hidden. This preserves billing truth.

Can I run Automations on my own AI?

Yes, in two ways. Azure Foundry: StackJack sets up a Foundry resource and model deployments in your own Azure subscription, and Azure bills the model use. Your own Anthropic key: add your Anthropic API Console key under Automations, then Credits, and runs, builder chat and AI Assist bill your Anthropic account. Either way needs BYOK Pro or BYOK Business, on the Automations page, or an Enterprise connector plan, and uses no StackJack credits. StackJack still records an audit entry for every run.

[ 06 // start ]

Recurring work, managed.

Automations are available today for every StackJack user. Run them on your Azure Foundry or your own Anthropic key for a flat monthly rate, or buy a credit pack to try one. Packs never expire, and you see real-time usage against your balance as your agents run.