Jira Service Management Pricing: Service Collection Plans Explained

Jira Service Management is now sold only as part of the Service Collection, which also includes Customer Service Management, Assets, and Rovo. You choose one of four plans: Free, Standard, Premium, or Enterprise.

When I first looked into these plans, I wanted to know which one includes asset management, and the posts I found online weren’t up to date. So I collected the key differences in one place, from the perspective of an Atlassian Marketplace vendor, and updated them in October 2026, after Atlassian introduced the Service Collection.

Service Collection Plans

You will find the basic information about each plan in the table below.

Source: Atlassian Service Collection pricing, checked on October 21, 2026. Prices depend on the number of agents, so use Atlassian’s calculator for your team size.

User limit: This is one of the most obvious factors when you choose your plan. If you have three or fewer agents, you can still consider the Free plan as a good starting point. If you have more agents, start with the Standard plan.

Asset and configuration management: Originally named Insight, it’s now included from the Standard plan, with 5,000 objects. Premium adds advanced asset management and more objects. It’s often an essential part of any serious Jira Service Management implementation.

Storage: In my opinion, this parameter is underrated as we are used to having as much free space as we need. 2GB from the Free plan is not enough when you attach many files to your tickets. At Appsvio, we use a support project to share app versions available to Data Center customers. They also include Jira Support zip which can be 50MB each. It can quickly become a limitation also for the sales and marketing teams. An interesting article about storage in Jira is available here.

Sandbox: This is my favorite feature, but unfortunately only available on the Premium and Enterprise plans. With the sandbox, you can test configuration changes or new apps on non-production instances. It can be a test or staging instance for the production Jira. Read more in Atlassian’s guide to sandboxes.

Data Residency (DR): Atlassian decided that all paid plans would include data residency, which was a reasonable action. Missing data residency was most often cited as the main reason why many European customers did not use Cloud. Today it is available to anyone with any paid plan.

Site renaming: At some point, you may need to rename your site. It can happen due to a company name change, an acquisition, or better customization of what you are doing. Note that this is not available with the Free plan.

Forms for Jira (formerly ProForma Cloud): This is a no-code form builder that Atlassian acquired in 2021 and built into Jira Service Management. Teams use it to create forms that capture the data they need to get the job done.

Which Service Collection Plan Is Right for You?

If you have three or fewer agents, go for the Free plan. It’s a huge benefit that you can use the Service Collection and some apps for free when you have a small team. Remember that not all apps are free for up to 10 users - this is a vendor’s decision. There are other restrictions and limitations, but you can upgrade to the Standard plan anytime.

Choose Standard for most teams. It includes Assets with up to 5,000 objects, Rovo, and a custom-branded help center. There are still some storage limitations. Nevertheless, 250 GB should be enough for any small to medium Jira instance for the first 3-5 years.

Choose Premium if you need change management, advanced incident and problem management, a virtual service agent, or more Assets objects. As part of this plan, you get a lot of tools to help you manage your Jira Cloud instance (sandbox, faster help from Atlassian, list of allowed IP addresses, and more).

Choose Enterprise if you need multiple sites, advanced security controls, or enterprise-wide analytics.

There are more differences than mentioned in this article. We recommend reviewing all of them here before making your purchase.

Other Options to Extend Jira Service Management

You can use apps to add features that Jira doesn’t have. Remember that apps don’t depend on your Service Collection plan, so an app works the same way on Free or Premium.

Apps are Jira extensions. When Jira doesn’t meet your needs out of the box, apps can be a good choice. For example:

• If you need customer and organization management, try Perspective;
• When you deal with many duplicate work items, Service Pack for Agents lets you merge them;
• If you use HubSpot, HubSpot CRM Integration for Jira shows CRM data on Jira work items;
• When your customers want to update their requests, Feature Bundle is what you need.

Hope you now find the Service Collection plans a bit more understandable.

This article was updated on October 27, 2026.