Browse, try, and buy add-ons for Atlassian products

Overview

The Atlassian Marketplace is where you can discover and try add-ons to extend your Atlassian products.

Use the FAQ below to find answers to common questions. If you don't see what you're looking for, feel free to contact our sales team.

General Marketplace Questions

1. What's the Atlassian Marketplace?

The Atlassian Marketplace is a platform for Atlassian customers to discover, try, and buy add-ons for Atlassian applications. You can use add-ons to customize and extend your Atlassian application. The Marketplace offers add-ons developed by both Atlassian and third-party developers.

2. What's an add-on?

Add-ons are small pieces of code that you (or your administrator) can install into your Atlassian application to enhance or change its functionality. Add-ons can also be remotely contained web applications that integrate into Atlassian Cloud instances. You can enable, disable, install, and uninstall add-ons anytime from the administration pages of your Atlassian product.

Add-ons change the way your Atlassian application behaves. Even though add-ons are designed to enhance your product, there can be unintended effects. When you use or install add-ons, you do so at your own risk. Third-party add-ons aren't supported by Atlassian.

The Marketplace sells add-ons written by both Atlassian and third-party developers. You can even write one yourself.

3. Which add-ons are available for Atlassian Cloud?

A full list of add-ons that are available for your Cloud applications is available here. New add-ons for Cloud applications are added constantly, so it's worth checking back.

4. How are add-ons reviewed?

Atlassian checks entries in the Atlassian Marketplace to ensure that add-on information is as complete as possible. However, we don't actively monitor or guarantee any code posted in this space. If you find dangerous or malicious code posted here, contact us immediately so we can take action.

5. How do I get an account to try or buy an add-on?

Log in to Atlassian Marketplace with your Atlassian account. If you don't have an Atlassian account, you can create one and then log in to the Marketplace.

6. Can I trust third-party add-ons?

The Marketplace gives you visibility to see if an add-on is reliable. We provide resources like the following so you can make informed decisions about the add-ons you use.

From the add-on details page:

  • Look for the Atlassian Verified badge, which indicates that the add-on vendor meets Atlassian benchmarks for add-on traction, timely support and vendor reliability.
  • Read reviews and ratings on the Marketplace.
  • Check the number of active installations to assess popularity.
  • From the Support tab, look for availability of a public issue tracker or support resources.
  • See if compatibility is kept up-to-date from the Versions tab.
  • Review screen shots and videos from the Overview tab.
  • See if the developer provides an end-user license agreement (EULA).

You can also ask a question in Atlassian Answers.

7. What's Atlassian Verified?

The Atlassian Verified program is designed to help you try and buy add-ons with confidence. Verified vendors display the Atlassian Verified badge, which means the vendor has met Atlassian benchmarks for add-on traction, timely support and vendor reliability. Atlassian measures these benchmarks for paid-via-Atlassian add-ons only. Here's what you can expect when you buy an add-on from a Verified vendor:

  • Add-on traction: We measure how many active customer instances have vendor add-ons installed. Add-ons must be installed in a minimum number of active applications for a vendor to be eligible for Verified status.
  • Timely support: Verified vendors adhere to service level agreements (SLAs), and provide support websites. Support is offered at least 8 hours a day, 5 days a week.
  • Vendor reliability: These vendors are routinely vetted by Atlassian to ensure they offer great customer experiences.

For more details on the Verified program, see the vendor-facing requirements for Atlassian Verified.

If you purchase a paid-via-Atlassian add-on from a Verified vendor and aren't satisfied with your experience, raise an issue with our Marketplace team.

Check out add-ons from Atlassian Verified vendors.

8. What is the Cloud Security Program?

The Cloud Security Program is a collaboration between Atlassian and add-on vendors to increase security awareness and improve security practices. A vendor may apply to the program via an annual self-assessment that addresses the following: 

  • Data security
  • Sensitive Data Handling
  • Backups and Disaster Recovery

The self-assessment answers are reviewed by Atlassian staff. The self-assessment encourages vendors to consider security carefully and allows Atlassian to make suggestions towards better security. It works on an honor system. We advise that you take any additional necessary steps to ensure the vendor and add-on meets your company'€™s security requirements. See details about the Cloud Security Program.

9. Are add-ons supported?

