Last updated Jul 20, 2022

Rate this page:

Pricing, payment, and billing

What payment models does the Marketplace offer?

All apps integrate with an Atlassian product, and adhere to one of three payment models:

  • Paid via Atlassian: Customers pay a fee to use your app. Customers evaluate and purchase these apps directly from Atlassian. Paid via Atlassian apps use the Atlassian Licensing API. Atlassian provides automated sales and licensing reports to you as a paid via Atlassian app partner.
  • Paid via Vendor: Customers pay a fee to use your app. Customers purchase apps from you or your external website. You supply your own licensing and billing system.
  • Free: Customers pay nothing to use your app. Free apps generally use open-source licensing.

Note that Paid via Atlassian is not available for Bitbucket Cloud apps. Request Paid via Vendor for Bitbucket Cloud apps by raising a ticket in the Marketplace Support service desk.

How does revenue sharing work for paid via Atlassian apps?

Atlassian will pay you, the publisher, the following percentages of gross revenue for Jira, Jira Service Desk, and Confluence apps:

  • 85% for cloud apps
  • 75% for Data Center apps
  • 75% for server apps

This pricing is effective 1 April 2022 through 31 March 2024.

For all new Forge apps listed on Atlassian Marketplace after 1 April 2022, Atlassian will pay you, the publisher, 95% of the gross revenue of all sales made within first year. After the first year, the revenue share will return to whatever the standard rate is for cloud apps at that time. This rate of 95% is a temporary incentive and will be reviewed periodically. This promotion excludes new apps built on Connect as well as former Connect apps that are rebuilt as Forge apps or migrated from Connect to Forge. In order to be eligible, Forge apps must use Atlassian-hosted storage and compute.

