Future Cloud pricing
Atlassian is updating the list price of all cloud subscriptions for the following products on October 16, 2024 PT:
- Jira: Standard, Premium, and Enterprise plans
- Confluence: Standard, Premium, and Enterprise plans
- Jira Service Management: Standard, Premium, and Enterprise plans
- Opsgenie: Standard and Enterprise plans
- Atlassian Guard: Standard plans
- Bitbucket: Standard and Premium plans
- Compass: Standard plan
This price update impacts new purchases as well as renewals and upgrades of existing subscriptions. If a quote is generated before October 16, 2024 PT, we will honor it under the prior price until the quote expires. Quotes generated on or after October 16, 2024 PT, will be based on the new prices.
This page provides FAQs related to the upcoming price updates and detailed pricing tables by product and user tier. New pricing will not go into effect until October 16, 2024 PT. If you would like to talk to us directly about how these changes impact you, please contact our support team.
Atlassian is also updating packaging and pricing models for Jira Service Management Cloud on October 16, 2024 PT. For details about these changes, please see this blog.
General questions
New prices will go into effect October 16, 2024 PT.
|
In the last 12 months, we've invested in enterprise-grade security and accelerated delivery of innovative new product features such as Summary, List, and Calendar views in Jira, Databases and Whiteboards in Confluence, embedded Atlassian Intelligence capabilities, and more.
These are just a handful of the improvements that have been made within the past year, with many more in the works. Be sure to check out our Cloud Roadmap to see the latest and upcoming features we’re building into our Cloud products. |
These changes reflect Atlassian’s continued commitment to deliver innovative, powerful tools that increase visibility, alignment and productivity across your organization - all backed by an enterprise-grade cloud platform. To see the latest improvements we have launched in the last 12 months, please refer to our product investments. |
Billing & licensing questions
If you’re looking to lower your monthly bill, here are a few strategies to consider:
If you're looking to lower your annual bill, here are a few strategies to consider:
|
Customers with an annual cloud subscription automatically receive a no-obligation quote to renew their subscription 90 days before it expires, unless they have an existing quote for another product on the same site. Customers need to be within 90 days of their renewal window to purchase a renewal (even if it’s purchasing an additional year for a 2-year contract). Customers on monthly plans cannot renew early unless they move to an annual plan. To move to an annual plan, please refer to “How do I sign up for annual payments?” Monthly customers can request an annual quote any time before October 16, 2024 PT, to receive existing pricing. Payment must be received before that quote expires, and the quote cannot be extended beyond November 13, 2024 PT. |
If you created or received a quote for an annual subscription before October 16, 2024 PT, we will honor that quote under the existing pricing until the quote validity date lapses. Quotes generated on or after October 16, 2024 PT, will be based on the new pricing. |
To calculate your updated price, you have two options depending on your role. If you are a billing and/or technical contact on a paid invoice, log into my.atlassian.com and follow these steps:
If you are a Site Administrator on a paid invoice, log into admin.atlassian.com and follow these steps:
A note on annual pricing: Atlassian uses a fixed price tiered model for annual pricing. For example, Jira Standard with 450 users would be calculated at the 500 user tier for an annual cost of $35,000. For additional clarity, consider the following scenario: If you add 75 users to your 450 users on Jira Standard, you would now have a total of 525 users on Jira Standard. This puts you in the 600 user tier at $41,000 annually - you would not pay for the 450 users and the 75 users separately in their respective tiers. Please note that annual tiered pricing varies across Atlassian products and plans. A note on monthly pricing: Atlassian uses a progressive per-user pricing model for monthly pricing. Progressive pricing is calculated using tier groups, each with a distinct per-user price. For example, Jira Cloud Standard with 450 users would be calculated as: $8.60/user for users 1-100 $7.30/user for users 101-250 $6.10/user for users 251-450 The total monthly price equates to $3,161.60/month, or an average of $7.03/user. Please note that monthly per-user pricing varies across Atlassian products and plans. |
We will honor all existing quotes generated before October 16, 2024 PT. If a quote is edited on or after October 16, 2024 PT, then any changes will reflect the new pricing. |
Pricing for Marketplace Partner apps (or non-Atlassian third party apps) are not changing as a direct result of Atlassian's pricing updates. However, Marketplace Partners can adjust their pricing at anytime, so please check marketplace.atlassian.com for up-to-date app pricing information. |
Academic discount percentages will remain the same. Qualifying collegiate-level or higher academic institutions can still receive 50% off of list price for new purchases, upgrades, and renewals. Confluence Cloud licenses can receive 75% off list price for qualifying collegiate-level or higher academic institutions. |
Community discount percentages will remain the same. You will still receive 75% off of cloud list price for new purchases, upgrades, and renewals. |
Customers with existing subscriptions will pay the new subscription list price for renewals that occur on or after October 16, 2024 PT. |
Yes, if you upgrade your user tier on or after October 16, 2024 PT, your cost will be calculated using the new list pricing in effect at that time. If you upgrade your user tier before October 16, 2024 PT, you will remain on your existing subscription pricing. |
Yes, if you upgrade your plan on or after October 16, 2024 PT, your cost will be calculated using the new list price in effect at that time for the new plan. If you upgrade your plan before October 16, 2024 PT, you will remain on your existing subscription pricing. |
If you add a new product to your existing cloud site on or after October 16, 2024 PT, you will pay the new subscription pricing for that product. |
Jira Service Management pricing and packaging updates
Jira Service Management is making packaging changes to the Standard plan and introducing consumption-based pricing to certain Premium and Enterprise features. Details on these changes can be found in this blog.
Jira Service Management pricing and packaging questions
We're updating our pricing and packaging for Jira Service Management Cloud plans to better align with industry standards and sustain our commitment to innovation.
This page provides FAQs related to the Jira Service Management pricing and packaging updates, including detailed volume discount pricing tables. The changes will not go into effect until October 16, 2024 PT. If you would like to talk to us directly about how these changes impact you, please contact our support team.
Consumption-based Pricing
We are updating the way we charge for Assets and Virtual Service Agent on Jira Service Management Premium and Enterprise plans. You will now be charged for stored objects and assisted conversations based on new usage limits. Included in Jira Service Management Premium and Enterprise plans, customers will be allowed to:
*See more information here. These changes align with the value these capabilities have already brought to customers and will allow us to invest more resources into innovation and scale. |
If you are currently storing more Assets objects or are executing more Virtual Service Agent assisted conversations than the new limits, or project your future usage will exceed the new limits, your bill may be impacted by this change. |
You should have received an email notification on September 17, 2024 PT. You can also check your site usage for Assets objects and Virtual Service Agent assisted conversations by navigating to Settings > Products > Jira Service Management > Feature usage. |
These new usage limits will be effective Oct 16, 2024. |
You can check your site’s usage of Assets objects and Virtual Service Agent assisted conversations by navigating to Settings > Products > Jira Service Management > Feature usage. Once the consumption-based pricing changes are in effect, we’ll notify you by email and in your Jira Service Management instance if you’re approaching the allowance limit. You can then add additional objects or assisted conversations to your site. From there, monthly subscribers can set a maximum usage limit and annual subscribers can pre-purchase a tier of usage. |
To access extra usage, you’ll need to subscribe to an add-on, either:
These add-ons will appear as separate line items to Jira Service Management in your bill. Add-ons will be available to install on your site once consumption-based pricing becomes effective on October 16, 2024. Visit this page to learn how to increase usage limits for Assets. Visit this page to learn how to increase usage limits for Virtual Service Agent. |
An object is a representation of a single, unique thing of a particular object type included in an object schema. The total number of objects includes all schemas across your site except system schemas. System schemas are schemas used by other features in Jira to store information, such as Services. Products, Entitlements, and Service are not part of consumption-based pricing and therefore, you will not be charged. Learn more: Feature usage and how it works | Jira Service Management Cloud | Atlassian Support |
We conducted extensive research about the object usage requirements for customers across various use cases, and this has helped inform the allowance limit. |
Assisted conversations include: Matched conversations – any conversation that was matched to an intent, regardless of whether the Virtual Service Agent resolves the issue or escalates it to an agent for further support. Read more about how intent matching works. AI resolved conversations – any conversation during which the Virtual Service Agent responds to the customer using Atlassian Intelligence answers, and the customer indicates that the response resolved their issue or abandons the conversation, resulting in the conversation being auto-closed. Learn more: Feature usage and how it works | Jira Service Management Cloud | Atlassian Support |
Consumption-based pricing only applies to Assets objects and Virtual Service Agent assisted conversations as part of our Premium and Enterprise editions. This new pricing model means that you’ll only pay for what you use beyond the in-plan allowance: 50,000 Assets objects and 1,000 Virtual Service Agent assisted conversations per month. You’ll be billed for over-limit usage (set by your Jira Administrator) as part of your current Jira Service Management billing cycle, monthly or annually. |
Consumption-based pricing works differently depending on whether you have a monthly and annual subscription for Jira Service Management:
|
For monthly subscriptions, we will charge for the following month’s usage based on the exact number of Assets objects or Virtual Service Agent assisted conversations used. For annual subscriptions, you’ll need to pre-purchase the tier of Assets objects or Virtual Service Agent assisted conversations that most closely matches your usage. |
Please see pricing tables here. |
We will email you when you’re approaching the new usage limit at thresholds of 80%, 90% and 100%. For Assets, once the limit is reached, no more objects will be able to be imported or created. Customers will still be able to use Assets functionality (e.g. Assets schemas, custom field, automation etc). For Virtual Service Agent, once the limit is reached, all conversations with a connected project will be escalated to an agent from that point onwards. Those that aren’t connected to a project (i.e. Help Center) will be redirected to normal search. |
For customers on monthly subscriptions, Jira Administrators will able to set a maximum usage limit of objects and assisted conversations to prevent overuse and increased bills. This limit can be changed at any time. |
Virtual service agent assisted conversations will reset to zero in alignment with the billing frequency of your Jira Service Management plan:
|
For monthly subscriptions, we will charge for the following month’s Asset objects or Virtual Service Agent assisted conversation usage based on the exact number used on the last day of your monthly billing cycle. This will be billed as part of the invoice for your monthly Jira Service Management Premium or Enterprise Cloud license. For annual subscriptions, usage tiers can be purchased via your billing page in Jira Service Management or through your account team. Additional Assets objects or Virtual Service Agent assisted conversations can be purchased if usage limits exceed a tier provision, which you can increase throughout the year if needed. |
No, seat expansion does not relate to usage of Assets objects and Virtual Service Agent assisted conversations. |
No, assisted conversations and objects usage do not roll over if unused within the billing cycle. |
No. Objects stored in Data Manager are not counted as Assets objects - we only count objects brought into Assets schemas. Therefore, testing the Data Manager feature will have no impact on billing for extra objects. Additionally, Compass components are not part of consumption-based pricing. Compass components sync with the Services schema in Assets. These are considered system schemas, which are excluded from the usage count for Assets. |
You can check your site usage for Assets objects and virtual service agent assisted conversations by navigating to Settings > Products > Jira Service Management > Feature usage. In addition to this, we will send you notifications via email and in-product when your site is at 80%, 90% and 100% of its usage limit. When this happens, you can manage the usage limit:
|
If your site breaches its usage limit for Assets objects or virtual service agent assisted conversations, the following will happen:
|
|
Enterprise plans allow you to have up to 150 sites of Jira Service Management at no additional cost. Each of these sites will be able to store 50,000 Assets objects and execute 1,000 Virtual service agent assisted conversations per month (or 12,000 per year) for free. Sites requiring additional usage beyond this limit will require a subscription to either the Extra objects add-on or the Extra assisted conversations add-on, and any additional usage beyond the limit will be billed for each site individually. |
Consumption-based pricing will not apply to Sandbox sites. |
Yes. The same discount percentages apply to consumption-based pricing for Academic and Community special pricing as Jira Service management. |
Packaging Changes
Advanced incident, problem, and change management capabilities will be moving out of Jira Service Management Free & Standard and into Premium & Enterprise. We’re making this change to better align our service management solution with industry standards and how similar solutions include advanced incident, problem, and change management features across their plans. Additionally, these changes will better enable customers to choose the plan that best matches their needs. In the past year, we’ve invested heavily in incident and change management capabilities to strengthen our IT Operations offering:
Our near-term Ops roadmap includes even more investments:
We will continue to invest in building the capabilities our customers need to deliver high velocity service management at scale. |
The following features will be removed from the Free and Standard plans:
Core incident management capabilities will remain as available in the Standard edition:
|
The best way to identify if the features are being used on a site is as follows: To identify Projects using Change and Problem management features:
To identify teams using Advanced incident management:
|
No. With the removal of advanced incident, problem, and change management capabilities from Jira Service Management Free & Standard, no customer data will be lost. Request types associated with Changes, Problems and Post-incident reviews work categories will become unassigned, and all issues of these request types will move into the “All Queues” section in the project navigation. |
If you have been using Changes, Problems and Post-incident reviews:
If you have previously used the IT Service Management project template to create a project, you will not lose access to any of the request types, issue types, custom fields or workflows that were created as a part of it. |
All customers on Jira Service Management Cloud Free and Standard plans using the capabilities listed above will be impacted by this change. | |
These changes will go into effect on Oct 16, 2024 PT. |