Atlassian is about to bill your automations by the step

For years, a Jira automation rule was one rule, and running it was one run. Starting December 3, it's a pile of steps, and each step goes on a meter. Somewhere, a very small spreadsheet is about to become very important to a lot of admins.

On September 1, 2026, Atlassian announced that it's expanding usage-based pricing across its cloud products. Rovo credits, automation steps, Assets objects and AI agent resolutions all get meters, and for most of them billing starts on December 3. Atlassian's own licensing page says subscriptions come with a monthly included allowance of these metered capabilities. Past that allowance, you pay for what you use.

What changes for automation

The part worth slowing down for is how automation gets counted. Until now the unit was the flow run: a two step rule and a twenty step rule each counted as one. According to the partner write-ups summarizing the announcement, the unit becomes the step. Every action, condition, branch and loop iteration counts. A rule that checks a field, branches three ways and posts a comment is not one thing anymore. It's several.

Two details from those summaries are the kind that bite later. First, steps count even when they accomplish nothing, so a condition that evaluates to "no match" still spends allowance. Second, the allowance is pooled across the organization and refreshes monthly without rolling over. One busy team with a chatty rule can use up what everyone else was counting on. One partner write-up reports overage at $0.50 per 1,000 steps. That's a single source, so check Atlassian's current terms before you put it in a budget.

Admins do get controls: a monthly cap on extra usage, the ability to switch off overage for a given meter, and usage packs. Each meter is tracked separately, so running out of automation steps doesn't touch your Rovo credits. That's sensible. It also means there are now several dials where there used to be one subscription line.

The mild comedy of it

Think about what automation was sold as. It was the thing that saved you from doing tedious work by hand. You set up a rule once and it quietly handled the busywork forever. Now the rule has a running cost per decision it makes, and the person who built it needs to audit how often it hesitates.

Somebody will end up writing a rule to monitor the rules. That rule will have steps. We'll leave that one there.

Fair is fair

Metering isn't villainous. Compute costs money, AI steps cost a lot of money, and flat pricing quietly makes light users subsidize heavy ones. Plenty of customers will prefer paying for what they actually run. If your rules are few and tidy, you may never notice the change. The honest case against it is mostly about predictability: a flat seat price is easy to approve, and a variable one needs somebody watching it.

What a small team should take from this

Automation exists because tracking work by hand in a complicated tool is tedious, and the tool generated the tedium in the first place. We made a version of this argument in why teams update their tools more than their work: the setup grows until it needs its own upkeep. Add a meter to the upkeep and the cost stops being just time.

If you're on Jira with a handful of people, the practical move is small. Before December, list the rules that run most often, and ask whether each one earns its steps. Some will. Some were built in a burst of enthusiasm and have been running at three in the morning ever since. If the whole exercise feels like too much for what you actually need, our comparison of Axtio and Jira and our list of Jira alternatives for small teams are good places to sanity check that.

There's a pattern here too, and it's not unique to one vendor. We looked at a related one in monday.com's shift away from small teams, and at the AI side in AI agents in project tools. Big platforms follow their biggest customers, and a bill that scales with activity is easier to justify at that size than at five people.

The simple alternative, stated plainly

Axtio doesn't automate anything, which is either a limitation or a feature depending on your mood. The free version keeps everything in your browser, has no usage meter, and answers one question: who has the ball on each action. Moving a card between Mine, Other, Next Steps and Done is a drag, and it costs exactly nothing, including at three in the morning. That won't suit a team running complex cross-project workflows, and we'd rather say so than pretend otherwise. For tracking what you owe and what you're waiting on, though, a lighter tool has one clear advantage: nothing to audit.

Sources

Atlassian usage-based pricing page for the monthly included allowance. The September 1, 2026 announcement date, December 3 billing start, per-step automation counting, pooled monthly allowances and the $0.50 per 1,000 steps overage figure come from partner summaries, including The Jira Guy and Mumo Systems, which are secondary sources. Allowance sizes by plan were not confirmed, so check your own plan's terms. Accurate as of October 2026.