It depends on the add-on. We make this information available on every add-on details page in the Marketplace. From the details page, you can see if an add-on is supported by Atlassian, supported by the vendor, unsupported, or Atlassian Verified. Support options are listed on the Support tab for any add-on details page.

10. Can add-ons make my application slower?

Sometimes, yes. It's possible for an add-on to cause performance problems. For this reason, we recommend learning all you can about an add-on.

You can evaluate an add-on in a staging environment before deploying it in production. You can also use the customer reviews to learn what other users have to say. Visit the website of the add-on vendor and review any support materials they have.

If you suspect an add-on is causing a problem in your Atlassian application, try disabling the add-on to see if the problem goes away.

11. Why would I disable an add-on? How do I disable one?

When you install an add-on, it has full access to your application and its data. Sometimes add-ons can have unintended side-effects. They might slow things down, or you might discover a problem. If so, it's easy to disable or uninstall an add-on.

For information on managing add-ons, see our Universal Plugin Manager (UPM) documentation.

12. What's add-on archiving?

To focus on current, relevant add-ons, the Atlassian Marketplace regularly archives add-ons that are out-of-date or, for any other reason, no longer relevant on the Marketplace.

Archiving prevents the add-ons from appearing in search results or in add-on browsing lists. The Marketplace archives add-ons automatically if the time since the end-of-life of the latest version of the Atlassian application it supports is greater than one year.

If you already have a license for an archived add-on, you can still download the add-on from its Marketplace listing and use it. However, new licenses for the add-on are not available. Contact the vendor to inquire about an updated version of the add-on.

13. Which countries can purchase add-ons from the Marketplace?

The Atlassian Marketplace will help vendors collect the appropriate sales and VAT taxes. We sell to customers everywhere, with the following exceptions:

  • Trade embargoed countries subject to United States export restrictions

 

14. Which countries have payment type restrictions when purchasing add-ons from the marketplace?

At this time there are restrictions for customers located in India, as Marketplace add-ons can only be purchased by credit card. 

If payment by credit card is not an option, we have a list of Atlassian Experts in the aproved region that you can contact directly to assist in providing atlernative payment options. 

Licensing and Pricing

1. Which license do I choose when purchasing an add-on?

Purchase the license tier that matches the number of users you have licensed for your host application. For example, if you have a 25-user Confluence license, purchase the Confluence add-on at the 25-user tier. The add-on will only function if its license matches or exceeds the tier of the host application – even if only some of your licensed users need to use the add-on.

For JIRA, you must purchase the add-on license that matches the highest JIRA application tier. For example, if you have a 500-User JIRA Software license, and a 20-Agent JIRA ServiceDesk license, your JIRA add-ons must be at the 500-User level. 

If you own a legacy JIRA Unlimited (100+ users) or Confluence Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

Learn more about legacy pricing tiers

2. Do you have Data Center pricing?

JIRA Software and Confluence Data Center are licensed starting at 500 users. To match your Data Center application license, purchase add-on licenses to match or exceed the number of users you have for the Server application. You don't need to purchase a license for each node of your application, just the total number of users. This doesn't impact add-on functionality or compatibility, the number of users just need to match your Data Center license. 

A 10,000+ user add-on license for your Server application will serve any number of Data Center 1000-user licenses. You can purchase licenses per 2000; 10,000; and 10,000+ users to fit your Data Center license.

For example, if you have a JIRA Software Data Center license for 2000 users, purchase one 2000 user license for JIRA Software Server. If you have 3000 users for your Data Center instance, the next available add-on tier is 10,000 users.

3. Do I need an add-on license for each instance of my Atlassian products?

Yep. Add-ons are licensed for single instances. This means if you have separately licensed instances, each instance requires its own add-on licenses as well. 

If you have a Data Center application running on multiple servers, we count this as one instance.

If you have separate developer instances, you can use developer licenses for your add-ons for development and testing. See how to get a developer license here.

4. Where do I get license keys for my new add-on?

You receive your license keys and applicable source code after your payment is successfully received and processed. We send you an email that includes instructions how to access the license key.

You can also log into My Atlassian to retrieve your license keys. Just like your application purchases, add-ons you purchase in the Marketplace are reflected in your My Atlassian account.

5. Am I eligible for academic pricing?

Academic pricing is available to qualified academic institutions for paid-via-Atlassian add-ons. Academic licenses are not eligible for the volume renewal discount.

