Rovo AI Credits in Small, Medium, and Large Organizations - Why the Model Needs an Update

[#1]

With the rollout of Atlassian Rovo AI, many teams are eager to use it daily for Jira, Confluence, Jira Service Management (JSM), and even third-party connectors like Outlook, SharePoint, and Google Drive.

But one common question in the community is:

“How are Rovo AI credits consumed, and is the current allocation realistic for daily operations in large organizations?”

Here’s what the current quotas look like, and why we believe Atlassian should rethink them.

---

Current Monthly AI Credit Quotas (Per Licensed User)

Subscription	App Type	Monthly AI Credits (per user)
Premium	Atlassian Apps (Jira, Confluence, JSM)	250 credits
	Non-Atlassian Apps (3P connectors)	70 credits
Enterprise	Atlassian Apps (Jira, Confluence, JSM)	625 credits
	Non-Atlassian Apps (3P connectors)	150 credits

Key Difference: Atlassian does allocate separate credits for internal Atlassian apps vs external connectors - but both still count against usage, and heavy usage can still lead to exhaustion mid-month.

---

Impact by Organization Size

Org Type	Example Users	Enterprise Tier Credits (Atlassian Apps)	Enterprise Tier Credits (Non-Atlassian Apps)	Daily Impact
Small	200 users	125,000 total	30,000 total	Comfortable for moderate daily usage.
Medium	1,000 users	625,000 total	150,000 total	Sustainable if Rovo is used strategically.
Large	5,000 users	3,125,000 total	750,000 total	Heavy usage across departments can deplete credits early.

---

Why This Is a Challenge for Large Enterprises

For many organizations, Atlassian App queries are core operations, not optional AI extras:

• Summarizing Jira epics and sprints.

• Drafting Confluence content.

• Analyzing service tickets in JSM.

Treating these core platform tasks the same way as querying a SharePoint file risks discouraging everyday usage especially in high-volume teams.

---

Recommendation to Atlassian

From a long-term adoption and enterprise planning standpoint, we recommend:

1. Exclude Atlassian App Queries from Credit Usage

   • Jira, Confluence, and JSM are core platforms. Rovo queries against them should not consume AI credits at all.

2. Daily Reset for Atlassian App Credits

   • If exclusion isn’t feasible, allow Atlassian App credits to reset every 24 hours, encouraging teams to use AI freely without rationing.

3. Consider Scaling Up Credits for Large User Bases

   • While 625 credits per user sounds high, at enterprise scale it’s possible to burn through this quickly especially with multiple prompts per user per day.

---

Why This Helps All Organizations

• Small orgs get predictable access without worrying about occasional usage spikes.

• Medium orgs can grow Rovo adoption without complex usage policies.

• Large orgs can embed Rovo into daily workflows without constant credit monitoring.

---

Community Discussion Question:

Would excluding Atlassian App queries from credit usage, or resetting them daily, change how your teams use Rovo AI?