For Atlassian products not stated above, you will receive a revenue share of 75% across all hosting types. For more information, see the [Atlassian Marketplace Partner Agreement] (, Section 4.2.

How do I set or change prices for my app?

You determine initial pricing for your app when you submit it for approval on the Marketplace. When you'd like to change prices for your app, here's how:

  1. Log in to with your partner account.
  2. Click Manage vendor account from the profile menu in the upper right.
  3. Click your app's name from the list.
  4. Click on the Pricing tab, then choose Cloud or Server. If your app is only compatible with one delivery model (Server or Cloud), you'll only see one option displayed.
  5. Make your changes accordingly.
  6. Click Save pricing.

Your change is active and displayed on the Marketplace site in 24 hours. After this, new customers pay your updated prices right away. Here are some important things to know when you change prices:

  • You can change prices every 30 days.
  • We highly recommend you communicate price changes with customers.
  • Existing customers get a 60-day price override so they can pay the lower price when they renew or purchase. They receive the renewal price override as long as they're on the same product edition and the quote is created before the renewal override date (60 days from the price change).
  • Existing evaluators in cloud can also pay the lower price if purchased before the evaluation expires.  
  • Existing evaluators in server/Data Center will receive the new price unless they have a a pre-existing quote.

How are renewal, upgrade and academic prices determined?

Renewal pricing is 50% of the new purchase price for server apps, and 100% of the new purchase price for cloud and Data Center apps.

Upgrade pricing is calculated as follows: (50% of new tier price) + (50% of difference between new tier price and old tier price).

Academic pricing (available for server apps only) is automatically set to 50% of the new purchase price.

When do I get paid for my paid via Atlassian app sales?

We owe you remittance for your sales after you reach $500 USD in profit. We pay you within 30 days after the end of the month in which you accrue $500+ USD in profit.

This means that we pay you within a minimum of 30 days from the time of sale, and no more than 60 days after. We designed this time frame around customer support needs, refunds, and chargebacks (payment disputes). We offer the same 30-day refund period for your apps as we do for other Atlassian products. After 30 days, we don't grant refund requests to customers.

Atlassian may remit funds early at our discretion.

How do Atlassian solution partner resellers work?

Employing Atlassian's worldwide network of resellers gives you a sales multiplier. When you opt into this program, Atlassian Solution Partners can purchase your app for their clients at a discount from the list price. For more information, see the Atlassian Marketplace Partner Agreement, Section 4.9.

You can opt in or out of the program on a per-listing basis, and when you edit pricing details for your app. You can learn about Atlassian Solution Partners here:

What about other resellers?

Paid via Atlassian apps are restricted from offering discounts to organizations that aren't part of the Atlassian Solution Partners program. If you'd like to sell your app at discount to individual customers, you can create a sales promotion.

Can I offer my app at a discount or promotion?

Yes, for cloud, server and Data Center apps. Check out our documentation on Sales promotions.

How does the remittance, invoice, and payment process work?

From August 1, 2020, each month you will receive two emails from

For any enquiries about a payment or report, email Accounts Payable at Also, see Frequently asked questions below.

Note, the numbering convention for transactions in these emails is:

  • Prefix MPV: Summarized sales
  • Prefix MPVCR: Summarized refunds
  • Invoice Number - “AT”: ELA bill
  • Invoice Number - “AT”+suffix A: Concession bill
  • Invoice Number - “ATL”+suffix A: 10k bill

Remittance report

This report contains:

  • Summarized bill based on accumulated amount of the invoices (sales) for the month (MPV).
  • Summarized bill credit based on accumulated credit memos (refunds) for the month (MPVCR).

The following appear as separate line items in the remittance report and are not reflected in the Marketplace Portal:

  • ELA (bills): This is the customer’s redemption of ELA credits that were previously prepaid. This is denoted by the prefix “AT”.

  • Concession (bills): This occurs when Atlassian gives a full discount to the customer, but maintains and pays the liability to the partner.

    • Community licenses
    • Free licenses
    • Customer concessions

Items that are included in the summarized bill (total sales for the month) on the remittance report, but are not reflected in the Marketplace Portal:

  • 10K Licenses
  • Adjustments - For example, a canceled refund.

The following screenshot shows an example remittance report: example remittance report

Note that this report is an updated version of the remittance report that was sent prior to August 1, 2020.

CSV of the summarized bill and bill credits

This CSV file contains the details of the summarized bill and bill credits. Note that this CSV was not sent prior to August 1, 2020.

Each record in the CSV includes the following information:

  • Sale Date
  • Order ID
  • License ID (Host SEN)
  • Customer Name
  • App Name
  • Sale Price
  • Net Revenue
  • Reference # (Remittance report reference #)

Concessions and ELA bills will not show up in the .CSV, as this is a $0 transaction to the customer.

Be aware that the expected date of the remittance report and the payment of a given month is between the 17th-20th of the payment month.

The following screenshot shows an example CSV: example bill and bill credits CSV

Frequently asked questions

  1. What if my remittance report doesn’t match my remittance payment? For any enquiries about a payment or report, email Accounts Payable at

  2. When can we expect to see 10k license bills on the remittance report? We plan to introduce higher user tiers for marketplace apps before the end of CY 2020, which should eliminate this problem.

  3. Why are there items included in the summation bill but not reflected in the Marketplace Partner Portal?

    • Concessions: This occurs when Atlassian gives full discount ($0 invoices) to the customer but maintain and pays the liability to the partner. This is denoted on your remittance report with the suffix A for the manual concession bills. The original invoice number is “AT+Bill Number-suffix A.”
    • Canceled refunds/adjustments: These changes would have been made after the information is synced in the Marketplace Portal for a specific time period.

Are Marketplace apps available to purchase worldwide?

We sell to customers everywhere, except for trade-embargoed countries subject to United States export restrictions. We help partner collect any taxes applicable for the customer's locale.

Can customers pay for apps with purchase orders (POs)?

Unfortunately customers cannot pay for apps with POs. Like Atlassian products, buying apps through a purchase order (PO) is not supported. Customers can reference purchase orders with their invoice. Find out more.

What about quotes, checks, and bank transfers?

The Marketplace handles quotes, checks and bank transfers for paid via Atlassian apps the same way as Atlassian products.

What if customers request a refund?

Atlassian offers full refunds within the first 30 days from a purchase, no questions asked.

Refund requests that fall between 31-60 days from a purchase will be at the discretion of Atlassian, unless the per-partner refund total exceeds $1,500. In that case, Atlassian will seek approval from the partner prior to issuing a refund.

In the event of upgrade requests between 31-90 days post-purchase, Atlassian will opt to reallocate funds for the remaining maintenance toward the higher-tiered license. This allows us to appease the customer while increasing revenue to our partners. Find out more.

How do license upgrades work?

Paid via Atlassian app licenses need to match the Atlassian host product license exactly. For example, if a user has a Confluence license for 500 users, they need to purchase the same license for apps. If customers upgrade their product license but not their app license, then we alert the product administrator to upgrade the app license for your app. Learn more about license upgrades.

How do renewals work?

Paid via Atlassian app licenses, just like Atlassian products, come with one year of maintenance. Maintenance includes support and access to any version upgrades for a year from date of purchase. When maintenance expires, customers need to renew app licenses to receive support or maintenance for the next 12 month period.

Our renewal system automatically notifies customers when app licenses are about to expire. A customer can renew in advance of expiration to ensure uninterrupted access to support and software updates. Learn more about maintenance renewals.

How do I set prices for cloud apps?

Use the “Price Guidance“ feature to help you compare the tier price for your apps against the same tier price for server and average price of all Data Center apps. Below are the two guidance values that are available via the Marketplace app pricing tool: price guidance selection modal

Cloud - Server price ratio guidance

This guidance value is a ratio of monthly per user price of the cloud version and the approximated monthly per user price of the server version for your app for each price tier. Since this guidance value is the ratio between your app price for cloud and server version, this ratio will keep changing as you update the price for your cloud app tiers. This guidance value will enable you to more readily compare the price differences between your server and cloud app deployments, and price your apps accordingly.

Calculating Cloud - Server price ratio guidance

  • Average monthly price for each tier: Divide each tier's average annual price by 10, since we charge 10 times monthly price as annual price for cloud apps.
  • Monthly average per user price for each tier: Divide the total monthly price of the tier with the number of users in the current tier. Note, given the tier structure for server pricing, we use the price of unlimited tiers to calculate the per user price for 10,000 users and above tiers.
  • Cloud-Server price guidance ratio: Divide the cloud app price by the server app price for the same tier. Refer to the Price guidance column in the sample screenshot below: cloud server ratio example

Normalized price ratio guidance:

The normalized price guidance is the approximate per user average monthly price of all Data Center apps calculated for the maximum number of users in each tier, which is normalized with reference to the price of the [11-100] tier for your app. Since this normalization is done against the price of the [11-100] tier, this guidance value will keep changing as you change the price for this tier. This guidance value signals how the app's price can be discounted across tiers for all of the Marketplace by setting lower per user price for higher tiers. The steps below show how we calculate the normalized price guidance value:

Calculating Normalized Price Ratio Guidance:

  • Average annual price across all Data Center apps: Take the average price of all apps for the number of users equal to the max user count for each cloud tier. i.e. To calculate the average annual price for the [101-250] tier, we took the average of all Data Center app prices for 250 users.
  • Average monthly price for each tier: Divide each tier's average annual price by 10, since we charge 10 times the monthly price as the annual price for cloud apps.
  • Monthly per user price (PUP) for each tier: Subtract the total monthly price of the previous lower tier from the tier's price. Divide the remaining value with the difference in the number of users between the current tier and the previous lower tier.
  • Normalized average monthly per user price for all DC apps: Set the guidance per unit price for the [1-100] tier equal to the per unit price of the same tier for your app. Normalize the price for all the other tiers on the basis of this per user price. Refer to the Price guidance column in sample screenshot below: normalized price example


More tools and flexibility to price your apps for cloud customers

Our goal is to help provide you, our Marketplace Partners and developer community, with the tools and flexibility you need to price apps for your customers in cloud. As Atlassian continues to help our customers adopt and migrate to our cloud products, pricing and total cost of ownership will continue to be a priority and focus area, to ensure our customers’ value gained from Atlassian products and apps outweighs their investment.

To that effect, we want to remind you of a number of key changes we introduced in the past year to help you better align your pricing to Atlassian’s core product pricing:

  1. Opt-in app migration discounts (July 2020) - These migration discounts reduce the total cost of ownership gap between on-premise and cloud, and minimize price as a blocker to migrations.

  2. Opt-in dual licensing (September 2020) - To help customers save on migration costs, customers can take advantage of free license extensions for up to one year.

  3. Additional per user pricing tiers for cloud apps (September 2020) - As we’ve increased the user tiers available for our cloud products, we’ve added new user tiers for apps to align to those tiers.

We know how important pricing flexibility is to your business, especially the ability to deliver targeted promotions to customers to support specific scenarios. Marketplace Partners and developers with existing server or Data Center apps may already be familiar with promo codes, which have been available and in use for some time. These promo codes are also widely used by Atlassian’s field sales and advocate teams to reduce friction in app adoption for larger customers. We’ve been hard at work rebuilding this capability for cloud licensing and billing based on your input and feedback (as we last shared in January 2021).

How and when to use cloud promo codes

Cloud promo codes are intended for targeted use, and not to encourage broad discount-seeking behavior with customers. Although you are welcome to create codes for customers that are discoverable via your Marketplace listing, we expect that most partners and developers will prefer to use them in one-to-few or one-to-one scenarios to incentivize a specific customer to purchase.

One example is offering promo codes to customers migrating to cloud, similar to Cloud Migration Trials which provide customers up to 12 months of cloud for free to help them avoid double-paying for products during the migration.

We recommend taking a holistic approach to app pricing for cloud that takes into account all of the tools listed above. Where possible, we suggest opting in to migration discounts (loyalty and extended trial licensing), and adjusting higher pricing tiers to offer progressive discounting.

Rate this page: