Rovo by Atlassian: What the AI can and can't do (2026)

TL;DR

Atlassian Rovo is the AI built into Jira, Confluence and the rest of Atlassian Cloud (search, chat, agents and the Studio builder), and my honest verdict is that it's worth using for the search and summaries you already pay for, but less predictable for heavy agent work.

It comes with every paid Standard, Premium and Enterprise Cloud plan (not Free), with 25, 70 or 150 Rovo credits per user per month on Jira or Confluence. Search, definitions and summaries are free. Chat and agents spend credits, and from December 3, 2026, usage above the allowance is billed at $0.01 per credit, with extra usage on by default.

If your support work runs through Jira Service Management, Slack, Teams or a helpdesk like Zendesk, and you want an AI that acts on tickets, I'd look at eesel, priced per ticket or chat instead of per Atlassian seat.

What is Atlassian's Rovo?

Atlassian pitches Rovo as an "AI teammate" inside products you already use, like Jira and Confluence. The pitch is pretty appealing: handle the repetitive stuff, dig up useful info, and bring all your team’s knowledge into one place. But how well does it actually work?

For most teams, Rovo isn't a separate app you buy (a standalone Rovo Standard seat is in beta). It’s more like a collection of AI features baked into Atlassian's cloud platform. Think of it as the smarts behind a bunch of new tools that are meant to work together. At its heart, Rovo has a few main parts:

• Rovo Search: This is a search bar that can look through your Atlassian tools and also connect to other apps like Google Drive and SharePoint to find what you need.

• Rovo Chat: A chatbot you can talk to. You can ask it to summarize documents, answer questions, or help you brainstorm ideas using your company's information. It also runs in Slack and Microsoft Teams, where it can create and update Jira and Confluence work.

• Rovo Agents: These are customizable AI helpers you can set up to manage specific, repeatable tasks, like reviewing code or figuring out why an IT system went down.

• Rovo Studio: This is a no-code builder for Rovo Agents, automation flows and (in beta) no-code apps, without having to be a developer. The unified Studio went GA on 6 May 2026.

The big idea from Atlassian is what they call "agentic AI" basically, AI that acts like a helpful teammate, not just a tool you use. Its main selling point is that it uses your company's own information from Jira tickets, Confluence pages, and other connected apps to give you relevant help.

How does Rovo work, and what can you use it for?

Rovo works through its tight connection with everything else Atlassian: agents you call up while writing, pre-built agents for specific teams, and custom agents you build yourself. Let’s look at how you might actually use it.

Rovo agents for content creation and review

When you’re writing in a Confluence page or a Jira issue, you can type /ai to summon a Rovo agent. This opens an editor where the agent can help you write a new draft, reword a tricky paragraph, or just give your writing a once-over.

For instance, Atlassian has a ready-made agent called the "Decision Director." It's built to help you write and review DACI (driver, approvers, contributors, informed) documents to make sure you’ve covered all the important points. It’s a cool idea, but there’s a catch: it only works in the editor if your org admin has enabled AI for that app. If not, you’re left using Rovo Chat and then manually copying and pasting what the agent says into your document.

Specialized Rovo agents for tech and IT teams

Rovo also has pre-built agents for specific team jobs, and this is where you start to see some interesting uses. Atlassian's out-of-the-box list now runs to 27 agents, including Request Resolver (formerly Rovo Service) for Jira Service Management and the Jira Coding Agent.

• Code Reviewer (part of Rovo Dev): This agent plugs into Bitbucket and does the first pass on pull requests. It checks the code against the requirements in the Jira story and your team's own coding standards. It can spot potential bugs or style issues before a human ever has to look, which could definitely speed things up.

• Ops Expert: When an IT incident pops up, this agent assists with on-call duties and offers guidance to mitigate the impact, aiming to cut the time to detect, respond to and recover from the incident. Atlassian's current list has no separate root cause analysis agent, so Ops Expert is the one to look at.

How do you build your own custom Rovo agents?

If the standard agents don't quite do what you need, you can make your own. Atlassian gives you two paths for this:

1. No-Code (Rovo Studio): This is a simple, visual builder for people who don't code. You can tell it what you want the agent to do, connect it to your data, and set up its tasks using plain English. A team lead, for example, could build an agent to automatically pull together a summary of the team's weekly progress in Jira. Agent creation is open to everyone by default, and admins can limit it to selected groups.

2. Developer-Built (Forge): For more complicated tasks, developers can use Atlassian's Forge platform to code custom agents from the ground up. This gives you total control to build agents that handle complex workflows or connect with other systems through APIs.

What does Rovo cost, and where does it hit limits?

Rovo has no separate fee on paid Atlassian Cloud plans, but chat and agent use is metered in Rovo credits, and from December 3, 2026 usage above your allowance is billed. Users also report uneven results from agents, so cost and reliability are the two things to check.

How is Rovo priced?

