When building apps for Atlassian cloud products, you have platform and framework options to help you develop secure, full-featured apps quickly. There are three main ways to develop cloud apps and integrations with Atlassian:
Atlassian has announced the timeline for phased end of support for Connect.
From Sep 17, 2025, only Forge apps can be submitted to the Atlassian Marketplace. All new extensibility features will be delivered only on Forge.
Have an existing Connect app? Find out how to incrementally adopt Forge from Connect.
If you're building a cloud version of a server or Data Center app, check out App migration for technical guidance.
This table compares the capabilities of Connect, Forge, and external apps and integrations.
| Forge | Connect | External apps and integrations | |
|---|---|---|---|
| App hosting | Hosted by Atlassian | Hosted by you | Hosted by you |
| UI extensibility | In-product UI modules (custom UI and UI kit) | In-product UI modules | No in-product UI elements |
| Product APIs | Managed REST and JavaScript APIs | REST and JavaScript APIs | REST APIs |
| App languages | Serverless Node.js functions | Any language (optional frameworks for Node.js and Java) | Any language compatible with your auth method |
| Auth and data implementation | Use built-in authentication, sandboxing, and development environments | You have complete control over auth and data implementation (or use JWT token by default) | OAuth 2.0 and basic auth available |
| Distribution | Make apps for your team or sell in the Marketplace | Make apps for your team or sell in the Marketplace | Make apps for yourself or your team |
| Compatibility | Jira and Confluence compatible | Jira, Confluence, and Bitbucket compatible | OAuth 2.0 apps are Jira Platform, Jira Service Management, and Confluence compatible. Other product REST APIs available through other auth implementations. |
You'll need to consider the different security responsibilities shared between you and Atlassian, depending on your chosen app architecture. Learn more about the Atlassian cloud shared responsibility model.
Forge is our new development platform that helps you build a secure Jira and Confluence Cloud app quickly and easily. We recommend Forge if you're building your first Atlassian cloud app, or you want to reduce infrastructure and hosting overhead.
Forge provides built-in security, Atlassian-hosted infrastructure, and UI extensibility options. It also offers a streamlined DevOps experience with development, staging, and production environments.
You'll write your app with serverless Node.js functions, manage the app with the Forge CLI, and create the front end with either custom UI or UI kit components.
You can share and sell Forge apps on the Atlassian Marketplace, and you can manage, distribute, and monitor your apps in the developer console.
For an introduction to creating and managing an app with the Forge CLI, check out this video:
Atlassian has announced the timeline for phased end of support for Connect.
From Sep 17, 2025, only Forge apps can be submitted to the Atlassian Marketplace. All new extensibility features will be delivered only on Forge.
Have an existing Connect app? Find out how to incrementally adopt Forge from Connect.
Atlassian Connect is a framework that enables developers to build apps and integrations on top of Jira, Confluence, and Bitbucket Cloud products.
Connect gives you complete control over the tech stack, infrastructure, and integration with Atlassian cloud products. You determine your security implementation and authentication with external cloud providers, such as AWS, Google Cloud, or Heroku.
You can write the app in any language, but we provide frameworks for Node.js and Java to help you test things out and get started with JWT token authentication.
See more on building Connect apps with Jira, Confluence, or Bitbucket Cloud.
You can also build some types of apps without Atlassian Connect or Forge. These apps can still access data and create content through the cloud product APIs.
For app security, you can use OAuth 2.0 (3LO) to pass information between your integration and Jira Platform, Jira Service Management, or Confluence, depending on your security needs. See the Authentication and authorization overview for more information.
OAuth 2.0 integrations are best suited for projects that need to access product data on behalf of a user, but don't need any in-product UI elements.
Note, OAuth 2.0 integrations cannot be listed in the Atlassian Marketplace, so if you eventually want to list your app, consider building a Connect app with user impersonation instead.
For more on OAuth 2.0 integrations and how to implement them, see our guides on OAuth 2.0 for Jira or OAuth 2.0 for Confluence.
For all our cloud product APIs, see the cloud API documentation.
We offer a number of resources to guide and support you as you build on cloud:
server-eos.For a full list of updates and resources, visit Atlassian communication channels.
To apply for Partner Portal access, you need at least one paid-via-Atlassian app and a private domain:
Rate this page: