Atlassian Intelligence and Rovo pricing explained

Disclosure: This article is published by eesel AI, a competitor of Atlassian. We encourage you to read Atlassian's own materials for their perspective.

TL;DR

Rovo and the AI features once branded Atlassian Intelligence are included with every paid Jira, Confluence, Service Collection and Teamwork Collection plan, with no separate line item. Free plans get neither. Each paid seat adds a monthly Rovo credit allowance, pooled across the organization: 25, 70 or 150 credits per user on Jira and Confluence, and 250, 700 or 1,500 on the two collections.

Rovo Search, definitions and summaries are free. Chat quick answers and basic agents cost 10 credits each, while Think deeper chats and advanced agents cost a variable amount. From December 3, 2026, usage past the allowance is billed at $0.01 per credit, and extra usage is on by default unless an admin caps it or turns it off.

What does Atlassian Intelligence include, and on which plans?

Atlassian Intelligence and Rovo are Atlassian's two distinct AI layers. Atlassian Intelligence is the in-product AI woven into Jira, Confluence, and Jira Service Management: inline text drafting, automatic summaries, JQL error correction, and AI-generated automation rules. Rovo goes wider: cross-product search across Atlassian and 30+ third-party connectors, a conversational Chat assistant, and configurable Agents that can read and write Jira and Confluence on your behalf. Atlassian's admin docs now describe the in-product features as Rovo AI features, and the admin setting now lives under AI and Rovo in Atlassian Administration.

Atlassian Intelligence is not a separate SKU. It is automatically activated for every Jira, Confluence, and JSM site on Standard, Premium, and Enterprise plans. Free-tier customers do not get access.

That means the pricing question for Atlassian Intelligence is really just: are you on a paid plan? For teams of up to 100 users on monthly billing, Jira Standard is $9.70 per user per month and Premium $19.60 (Jira licensing). Confluence Standard is $7.15 per user per month and Premium $14.10 (Confluence licensing). Jira Service Management is now sold inside Service Collection, at $26.90 per agent per month on Standard and $61.60 on Premium for 1 to 15 agents (Service Collection licensing). Larger teams pay less per user.

The headline figures on the Jira pricing page ($8.48 and $15.56), the Confluence pricing page ($5.78 and $11.16) and the Service Collection pricing page ($21.50 and $55.28) are averages at the calculator's default size of 300 users or 75 agents. Annual billing reduces those figures by up to 17%.

Once you're on any paid plan, Atlassian Intelligence features (drafting, summarization, change summary, JQL fix, automation rule generation, ticket triage suggestions) are available without an additional line item.

There is one activation gate worth knowing: Rovo must be enabled at the organization level by an admin with a verified business domain. Organizations registered under generic email domains like gmail.com or outlook.com cannot enable it.

Is Rovo sold separately, or bundled with paid plans?

Rovo is bundled. Rovo credits are included in all paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscriptions, according to Atlassian's Rovo credits guide. The per-user add-on pricing that Rovo originally launched with no longer applies; you will not be invoiced separately for Rovo once it is enabled for your site.

The one standalone option is Rovo Standard, a beta seat for people who don't have Jira or Confluence. It is free during the beta and costs USD 5 per user per month afterwards if an admin opts in (Rovo Standard billing).

What you get from bundling is a monthly credit allowance per licensed seat. Credits pool at the organization level, scale with seat count, reset monthly, and do not roll over.

Source: Rovo usage limits documentation.

What do Rovo credits buy, and what's free?

Not everything in Rovo costs credits. Under the rate card that applies from August 31, 2026, these features are free and do not draw from your allowance: Rovo Search in Atlassian apps, definitions, and summaries.

The features that do consume credits today are:

Source: How Rovo credits work. In chat, each user message is one billable event; for agents and AI features, each invocation is one. Request Resolver, for example, uses 100 credits each time it generates a resolution plan.

To put those numbers in context: a Standard-plan team with 50 users has a pooled monthly allowance of 1,250 credits (50 x 25). That covers 125 Basic Rovo Chat messages or agent runs per month across the whole organization, and fewer once Think deeper or advanced agents enter the mix. A Premium team of the same size has 3,500 credits, and an Enterprise team has 7,500.

Indexed objects (the documents and items Rovo connectors pull in from Google Drive, SharePoint, Slack, and other sources) do not consume credits and will not be billed. They appear in your usage dashboard for visibility only.

What happens when you hit the Rovo credit limit?

