For a small remote team that needs more Jira automation capacity, our starting recommendation is Standard plus measured overage. A prepaid pack deserves consideration when advance budgeting matters; Premium deserves consideration when you need its advanced features. Our worksheet below shows why: the modeled Standard overage is just $2.19–$9.19 monthly for 5–25 people.
By Remote Work Picks
Updated September 5, 2026
We compared documented features and pricing. All workloads below are hypothetical estimates, not measurements from a customer account or hands-on testing.
Affiliate disclosure: Remote Work Picks may earn commissions from links marked as affiliate links. The Atlassian links in this draft are direct source links and carry no affiliate tracking.
Jira automation steps pricing as of September 2026: what changes on December 3
Atlassian announced expanded usage-based pricing on September 1, 2026, with allowance enforcement and extra-usage billing scheduled for December 3, 2026. Automation is measured by executed steps rather than completed flows, so a recurring assignment workflow can consume multiple steps each time it runs. Source: Atlassian’s announcement.
Treat this as a planning worksheet for the announced change. The estimated charges below are not a claim that Atlassian is already collecting those charges on September 5.
Published specifications — As of September 2026
| Item | Published allowance or price | Buying implication |
|---|---|---|
| Jira Free | 150 steps per subscription monthly; up to 10 users | Allowance is not multiplied by users |
| Jira Standard | 400 steps per user monthly | Starting allowance for our worksheet |
| Jira Premium | 750 steps per user monthly | Adds 350 steps per user over Standard |
| Extra automation usage | US$0.50 per 1,000 steps | Pay for consumption beyond allowance |
| Minimum automation usage pack | US$20 for 40,000 monthly steps | Prepay for additional capacity |
| Unused pack allowance | No rollover | Size against a normal month, not one exceptional spike |
Sources: Jira pricing, Automation licensing, and usage-pack terms.
The useful distinction is between three separate purchases: your Jira subscription, additional automation capacity, and access to advanced automation features. Buying more capacity does not itself upgrade your plan.
Count your remote team’s executed steps, including checks that do no work
A flow that checks a condition and exits can still consume steps. Atlassian’s calculation documentation includes executed triggers, conditions, actions, branches, and loops. It also counts certain outcomes where nothing changes, including NO_ACTIONS_PERFORMED, and a trigger returning NO_MATCH. System-side errors and throttled runs where no step executes are excluded. Rovo-powered components use a separate credit meter. Source: Atlassian’s usage calculation guide.
That makes “we have six automation rules” an unhelpful budget input. You need execution frequency and the paths those executions take.
Consider an assignment flow:
- A work item triggers the flow.
- A condition checks whether it needs assignment.
- An action assigns an owner.
- An action sends a handoff notification.
For this simplified model, a successful pass uses four steps. If the condition stops the flow after the second component, that pass uses two. Those are estimates based on the described execution paths; reconcile them with your account’s usage data.
A workload you can replace with your own numbers
Assume 22 working days each month and the following activity:
Hypothetical workload inputs — As of September 2026
| Workflow | Assumed monthly activity | Estimated monthly steps |
|---|---|---|
| Assignment and handoff | 5 executions per person per working day, all taking the four-step path | 440 per person |
| Async status notification | 10 executions per person per working day, each with a trigger, condition, and notification | 660 per person |
| Scheduled check finding no match | 40 trigger executions per working day across the organization | 880 per organization |
| Total | N Jira users | 1,100 × N + 880 |
The assignment calculation is 5 × 22 × 4 = 440. The notification calculation is 10 × 22 × 3 = 660. The shared checks add 40 × 22 = 880.
These assumptions deliberately expose two different drivers: activity that grows with the team and scheduled activity that continues regardless of headcount. They are not benchmarks for a “typical” remote company.
For a lighter case, halve both per-person execution counts while keeping the shared checks. Estimated usage becomes 550 × N + 880. For a busy month, double the original per-person counts: 2,200 × N + 880.
Before using either estimate, include any repeated branch actions, retries, weekend schedules, or other flows your organization actually runs. A multi-item branch needs its own execution model; counting its diagram boxes once can miss repeated work.
Calculate your pooled allowance and monthly overage for 5, 10, or 25 people
Automation allowances are pooled across the organization. Your Jira contribution is only part of the picture if other eligible subscriptions contribute capacity—and their automation activity also consumes the pool. Atlassian’s billing documentation describes the total allowance as the sum of contributions from relevant subscriptions. Source: How usage-based pricing works.
Our examples assume one standalone Jira subscription, no other allowance contributions, and no existing packs. They also assume the team’s headcount equals its eligible Jira user count. Use your admin dashboard’s allowance when those assumptions do not fit.
The worksheet formulas are:
Standard allowance = Jira users × 400
Premium allowance = Jira users × 750
Excess steps = max(0, total monthly steps − pooled allowance)
Estimated overage = excess steps ÷ 1,000 × $0.50The rate calculation follows Atlassian’s published overage formula.
Base workload estimates — As of September 2026
| Jira users | Estimated steps | Standard allowance | Standard excess | Standard overage | Premium allowance | Premium overage |
|---|---|---|---|---|---|---|
| 5 | 6,380 | 2,000 | 4,380 | $2.19 | 3,750 | $1.32 |
| 10 | 11,880 | 4,000 | 7,880 | $3.94 | 7,500 | $2.19 |
| 25 | 28,380 | 10,000 | 18,380 | $9.19 | 18,750 | $4.82 |
These are automation charges only, excluding subscriptions and taxes. Dollar estimates are rounded to cents; they do not reproduce invoice rounding rules.
In the lighter scenario, Standard overage falls to $0.82, $1.19, and $2.32 respectively. In the busy scenario, it rises to $4.94, $9.44, and $22.94.
That sensitivity check matters more than choosing one confident-looking forecast. The 25-person team crosses the minimum pack’s $20 price in the busy scenario, but that does not establish a pack discount. It simply means the team would consume more than 40,000 extra steps.
Add your chosen estimate as a separate line in your remote-team software budget. Keeping subscription and consumption costs separate makes later changes easier to explain.
Pay overage or buy a usage pack: the $20 minimum and unused-capacity tradeoff
As of September 2026, Atlassian lists automation overage at $0.50 per 1,000 steps and prepaid packs starting at $20 for 40,000 monthly steps. The published unit rates match. Unused pack allowance does not roll over, making budgeting predictability the principal distinction. Sources: Automation pricing and usage packs.
Our calculation is straightforward: $20 ÷ 40,000 × 1,000 = $0.50 per 1,000 steps.
At the published rates, prepayment has no per-step discount. If you consume fewer than 40,000 additional steps, the minimum pack costs more than paying for that consumption afterward.
Minimum-pack comparison on Standard — As of September 2026
| Jira users | Base-model excess steps | Postpaid estimate | Minimum pack | Unused pack steps | Additional cost of pack |
|---|---|---|---|---|---|
| 5 | 4,380 | $2.19 | $20.00 | 35,620 | $17.81 |
| 10 | 7,880 | $3.94 | $20.00 | 32,120 | $16.06 |
| 25 | 18,380 | $9.19 | $20.00 | 21,620 | $10.81 |
At exactly 40,000 excess steps, both approaches cost $20. At 50,000 excess steps, postpaid costs $25; a 40,000-step pack plus 10,000 postpaid steps also totals $25, assuming extra usage is enabled and permitted.
Choose overage when consumption is uncertain or below the minimum pack size. Its tradeoff is a variable bill, which needs monitoring.
Choose a usage pack when your organization values prepayment and expects to consume the purchased allowance. Its tradeoff is paying for unused capacity. Confirm the checkout terms, particularly if your underlying subscription is annual; the published pack table expresses capacity and prices monthly. Source: Atlassian’s pack documentation.
A pack alone is not a total spending cap if extra usage remains enabled. Conversely, disabling extra usage makes available capacity a constraint on continued operation. Atlassian also documents configurable monthly extra-usage limits, giving postpaid buyers a budgeting control without requiring prepayment. Source: Manage extra usage.
Our preference for the base workload is overage at all three team sizes. Paying $20 to cover a modeled $3.94 month would need an administrative reason.
Upgrade to Premium: compare the subscription increase with capacity savings and advanced features
As of September 2026, Jira Standard includes 400 automation steps per user monthly; Premium includes 750. The extra 350 steps offset at most $0.175 per user in monthly overage. This is Remote Work Picks’ calculation, not a vendor savings claim. Sources: Jira pricing and overage rates.
The calculation is 350 ÷ 1,000 × $0.50 = $0.175.
That ceiling assumes you would otherwise pay overage and consume every additional included step. If your existing organization-wide allowance already covers the workload, the capacity saving is zero.
Capacity-only upgrade ceiling — As of September 2026
| Jira users | Additional monthly steps | Maximum monthly overage avoided, before rounding |
|---|---|---|
| 5 | 1,750 | $0.875 |
| 10 | 3,500 | $1.750 |
| 25 | 8,750 | $4.375 |
For 25 users, a Premium subscription increase above approximately $4.38 monthly cannot be recovered through this allowance increase alone under the unchanged-workload model.
Use your actual subscription quotes
Jira’s pricing calculator accepts a user count and billing cycle. Its documentation distinguishes exact-user monthly pricing from annual user tiers. A headline per-user price is therefore insufficient for a five-person purchasing decision. Source: Jira’s subscription pricing explanation.
Get Standard and Premium quotes for the same 5, 10, or 25 users, currency, billing cycle, and tax treatment. Record the quote date. For annual quotes, divide the annual total by 12 for comparison, while keeping the upfront payment visible.
Let S be your Standard monthly subscription quote and P your Premium quote. Using the base workload:
Quote worksheet — As of September 2026
| Jira users | Standard plus overage | Standard plus minimum pack | Premium plus overage |
|---|---|---|---|
| 5 | S + $2.19 | S + $20.00 | P + $1.32 |
| 10 | S + $3.94 | S + $20.00 | P + $2.19 |
| 25 | S + $9.19 | S + $20.00 | P + $4.82 |
These are formulas to complete with account-specific quotes, not quoted subscription totals.
For example, if a 10-person team’s actual Premium quote is $60 more each month, the base model leaves $60 − $1.75 = $58.25 for Premium’s features to justify. The $60 is an illustrative input, not an Atlassian price.
When Premium has a defensible case
As of September 2026, Atlassian reserves advanced automation steps for Premium and Enterprise. Its documentation includes Branch at the same time, Branch with conditions, Delay until, and Loop, with app-specific eligibility. Source: Advanced automation steps.
For a distributed team, a plausible reason to evaluate Premium is coordinating parallel onboarding tasks or waiting for an event before continuing a handoff. Write down the exact workflow and required component before upgrading.
Then estimate the work that component could replace. If it removes a recurring manual coordination task, compare that expected benefit with the subscription difference remaining after capacity savings. Treat time savings as a hypothesis to validate.
Also recalculate usage after redesigning the flow. Advanced logic can change how many components execute; a cleaner diagram does not establish a lower bill.
If the underlying issue is broader project coordination, revisit your project-management tool requirements before letting an automation allowance dictate the software decision.
Protect assignments and async handoffs before enforcement begins
The operational risk deserves more attention than a few dollars of modeled overage. Atlassian says that when capacity is exhausted with extra usage disabled, new flow executions stop while in-flight flows finish. Triggering events during the pause are not queued for later replay. There is no individual-flow priority designation. Source: Automation licensing FAQ.
For a remote team, plan around the handoff someone could miss while the owner is offline.
- Record a baseline. Open Atlassian Administration → Insights → Platform usage and inspect the automation meter. Capture the allowance, consumption, and contributing subscriptions. This path is documented in Atlassian’s billing guide.
- Name the essential flows. Identify assignments, customer escalations, and onboarding handoffs that require a manual fallback. Put that fallback alongside your remote onboarding procedure.
- Assign a billing owner and backup. Decide who reviews alerts and who can adjust capacity when that person is away.
- Choose a spending policy. Document whether overage is enabled, the permitted limit, and who can approve an increase. Atlassian documents notifications at 80% and 100%, but reaching a configured extra-usage limit can restrict metered features. Source: Extra-usage controls.
- Reduce low-value checks first. In our model, eliminating half the no-match checks removes 440 steps—only $0.22 of potential overage. Avoid disrupting useful handoffs to chase pennies.
Start with your measured usage and request the matching Jira subscription quotes. For the modeled workloads, Standard plus overage is the economical starting point. Buy a pack for a documented budgeting need, and buy Premium for a workflow capability worth its remaining cost.
Refresh required December 3, 2026: Verify enforcement and billing behavior when the announced changes take effect. Recheck earlier if allowances, rates, pack terms, feature eligibility, subscription quotes, or the launch date change. Source: Atlassian’s announcement.