Rate this page:
Pricing, payment, and billing is an integral part of selling your app on the Atlassian Marketplace. Learn about our revenue-sharing models, how to set or change prices for your app, what a remittance report looks like, and more.
As we continue to move towards a cloud future together, new server app sales and installs are no longer available for customers. As of Feb 15, 2023, renewals of server apps will automatically be prorated until the end of support for server on Feb 15, 2024.
Get more cloud pricing resources in the Partner Portal. You'll find webinars, calculators, and tools to help you strategize your app's revenue.
All apps integrate with an Atlassian product, and adhere to one of three payment models:
To provide a unified experience for billing and invoicing across all Atlassian cloud products, Atlassian Marketplace is migrating to a new cloud billing engine. Learn more about this change from our billing engine FAQs.
Atlassian will pay you, the publisher, the following percentages of gross revenue for Jira, Jira Service Desk, and Confluence apps:
This pricing is effective 1 April 2022 through 31 December 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] (https://www.atlassian.com/licensing/marketplace/publisheragreement), Section 4.2.
You can set the initial pricing for your app when you submit it for approval on the Marketplace. When you’d like to change prices for your app, you need to:
Your change becomes active and will reflect on the Marketplace site in 24 hours. Following this, new customers will pay updated prices. Few things to note when you change prices:
When trying to change the Payment model for an existing app, the following message is displayed in the UI:
You can't alter the Payment model for existing apps in the following scenarios:
You can change the Payment model in the following situations:
In order to change the Payment model for an existing app (except for the two situations listed above), you'll need to release a new version with this change in place.
In your add/remove licensing param from .
For details, see Adding licensing support to server apps.
Set the enableLicensing flag in the app descriptor file to to add licensing or remove the flag to set the app version to free.
For details, see Cloud app licensing
'Paid via Atlassian' app licenses have to exactly match the Atlassian host product license. For example, if a customer has a Confluence license for 500 users, they need to purchase the same license for apps. For Server and DC, 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 according to your change in product license. For Cloud apps, app tier is upgraded along with the product tier upgrade to ensure that app and product tier always remain in sync. Learn more about license upgrades
'Paid via Atlassian' app licenses for Server or Data Center come with one year of maintenance just like any other Atlassian product. Maintenance includes support and access to any version upgrades for a year from the date of purchase. When maintenance expires, customers have to renew app licenses to receive support or maintenance for the next 12-month period.
For cloud Paid via Atlassian app licenses, we offer both monthly and annual billing options to customers. Based on the customer billing cycle, the app is renewed either for one month or for a 12-month period. Please note that cloud subscriptions that renew monthly are setup for automatic renewals by default.
Our renewal system automatically notifies customers when the 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
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.
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: https://www.atlassian.com/partners.
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.
Yes, for cloud, server and Data Center apps. Check out our documentation on Sales promotions.
From August 1, 2020, each month you will receive two emails from firstname.lastname@example.org:
Note, the numbering convention for transactions in these emails is:
This report contains:
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.
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:
The following screenshot shows an example remittance report:
Note that this report is an updated version of the remittance report that was sent prior to August 1, 2020.
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:
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:
What if my remittance report doesn’t match my remittance payment? For any enquiries about a payment or report, email Accounts Payable at email@example.com.
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.
Why are there items included in the summation bill but not reflected in the Marketplace Partner Portal?
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.
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.
The Marketplace handles quotes, checks and bank transfers for paid via Atlassian apps the same way as Atlassian products.
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.
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:
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
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:
Our goal is to provide Marketplace partners and the developer community with the tools and flexibility needed to price your apps for the customers in cloud. As Atlassian continues to help the customers adopt and migrate to our cloud products, pricing and total cost of ownership will continue to be our priority and focus area. We want to ensure that the value our customers gain from Atlassian products and apps outweighs their investment.
To enable the same, we introduced key changes in the past year to help you align your pricing effectively with Atlassian’s core product pricing:
Opt-in app migration discounts (July 2020) - These migration discounts reduce the total cost of ownership gap between on-premise and cloud. Through this, the impact of pricing being a blocker to migrations will be minimized.
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.
We know how important pricing flexibility is to your business, especially the ability to deliver targeted promotions to customers in order to support specific scenarios. Marketplace partners and developers with existing cloud 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.
Rate this page: