PPlatformAppStores

Atlassian Marketplace

Developer Tools

Atlassian Corporation · Developer tools & code hosting

Best for: Teams building enterprise integrations and add-ons for Jira, Confluence, and Bitbucket Cloud.

Overview

Atlassian Marketplace connects developers with Jira and Confluence users. Apps can be built with Forge (Atlassian's serverless runtime) or Connect (external-hosted). Forge simplifies hosting and security; Connect offers deeper UI extensibility and custom backends.

How to build & ship

  1. 1Register as an Atlassian Marketplace vendor and set up a developer account
  2. 2Build a Forge app (recommended) or a Connect app against Jira/Confluence/Bitbucket REST APIs
  3. 3Develop and test with the Forge CLI (forge deploy) or your Connect descriptor and tunnel
  4. 4Create a Marketplace listing with app details, pricing, and privacy/security info
  5. 5Submit for Atlassian approval, addressing the app approval and security guidelines
  6. 6Optionally pursue the Cloud Fortified badge for enhanced reliability/security signals

Key APIs & SDKs

Forge platform (CLI, UI Kit, Custom UI, FaaS runtime)
Connect framework (app descriptor, iframes, JWT auth)
Jira/Confluence Cloud REST APIs
Marketplace REST API (licensing, versions, listings)
Forge storage and remote/async events APIs

Integration types

Embedded app
Connector
Workflow action

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key, JWT
  • Security review: Required
  • Forge apps run in Atlassian-managed sandboxes; Connect apps require data-residency and security declarations.
  • New apps and paid/data-handling apps go through Atlassian's manual approval against app approval and security guidelines before listing, typically days to a few weeks depending on complexity.
  • Forge and Connect rate limits differ; Connect relies on product API quotas.
Auth docs Store policies

Monetization

Paid app
Usage-based
Onboarding
$0
Commission
15% on paid app sales
Merchant of Record
Atlassian acts as MoR for Marketplace transactions

Pros & cons for builders

Pros

  • Access to a large enterprise customer base already inside Jira/Confluence
  • Atlassian handles licensing, billing, and payouts for paid apps
  • Forge provides hosted infrastructure, auth, and storage out of the box
  • Cloud Fortified program offers a trust/quality differentiator

Cons

  • Approval and security review can be slow and prescriptive
  • Forge platform constraints and quotas limit some architectures
  • Ongoing compliance obligations (e.g., data residency, security) for listed apps

Frequently asked questions

How do I get my app approved on Atlassian Marketplace?

New apps and paid/data-handling apps go through Atlassian's manual approval against app approval and security guidelines before listing, typically days to a few weeks depending on complexity.

What authentication does Atlassian Marketplace use?

Atlassian Marketplace apps primarily authenticate with OAuth 2.0, also supporting API key, JWT.

How is Atlassian Marketplace monetized?

Atlassian Marketplace supports Paid app, Usage-based. Typical commission: 15% on paid app sales. Onboarding fee: $0.

Is a security review required to list on Atlassian Marketplace?

Yes, Atlassian Marketplace requires a formal security or listing review before apps go live. Forge apps run in Atlassian-managed sandboxes; Connect apps require data-residency and security declarations.