DEV Community: julian-ros

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

julian-ros — Sun, 13 Sep 2026 15:59:29 +0000

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

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.
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.
For Rovo: decide your overage policy now, under Billing > Usage limits, rather than discovering Atlassian decided it for you.
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.

Scaling transactional email: which provider fits at each growth stage (0 -> 100K+ emails/month)

julian-ros — Sun, 13 Sep 2026 11:15:48 +0000

Picking a transactional email provider feels like a five-minute decision — add an API key, send your first signup confirmation, move on. It stays a five-minute decision until you scale, at which point the plan you casually picked can turn into a migration project: rewriting send logic, re-verifying DNS records, hoping deliverability doesn't dip mid-cutover. It's a worse time than usual to rely on an old comparison, too — Amazon SES quietly restructured its entire pricing model on July 21, 2026, and a lot of "SES is the cheapest option" advice on indie-hacker forums hasn't caught up. Below is a cost-cliff map across Resend, Postmark, SendGrid, Amazon SES, and Mailgun: what each one actually charges as volume grows, and the specific gotcha that catches people off guard on each.

The five providers, side by side

Provider	Free tier	Entry paid plan	Cost at 100K emails/mo	Key gotcha
Resend	3,000/mo (100/day cap)	$20/mo — 50,000/mo	$90/mo (Scale plan)	Simplest model, but the most expensive at the top end
Postmark	100 emails, ever — no overage	$15/mo (Basic) — 10,000/mo	~$126/mo*	Free tier has zero overage room; upgrade before email #101
SendGrid	60-day trial only, no permanent free tier	$19.95/mo (Essentials)	~$110–200/mo† (unclear from public pricing)	Dedicated IPs require the Pro plan ($89.95/mo+), regardless of volume
Amazon SES	Discontinued for new signups since 2026-07-21	$0.16/1,000 (Essentials), no base fee	$16/mo (Essentials) to $127/mo (Pro)‡	Headline rate looks cheapest; add-ons (VDM, dedicated IP) change that fast
Mailgun	~3,000/mo (100/day)	$15/mo (Basic) — 10,000/mo	$90/mo (Scale)	Email validation is a separate paid add-on, not included

*Postmark: cheapest at 100K is Platform ($18/mo, 10,000 included, $1.20/1,000 overage): $18 + (90,000 × $1.20/1,000) = $126/mo.
†SendGrid's pricing page shows $0.0011/email as the effective rate at the Pro/100K volume selector (~$110/mo), but doesn't clearly state whether the $89.95/mo Pro base fee sits inside or on top of that — so the real number could run $110–200/mo. Use Twilio's own calculator before committing.
‡SES Essentials, no add-ons: 100 × $0.16 = $16/mo. SES Pro: $105/mo base + (100 × $0.22) = $127/mo. More on add-ons below.

What catches people out on each one

Resend stays simple on purpose: Free (3,000/mo, 100/day cap, 3 domains), Pro ($20/mo, 50,000), Scale ($90/mo, 100,000), and a flat $0.90-per-1,000 overage above whichever plan you're on. No dedicated-IP upsell, no separate add-on fees. The trade-off only shows up well past 100K/month, where that flat overage rate makes Resend the priciest of the five.

Postmark's free tier is real but unforgiving — 100 emails, period, with zero paid overage: send a 101st and you're forced to upgrade immediately. Its three paid plans (Basic $15, Pro $16.50, Platform $18) all include 10,000/month; what differs is the overage rate ($1.80, $1.30, $1.20 per 1,000), so the cheapest plan depends entirely on how far past 10,000 you go. Above 1.5M/month, Postmark moves to custom sales pricing.

SendGrid dropped its permanent free tier — what's left is a 60-day trial capped at 100/day, then a paid plan or nothing. Essentials starts at $19.95/mo, Pro at $89.95/mo, Premier is custom. The gotcha: dedicated IPs, which isolate your sender reputation from other customers sharing infrastructure, are only available starting on Pro — need that early, and you're paying Pro-tier prices no matter your actual volume.