Rovo is included in every paid Standard, Premium and Enterprise Cloud plan of Jira, Confluence, Service Collection and Teamwork Collection, so it doesn't show up as its own line on your Atlassian plans. Free plans don't include it. The only standalone option is a Rovo Standard seat, free during its beta and USD 5 per user per month afterwards if your admin opts in.

Instead of a per-user fee, each paid user adds a monthly credit allowance to a pool shared across the organization. Search in Atlassian apps, definitions and summaries cost nothing. Quick-answer chat messages and basic agents cost 10 credits each, while Think deeper, agents in Jira, Request Resolver and other premium features use a variable number of credits, per Atlassian's credits guide.

Pro Tip: Extra usage is switched on by default. If you'd rather Rovo pause than bill, ask an org or billing admin to set a spending cap, or turn extra usage off, before December 3, 2026.

What happens when you go over Rovo's allowances?

From December 3, 2026, Rovo credits used above your allowance are billed at $0.01 each ($10 per 1,000), with admin alerts at 80% and 100% and an optional spending cap. Two allowances are shared across your whole company, based on how many users you're paying for:

• Indexed objects: These are the individual things Rovo pulls from your synced knowledge sources, like a single Google Doc, Slack thread, or Confluence page. Jira and Confluence plans add 100, 250 or 625 objects per user (Standard, Premium, Enterprise), and the collections add 1,000, 2,500 or 6,250. Storing them doesn't use credits.

• Rovo credits: These are spent each time your team sends a Rovo Chat message or invokes an agent. Jira and Confluence give 25, 70 or 150 credits per paid user each month, and Service Collection or Teamwork Collection give 250, 700 or 1,500. Unused credits don't roll over.

Atlassian announced this new billing model on September 1, 2026. Until then, going over cost nothing, so a busy month that used to be free can now show up on the invoice.

How reliable are Rovo agents in practice?

Results are mixed. Fans like it for fuzzy search, but it can take a lot of trial and error with your prompts to get an agent to do what you want. Studio now opens with a prompt box and can recommend what to build from a plain description of your problem, yet complex agents still trip up:

"Agents struggle with too many skills or too complex instructions, so leveraging subagents and automation is a must."

-- u/Happybadger96, r/atlassian

Bigger jobs hit limits too. Atlassian caps bulk actions in Jira at 20 work items at a time, and in chat an agent asks for confirmation before tools that change data, so a long string of tasks, like updating several fields on a Jira ticket, adding a comment, and pinging a user, can take several nudges. The same Reddit user found agents stumble "when updating too many fields at once in a conversation track," and another found Rovo could only analyze "a restricted number of tickets at once."

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

Rovo is strongest where your work already lives. It's built into Jira and Confluence, its search respects the permissions people already have, search, definitions and summaries are free, and every paid seat comes with credits. For a team that lives entirely in Atlassian and mostly wants search and summaries it already pays for, Rovo is still the better pick.

The limits show up with heavy agent use. Chat and agent runs draw on 25 to 150 credits per user on Jira or Confluence, agents in Jira use a variable number, and from December 3, 2026 anything over the allowance is billed at $0.01 per credit unless an admin turns it off (Atlassian's credit rules). Reliability is the other question: one product owner on r/atlassian called agents "extremely unreliable in my experience."

eesel AI fits when support work spans more than Atlassian. It's an AI teammate that works inside Jira Service Management through its Jira integration and reads your docs through its Confluence integration (read only).

It also answers in Slack, Microsoft Teams and helpdesks like Zendesk. It acts, not just searches: it creates, assigns, labels and transitions Jira issues, replies to the customer or leaves an internal note. Rovo has Slack and Teams apps too, but everyone who asks it something needs an Atlassian account on a Rovo-enabled site, and replies in public channels need a shared account an admin sets up. With eesel, the person asking needs no Atlassian seat. One difference to know: eesel reads Confluence through one Atlassian API token, so it sees what that account can see rather than each asker's own permissions.

Pricing is per ticket or chat handled, not per Atlassian seat: a free plan with 100 credits, then from $299 a month for 500 credits. Lesson Pro had it work 1,900 Zendesk tickets in a month. For more options, see my Rovo alternatives guide.

Is Rovo the right AI teammate for you?

Yes, if you're already heavily invested in the Atlassian ecosystem and paying for a Standard, Premium or Enterprise Cloud plan, Rovo is a pretty powerful tool you already have. That tight connection with Jira and Confluence is its greatest strength.

But that strength is also its biggest weakness. Rovo's cost is tied to your Atlassian seats plus a credit allowance that starts billing overages on December 3, 2026, and it is so focused on Atlassian that you risk being stuck with one provider. For a lot of teams, those downsides will be dealbreakers.

If you’re looking for an AI solution that’s more affordable, predictable, and works with all the tools you love, eesel AI is the better way to go. It gives you great features like AI Agent, AI Copilot, and AI Internal Chat, all with a price tag that helps you grow instead of holding you back.

Ready for an AI that works for your team, not the other way around? Try eesel AI for free or book a demo today and see just how simple powerful AI can be.