Before purchase
- 01Listing and seller verified.
- 02Host, edition, and tier confirmed.
- 03Trial, permissions, and data examined.
- 04Contracts and support connected.
Understand the cost before leaving this site.
Many publishers delegate everything to the Marketplace. Our model first explains what shapes the decision, then points to the only official price source when a listing exists.
Source of truth
Price, tier, currency, and evaluation period will be read from the Atlassian Marketplace. No demonstration amount is presented as commercial fact.
A licensing decision in four readings.
Each area separates fact, assumption, and source so the official price remains consistent with the complete decision.
01
Eligibility
Host product, hosting model, and app actually available.
02
Tier
Number of users counted under the Marketplace rule.
03
Evaluation
Duration, conditions, and installation path from the official listing.
04
Total cost
Configuration of the app, app-data migration, governance, and support around the license.
Price is only one state in the buying lifecycle.
The most useful journeys also explain quoting, administration, and exit. These areas define what every published app must make verifiable.
Quote and activation
- 01Quote source and currency explicit.
- 02Billing administrator identified.
- 03Start and renewal dates readable.
- 04Installation on an authorized test site.
Maintenance and exit
- 01Updates and compatibility tracked.
- 02Price changes announced and versioned.
- 03Expiration and unlicensed behavior explained.
- 04Export, uninstallation, and deletion documented.
What every product page must display.
Not a table full of checkmarks: a short path to the parameters that genuinely change the bill.
- 01Publication status and available hosting models.
- 02Direct link to the app’s Marketplace calculator.
- 03Tiering rule explained in unambiguous language.
- 04External costs or services shown separately.
- 05App-data migration and termination conditions documented.
A pricing announcement is a versioned record.
- 01Publication and effective dates kept distinct.
- 02Apps, hosting models, currencies, and tiers actually concerned.
- 03Previous and new official sources, without values copied out of context.
- 04Effect on open quotes, renewals, and eligible app migrations.
- 05History retained, questions answered, and commercial channel linked.
Licensing questions, without invented answers.
The current answers define the information standard. They will be replaced or completed by the facts of each listing.
Why not show a price here?
No real product is connected to a listing yet. Once published, the official pricing source will be the Atlassian Marketplace calculator so this site never diverges from the purchase price.
Does the Jira or Confluence user count affect price?
Marketplace licenses generally follow the user tier of the host product, but the exact rule depends on the listing, hosting model, and edition. The final page will document those parameters instead of guessing them.
How should Cloud and Data Center be handled?
Each hosting model must be shown separately with its availability, license, and limitations. The current concepts represent Cloud surfaces and claim no Data Center version.
How should total cost be evaluated?
The license price is only one element. Also consider app configuration, app-data migration, governance, support, and the cost of the current process. The ROI calculator keeps every assumption editable.
What should a license include?
A published listing must name usage, updates, fixes, support, and any included services precisely. None of these are promised before the listing and corresponding terms exist.
What happens at expiration or termination?
The final answer must explain access, data, export, uninstallation, and return to a safe state. For the current concepts, those behaviors are publication requirements, not guarantees.
How should a price change be announced?
A versioned notice must state its effective date, affected apps and tiers, official source, treatment of quotes and renewals, and a question channel. No hypothetical change is presented here as decided.
Measure the process the app must improve first.
The calculator assumes no product gain. You enter the team size, current time, and value of an hour; the formula remains visible.