Last updatedSep 6, 2019

Cloud, server, and Data Center for developers

Atlassian offers three deployment options for our products: cloud, server, and Data Center. This article covers the differences in developing an app for the different deployment options.

New app developers and app developers who want to target more than one deployment type should read this page before getting started. In doing so, you'll be better prepared to make the right architectural decisions while developing your app.

Cloud

Customers can sign up online and create an instance of one of our cloud products, like Jira or Confluence. The instance is hosted on Atlassian's infrastructure, with an .atlassian.net subdomain by default. All cloud instances can be accessed through the public internet.

Server and Data Center

Server and Data Center products are available for customers to host on their own infrastructure. Server deployments run on a single server, and Data Center deployments can run on a cluster.

For best practices developing apps for Data Center, see Developing apps for Atlassian Data Center products.

Comparing deployment options

So, what's the difference between Jira Cloud and Jira Server? Or Confluence Cloud and Confluence Server? It may be the same Atlassian product, but that doesn't mean apps will automatically work on all deployment options.

The table below shows key differences between the deployment options for app developers to consider.

Cloud Server and Data Center
Distribution
  • Web apps
  • Hosted by developer (you)
  • Java backend
  • Hosted by customer
Internet availability
  • Can access the public internet
  • No guarantee of access to the public internet
  • Many customers keep their instances inside secure, private intranets (behind the firewall)
Tools and languages
  • Written using any framework or language appropriate for the authentication method.
  • Atlassian provides starter kits for:
Persistent storage
Authentication
  • Atlassian Connect is available to extend the product UI. Use Connect to display repository, build, deployment, or feature flag details on each issue.
  • OAuth 2.0 is available for REST APIs.
  • OAuth 1.0a is available for REST APIs. This method requires site admins to generate a private/public key pair and configure an incoming application link for your app.
  • Java APIs need no special authentication beyond requesting the needed permissions upon install.
  • OAuth 1.0a is available for REST APIs. This method requires site admins to generate a private/public key pair and configure an incoming application link for your app.
Versioning
  • Atlassian manages all product updates.
  • Customers are responsible for product updates.
  • When listing your app on Marketplace, you must specify the range of product versions your app is compatible with.

It's possible for your cloud app to also interact with server and Data Center. For this to be possible, the customer's instance must be accessible to the internet (see Internet availability above), and you must authenticate using OAuth 1.0a (See Authentication above).

Not all Atlassian products are available on all deployment options.

For more information about the differences between cloud and server from a customer's perspective, see Compare Atlassian cloud vs server.