How do credits translate to tokens?

[Matt P]

I just got an email about the ending of the beta. At the moment in the beta there's 5 million tokens per day. The invitation to upgrade for $20 a month on the standard plan offers 2,000 credits per month.

Is this more or less than the current 5 million daily token limit?

Apologies for my confusion, I just struggle to understand how the current token limit converts to credits. 

[Ciara TN · Accepted solution]

Hi @Matt P 

I reached out to Atlassian Support on your behalf and got the following response: 

"This is from the Atlassian support:Previously, Rovo Dev used a token-based system, where each user had a daily allowance of 5 million tokens for various actions. We have now transitioned to a credit-based system, where each user receives 2,000 credits per month.
What’s the difference?

• Tokens: Represented the number of actions or data processed each day, resetting daily.
• Credits: Provide a monthly allowance, making it easier to track and manage usage over time. Credits are deducted based on the actions you perform in Rovo Dev.

How does this impact you?

• The new credit system is designed to offer more predictable and transparent usage tracking.
• You can monitor your monthly usage and plan accordingly.
• If you need more credits, there are options to increase your allowance.

Here is the Rovo Dev pricing plans: https://www.atlassian.com/software/rovo-dev/pricing

8:27"

So in short no more token just credits. The number of credits each request takes is depending on the complexity of the request which cannot be predefined as of now.

I know not a definite answer but as LLMs become cheaper to run and Atlassian see usage I think there will be no exact answer yet. 

I hope this helps. 

-Ciara 

[Dr Valeri Colon (Connect Centric)]

@Matt P,

@Rebekka Heilmann _viadee_, @Ciara TN @Val Knapp and I had a whole Slack discussion on your question. Here's my add: Credits and tokens don’t convert 1:1. The old 5M daily tokens were part of the beta and aren’t comparable. In paid plans, 2,000 credits/month covers normal usage for chat, agents, and search—each action consumes a few credits per request, not millions. Credits are a request-based model, not a token-based one, so you’ll use far fewer than 5M tokens per day.

Before announcing the new model at Teams it would be really helpful if Atlassian clarified all these types of questions for the entire community.

[Rebekka Heilmann _viadee_]

Hi @Matt P 

I think it's just different wording between Beta and GA. As Rovo Dev and Rovo are two seperate products, i guess the teams used different wording at the start but now standardize the documentation and pricing models.

I couldn't find any details on what action uses how many credits unfortunately. I'll try to get someone from the Rovo Dev team on it to update the documentation, but no promises made.

Rovo Dev credits represent units of usage based on interactions with specific Rovo Dev AI features. For example, reviewing a pull request or interacting with Rovo Dev CLI.

Credits are allocated per user and the amount of credits an interaction uses depends on the complexity of that interaction.

For Rovo Dev Standard, when a user’s allocated credit limit is reached, additional usage incurs charges of $0.01 per credit, with a default monthly limit of 2,000 Rovo Dev credits per user. Admins can set custom limits and controls on a per-site basis.

For more information on Rovo Dev credits, please review Rovo Dev documentation.