Atlassian Intelligence and Rovo pricing explained

Table of Contents

• Atlassian Intelligence: what's included, and at what plan tier
• Rovo is bundled with paid subscriptions, not sold separately
• What Rovo credits actually buy, and what's free
• What happens when you hit the limit
• Service desk specifics: Rovo Customer Service and the Virtual Service Agent
• Looking for something with simpler cost structure?
• Bottom line

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

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.

For teams already embedded in the Atlassian ecosystem, both tools offer real productivity value. The question that matters for budgeting is how they're priced, because the answer changed significantly in 2024 and continues to evolve.

Atlassian Intelligence: what's included, and at what plan tier

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? Jira Standard runs $7.91 per user per month, Premium $14.54 per user per month. Confluence Standard is $5.42 per user per month, Premium $10.44 per user per month. JSM Standard is $20 per agent per month, Premium $51.42 per agent per month. 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.

Rovo is bundled with paid subscriptions, not sold separately

Rovo is now included in all paid Jira, Confluence, Service Collection / Jira Service Management and Teamwork Collection cloud subscriptions. 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.

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 Rovo credits actually buy, and what's free

Not everything in Rovo costs credits. The following are currently free and do not draw from your allowance: Rovo Search queries, inline summaries, chart insights, and definitions.

The features that do consume credits today are:

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 Rovo Chat or Agent requests per month across the whole organization, or 12 Deep Research requests. 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 limit

This is the part that matters most for budget planning, and the current situation is worth stating precisely.

Atlassian is not currently billing for usage above your included Rovo credit allowance. Requests that exceed the monthly pool will still go through; there is no hard cutoff that blocks usage. Atlassian has committed to providing at least 90 days' notice before any overage becomes billable, and has said it will require an explicit opt-in before applying charges. No automatic fees will be triggered.

You will receive notifications when your organization reaches 80% and 100% of its monthly allowance, which gives teams time to evaluate usage before any policy changes arrive.

That said, Atlassian has clearly reserved the right to introduce consumption-based billing in the future. Monitoring your usage dashboard now, while there's no cost pressure, is the lowest-effort way to avoid a surprise later.

Service desk specifics: Rovo Customer Service and the Virtual Service Agent

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

Rovo Customer Service is an AI agent that handles incoming customer support requests within Service Collection. It is included in Standard, Premium, and Enterprise JSM plans at $1 per resolution, charged only when it fully resolves a ticket without escalation to a human agent.

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.

Looking for something with simpler cost structure?

For teams that find per-seat pricing complicated to forecast (particularly those with variable headcount, seasonal staffing, or multiple departments sharing AI access) there are alternatives worth evaluating alongside Atlassian's suite.

eesel AI is an AI agent platform built for customer support and internal knowledge management. Its pricing is based on the tasks the agent handles rather than the number of users with access, so adding team members does not automatically increase the bill the way per-seat models do. It connects to tools like Google Drive, Slack, Zendesk, and others as knowledge sources for the agent.

If you're comparing options, eesel offers a free trial with no payment information required.

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), and the features with the highest practical value (Chat, Agents, and Deep Research) 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.

The good news is that Atlassian has been transparent about the no-billing-yet status and the 90-day-notice commitment. There's no urgency to act before usage becomes measurable. The right move is to enable the tools, watch usage patterns for a month or two, and make an informed tier decision before any billing changes arrive.

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