One Rovo Think deeper message cost 86 credits in a test org ahead of Atlassian's overage billing
Atlassian will start billing Rovo credit overage on 3 December 2026, according to a dev.to test that measured 10 to 86 credits per message. At one quick question per person per working day, a 200-seat Jira Standard pool lasts about 2.5 days.
The Engineer · Build desk
Key figures: one 86-credit Think deeper message equals 3.44 months of one Jira Standard seat's credits; a Jira Standard seat carries 25 Rovo credits; one seat funds 2.5 quick messages at 10 credits each.
| Figure | Value | Note | Claim |
|---|---|---|---|
| 86-credit message as months of one Jira Standard seat | 3.44 months | 15 | |
| Jira Standard seat | 25 Rovo credits | 10 | |
| Quick messages one seat funds | 2.5 messages | at 10 credits each | 16 |
What happened
- A three-message Quick answers thread cost 30 credits in the author's 14 October test, because each message a user sends is billed.
- Atlassian lists Think deeper only as "Variable credits per billable event" and publishes no per-message number for it.
- About two and a half minutes after the last answer, the usage page said "Allowance used 609" while the Features tab still said 483.
- Deep Research replied "temporarily unavailable" three times, so the author has no credit figure for it and cannot say whether the failed replies were charged.
Why it matters
- cost For 200 people sending one quick question each working day, the author puts Jira Standard overage at about $370 a month, a charge Atlassian was not billing before December.
- constraint Think deeper cannot be budgeted from Atlassian's table, and Let Rovo decide can escalate to it on an open-ended prompt, so users may spend deep-tier credits without choosing to.
- decision Admins on Jira plus Confluence Standard can compare Teamwork Collection Standard before December: at 200 seats it lists $110 a month lower with a pool five times larger.
Andrew Fleig did the quick-answer sum in June. He asked on the Atlassian Community: "70 credits...10 per chat? So, only 7 chats per month on a paid plan?" [1] An Atlassian team member told him the credits are pooled and that overage was not being billed yet [2]. The post's author says that ends on 3 December 2026 [3].
The billing unit is the message. Atlassian's table, as the post quotes it, reads "10 Rovo credits per billable event" and "each user message is a billable event" [7]. Empyra, an Atlassian partner, wrote that a five-message Quick answers thread "costs 50 credits, not 10" [11]. A Jira Standard seat carries 25 credits [10], which funds 2.5 quick messages [16]. Pooling lets heavy users draw on light ones.
The 2.5-day estimate rests on two assumptions. The pool is 200 seats times 25 credits, or 5,000 [17]. All 200 people send one 10-credit message a day, or 2,000 credits [18]. That empties the pool in 2.5 working days [19].
Think deeper is where any estimate gets loose. The two messages cost 65 and 86 credits [6]. The 65-credit prompt compared Scrum and Kanban for a support team of 12. The 86-credit prompt asked for a one-page plan setting up change advisory at a company of 40 people [13]. At 86, one message is 3.44 months of a single seat's 25 credits [15].
For those figures to transfer, your users' prompts have to look like these two. They also have to trigger a similar amount of searching and tool use. Atlassian says Think deeper credits depend on "Reasoning steps", "Search volume", "Tools invoked" and "Model power" [9]. Two messages from one org cannot bound the range.
The method is careful for what it is. The author read the meter endpoint before each action and every 20 seconds after it, on a real Atlassian Cloud org, on 14 October [4]. Idle checks of two to four minutes never moved the total (408, 483 and 569) [14]. In four clean runs the total moved within 22 seconds of the answer [12]. Other numbers lagged, leaving the Features tab 126 credits behind the "Allowance used" figure [20].
What to watch
- Whether Atlassian publishes a per-message credit figure for Think deeper before 3 December.
- Whether Deep Research becomes available in the author's org, and whether Atlassian bills failed replies.
- Whether the pool sizes and list prices for Jira Standard and Teamwork Collection Standard change before billing starts.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence58
- Adoption
- Insufficient
- Hype gap−10
- Incentives
- Insufficient
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
In June, Andrew Fleig asked on the Atlassian Community: "70 credits...10 per chat? So, only 7 chats per month on a paid plan?"
- [2]
An Atlassian team member told Fleig at the time that the credits are pooled and that Atlassian was not billing overage yet.
- [3]
Atlassian will start billing Rovo credit overage on 3 December 2026.
- [4]
The author ran Rovo Chat on their own real Atlassian Cloud test org on 14 October, reading the Rovo credits meter endpoint before each action and every 20 seconds after it.
- [5]
On the test org a single Quick answers message cost exactly 10 credits, and a three-message Quick answers thread cost 30.
- [6]
A Think deeper message cost 65 credits in one test and 86 credits in another.
- [7]
Atlassian's table says "10 Rovo credits per billable event" and "each user message is a billable event".
- [8]
Atlassian lists Think deeper as "Variable credits per billable event" and publishes no number for it.
- [9]
Atlassian says Think deeper credits depend on "Reasoning steps", "Search volume", "Tools invoked" and "Model power".
- [10]
A Jira Standard seat carries 25 Rovo credits.
- [11]
Empyra, an Atlassian partner, wrote that a five-message Quick answers thread "costs 50 credits, not 10".
- [12]
The meter total moved within 22 seconds of the answer in the four clean runs the author timed.
- [13]
The 65-credit message was a comparison of a Scrum board and a Kanban board for a 12-person support team; the 86-credit message was a one-page plan for a change advisory process at a 40-person company. They took 75 and 110 seconds to answer.
- [14]
At the start of three runs the author watched the total for two to four minutes to confirm nothing else on the org used Rovo; it never moved (408, 483 and 569, all steady) and did not move between runs.
- [15]
86 credits is 3.44 months of one Jira Standard seat's 25 credits.
- [16]
A 25-credit seat funds 2.5 quick messages at 10 credits each.
- [17]
A 200-seat Jira Standard pool is 5,000 credits, assuming the pool scales as 25 credits per seat.
- [18]
200 people sending one 10-credit quick message a day draw 2,000 credits a day.
- [19]
A 5,000-credit pool lasts 2.5 working days at 2,000 credits a day.
- [20]
The Features tab (483) was 126 credits behind the 'Allowance used' figure (609).
- [21]
Let Rovo decide stayed at 10 credits for a simple question, but Atlassian says Rovo switches to Think deeper by itself on "a multi-layered or open-ended prompt", so an auto prompt can cost more.
- [22]
At 23:14 UTC, about two and a half minutes after the last answer, the usage page said "Allowance used 609" and "Credits this period 579", while the Features tab still said 483. The author also estimates that on Jira Standard, 200 people asking one quick question a working day would cost about $370 a month in overage.
- [23]
200 seats of Jira and Confluence Standard cost $3,050 a month at list price with a 10,000-credit pool; Teamwork Collection Standard lists at $2,940 with a 50,000-credit pool.
- [24]
Teamwork Collection Standard lists $110 a month below Jira plus Confluence Standard at 200 seats and has a pool five times larger.
- [25]
Deep Research answered "Deep Research is temporarily unavailable" three times on 14 October 2026; the author has no credit number for it and cannot tell whether those failed replies were charged.
Get this ledger inside ChatGPT. Ask about any of our stories and the answer brings its figure, each claim’s verdict and the sources. Free, no account.
Sources
1 independent publisher whose own reporting we read for this story.
- dev.toRovo Credits per User: Cost and Usage per Action, Measured
1 article · October 15, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.