Atlassian Marketplace Apps: Licensing, Cost Control, and EOL Impact

What Makes Atlassian Marketplace App Licensing Different

Atlassian Marketplace apps follow a unique licensing rule that distinguishes them from most enterprise software add-ons: every app must be purchased for the full licence count of the underlying Atlassian product. If your organisation has 500 Jira Software licences, every Jira Marketplace app you install must be purchased for all 500 users — regardless of how many users actively use that app.

This all-or-nothing licensing rule has significant financial implications. Unlike enterprise software where you can licence a feature for the team that actually uses it, Atlassian Marketplace apps apply to the total licence tier. An organisation that installs a specialised diagramming app for 20 developers pays for that app across all 500 Jira licences. The per-user app cost multiplied by the full licence count — not the active user count — is the true app cost.

For most enterprise Atlassian deployments, this creates a pattern of systematic overpayment: apps that were installed for specific projects or teams continue to renew at full licence count for years after the original use case has ended. App shelfware — paying for apps nobody actively uses — is one of the most prevalent and least scrutinised forms of software waste in Atlassian environments.

Understanding how Atlassian pricing changes in 2026 affect both base licences and Marketplace apps is essential context for any organisation managing Atlassian spend at scale.

Marketplace App Pricing Models

Per-User Monthly Subscription (Cloud)

The dominant pricing model for Cloud Marketplace apps is per-user per-month subscription, applied to all licenced users. App vendors set their own per-user rates, which typically range from $1 to $25 per user per month depending on the app category. Analytics and reporting apps tend to be lower cost ($1 to $5 per user per month). Advanced automation apps and specialist tools can reach $10 to $20 per user per month. Enterprise integration and security apps often command $15 to $30 per user per month.

The cumulative impact of multiple apps at mid-range pricing is significant. An organisation with 500 Jira users running six Cloud Marketplace apps at an average of $8 per user per month pays $288,000 per year in app fees on top of the Jira subscription. This frequently exceeds the base Jira Software subscription cost.

Tiered Pricing with User Bands

Like Atlassian's base products, most Marketplace apps use tiered pricing with predefined user bands (typically matching Atlassian's own tier structure). The per-user effective rate typically decreases as the user tier increases, creating volume discount effects at higher user counts. However, organisations that sit just above a user tier threshold pay for the next full band — the same overpayment dynamic that affects base product pricing applies to every Marketplace app independently.

Flat Monthly or Annual Fee (Some Apps)

Some Marketplace apps, particularly those providing instance-level functionality (admin tools, backup solutions, security scanners), charge a flat monthly or annual fee regardless of user count. For large user bases, flat-fee apps can be significantly more cost-effective than per-user alternatives. Identifying opportunities to replace per-user apps with flat-fee equivalents is a viable cost optimisation strategy.

Consumption-Based Pricing (Emerging)

A minority of Marketplace apps, particularly those integrating with external AI or automation services, have moved to consumption-based or outcome-based pricing models. These apps charge per action, per workflow execution, or per AI query rather than per user. Consumption pricing introduces cost unpredictability similar to public cloud consumption models — it scales well when usage is modest but can grow rapidly with adoption. Any consumption-priced Marketplace app requires active monitoring and budget controls.

The Data Center EOL Impact on Marketplace App Portfolios

The Atlassian Data Center end-of-life timeline has profound implications for Marketplace app portfolios. The key dates create a structured urgency that every DC customer with Marketplace apps must understand and plan for:

March 30, 2026 — No New DC Subscriptions for New Customers

From March 30, 2026, new customers could no longer purchase Data Center subscriptions or Data Center Marketplace app licences. This date has already passed. Any organisation that was not an existing DC customer before this date cannot add new DC app licences. This milestone signals the formal end of Data Center as a growth platform.

March 30, 2028 — Last Expansion Rights for Existing Customers

