Atlassian Marketplace App Licensing Explained: Tier Matching and Real Costs
This page explains how Atlassian Marketplace app licensing actually works — tier matching, annual billing, what changes on a Cloud migration, and what the Data Center end-of-life timeline does to your apps. It covers the mechanics first, then the specific vendors most ReleaseTEAM clients run.
The short answer: paid app licences must match your host product tier exactly — you cannot licence 20 of your 500 Jira users. Cloud annual app billing is ten times the monthly rate, so annual carries an effective two months free. And two dates matter more than anything else on this page: Marketplace app purchases for Data Center end 30 March 2028, and Data Center apps expire and go read-only on 28 March 2029.
Tier matching: the rule that drives everything
Atlassian requires that paid app licences match the host product licence tier. Its developer documentation puts it as “paid via Atlassian app licenses have to exactly match the Atlassian host app license”; its support documentation says the app functions only if its licence “matches or exceeds” the host tier. Either way, the buyer-facing rule is the same: you cannot licence below your host tier, and there are no partial seats.
The clearest worked example is a test management or Git integration app. A 2,000-seat Jira with 20 QA engineers pays the 2,000-user tier for its test management app. The app is used by 1% of the licensed population and billed against 100% of it.
What happens when you upgrade the host product
Cloud app tiers sync automatically with Atlassian product tier upgrades. Every paid app repositions to the new tier — there is no per-app opt-out short of uninstalling. Re-billing lands from the start of the next billing cycle rather than instantly. For mid-term Cloud and Data Center tier upgrades, the default is proration through the current term end date.
Two multi-product nuances people miss. If you run both Jira and Jira Service Management, you must buy the app licence matching the highest user tier. And crossing a single tier threshold can step total app spend up noticeably in one move — while dropping users back below the threshold does not reliably drop you back down, which makes tier boundaries closer to a one-way door in practice.
Annual billing is ten times monthly
This is stated directly in Atlassian’s partner-facing pricing documentation, as an instruction to vendors converting their price lists: Atlassian charges ten times the monthly price as the annual price for Cloud apps. So annual app billing carries an effective two-months-free discount, Marketplace-wide, not as a per-vendor promotion.
But the billing cycle of the app must match the parent product. You cannot run Jira monthly and the app annually. Capturing the annual app discount means moving the host product to annual too — which is a bigger decision, because Atlassian annual billing also locks a fixed user tier you cannot change mid-term.
Why apps cost more after a Cloud migration
The structural difference is real. On Data Center, apps are licensed to a user tier as an annual term licence. On Cloud, they are per-user subscriptions billed alongside the core product, and many cost more per user than their Data Center equivalent.
We could not find a citable figure for the Data Center to Cloud app uplift specifically, and we will not publish one we cannot stand behind. What is better evidenced is the proportion: at enterprise scale, Marketplace apps commonly add 35–75% on top of base Jira licensing. If your migration business case models product licences only, it is missing a third to three quarters of the real number.
What the Data Center end of life does to your apps
| Date | What happens |
|---|---|
| 16 December 2025 | New Data Center apps can no longer be submitted to the Marketplace |
| 30 March 2026 | New customers can no longer buy Data Center subscriptions or new Marketplace DC apps |
| 30 March 2028 | Last date for existing customers to buy new DC licences, Marketplace apps, or licence expansions. Renewals only after this |
| 28 March 2029 | Data Center end of life. Subscriptions and any associated Marketplace apps expire, making products and apps read-only |
App licences die with the host licence, on the same date, automatically. There is no separate grace period for apps.
The interaction nobody spells out. Between March 2028 and March 2029 you cannot add a single app or a single user — only renew what you already hold. But tier matching still applies. So if your Data Center host tier rises in that window, you may be unable to buy the matching app tier, and could be stranded on an app you still depend on. If you are planning to stay on Data Center to 2029, model your user growth against that 2028 cutoff now.
Two exceptions worth knowing: Bitbucket Data Center apps are exempt from the end-of-life timeline and will continue to be available and supported, and extended maintenance beyond March 2029 exists by individually negotiated agreement for organisations with unique constraints.
Cloud Fortified is being retired
This is the most time-sensitive fact on the page, and it contradicts nearly every partner article still circulating on the topic. Atlassian stopped accepting new Cloud Fortified submissions from 1 September 2026, and the programme retires on 31 December 2026. It is being replaced by a new Atlassian Enterprise Certified programme. Atlassian’s own marketing pages still describe Cloud Fortified as active, so the badge is a depreciating signal rather than a current one.
For context on what the badges mean while they last: Cloud Fortified covered bug bounty participation, published SLOs, 24-hour support response on critical issues and a security review. Runs on Atlassian is different — it marks Forge apps hosted entirely on Atlassian infrastructure with data stored in Atlassian, giving automatic data-residency compliance, and it is applied automatically to eligible apps rather than applied for. Neither badge changes what a buyer pays.
Atlassian is also adding Marketplace filters for SOC 2, ISO 27001, penetration testing, bug bounty and partner trust centres — broadening trust signals beyond the two badges.
Free tiers, discounts and trials
“Apps are free under 10 users” is not a rule. Atlassian gave vendors the option of a $0 price point at the 1–10 user tier. Many large vendors took it up — Gliffy and BigPicture among them — and others did not. Check the individual listing rather than assuming.
- Trials: any Marketplace app, Cloud or Data Center, is free for 30 days, initiated by an admin. On monthly Cloud billing the app cost is automatically added to your next bill unless you manually deactivate it — a genuine bill-shock trap. On annual, a manual quote and purchase is required or the app simply stops working.
- Price protection quirk: if a vendor price rise is pending, buying before your trial expires locks the lower price.
- Academic: 50% off most apps, 75% off Confluence apps. Classroom: 75% off most apps. Open source: 100% off select Standard tiers. Nonprofits: no-cost Social Impact Licenses by application.
- Refunds: 30 days, no questions asked. Beyond that, vendor discretion.
- Delisted apps: Atlassian archives out-of-date apps, removing them from search. Existing licensees keep working and can still download — but new licences are unavailable. Combined with tier matching, that means a host tier increase on a delisted app can leave you unable to buy the matching tier.
Vendor-specific notes
| Vendor / app | Licensing model and the quirk to know |
|---|---|
| Appfire | Per-app pricing; we found no portfolio or bundle discount. Worth knowing that Appfire is a roll-up — BigPicture and others are Appfire-owned, so spreading across “different vendors” in that portfolio does not diversify commercial risk |
| Tempo | Timesheets, Capacity Planner, Financial Manager and Structure PPM are bought independently, not as a suite, though cross-product features unlock between them. “Cost Tracker” is the legacy name for Financial Manager. Tempo restates the tier rule itself: your Tempo licence size must match your Jira licence size |
| Xray | Standard and Advanced editions, changeable any time. The clearest illustration of tier matching: licensed by total Jira user count, not QA headcount |
| Gliffy | Free up to 10 users with no time limit. A Zero Egress variant targets Atlassian Government Cloud. On non-renewal, Cloud diagrams become read-only; Data Center keeps functioning but loses support |
| Lucid | The structural exception. The Marketplace connectors are free apps; the value sits in a separate paid Lucid subscription. So Lucid sits entirely outside Atlassian tier matching, co-terming, refunds and academic discounts — a separate vendor contract with separate seat counts. That cuts both ways |
| BigPicture | Free 1–10 user tier. Appfire-owned (formerly SoftwarePlant). A BigPicture Enterprise tier exists; edition pricing is not broken out publicly |
| Revyz | Per user, auto-matched to your Atlassian licence count. Unusually, pricing is cumulative across bands rather than one flat rate at the top band |
| Rewind | Per user, per product, volume-tiered, billed through the Marketplace. Standard and Advanced plans; custom terms only above a $3,000 monthly commitment |
| GitProtect / Xopero | One company, not two — GitProtect is the product, Xopero Software is the Marketplace vendor of record. Billing increments in 10-user blocks, a different granularity from Atlassian’s tier bands. Unlimited cloud storage included |
| Git Integration for Jira | Per Jira user seat, no repository-count component and no free tier. Cost scales with total Jira seats even though only developers connect repositories |
For the backup apps specifically, the landscape changed. Atlassian now sells a first-party Backup and Restore product — native, not a Marketplace app, annual, priced on user count, and available only on Premium or Enterprise plans billed annually. It restores everything or nothing, retains for 30 days, and does not cover Marketplace app data. That does not make the third-party tools redundant, but it does change the starting question.
Buying or renewing? ReleaseTEAM sells and renews Atlassian licenses and add-ons on one bill; see buy and renew Atlassian licenses.
Frequently asked questions
Can we license an app for only the people who use it?
No. Paid app licences must match the host product tier, even if only a handful of users need the app. This is the single most expensive characteristic of Marketplace licensing and there is no workaround within the rules.
Do our apps upgrade automatically if we upgrade Jira?
Yes. Cloud app tiers sync automatically with host product tier upgrades, and the new pricing lands from the next billing cycle. Budget for it as part of any host upgrade rather than treating it as a separate decision.
Is annual app billing really two months free?
Effectively, yes — Atlassian charges ten times the monthly rate as the annual price. The constraint is that the app billing cycle must match the parent product’s, so you cannot take the app discount without moving the host product to annual.
What happens to our Data Center apps in 2029?
They expire with the host licence on 28 March 2029 and go read-only. More urgently, you cannot buy new apps or licence expansions after 30 March 2028 — so plan user growth against that date, not the 2029 one.
Is a Cloud Fortified app still a meaningful signal?
Decreasingly. The programme stopped accepting submissions in September 2026 and retires at the end of the year, replaced by Atlassian Enterprise Certified. Treat the badge as a legacy marker and look at the new certification and the SOC 2 / ISO 27001 filters instead.
Are apps free under 10 users?
Many are, but it is a vendor option rather than an Atlassian rule. Check each listing.
What happens if an app we depend on gets delisted?
Existing licensees keep working and can still download it, but no new licences are available. The danger is tier matching — if your host tier rises, you may be unable to buy the matching app tier for a delisted app.
Licensing mechanics verified 19 September 2026 against Atlassian’s developer documentation, purchasing and licensing pages, Marketplace changelog and Data Center end-of-life notices, plus each vendor’s own published pricing. Several vendor figures were stale or contradictory at the time of checking — confirm current pricing on the Marketplace listing before budgeting.
Apps are usually the part of the migration nobody costed
We model Marketplace app spend across Data Center and Cloud, work out which apps survive a migration and which get replaced by native capability, and flag where the March 2028 expansion cutoff will bite.