Stores & marketplaces

Atlassian Marketplace

Teams buy add-ons for Jira and Confluence here.

Visit marketplace.atlassian.com
Cost
Revenue share

Free to list. Atlassian takes a share of paid app sales. Check current terms.

Verdict
slow burn

Slow burn: teams buy Jira and Confluence add-ons here.

Difficulty
Hard

Gatekept or reviewed, or needs an existing audience or reviews first.

Effort
High

About 10 or more hours a month, mostly during launches or a regular posting habit.

First result
1 to 3 months

A rough range for one person working on it part-time.

Payoff
Compounds

keeps growing while you keep at it.

Best for

Tools that extend Jira or Confluence.

Not for

Products outside the Atlassian stack.

Pros

  • Teams buy add-ons here
  • Clear buyer intent

Cons

  • Heavy build and review
  • Only for Jira and Confluence

The full guide

Last verified 2026-10-30

Links checked 2026-10-30 · All links answer

01What it is and who is there

The Atlassian Marketplace sells apps that extend Jira, Confluence and other Atlassian products. Teams and admins search it for add-ons that fill gaps, and many buy through their existing Atlassian billing. Buyer intent is high, but building and listing an app is serious work.

02Cost and what you actually pay for

Atlassian sets the terms for paid apps sold through the marketplace, including its share of revenue. Check Atlassian's current marketplace partner terms before pricing.

03Is it right for you?

It fits tools that extend Jira or Confluence, such as reporting, time tracking or workflow apps. It fits poorly for products outside the Atlassian stack. Expect a large build and review effort.

04Before you start

  • An Atlassian developer account.
  • Read the marketplace partner agreement and app approval guidelines.
  • Decide on the platform (for example Forge or Connect) based on Atlassian's current guidance.
  • Prepare documentation, a support channel and a privacy policy.

05Step-by-step: how to distribute here

  1. Build the app and test it on a development site.
  2. Check it against Atlassian's approval guidelines.
  3. Submit the listing with screenshots, docs and pricing.
  4. Respond to review feedback.
  5. Offer a free trial through the marketplace, if supported.
  6. Support customers quickly; reviews influence ranking.

06What to post or submit

Tagline:

[Product] for [Jira/Confluence]: [result for teams]

07Common mistakes and do-nots

  • Do not ship without documentation.
  • Do not ignore security requirements.
  • Do not neglect support tickets.

08How to measure it

  • Track evaluations, installs and paid conversions in the vendor dashboard.
  • Track review ratings.
  • A realistic test: three months after approval.

09Time budget

  • Before: 40 or more hours to build and list.
  • Ongoing: 5 to 10 hours a month.

10Pair it with

11Sources

Sources