Atlassian's new usage-based pricing lands Dec 3: what it actually costs a small team running Jira Automation and Rovo

December 3rd is when Atlassian starts charging for usage on Automation Steps, Rovo AI credits, and a handful of other meters — unless you're still on Server/Data Center Jira, this affects you. Atlassian announced the change on its own company blog September 1st (the meters went live in your Admin settings the same day), and if your team runs any meaningful automation or touches Rovo AI beyond a basic search, you'll want to know the actual numbers before the clock runs out.

What's actually changing

Atlassian is layering usage-based "overage" billing on top of the existing per-seat price for five areas:

• Rovo AI credits — actions like Chat, Agents, Think Deeper, the Coding Agent, Confluence AI Slides, and Teamwork Graph queries. Search, inline summaries, and rewrites stay free.
• Automation Steps — every trigger, condition, action, branch, or loop in a workflow (loops count per iteration).
• Assets objects — unique asset records stored in Jira or Teamwork Collections.
• CSM AI Resolutions — outcome-based billing when Rovo's Customer Service AI closes a ticket with zero human involvement.
• Bitbucket resources — build minutes, Git LFS storage, package storage, network usage, now pooled at the organization level.

For most small teams in Jira or Confluence, the two that actually bite are Automation Steps and Rovo credits. The mechanic is simple: your tier gets a monthly allowance per user, pooled across the whole org. Go over it, you pay overage. Here's where that allowance lands, by product and tier:

Tier	Jira	Confluence	JSM	Teamwork	JPD
Free	150	50	1,250	200	100
Standard	400	100	3,000	2,500	300
Premium	750	250	6,500	5,000	500
Enterprise	1,000	500	9,500	7,500	750

Overage costs $0.50 per 1,000 steps. Simple enough — until you look at what actually changed underneath it.

Automation: the part that should worry you more than the price

Enterprise customers used to get unlimited automation. That's gone — Enterprise Jira now tops out at a pooled 1,000 steps per user per month, same finite-allowance structure as everyone else. Independent Atlassian community analyst thejiraguy.com put it bluntly: "removing an unlimited tier changes what a customer is buying." That's not hyperbole; it's a genuine downgrade in what Enterprise pricing used to promise, dressed up as a metering change.

The quieter, more expensive change: Atlassian's old billing only counted successful automation runs. The new meter counts every step execution — including failed runs and empty ones. A five-step workflow that errors out on step three still burns five steps. An automation that fires but matches no conditions and does nothing still costs a step. If your automations have a flaky failure mode nobody ever bothered to fix, you're about to pay for it monthly.

Worked example: a 5-person Standard team pools 5 × 400 = 2,000 Jira automation steps a month. Run status-sync automations, Slack notifications, and a couple of CI-triggered escalations, and 3,000 steps in a month isn't a stretch for a team that's automated its ticket lifecycle. That's 1,000 steps over allowance — at $0.50 per 1,000, a $0.50/month overage. Trivial today. Add a second team, a flaky workflow re-triggering on failure, or a company-wide automation habit, and that $0.50 becomes $15–$30 fast, for work nobody explicitly signed off spending on.

Rovo credits: check the default before December 3rd

Rovo AI runs on credits: 25 per user/month on Standard, 70 on Premium, 150 on Enterprise, pooled org-wide. A basic AI action costs roughly 10 credits; a "Deep Research" query costs roughly 100. A 5-person Standard org's pooled 125 credits covers about a dozen basic actions for the whole team, or a single Deep Research query — not both, and not much else.

The thing you actually need to check before December 3rd: overage billing is enabled by default. If your team exceeds its Rovo allowance, Atlassian charges $0.01 per credit ($10 per 1,000) automatically, unless an admin explicitly opts out. No warning bill, no soft cap — it just bills. A team running a few Deep Research queries a month can land at 200+ credits against a 125-credit allowance; that's 75 credits over, or $0.75. Small money, deliberately structured so nobody notices it until it isn't.

Atlassian does give you the controls to prevent this: admins can disable overages outright (automations and AI actions simply stop when the allowance runs dry, no bill), set a hard spending cap, or pre-buy usage packs. Usage notifications fire at 80% and 100% of allowance — but only inside the Admin console, not by email or Slack, so nobody sees them unless someone goes looking.

Before December 3rd, actually do this

1. Log into Admin > Usage and check where you stand today. Meter data can take up to a week to populate, so don't wait until December 2nd.
2. For Automation: tally your active workflows' rough monthly step count. Close to your allowance? Upgrade the tier, turn off overages and accept stalled workflows past the cap, or simplify the automations — a good excuse to finally delete the ones nobody remembers building.
3. For Rovo: decide your overage policy now, under Billing > Usage limits, rather than discovering Atlassian decided it for you.
4. Running Jira Service Management: your Automation allowance is far more generous (9,500 steps on Enterprise), but CSM AI Resolutions bill separately at $1.00 per ticket Rovo closes without human help — worth knowing if you're leaning on autonomous ticket resolution.

None of this touches base seat pricing, which is unchanged by this announcement — Jira Standard runs roughly $7.91/user/month, Premium roughly $14.54 (third-party pricing trackers, not an Atlassian-published figure, so treat it as directionally correct rather than exact). Everything above is pure incremental cost stacked on top of what you already pay.

When switching actually makes sense

If your team is purely dev-focused and doesn't touch Jira's ITSM or service-management side, Linear is worth a serious look. Its official pricing: Free ($0 — unlimited members, 2 teams, 250 issues), Basic ($10/user/month billed yearly, 5 teams, unlimited issues), Business ($16/user/month billed yearly, unlimited teams, more integrations), Enterprise (custom).

The catch: Linear's own advanced AI features — Coding sessions, AI-assisted loops — also draw on separate credits beyond the base plan. Same structural bet as Atlassian's change, just a smaller blast radius. You're not escaping metered AI billing by switching; you're escaping Jira's ITSM weight and a considerably more complex product to reason about. For a pure dev team drowning in Jira admin overhead, that trade might be worth making anyway — just don't go in expecting a flat-rate refuge.

Researched and drafted with AI assistance, checked against primary and vendor sources.