How are you managing Marketplace app licensing across multiple Atlassian Cloud instances?

[Mirek]

I’m curious how organizations in Atlassian Enterprise setups handle Marketplace apps when they operate multiple Jira or Confluence Cloud instances.

What I’ve seen is that once you go multi-instance, the app licensing model becomes much harder to reason about. The same app might be used across different products, teams, or even business units, but the cost is often not clearly attributable in a consistent way.

In some cases, everything is centralized under a platform budget, but then it becomes difficult to understand actual consumption per instance. In other setups, costs are split by instance or even by team, but that tends to create a lot of overhead in tracking usage and justifying allocations.

What I’m trying to understand is how others are approaching this in practice.

Do you centralize Marketplace app licensing across all instances, or try to break it down per instance or business unit? And how do you actually make usage and cost transparent enough to manage it at scale?

[Ollie Guan]

Hi @Mirek ,

Regarding the challenges of managing Marketplace app licensing across multiple instances, I’d like to share how we handle this in our organization, which might offer a practical solution for your setup.

Our Model: Subsidiary-based Isolation
In our group architecture, Jira instances are split strictly by subsidiary. Each subsidiary operates its own independent Jira instance and app environment, maintaining a high level of "relative isolation."

The Core Logic of This Model:

1. Core Advantage: Clear Financial Boundaries.
   Under the Atlassian Cloud Enterprise plan, while core product licenses (Jira/Confluence) are billed based on "Unique Users" at the organization level, Marketplace app fees remain tied to the specific instance (Site) of each subsidiary. This means Subsidiary A and Subsidiary B are billed independently even if they use the same app. This naturally solves the "cost attribution" issue you mentioned—the cost is automatically allocated to the site that uses it.

2. Main Challenge: Administrative Redundancy.
   The trade-off is the overhead of managing multiple environments. The same app may require separate security vetting and configuration for each instance, and global settings cannot be easily shared across sites.

My Recommendations for You:

• Leverage "Unique User" Billing for Core Products: Centralize the core product budget at the Group level to take full advantage of the Enterprise plan’s cost-saving mechanism.

• Allocate App Costs by Instance: Keep app licensing tied to specific sites. You can pull site-specific app expenditures directly from the billing reports in admin.atlassian.com for precise financial reconciliation.

• Establish a Group-wide Whitelist: Even with isolated instances, maintain a centralized list of approved apps to ensure that all subsidiaries meet the same security and compliance standards.

This "hybrid approach" allows you to benefit from the Enterprise plan's core licensing efficiencies while maintaining strict financial transparency and administrative isolation at the app level.