Do multiple instances affect Marketplace app costs in Enterprise plans?

When you have an Enterprise plan, you can add up to 150 instances of an Atlassian app without paying extra for those instances. However, Marketplace app are not included in your Enterprise plan.

For Enterprise plans of Jira and Confluence, Marketplace apps use different pricing models based on how you use them:

Single-instance pricing: You pay for the Marketplace app license once for each Atlassian site. The cost is usually based on the number of users on that site or the number of people using the Marketplace app. See Flexible instance-based pricing options for Marketplace app

Multi-instance pricing: You buy the Marketplace apponce for Jira or Confluence and can use it across many instances. You are charged based on the number of unique users of the Marketplace appacross all those instances. If a person uses the app in more than one instance, they are only counted once. See How pricing works for multi-instance Marketplace apps

Whether adding more instances changes your Marketplace appcosts depends on the app’s pricing model and how many people use the appacross your instances.

How does Marketplace app billing affect large product instances?

In a large Atlassian app instance, you might have a Marketplace appthat only a few users need. Depending on how the Marketplace app is billed, you could end up paying for users who never use the app.

Single-instance pricing

With single-instance pricing, you are usually billed based on the user tier of the Atlassian app or the number of Marketplace app users in that instance. If only a few users need the app, you can create a separate instance with fewer users and install the Marketplace app only there.

Example scenario

Acme has 8,000 development team members and 200 sales team members using the same Jira instance. The sales team’s projects are only open to the sales team. Everyone uses a diagram Marketplace app, but only the sales team uses a customer relationship management (CRM) Marketplace app.

With this setup, Acme pays for:

• Jira Enterprise

• 8,200 Marketplace app users for the diagram app

• 8,200 Marketplace app users for the CRM app

To lower costs, Acme could move the sales team’s projects to a separate Jira instance. The sales team would still have access to the main Jira instance used by the development teams.

With this change, Acme would pay for:

• 8,400 Marketplace app users for the diagram app (8,200 in the main instance + 200 in the sales instance)

• 200 Marketplace app users for the CRM app (only in the sales instance)

This means Acme only pays for CRM app users who need it, which could save money. But the sales team would need to work in two Jira instances, which could make their work more complex.

Multi-instance billing

With multi-instance billing, you are billed based on the number of unique users of the Marketplace app across all your Jira or Confluence Enterprise instances. Splitting users across multiple instances will not lower costs if the same users still use the Marketplace app.

Example scenario

From the previous example, the CRM Marketplace app uses multi-instance billing for Cloud Enterprise Jira.

In this case:

• Acme buys the CRM app once for Cloud Enterprise Jira.

• The app can be installed on more than one Jira instance in the same Atlassian organization.

• Billing is based on the number of unique CRM app users across all instances.

In Acme’s setup, only the 200 sales team members need the CRM app, even if they use more than one Jira instance. These 200 users are counted once for CRM app billing, no matter how many instances they use.

This means:

• Creating a separate Jira instance for the sales team does not change the CRM app cost if the same 200 users still use the app.

• The choice to add another instance is now based on data separation, collaboration, and admin needs than than by reducing CRM app licenses.

Estimate the actual costs of Marketplace app

Marketplace app pricing changes by user tier. Sometimes, a lower user tier has a higher price per user. We recommend estimating the real costs before deciding where to install apps or how to set up your instances.

• For single-instance pricing, estimate costs based on the user tier for each instance where you install the Marketplace app.

• For multi-instance pricing, estimate costs based on the total number of unique users of the app across all your Jira or Confluence Enterprise instances. A user with access to more than one instance is only counted once for the app.

To estimate Marketplace app costs, go to the app listing on the Atlassian Marketplace and select the Pricing tab. Use the estimate tool to see how your bill changes with different user counts. Make sure to select Annual for the billing cycle. More about multi-instance Marketplace pricing

When is the best time to add more Atlassian app instances?

If you are considering adding more Atlassian app instances, we recommend doing this before new teams or users are onboarded. This is because moving teams and their data around after people have already been using the Atlassian apps for some time can be difficult, and may involve exporting and importing data between instances, or performing a cloud-to-cloud migration.