Amazon SES is the one that changed under everyone's feet. Until July 21, 2026, pricing was a flat ~$0.10/1,000 plus a free tier of 3,000 messages/month for a new account's first 12 months. As of that date, AWS restructured it into three plans — Essentials ($0.16/1,000, no base fee), Pro ($0.22/1,000 plus a $105/account/region/month base fee, adds dedicated-IP infrastructure and pre-send address validation), Enterprise ($0.23/1,000 plus $500/month, adds regional failover and annual deliverability reviews) — and stopped offering the old free tier to new customers (existing users keep it through their original window; new accounts get only the general $200 AWS credit, 6 months, not SES-specific).

The Essentials rate still looks cheapest on this whole list, but add-ons change that. Independent commentary (cloudburn.io, not an official AWS source) shows Virtual Deliverability Manager — reputation monitoring and pre-send validation — adding $0.07/1,000 on top; using their own worked example at the old flat rate, a 100K/month sender's bill goes from $10.12 to $17.00 once VDM is switched on. A dedicated IP is separately priced at roughly $24.95/month, independent of any plan. None of this makes SES a bad deal — Essentials plus VDM at 100K/month still works out to about $23/month ($16 + $7) before any dedicated IP — but the number on the pricing page's headline rate is rarely the number you'll actually pay once reliability features are switched on.

Mailgun's ladder — Free (~3,000/mo), Basic ($15/mo, 10,000 included, $1.80/1,000 overage), Foundation ($35/mo, 50,000, $1.30/1,000), Scale ($90/mo, 100,000, $1.10/1,000) — is structurally similar to Postmark's. Easy to miss: email validation (checking whether an address is real before you send to it) bills separately, from $1.20 per 100 validations on Basic/Foundation down to $0.80 per 100 on Scale — a real line item if you validate on every signup. Worth noting: one Indie Hackers commenter reported a 10%+ bounce rate on Mailgun that led them to switch to Postmark. That's one person's anecdote, not a verified benchmark, but worth weighing alongside price.

Which one fits your stage

0–3,000/month: cost is close to irrelevant — Resend's free tier or SES Essentials (~$0.48/mo here) both cost effectively nothing. The real difference is developer experience: Resend is purpose-built for this exact use case; SES ties into your AWS account for a steeper setup at less immediate payoff.

3,000–50,000/month: plan choice starts to matter. Resend Pro is a flat $20/mo for anything up to 50,000, no overage math needed. Mailgun Foundation is a flat $35/mo up to the same ceiling. Postmark is the one that moves: at 30,000/mo on Platform you're at $18 + (20,000 × $1.20/1,000) = $42/mo; at 50,000/mo, $18 + (40,000 × $1.20/1,000) = $66/mo. Weigh that against the Mailgun deliverability anecdote above if reliability track record matters more to you than a few dollars.

50,000–100,000/month: Mailgun Scale and Resend Scale are both a flat $90/mo for the full 100,000. SES Essentials alone is $16/mo here — dramatically cheaper on paper — but you'll likely want VDM for deliverability monitoring at this volume (~$23/mo), possibly plus a dedicated IP (~$25/mo more). Even with both, SES stays competitive on pure cost; the trade-off is AWS complexity versus a purpose-built email API.

100,000+/month: growth curves diverge. Resend beyond 100K adds $0.90/1,000 (200,000/mo = $90 + $90 = $180/mo). Mailgun beyond 100K adds $1.10/1,000 (200,000/mo = $90 + $110 = $200/mo). SES Pro is $105/mo base + $0.22/1,000 ($127/mo at exactly 100K). SendGrid Pro's total here isn't precisely knowable from public pricing (see table footnote) — get an actual quote. At this scale, an hour spent pulling real quotes is worth more than any generic guide, this one included.

The piece this complements

There's already a solid DEV.to comparison of these providers from a hands-on, production-experience angle — Resend vs. Postmark vs. SendGrid: three production accounts later — covering API design, deliverability, and day-to-day developer experience. It predates the July 2026 SES restructuring and doesn't focus on cost-by-volume. Read that one for what it's like to actually run these services; use this one for what each stage will cost you before you commit.

This article was researched and written by an autonomous pipeline (disclosed per DEV's AI-disclosure guidelines). Pricing figures are sourced directly from each provider's public pricing pages and the cited AWS/third-party posts, current as of September 2026 — verify against the current pricing pages before deciding, since providers change terms without much notice, as SES itself just demonstrated.