Atlassian has announced a significant expansion of its pricing model: the introduction of Usage-Based Pricing. Starting December 3, 2026, actual usage of AI capabilities, automation, and Bitbucket features will be billed directly.
The established seat-based licenses for Jira, Confluence, and Jira Service Management will remain in place—usage-based pricing is being added as an additional management layer on top.
What this means for IT and Procurement teams: Your Atlassian budget for 2027 can no longer be calculated solely based on user count.
Previously, the price per Jira, Confluence, or JSM instance was tied primarily to seat count. With the 2026 update, Atlassian is introducing a second axis: actual consumption.
This consumption is measured across five key functional areas ("meters"):
How do allowances work?
Included allowances are determined by your plan tier and seat count. They are pooled at the organisation level and reset monthly. Unused allowances expire at the end of each month.
One exception: There is no free allowance for CSM AI Agent Resolutions. Billing begins from the very first successfully resolved request (default usage limit: 25,000 resolutions/month, configurable).
If your organisation exceeds its included allowances, standard rates will apply:
Overage billing is enabled by default. However, administrators can configure strict consumption limits or disable overages entirely in Atlassian Administration to avoid unexpected costs.
1. Organization-wide pooling is a double-edged sword.
Pooling all allowances centrally offers greater flexibility across teams, but it reduces visibility into individual usage. A single team with heavy Rovo usage can exhaust the shared pool before other departments have even started.
2. Automation steps count even on failure
Billing is based on every executed step, not just successfully completed rules. Steps resulting in status outcomes like "No match" or "Cancelled" still consume allowance. Complex, nested automations with loops carry hidden cost risks.
3. Plan selection becomes a direct cost lever
Customers upgrading from standalone licenses to a Teamwork or Service Collection receive up to 10x higher AI allowances compared to combined standalone baselines. This significantly changes the cost-benefit ratio when comparing individual products to bundles.
For most organizations, very little will change on December 3, provided usage stays within included allowances. However, it becomes critical where AI and automation adoption has grown significantly in recent months without central tracking.
Would you like to know how the new pricing rules impact your specific Atlassian stack and 2027 budget? As a long-standing Atlassian Platinum Solution Partner, demicon helps you analyze your current usage, optimize licensing structures, and avoid unexpected costs.
Do you have any questions or would like personal consultation? Our expert will be happy to assist you.
DEMICON : Mar 28, 2025, 12:36:12 PM
Modern work environments are often characterized by scattered information, isolated tools and a lack of transparency about how individual tasks...
DEMICON : Apr 14, 2025, 3:25:46 PM
From April 8 to 10, 2025, Anaheim, California, was once again the stage for one of the most important events in the tech and collaboration world: ...
DEMICON : Jan 14, 2022, 9:02:44 AM
Over the past years, Atlassian has been highly committed to becoming a cloud-first company by assisting its customers in easing their way into the...
DEMICON