A1 ratingsAtlassianRovo Dev

Rovo Dev

Atlassian · agent · Any industry
B
BGrade
65Score
±1495% range
≈#154Rank of 1134
0%From fleets
FR-CAT-00264Catalog no.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Admin or analytics API · prices published
63±38
Desk research 76 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

None public; Atlassian Administration > Insights > Rovo Dev credits (Users tab, Credit settings) and billing Usage tab
86±27
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By user
50±27
Desk research 50 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

Remote MCP connector · Atlassian Rovo MCP server (cloud-hosted, OAuth 2.1 or API token) lets an external agent read/write Jira, Confluence, Bitbucket; tool calls land in the org audit log.
86±27
Desk research 100 · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

Spend cap: Hard cap · Per-agent keys: Scoped · Audit log: By API · Revoke: Console only · SSO: SSO + SCIM
73±38
Desk research 96 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans don't get the data
14±27
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research62%Neutral starting point38%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Spend capHard cap
Per-agent keysScoped
Audit logBy API
RevokeConsole only
SSOSSO + SCIM
PricesPublished

Price changes: Cloud terms (per third-party summary): fee changes with at least 30 days notice; renewals at then-current rates.

Rovo Dev extra usage is opt-in and org admins can set a limit or disable it (Rovo Dev stops at the limit). Service accounts get scoped, expiring tokens revoked in the admin console; the audit events API, SAML SSO and SCIM require Guard or Cloud Enterprise.

History

11-11 B 6511-12 B 6511-13 B 6511-14 B 6511-15 B 6511-16 B 6511-17 B 6511-18 B 65
Rated since 2026-10-02. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Admin or analytics API Declared
medium confidence
2026-10-27
1 earlier
[1][2][3] Correct
Prices published
Cost
Yes Inferred 2026-10-27
2 earlier
[1][2][3][4] Correct
Usage API
Usage
None public; Atlassian Administration > Insights > Rovo Dev credits (Users tab, Credit settings) and billing Usage tab Declared
medium confidence
2026-10-27
1 earlier
[1][2][3] Correct
Cost per agent
Per agent
By user Declared
medium confidence
2026-10-27
1 earlier
[1][2][3] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
medium confidence
2026-10-27
1 earlier
[1][2][3] Correct
Per-agent keys
Controls
Scoped Inferred 2026-10-27
2 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Inferred 2026-10-27
2 earlier
[1][2][3][4] Correct
Revoke access
Controls
Console only Inferred 2026-10-27
2 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Verified 2026-11-02
3 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Inferred 2026-10-27
2 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-27
1 earlier
[1][2][3] Correct

Prices · Rovo Dev Free 350 Rovo Dev credits/user/mo per Jira site (no extra usage); Standard $20/user/mo incl. 2,000 Rovo Dev credits; extra usage $0.01/credit

Notes · Rovo Dev uses its own credit meter separate from Rovo credits (per Atlassian licensing page). Billing doc says 2,000 credits per user per month; the usage doc describes it as an org-level pool, so allocation wording is inconsistent. Extra usage is optional, can be limited or disabled by org admins; Rovo Dev stops when credits run out. No usage API found.

Scored with the rubric for Agents and agent platforms (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Run agents on Rovo Dev?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.