Atlassian Rovo vs Rovo Dev CLI: pricing, features and which to choose

Rovo is Atlassian's AI product, announced in April 2024 and made available to all paid cloud customers in 2025. Atlassian, the Australian-founded company behind Jira, Confluence, Trello, Loom and Bitbucket, built Rovo on its Teamwork Graph, which maps the relationships between people, projects, pages, tickets and code across Atlassian apps and connected tools such as Google Drive, Slack, GitHub, Microsoft SharePoint and Figma. The goal is to give teams one place to find and act on company knowledge without leaving their work apps. Rovo is not sold as a separate product. It turns on automatically for organizations with Standard, Premium or Enterprise cloud plans on a verified business domain.

Rovo has four main parts. Search finds pages, work items, files and conversations across Atlassian and connected apps, respecting each source's permissions. Chat answers questions with citations, summarizes projects and drafts content, with a Think Deeper mode for longer reasoning. Agents are specialized helpers that groom Jira backlogs, organize Confluence spaces, review content against style rules, or resolve service requests. Atlassian ships ready-made agents and lets teams build their own in Rovo Studio, which was expanded at Team '26 in May 2026 to recommend agents, automations or apps from a plain description of a problem. Apps, in beta, generate custom Forge apps from a single prompt.

Rovo's main advantage is context. Because it reads Jira, Confluence and Loom natively, it can answer questions about project status and ownership that general assistants cannot. Its drawbacks are cost uncertainty under the new credit model, a requirement for Atlassian cloud plans and a smaller set of connectors than dedicated enterprise search. Glean is the closest rival for company-wide AI search and agents across hundreds of apps. Microsoft 365 Copilot suits organizations built on Teams and SharePoint. Notion AI and ClickUp Brain serve teams that run work in those apps. Choose Rovo if Jira and Confluence are where your work already lives.

Rovo Dev CLI is Atlassian's command line interface for software development tasks, with local repository access and connections to Atlassian work data. Atlassian began rolling it out in October 2025 after beta testing. The service targets teams using Jira Standard or Premium, where administrators can enable the CLI separately from Rovo Dev code reviews. Atlassian now says Rovo Dev is reaching end of life as a standalone product. Its capabilities are moving into eligible Jira and Teamwork Collection subscriptions, and Rovo Dev CLI is becoming Rovo CLI. That gives the current tool a clear practical use, but also makes its name and billing model transitional. Atlassian does not publish a company founding or Rovo Dev user count in these product documents.

A normal session starts with `acli rovodev run`, either interactively or with one instruction for a discrete task. From the terminal, the agent can inspect a repository, explain code, generate documentation, create or refactor files, and run development tasks. Jira commands show connection status, set a global project, apply a workspace-specific project, or disable the integration, helping teams align terminal work with tracked issues. The `--worktree` option isolates changes in a Git worktree, which is useful for parallel experiments or safer reviews. Session controls restore, fork, rename, clear, or prune context. Administrators can configure MCP servers, memory files, saved prompts, hooks, subagents, and permitted directories. Plan and read-only ask modes support review before edits, while model selection, usage reporting, server mode, and an optional IDE plugin extend the workflow.

The largest limitation is the product transition. Atlassian says standalone Rovo Dev is ending, while the move to Rovo CLI changes commands, settings, authentication, and credit accounting. Teams evaluating it should therefore test migration procedures before standardizing scripts, configuration files, or onboarding documentation. The rollout documentation says Rovo Dev does not support data residency, is not HIPAA compliant, and has not yet been externally audited for ISO 27001 or SOC 2 compliance. The free allowance can support initial trials, but usage stops when 350 credits are exhausted; Standard costs $20 per developer monthly for 2,000 organization-level credits, with extra usage priced at $0.01 per credit. GitHub Copilot CLI, Claude Code, and Aider offer different terminal approaches. Rovo Dev suits Jira-centered teams willing to manage transition risk and needing Atlassian context inside development sessions.