From December 3, 2026, Atlassian bills Rovo credits used beyond your allowance. The list price is $0.01 per credit, or $10 per 1,000 credits, and extra usage is on by default. Billing continues up to an admin-defined spending cap, at which point billable features pause until the allowance resets or more credits are bought. Organization and billing admins can also turn extra usage off, which pauses billable features at 100% instead.

You will receive notifications when your organization reaches 80% and 100% of its monthly allowance. Free features such as Rovo Search, summaries and definitions keep working after the allowance runs out.

Using the 50-user Standard team above: if it uses 3,000 credits in a month, it is 1,750 credits over (3,000 - 1,250), which costs 1,750 x $0.01 = $17.50 that month. Prepaid annual credit packs with volume discounts are also available.

One page has not caught up. The FAQ on Atlassian's Jira pricing page still says overage needs 90 days' notice and an explicit opt-in, while the support documentation and usage-based pricing hub say extra usage is on by default. I'd plan around the support documentation and check the setting under Insights, then Platform usage in Atlassian Administration.

How are the service desk AI agents priced?

Teams using Jira Service Management encounter two separate AI surfaces that have their own pricing structures.

The Customer Service AI agent is an AI agent that handles incoming customer support requests within Service Collection, as part of Customer Service Management. It is included in Standard, Premium, and Enterprise Service Collection plans at $1 per resolution, charged only when it fully resolves a ticket without escalation to a human agent. Those usage charges start on December 3, 2026, and there is no included allowance.

The Virtual Service Agent is a customer-facing chatbot combining deterministic intent flows with AI answers drawn from your Confluence knowledge base. It is available on Premium and Enterprise only, and each plan includes 1,000 assisted conversations per month (or 12,000 per year for annual billing). An assisted conversation counts when the virtual agent matches a customer to an intent flow or when an AI answer resolves the issue and the ticket is closed. Above the included quota, overages start at $0.30 per assisted conversation per month, with volume discounts for higher volumes.

These two tools operate independently of your Rovo credit pool. The help center self-service agent and Request Resolver are the exception on the JSM side: both sit in the Premium tier of the Rovo credit rate card.

Where does Rovo fall short, and when should you use eesel instead?

Rovo is good at what it was built for. It sits inside Jira and Confluence, its search respects the permissions you already set, and Search, definitions and summaries cost nothing. Every paid seat also brings a credit allowance, so light use is covered by what you already pay.

The limits show up in the bill. Past the pooled allowance, credits cost $0.01 each from December 3, 2026, with extra usage on by default (How Rovo credits work). Think deeper chats, advanced agents and the JSM self-service agent are Premium features at variable credits, so the cost of a single request is hard to predict. One Jira Cloud Standard admin with 123 users reported "a much bigger chunk of credits (2,000+) showing up under a category called "Jira Administration" with no clear feature label" (Atlassian Community).

eesel fits when the work runs past search. eesel is an AI teammate that works inside Jira Service Management and Confluence, and across Slack, Microsoft Teams and helpdesks like Zendesk and Freshdesk. It acts on tickets: it replies to customers, adds internal notes, assigns, labels and transitions issues, and reads Confluence live for answers (read only, through one connected Atlassian account). Unlike Rovo's Slack and Teams apps, where every asker needs an Atlassian account on a Rovo-enabled site, the people asking eesel need no Atlassian seat. Pricing is per ticket or chat handled, not per Atlassian seat, from $299/month for 500 credits. See the Jira integration, the Confluence integration, or my list of Rovo alternatives.

Rovo is still the better pick if your team lives entirely in Atlassian and mostly wants search and summaries it already pays for.

Bottom line

Atlassian Intelligence and Rovo together cover a wide range of AI use cases: in-product writing assistance, cross-platform search, conversational chat, configurable agents, and customer-facing service bots. Both are now bundled into paid Atlassian plans rather than sold as separate add-ons, which simplifies the initial purchasing decision.

The complexity today is in the credit model. What you get per seat varies significantly by plan tier (25 versus 70 versus 150 credits per user per month on Jira and Confluence), and the features with the highest practical value (Chat, Agents, and Think deeper) are exactly the ones that draw from that pool. For large teams on Standard plans, the pooled allowance may be tighter than it looks on paper.

Atlassian has now published the overage price: $0.01 per credit from December 3, 2026, with extra usage on by default. The right move before that date is to check your usage in Atlassian Administration, set a spending cap, and compare the cost of extra credits with a higher tier or Teamwork Collection, which carries 10x the allowance of standalone Jira or Confluence on the same plan.

If the per-seat structure itself is the obstacle rather than the AI features, that's a signal to evaluate whether a per-ticket priced tool like eesel AI fits your team's growth plans better.