A1 ratingsAtlassianAtlassian Rovo

Atlassian Rovo

Atlassian · platform · Any industry
C
CGrade
43Score
±1495% range
≈#549Rank of 1134
0%From fleets
FR-CAT-00259Catalog no.

The six pillars

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

Can you see what it costs?

Nothing a buyer can read · prices published
35±38
Desk research 20 · 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?

No usage API found
14±27
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

Nothing a buyer can read
14±27
Desk research 0 · 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
90±17
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 research63%Neutral starting point37%

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.

Extra usage on by default; admins can set spending limits or disable it (features pause until reset); 80%/100% alerts.

History

11-12 C 4311-13 C 4311-14 C 4311-15 C 4311-16 C 4311-17 C 4311-18 C 4311-19 C 43
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
None found Declared
medium confidence
2026-11-15
2 earlier
[1][2][3][4] Correct
Prices published
Cost
Yes Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Usage API
Usage
None found Declared
medium confidence
2026-11-15
2 earlier
[1][2][3][4] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-11-15
2 earlier
[1][2][3][4] Correct
How an agent reports out
Reports out
Remote MCP connector Declared
high confidence
2026-11-15
2 earlier
[1] Correct
Per-agent keys
Controls
Scoped Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Audit log
Controls
By API Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Revoke access
Controls
Console only Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Spend cap
Controls
Hard cap Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
SSO
Controls
SSO + SCIM Inferred 2026-11-15
3 earlier
[1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-11-15
2 earlier
[1][2][3][4] Correct

Prices · Rovo included in Standard/Premium/Enterprise Cloud plans with pooled monthly credits: Jira/Confluence 25/70/150 credits/user/mo; Teamwork or Service Collection 250/700/1,500; extra-usage billing begins Dec 3, 2026 per Atlassian doc

Notes · Pricing page and usage-limits doc confirm allowances (25/70/150; collections 250/700/1,500), $0.01/credit overage and Dec 3, 2026 extra-usage billing start; still no usage API.

Scored with the rubric for Platforms and APIs (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

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Atlassian Rovo?

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.