The following organizations are eligible for an Atlassian Academic License:

  • Educational institutions: Public or private K-12, vocational schools, correspondence schools, junior colleges, colleges, universities, or scientific or technical schools that are accredited by a national accrediting agency.
  • Administrative offices & boards of education: Provincial, district, regional, national and state administrative offices and authorities of the Educational Institutions defined above.
  • Public libraries
  • Home-school programs
  • Research institutes that are affiliated with an accredited university.
  • Teaching hospitals that are affiliated with an accredited university.
  • Training and teaching organizations that are accredited by a statutory government qualifications body.

Proof of accreditation or affiliation may be required when ordering an Atlassian Academic License for your add-on. Academic pricing is always half the cost of commercial pricing. In the same manner, academic renewal pricing is always half of commercial renewal pricing.

6. How are license upgrade prices calculated?

You can upgrade licenses at any time from a lower tier to a higher tier. Upgrades for Server add-ons include 12 months of maintenance commencing from the date payment is processed. This will override any existing maintenance period.

The price to upgrade from a lower to higher license tier is calculated based on Atlassian's formula, as seen here for JIRA Software. We automatically calculate the appropriate price based on the license upgrade formula when you add the license upgrade to your shopping cart.

7. How do I get an Atlassian Community license for an add-on?

Atlassian supports organizations that seek to do good in the world. If yours is a charitable organization, you can apply for a no-cost community license for Server add-ons. Cloud add-ons are not part of the program. Once your organization has a community license for an Atlassian Server product, you can request additional licenses from Atlassian sales representatives, including community licenses for Server add-ons you obtain through the Marketplace.

Request an Atlassian Community license here for Server add-ons

If you have an existing community license for an Atlassian product, you can contact us to request additional Atlassian Community licenses for other products and server add-ons.

8. What are Atlassian Open Source and Atlassian Classroom licenses?

Atlassian offers a number of free licenses for individuals and organizations involved in open source or classroom efforts. Once your organization has an open source or community license for an Atlassian product, you can request additional licenses from Atlassian, including community licenses for Server add-ons you obtain through the Marketplace. Cloud add-ons are not part of the program.

Once your organization is approved for either of the above license types, you can request additional licenses for Server paid-via-Atlassian add-ons.

 

9. Are Starter licenses available for add-ons?

All add-ons have licenses at the entry-level pricing tier. However, the Starter License program only includes Atlassian add-ons, not third-party add-ons.

Announcements

1. IE 8 support ending after May 1st, 2014

As of May 1st, 2014, Atlassian Marketplace will no longer test compatibility with Microsoft Internet Explorer 8 (IE 8). From time to time, we need to stop designing for older web browsers and platforms so that we can devote our resources to current technology. This lets us focus on creating great user experiences for the majority of our customers. In this case, we’re ending testing in IE 8 as of May 1st, 2014. We'll also stop fixing bugs in IE 8 unless there is a security concern.

2. End of Legacy Pricing Tiers after December 16th, 2014

In 2012 we announced the retirement of the following pricing tiers for JIRA and Confluence Server:

  • JIRA legacy Unlimited (100+) users
  • Confluence legacy 2000 users
  • Confluence legacy Unlimited (2000+) users

Effective December 16, 2014, it is no longer possible to renew or purchase add-ons at the legacy tiers.

If you own a legacy JIRA or Confluence license, you will be moved to a current (non-legacy) tier at your next renewal.

  • JIRA legacy Unlimited (100+) users: Renewed at 250, 500, 2000, 10000 or 10000+ tier, per your choice (or 10000+ if not specified)
  • Confluence legacy 2000 users: Renewed at non-legacy 2000 tier
  • Confluence legacy Unlimited (2000+) users: Renewed at 10000+ tier

Once you have renewed your license at a non-legacy tier, you can purchase add-ons at that same tier.

If you choose not to renew your legacy JIRA or Confluence license, you can still purchase add-ons, but you'll need to do so at the currently available pricing tiers:

  • JIRA legacy Unlimited (100+) users: Add-ons must be purchased at the JIRA 10000+ users tier
  • Confluence legacy 2000 users: Add-ons must be purchased at the Confluence 2000 users tier
  • Confluence legacy Unlimited (2000+) users: Add-ons must be purchased at the Confluence 10000+ users tier