Existing Data Center customers retain the ability to expand their DC licences and add new Marketplace app licences until March 30, 2028. After this date, no new DC app licences can be purchased, and existing customers cannot expand their user counts. This represents the final window for DC-side licence planning before the EOL sequence completes.

March 28, 2029 — Full End of Life: All DC App Licences Expire

On March 28, 2029, all Data Center product licences — including every associated Marketplace app licence — expire and become read-only. Apps that power mission-critical workflows, automation pipelines, integrations, and reporting systems will stop functioning at this date. There is no grace period, no extended support option, and no ability to purchase DC-tier support beyond this date for most products. Bitbucket Data Center is specifically excepted from this timeline.

The operational impact is severe for organisations that delay migration planning. Workflows built on Data Center Marketplace apps — such as ScriptRunner automations, Tempo time-tracking integrations, or Zephyr test management pipelines — will break simultaneously at the EOL date. Planning and executing Marketplace app migration is not a background task; it is a primary work stream that requires dedicated project management and technical resources.

Assessing Your Marketplace App Portfolio

The App Inventory Audit

The first step in Marketplace app cost control is building a complete inventory of every installed app, its licence cost, its active user count, and its business criticality. Most enterprise Atlassian environments contain 10 to 30 installed Marketplace apps, of which typically 30 to 50 percent are either rarely used or unused entirely. An app installed for a project three years ago and never removed generates the same annual renewal cost as an app used daily by the entire team.

Atlassian provides app usage analytics within the admin console that show last-login activity and feature engagement for installed apps. These analytics are the starting point for any rationalisation effort. Apps with zero active users in the past 90 days are candidates for immediate removal. Apps with fewer than 20 percent of licenced users actively engaging are candidates for downgrade or removal review.

Categorising Apps by Business Criticality

A structured app portfolio review categorises each app into one of four groups: mission-critical (workflows or integrations that would fail without the app), high-value (significantly used by 30 percent or more of users), low-value (used by fewer than 20 percent of users with limited business impact), and unused (no active usage detected). Mission-critical and high-value apps are retained and their Cloud migration path is planned. Low-value apps trigger a replacement evaluation. Unused apps are removed before the next renewal cycle.

Cloud Equivalency Assessment

For each Data Center Marketplace app, the migration assessment must answer three questions: Does the vendor offer a Cloud equivalent? Does the Cloud equivalent provide equivalent functionality, or does it have known gaps? What is the pricing difference between the DC app and the Cloud equivalent? Some DC apps were purpose-built for the Data Center architecture and have no direct Cloud equivalent — these require replacement with alternative tools or architectural redesign of the dependent workflows.

Atlassian's developer community has responded to the EOL announcement with a significant push toward Cloud-native app development, and the majority of top-tier DC apps now have Cloud equivalents. However, legacy apps from smaller vendors, custom-built apps, and niche apps for specialist industries may have limited or no Cloud options. These are the highest-risk items in any DC-to-Cloud app migration and require early identification and resolution planning.

Our Atlassian cloud migration guide 2026 includes a structured Marketplace app assessment framework that maps DC apps to Cloud equivalents and identifies gaps requiring alternative solutions.

Cost Optimisation Strategies for Cloud Marketplace Apps

Annual Licence Rationalisation

Treat Marketplace app licences as an annual budget line requiring active management, not passive renewal. Before each app renewal cycle, review the usage analytics, confirm business criticality with the primary users, and evaluate whether the app's functionality has been replicated by a newer Atlassian native feature or a more cost-effective alternative. Atlassian has progressively absorbed functionality from popular Marketplace apps into core product tiers — features that required paid apps in 2020 may now be native in Jira or Confluence Premium.

App Consolidation

Enterprise Atlassian environments often carry multiple apps that partially overlap in functionality — two reporting tools, three integration apps, or multiple automation frameworks. Consolidating to the single best app per functional category and removing duplicates reduces both app spend and operational complexity. An organisation paying for both a Marketplace automation app and Atlassian's native Automation rules (included in Premium) is paying twice for the same capability.

Tier Alignment

App pricing tiers must align with Atlassian product licence tiers. If your organisation has reduced its Jira user count (for example, through a licence rationalisation exercise), the app tiers should reflect the new user count. Apps that were purchased for a higher tier than the current Jira licence level are overpaying. Validate app tier levels against current Atlassian licence counts at every renewal.

Multi-Instance Pricing for Enterprise Customers

Atlassian Cloud Enterprise customers benefit from multi-instance app pricing, which was made available to customers in Q4 2025. This pricing model charges based on unique users of the app across multiple Atlassian instances, rather than summing users across all instances independently. For Enterprise customers running multiple Jira or Confluence Cloud instances, multi-instance pricing can significantly reduce the effective per-user app cost by eliminating double-counting of users present in multiple instances.

Any Enterprise customer who has not yet re-evaluated their Marketplace app contracts under the new multi-instance pricing terms is likely overpaying for cross-instance app deployments.

Billing Model Change: Maximum Quantity Billing (July 2025)

Atlassian changed the billing model for monthly Cloud subscriptions in July 2025, introducing maximum quantity billing. Under this model, monthly billing is calculated based on the peak user count during each billing period, rather than the user count at the start of the period or an average. Organisations with variable headcount — for example, seasonal workers, contractors, or departments undergoing reorganisation — face higher monthly charges under maximum quantity billing when user counts fluctuate upward during a billing period.

The practical implication is that organisations on monthly billing should either migrate to annual billing (which offers pricing certainty) or implement strict user provisioning governance to prevent temporary peak counts from inflating monthly charges. Provisioning a batch of users for a short-term project and then deprovisioning them incurs the charge for the full month at peak tier regardless of how long those users were active.

The True Cost of Marketplace App Shelfware

Marketplace app shelfware — apps that are installed and renewing but not actively used — is endemic in enterprise Atlassian environments. The drivers are consistent: apps installed for projects that have ended, apps procured speculatively and never fully adopted, apps that were superseded by native Atlassian features but never removed, and apps that were required for a specific integration that has since been decommissioned.

The financial impact is systematic because Marketplace apps auto-renew by default. An organisation with 500 users paying $5 per user per month for an unused app spends $30,000 per year before anyone notices. Across a portfolio of 15 apps where four are effectively shelfware, the unnecessary spend reaches $120,000 per year. Over a three-year contract, that represents $360,000 in waste that is entirely preventable through active app portfolio management.

Our Atlassian licensing optimisation specialists have identified an average of $85,000 to $200,000 in Marketplace app savings per engagement for enterprise Atlassian customers when conducting a comprehensive spend audit. The savings typically require no functionality sacrifice — they come entirely from removing unused apps and renegotiating active ones.

The EOL Migration Compounding Problem

The Data Center EOL timeline intersects dangerously with the Marketplace app cost problem. Organisations that delay DC-to-Cloud migration because of perceived app migration complexity are simultaneously: continuing to pay for Data Center Marketplace app licences that are depreciating toward their 2029 expiry, accumulating technical debt in DC app configurations that will require migration effort, missing the commercial window to negotiate favourable Cloud pricing during migration, and reducing the time available to address Cloud apps that have no DC equivalent.

Every quarter of delay on DC migration increases the total migration cost and reduces the commercial leverage available. Atlassian's Cloud sales teams are most motivated to offer credits and introductory pricing during the migration negotiation phase — not after migration is complete. The Atlassian Cloud contract negotiation playbook documents these migration leverage points in detail.

Real-world example: In one engagement, a financial services enterprise discovered 23 of their 61 Marketplace apps had no cloud migration path. Redress identified vendor alternatives and negotiated transition pricing, avoiding $210,000 in emergency re-implementation costs. The engagement fee was under 4% of the saving.

Governance Framework for Marketplace App Spend

Controlling Marketplace app costs requires governance, not just periodic audits. The most effective approach is a formal Marketplace app review process integrated into the annual IT planning cycle. The review should include four elements: a full installed app inventory with active user counts and last-usage dates; a per-app renewal decision (renew, remove, downgrade, or replace); a Cloud equivalency mapping for any DC apps under the EOL timeline; and an annual budget allocation that explicitly accounts for app spend as a separate line from base product subscriptions.

Organisations that treat Marketplace app spend as part of the general Atlassian line item — rather than a separately tracked and managed budget category — consistently underestimate and overrun their Atlassian cost year over year. The apps are not the problem; the absence of governance is.

Atlassian's Cloud Marketplace: What's Changed

Atlassian has made significant investments in the Cloud Marketplace ecosystem to accelerate app development and address the DC-to-Cloud transition. Cloud Marketplace apps now represent more than 90 percent of Atlassian's Marketplace app ecosystem in terms of total installs, with Data Center-specific app development effectively frozen as vendors redirect their investment to Cloud-native versions. Cloud apps benefit from Atlassian's Forge developer platform, which provides tighter integration, better security sandboxing, and more reliable performance than the older Connect framework.

For buyers, the Cloud Marketplace maturity means that the app coverage gap that previously deterred some DC customers from migrating has narrowed significantly. The proportion of DC apps without a Cloud equivalent has fallen consistently since 2023 and continues to decline as the 2029 EOL deadline approaches and vendor resources redirect toward Cloud development.

However, buyers should note that Cloud app pricing has generally increased versus DC app pricing as vendors have repriced their subscription models for the Cloud environment. Legacy DC customers may find that the Cloud equivalent of their current DC app carries a higher per-user annual cost. This price differential should be factored into the full Cloud migration cost model.

Sub-Pages in This Series

This pillar guide is supported by detailed sub-pages covering specific aspects of Atlassian Marketplace app licensing:

• Atlassian Marketplace App Licensing: How Costs Scale with Users — deep analysis of per-user tiers, band thresholds, and the real cost of user growth on Marketplace app spend.
• Top 10 Atlassian Marketplace Apps: Cost Analysis and Alternatives — independent cost analysis of the most widely deployed Marketplace apps with alternative comparisons.

Eight Priority Actions for Marketplace App Governance

1. Build a complete installed app inventory today. Pull the full list of installed Marketplace apps from your Atlassian admin console, including per-app annual cost and active user count. This inventory is the foundation for all subsequent decisions.

2. Remove unused apps before the next renewal cycle. Any app with zero active users in 90 days should be removed immediately. Configure auto-renewal off for low-value apps to force an active renewal decision at each cycle.

3. Map every DC app to its Cloud equivalent. Complete this mapping now — not at the point of migration. Apps with no Cloud equivalent require the most lead time to address and represent the highest migration risk.

4. Consolidate overlapping apps. Identify any functional categories where more than one app is installed and doing similar work. Reduce to the single best app per category and remove duplicates.

5. Negotiate app pricing at the same time as base product renewal. App vendors are more responsive to pricing requests when renewals are coordinated with the Atlassian base product renewal. Combined negotiation also gives Atlassian partners additional leverage.

6. Evaluate multi-instance pricing for Enterprise customers. If you are an Atlassian Cloud Enterprise customer with multiple instances, request a recalculation of your Marketplace app costs under multi-instance pricing. The savings can be material for organisations with duplicated users across instances.

7. Set a Marketplace app budget and enforce it. Establish an annual Marketplace app spend ceiling and require a business case approval for any new app installation. This governance control is the single most effective mechanism for preventing app sprawl.

8. Include app migration in your DC EOL project plan. App migration should not be a sub-task of the data migration workstream — it is an independent workstream with its own dependencies, risks, and resource requirements. Plan it explicitly and allocate appropriate project time.