Rovo
Atlassian · Atlassian Rovo: AI Search, Chat and Agents Built into Jira, Confluence and Jira Service Management
Rovo is Atlassian's AI layer for Jira, Confluence, Jira Service Management and the rest of Atlassian Cloud. It combines search across Atlassian and connected apps, a chat assistant, ready-made and custom agents that create and update Jira work items and Confluence pages, and agents that run inside automation flows. It suits teams that already plan and document their work in Atlassian and want AI grounded in that context, with usage metered in Rovo credits included in paid cloud plans.
Best for
Organizations already running projects, documentation and service work in Jira, Confluence and Jira Service Management cloud that want AI search, chat and agents grounded in that work, built and governed by Atlassian admins without a separate AI rollout
Not ideal for
Teams that mostly work outside Atlassian, organizations on Atlassian Free plans or Data Center that need self-hosted AI, and buyers who need predictable flat AI pricing rather than pooled, variable credit consumption
Who it's for
Teams on Atlassian Cloud (software, product, IT and service, and business teams), plus the Atlassian admins and makers who build and govern agents and automations
Capabilities
- Rovo Search across Jira, Confluence and connected third-party apps such as Google Drive and Slack, filtered by each user's existing permissions
- Rovo Chat inside Jira, Jira Service Management, Jira Product Discovery and Confluence, with memory controls, shareable chats, @mentionable agents and custom skills added in September 2026
- Out-of-the-box agents for writing, planning and service work, such as Release Notes Drafter (up to 20 Jira work items at a time), Decision Director, OKR Generator, Work Item Planner, Ops Expert and Request Router
- Nine out-of-the-box third-party agents built on vendor MCP servers (Figma, Canva, Box, Amplitude, HubSpot, Intercom, Gamma, Replit in beta and Lovable), enabled by a site admin on Premium or Enterprise plans
- Rovo Studio, a no-code builder for agents, automation flows and apps, where makers describe what they need in Chat or configure instructions, knowledge sources, skills, tools, subagents and a reasoning tier by hand
- Agents in automation flows: add a trigger to an agent or a "Use agent" step to a flow so the agent updates work items, creates pages or posts comments when events fire
- Teamwork Graph context connecting people, work items, pages, code and connected tools, also available to outside agents through Teamwork Graph tools in the Atlassian MCP server and the generally available Teamwork Graph CLI for coding agents such as Claude Code, Cursor and Codex
- Atlassian MCP server with 220+ tools across Jira, Confluence, Bitbucket Cloud, Loom and Goals for clients such as ChatGPT, Claude and Cursor, running under each user's Atlassian permissions
- OpenAI model selection for Rovo agents, with available model options varying by plan, region and product configuration; agents with model selection are billed at variable credit rates
- Rovo browser extension, mobile app for Android and iOS, Rovo Desktop for Windows and macOS (beta), and Rovo apps for Microsoft Teams and Slack
- Admin controls for Rovo credit usage, extra-usage caps, agent permissions, usage tracking, agent evaluation and conversation review
- Rovo Dev coding capabilities: AI code review for Bitbucket and GitHub pull requests checked against Jira acceptance criteria, moving into paid Jira subscriptions, and a CLI that is evolving into a unified Atlassian Rovo CLI
Limitations
- Rovo is built around Atlassian Cloud: Rovo credits are included with paid Jira, Confluence, Service Collection and Teamwork Collection cloud subscriptions, and most of its value depends on how much of your work and knowledge already lives there
- Free Atlassian plans don't include Rovo, and Rovo can't be turned on for organizations registered with a generic email domain such as gmail.com
- Credit costs vary by feature: basic chat and agent requests cost 10 credits, but advanced agents, Think Deeper, slides and agents in Jira draw a variable number of credits based on reasoning steps, tools and model, which makes monthly use hard to forecast
- From December 3, 2026, usage beyond the pooled allowance is billed at $0.01 per credit and extra usage is on by default, so admins who want a hard limit must set a spending cap or disable it
- Third-party agent and context use counts too: enriched Teamwork Graph calls from tools such as Claude or ChatGPT through the MCP server or CLI typically cost 1 to 10 credits each
- Several pieces are still in beta or announced: Rovo Desktop, standalone Rovo Standard seats and the Jira Service Management MCP server; autonomous work-item pickup and multi-agent orchestration with OpenAI are described as on the horizon
- Rovo Dev is in transition: the standalone product (Rovo Dev Standard, $20 per developer per month) is reaching end of life with no final date yet, Code Reviewer moves to Rovo credits on December 3, 2026, and standalone Rovo Dev IDE features are being retired; Atlassian's docs also say Rovo Dev is not HIPAA compliant
- No self-hosted or Data Center deployment is documented: Rovo runs as part of Atlassian Cloud
Use cases
- Asking Rovo Chat what was decided about a feature and getting an answer drawn from Confluence pages, Jira work items and connected Google Drive or Slack content you can access
- Drafting release notes from a set of up to 20 Jira work items with the Release Notes Drafter agent
- Running an automation flow that triggers an agent whenever a work item is created without a parent, so it suggests the right epic in a comment
- Building a custom triage or onboarding agent in Rovo Studio with its own instructions, knowledge sources and tools, then embedding it in Jira or Confluence
- Letting ChatGPT or Codex read a Jira work item and its linked Confluence decision through the Atlassian MCP server before proposing an implementation plan
- Reviewing pull requests in Bitbucket or GitHub against a work item's acceptance criteria with Rovo Dev's Code Reviewer
Our take
Rovo's case rests on context rather than on any one feature. If your plans, decisions and tickets already live in Jira and Confluence, Rovo starts with permission-aware access to all of it, and Studio plus automation flows turn that into agents that act where the work is tracked. Atlassian is also opening the same context to ChatGPT, Codex, Claude and other tools through MCP and the Teamwork Graph CLI, so Rovo is becoming as much a context layer as an assistant. The main thing to manage is cost. Credits are included, but advanced features draw variable amounts, outside tools using the Teamwork Graph count against the same pool, and extra usage billing starts on December 3, 2026 with overage enabled by default. Before then, check your organization's usage in Atlassian Administration and set a spending cap. Teams whose work mostly lives elsewhere will get more from a general workplace assistant with an Atlassian connector.
Who should use it
Atlassian Cloud customers whose software, product, IT or service teams spend time hunting through Jira and Confluence, writing up the same artifacts, or triaging requests by hand, and whose admins want agents and automations governed in one place.
Who should skip it
Teams with little Atlassian footprint, organizations on Free plans or self-managed Data Center, and buyers who need fixed AI costs or self-hosted models.
Strengths
- Grounded in Jira, Confluence and Jira Service Management data through the Teamwork Graph, respecting existing permissions
- Included in paid Atlassian Cloud plans, with Rovo Search free and credits pooled across the organization
- No-code agent building in Rovo Studio, and agents can run inside automation flows
- Open to outside AI tools through the Atlassian MCP server and Teamwork Graph CLI
- Many surfaces: in-app, browser extension, mobile, desktop beta, Microsoft Teams and Slack
- Rovo and Atlassian AI have completed SOC 2 and ISO 27001 assessments, with data residency support
Weaknesses
- Most useful only if your work lives in Atlassian Cloud
- Variable credit consumption for advanced features makes costs hard to predict
- Extra usage billing is on by default from December 3, 2026
- Several pieces are beta or announced rather than generally available
- No self-hosted option, and Free plans don't include Rovo
Rovo pricing
Standard (Jira, Confluence)
Included; 25 Rovo credits per user
Billed monthly
- Rovo Search, Chat and agents
- Service and Teamwork Collection Standard: 250 credits per user
- Credits pooled across the organization
Premium
Included; 70 Rovo credits per user
Billed monthly
- Service and Teamwork Collection Premium: 700 credits per user
- Out-of-the-box third-party MCP agents (Figma, Canva, HubSpot and more)
Enterprise
Included; 150 Rovo credits per user
Billed monthly
- Service and Teamwork Collection Enterprise: 1,500 credits per user
- Out-of-the-box third-party MCP agents
Extra usage
$0.01 per credit ($10 per 1,000)
- Billing takes effect December 3, 2026
- Enabled by default with admin spending caps
- Prepaid annual packs with volume discounts
Rovo Dev Standard
$20 per developer
Billed monthly
- 2,000 Rovo Dev credits per developer per month
- Additional credits at $0.01 each
- Reaching end of life as a standalone product
Free tier limits: Free Atlassian plans don't include Rovo. On paid plans, Rovo Search, definitions, summaries and single-product Teamwork Graph lookups and writes don't consume credits. Jira Standard and Premium sites have a Rovo Dev Free allowance of 350 credits per user per month.
Note: Basic interactions cost 10 credits per billable event; advanced agents, Think Deeper, slides and agents in Jira cost variable credits. Allowances are pooled at the organization level, stack across apps and reset monthly without rollover; the credit table applies to usage from August 31, 2026, and AI features in beta don't currently count. Rovo Standard (standalone seats for people without Jira or Confluence) is in beta at no charge. Atlassian says Rovo Dev is reaching end of life as a standalone product (final date not yet announced), with Code Reviewer moving into paid Jira and Teamwork Collection subscriptions on Rovo credits from December 3, 2026.
Technical specs
API pricing
Teamwork Graph API, MCP and CLI calls: single-product lookups and writes are free; enriched context calls consume Rovo credits (typically 1-10 per call)
Available models
Where Rovo excels
Triaging new Jira work items automatically
Atlassian's automation docs show a flow where, when a work item is created without a parent, the Jira work item organizer agent finds a relevant parent or epic and explains its suggestion in a comment.
Reviewing decision documents in Confluence
Atlassian's documented example triggers the Decision Director agent when a page with "DACI" in the title is published, and posts its recommendations as a comment on the page.
Giving coding agents Jira context
Atlassian says more than 3,000 of its own developers use Codex, with Teamwork Graph-powered plugins pulling relevant work items and technical documentation into coding sessions.
Rovo vs. competitors
Rovo vs. Microsoft Copilot
Microsoft 365 Copilot is the AI layer for Word, Excel, Outlook and Teams, grounded in Microsoft 365 work data, with Copilot Studio for custom agents. Rovo plays the same role for Atlassian Cloud, grounded in Jira, Confluence and Jira Service Management through the Teamwork Graph, with Rovo Studio for agents and automation flows and usage metered in pooled credits.
Rovo vs. Notion AI
Notion AI runs inside a Notion workspace, with Notion Agent, Custom Agents and Enterprise Search over Notion and connected apps. Rovo does the equivalent for teams whose projects and documentation live in Jira and Confluence, and adds agents in Jira Service Management and automation flows. The choice usually follows which workspace your team already uses.
Rovo vs. Cohere North
Cohere North is a standalone, model-agnostic agent workspace that connects to tools such as Jira, SharePoint and Slack and can be deployed in your own VPC, on-premises or air-gapped. Rovo is delivered only as part of Atlassian Cloud, with deeper native access to Atlassian data and actions but no self-hosted option.
Frequently asked questions
What is Atlassian Rovo?
Rovo is Atlassian's AI layer across Jira, Confluence, Jira Service Management and other Atlassian Cloud apps. It includes Rovo Search across Atlassian and connected apps, Rovo Chat, out-of-the-box and custom Rovo agents that can create and edit Jira work items and Confluence pages, Rovo Studio for building agents and automations, and Rovo Dev for software teams. It draws on the Teamwork Graph, which connects people, work and content across Atlassian and connected tools.
How much does Rovo cost?
Rovo is included in paid Standard, Premium and Enterprise cloud plans for Jira, Confluence, Service Collection and Teamwork Collection, with usage measured in Rovo credits. Jira and Confluence include 25, 70 or 150 credits per user per month by tier, and Service and Teamwork Collection include 250, 700 or 1,500. Credits are pooled across the organization and do not roll over. From December 3, 2026, extra usage is billed at $0.01 per credit ($10 per 1,000); it is on by default, and admins can set spending caps or turn it off. Free Atlassian plans don't include Rovo.
What uses Rovo credits?
Rovo Search, definitions, summaries and simple Teamwork Graph lookups or write operations are free. Basic interactions such as Quick Answer chat and basic agents without model selection cost 10 credits per billable event. Advanced agents with model selection, Think Deeper mode, slides generation and agents in Jira cost a variable number of credits depending on reasoning steps, search volume, tools and model. Enriched Teamwork Graph calls, including those made by tools like Claude or ChatGPT through the MCP server or CLI, typically cost 1 to 10 credits. Atlassian says AI features in beta don't currently count against credits.
Can I build my own Rovo agents?
Yes. Rovo Studio lets makers create agents by describing them in Chat or configuring them step by step with instructions, knowledge sources, skills, tools and subagents, then choose where the agent appears, such as Rovo Chat or embedded in Jira or Confluence. Agents can also be added to automation flows so they act on events like a work item being created.
Does Rovo work with ChatGPT, Claude or Codex?
Yes, in both directions. The Atlassian MCP server lets ChatGPT, Codex, Claude, Cursor and other MCP clients read and act on Jira, Confluence and other Atlassian data under each user's permissions, and the Teamwork Graph CLI offers the same for terminal and CI workflows. Inside Rovo, agent builders can choose OpenAI models for Rovo agents, and Rovo also uses models from Anthropic, Google and open-source models hosted by Atlassian.
Is Rovo Dev part of Rovo?
Rovo Dev is the Rovo-branded coding agent, with a CLI, IDE features and AI code review in Bitbucket and GitHub. It has been sold separately as Rovo Dev Standard at $20 per developer per month with 2,000 credits, alongside a Rovo Dev Free allowance of 350 credits per user per month for Jira Standard and Premium sites. Atlassian says Rovo Dev is reaching end of life as a standalone product, with at least 60 days' notice before the final date. Code Reviewer becomes part of paid Jira and Teamwork Collection subscriptions and is measured in Rovo credits from December 3, 2026, the CLI is evolving into a unified Atlassian Rovo CLI, and standalone Rovo Dev IDE features will be retired.
Can I use Rovo without Jira or Confluence?
Atlassian offers Rovo Standard, which gives people standalone access to Rovo Chat, Search, Studio and Rovo's apps without a Jira or Confluence subscription. It is in beta and not charged during the beta; afterward organizations return to Rovo Free unless they opt into the paid Standard plan.
Rovo vs Microsoft 365 Copilot: what is the difference?
Microsoft 365 Copilot is grounded in Microsoft 365 email, files, meetings and chats and works inside Word, Excel, Outlook and Teams. Rovo is grounded in Jira, Confluence, Jira Service Management and connected tools through the Teamwork Graph, and its agents act on work items, pages and automation flows. Organizations that use both often connect them, for example through Rovo's Microsoft Teams app and SharePoint connector.
Integrations & fit
Alternatives to consider
Microsoft
Individuals and teams using Microsoft 365 and Windows who want AI inside the apps they already use
FreemiumNotion
Teams already using Notion who want AI agents and writing assistance embedded in their existing docs, databases, and meetings
Paid
Cohere
Large enterprises and public-sector organizations in finance, healthcare, telecom, energy, manufacturing and government that want employees building and sharing agents and automations, but must keep data and inference in their own VPC, on-premises or air-gapped environment with per-user and per-group token limits and spend tracking down to each agent
CustomAbout Rovo
Rovo is less a separate product than the AI built into Atlassian Cloud. Rovo Search looks across Jira, Confluence and connected third-party apps such as Google Drive and Slack, showing only what each user already has permission to see. Rovo Chat answers questions and drafts content from that data inside Jira, Jira Service Management, Jira Product Discovery and Confluence, and through a browser extension, mobile app, a desktop app in beta, and Microsoft Teams and Slack apps. Rovo agents are the agentic part: Atlassian ships out-of-the-box agents such as Release Notes Drafter, Decision Director, Work Item Planner and service agents for Jira Service Management, plus nine third-party agents built on vendor MCP servers (Figma, Canva, Box, HubSpot and others) for Premium and Enterprise plans. Teams build their own agents in Rovo Studio, generally available since May 2026, by setting instructions, knowledge sources, skills, tools, subagents and a reasoning tier, and can drop an agent into an automation flow so it acts on triggers like a new work item or a published page. Underneath sits the Teamwork Graph, Atlassian's map of people, work items, pages, code and connected tools, which Atlassian also exposes to outside agents through the Atlassian MCP server and the Teamwork Graph CLI. That openness is the newest part of the story: on October 6, 2026 Atlassian and OpenAI expanded their partnership, with OpenAI frontier models available for Rovo agents and ChatGPT and Codex connecting to Jira and Confluence through Atlassian MCP, while autonomous work-item pickup and multi-agent orchestration are still described as on the horizon. Pricing is folded into Atlassian plans: paid Jira and Confluence cloud plans include 25, 70 or 150 Rovo credits per user per month by tier, Service and Teamwork Collection plans include ten times that, Rovo Search is free, and from December 3, 2026 usage beyond the pooled allowance is billed at $0.01 per credit unless admins cap or disable it. The tradeoffs: Rovo's value depends on how much of your work lives in Atlassian, heavier features draw variable credits that make costs hard to predict, Free Atlassian plans don't include Rovo, and Rovo Dev, the coding agent, is being retired as a standalone product while its code review and CLI move into Jira subscriptions on Rovo credits.
Updates from Rovo
On October 6, 2026, at Team '26 Europe, Atlassian and OpenAI expanded their partnership. Atlassian says OpenAI frontier models power reasoning across Rovo, Rovo agent builders can choose OpenAI models, and ChatGPT and Codex connect to Jira and Confluence through Atlassian MCP. Autonomous agents that pick up work items, run tests and sync session history, plus multi-agent orchestration with human checkpoints, are described as on the horizon. Atlassian also announced a redesigned, generally available Atlassian MCP server with 220+ tools that, in Atlassian's benchmarks on Claude models, uses up to 25% fewer tokens than the previous version, with a Jira Service Management MCP server coming soon.
Atlassian made memory controls, @mentionable agents and shareable chats generally available in Rovo Chat and began rolling out custom skills, which encode team workflows as reusable skills created in Chat or Rovo Studio.
Atlassian made Rovo Studio generally available as a single workspace for building agents, automations and apps with roles, approvals, versioning and audit logs. It also announced Max mode, a reasoning mode in Rovo Chat for multi-step tasks, as coming soon in early access, and new Teamwork Graph tools in the Rovo MCP server and CLI.
Are you the founder? Claim this listing →