Features, Price and Security Comparison

Choose your AI provider

✅ OpenAI, Gemini or Claude, several side by side

❌ Atlassian routes its own models

⚠️ Switches between Atlassian-offered models

Choose the exact model per conversation

✅ From the composer

❌

⚠️ In the CLI

Bring your own API key and provider contract

✅

❌

❌

New models on release day

✅ Read live from your provider account

❌ When Atlassian rolls them out

❌

Run two providers for resilience

✅

❌ Single vendor

❌

Image generation

✅ Raster on OpenAI, vector (SVG) on Claude and Gemini

⚠️ Not documented

⚠️ Not documented

Diagram generation (flowchart, sequence, class, gantt, …)

✅ Any provider, no setup

⚠️ Not documented

⚠️ Not documented

Custom prompts

✅

✅

✅

Summarize, explain, translate, improve writing

✅ One click on a page or a selection

✅ Through chat

⚠️ Not its purpose

Text generation in pages

✅

✅

❌

Upload files and query them

✅ Per user, per AI service

✅ Reads existing Atlassian attachments

✅ Repository files

Save the answer into Confluence — create, replace, append, prepend

✅ Four modes

⚠️ Agents can create and edit pages

❌

Quick access from page actions, byline, space, Apps menu, home feed

✅ Six entry points plus an /ai page macro

✅ Chat panel and product surfaces

❌ CLI and IDE

Assistant embedded in a page or template

✅ The /ai macro

❌

❌

Voice input and spoken answers

✅ In the composer

✅ Confluence mobile app

❌

Confluence and Jira actions on the user's own permissions

✅

✅

✅ Repository scope

Confirmation shown before anything is written

✅ Every write

⚠️ Varies by agent and action

⚠️ Varies

Restrict access by Atlassian group

✅ Four levels: AI service, model, connector, individual tool

✅ Admin controls for Rovo, agents and connectors

⚠️ Product-level

Scan a space for secrets and PII

✅ Restricted to site administrators by default

⚠️ Not documented

⚠️ Not documented

Connect third-party systems over MCP

✅ Catalog servers, or any server by URL

✅ Registered by an org admin

✅

Federated search over third-party SaaS

❌ No search index of its own

✅ 50+ connectors

❌

No-code agent builder

❌ Not in v11.0.0

✅ Rovo Agents and Rovo Studio

❌

Coding agent for repositories

❌

❌

✅ Its whole purpose

Works on Confluence Free and Standard plans

✅ Any Confluence Cloud plan

❌ Not on Free plans

❌

The product

See the Marketplace listing for current pricing

Included with paid Standard, Premium and Enterprise Jira, Confluence and JSM Cloud plans; a separate Rovo Standard SKU covers organizations without a qualifying plan

Priced separately — see Rovo Dev pricing

The AI usage

Billed by your provider, on your key, at their list price. No resale, no markup, no per-seat AI fee.

Rovo credits, pooled across the organization, reset monthly

Its own allowance

What you can see

✅ Cost per request in your provider's usage dashboard. A dedicated key per AI service splits spend cleanly.

Credit and usage data reaches the Atlassian Administration billing dashboard from August 2026

Per its own plan

The ceiling

✅ A budget cap and alert you set on your own provider account — a hard stop you control

Credit allowances per plan

Per its own plan

Free Atlassian plans

✅ Only your provider costs apply

❌ Not available

❌

Who processes our content?

✅ The provider you chose, under your own agreement, on your own key

Atlassian, and the LLM providers it contracts with on your behalf

Is our content used to train models?

Governed by your own provider agreement. The app sends content nowhere else.

Atlassian states its LLM providers do not use customer inputs or outputs to improve their services

Can a user reach content they are not entitled to?

✅ No. Every read and write runs on that user's own Atlassian permissions.

No. Rovo respects existing product permissions.

Where are credentials kept?

API keys and OAuth secrets encrypted in Forge app storage, never displayed back

Not applicable — you supply no model credentials

Is page content stored by the vendor?

✅ No copy is kept. Chat history stays in the user's browser.

Chat session logs and agent configuration are stored by Atlassian

Named model and named provider for procurement

✅ You name both, and can change either

Atlassian selects and routes

Data residency

Determined by the provider account and region you choose

Inherits your organization's Atlassian residency pinning

Certifications

Those of the AI provider you selected, plus Atlassian's for the Forge platform the app runs on

Atlassian's cloud attestations

Audit trail

Actions appear in the target system's own audit log, under the user who performed them

Organization-level Rovo audit logs require Atlassian Guard

Turn it off

Remove the AI Services — nothing works without one

Admin disables it for the organization or product

Procurement requires a named model, a named provider and your own data-processing agreement

AI ChatGPT for Confluence

You want AI cost to be a measured, attributable line item rather than a per-seat licence

AI ChatGPT for Confluence

You need generated images or diagrams inside Confluence pages

AI ChatGPT for Confluence

Different teams should get different models, and only some the expensive one

AI ChatGPT for Confluence

You are on Confluence Free or Standard and do not want to change plan to get AI

AI ChatGPT for Confluence

You want the assistant embedded in a page or a template

AI ChatGPT for Confluence

You want one assistant across Jira, Confluence, Bitbucket, Slack and Teams

Rovo

You need search across Google Drive, SharePoint, Figma and Notion alongside Atlassian

Rovo

You want autonomous agents built without code

Rovo

You want an agent that writes and reviews code in your repositories

Rovo Dev

You want your own model to be able to act on Atlassian data

Both — add Rovo as a connector inside this app