Isolated Cloud is Atlassian's single-tenant cloud environment that provides fully isolated data and compute for customers with strict security and compliance needs, such as those in regulated industries. These customers require dedicated storage, compute, and networking, with strict control over data egress and residency.

Isolated Cloud supports all Forge apps. Connect and Connect-on-Forge modules are not supported.

Because Isolated Cloud customers make app decisions based on their own security profile, residency requirements, and trust criteria, the architecture you choose for your Isolated Cloud app should be shaped by your customer's specific needs rather than a single platform-wide constraint.

Use this guide to understand what's required and how to publish your Isolated Cloud app on the Marketplace.

Who is eligible

Your app must meet both of the following criteria:

Have a public cloud version already live on the Marketplace.
Be built with Forge.

Technical requirements

Connect and Connect-on-Forge modules are not supported.

There are no platform-enforced egress restrictions specific to Isolated Cloud. Whether to install an app with egress requirements is at the customer's discretion, based on their own security and compliance policies.

As a general rule, Isolated Cloud customers expect their data to remain strictly within the Isolated Cloud environment. Apps that keep data within the Isolated Cloud environment are most likely to meet the broad security expectations of Isolated Cloud customers. We recommend discussing your app's architecture with your customer early to confirm it aligns with their requirements.

Like Atlassian Government Cloud, some Forge platform features may be available in Atlassian Commercial Cloud before they reach Isolated Cloud. Check the Forge changelog for the latest feature availability.

Pre-publishing checklist

Before you begin, ensure you have:

A cloud app live on the Marketplace. Your Isolated Cloud version will appear as a new hosting category alongside your existing cloud versions.
An Isolated Cloud specific App ID. You need one App ID for your cloud hosting type and a separate App ID for Isolated Cloud hosting type. Create a new app in the developer console.
Licensing configuration and app deployment. Set the licensing details in the manifest as per the desired payment model for the app and deploy it using forge deploy -e production.
Isolated Cloud specific product and support information ready. You'll need to customize your listing details and support documentation for Isolated Cloud customers.
Isolated Cloud specific privacy and security information ready. You'll need to complete a Privacy and Security tab for your Isolated Cloud app listing.
Sharing enabled for your app.

Transitioning an Isolated Cloud app between FREE and PAID (or vice versa) is not allowed. Once your Isolated Cloud app is published with a pricing model, you cannot switch it from FREE to PAID or from PAID to FREE. Be careful to choose the correct pricing model before you publish.

Before you can list an Isolated Cloud app on the Marketplace, you need to first enable Sharing for it. To do this:

Open the app in the developer console at developer.atlassian.com.
Select Distribution.
In the Distribution controls section, select Edit.
Set the Distribution status to Sharing and select Save changes.

Isolated Cloud uses the same developer console as your standard Cloud apps at developer.atlassian.com.

Create your Marketplace listing

Once the app's distribution is set to Sharing, you can create its Marketplace listing:

Log in to Marketplace Partner Portal with your partner account.
Select Manage partner account from the profile menu in the upper right.
Select your existing cloud app.
Select Create version.
From the Upload app dropdown list, select Forge app for Isolated Cloud.
Select your Isolated Cloud app from the dropdown. A dropdown will appear showing your unpublished apps. Select the correct Isolated Cloud app.

For Isolated Cloud, the portal provides a dropdown of your available unpublished apps to select from.

Select Next: Make public. This takes you to the listing details page where you can review and update your app's information before submitting.

Update your app listing

Next, review and update your app listing's details to reflect Isolated Cloud specific information.

We'll be reusing content from your cloud app version, but you'll need to customize these details for Isolated Cloud requirements.
All updates you make are only for the Isolated Cloud version of your app. This will not change any existing details of your existing cloud app.

Follow the guided process to review and, if necessary, update your app details before submitting your Isolated Cloud app version. When you're done, select Submit.

An Isolated Cloud icon will appear on your listing. This icon is visible across your listing page and pricing section, helping customers identify apps compatible with Isolated Cloud.

Complete the Privacy and Security tab for your Isolated Cloud app

Isolated Cloud apps have their own Privacy and Security tab on the Marketplace listing. Complete this tab with information that accurately reflects how your app runs in the Isolated Cloud environment.

To add Privacy and Security information for your Isolated Cloud app:

Log in to Marketplace Partner Portal with your partner account.
Select Manage partner account from the profile menu in the upper right.
Select the required app's name from the list.
Open the Privacy and Security tab.
Select Isolated Cloud as the environment you want to update.
Complete the questionnaire with Isolated Cloud specific information about your app's data handling, permissions, hosting, operational controls, compliance posture, and support model.
Review your answers, then select Save Draft or Submit.

If your cloud app already has a completed Privacy and Security tab, you may be able to use the Copy from Cloud feature to populate matching fields in the Isolated Cloud form. Copy from Cloud only fills the form as a starting point. You must review the copied answers and manually save or submit them before they are stored.

Maintain separate Privacy and Security information for your cloud and Isolated Cloud app versions. Changes to one environment's Privacy and Security tab don't automatically sync to another environment.

For more details, see Privacy and Security tab in your Marketplace listing.

Releasing a new Isolated Cloud version

To release a new version of your Isolated Cloud app, deploy the updated version using the Forge CLI within the Atlassian Commercial Cloud environment:

1
2
forge deploy -e production

Make sure you run this command with your Isolated Cloud specific App ID configured. The new version will automatically inherit the visibility settings of the previous version.

Marketplace listing considerations

When publishing your app's Isolated Cloud version, your listing will appear alongside your existing cloud version under a single Marketplace listing. To help Isolated Cloud customers quickly identify your app and set the right expectations, consider the following:

Clarify Isolated Cloud compatibility in your description. Explicitly state that this version is built for Isolated Cloud and describe your app's Forge hosting capability.
Highlight feature parity or differences. If your Isolated Cloud version has any limitations compared to your cloud version (for example, features disabled due to egress restrictions), state this clearly to avoid customer confusion.
Use Isolated Cloud relevant screenshots. Where possible, include screenshots that reflect the Isolated Cloud experience. Avoid screenshots that reference third-party integrations that are unavailable in Isolated Cloud.
Tailor your support details. Ensure your support documentation and contact information reflects any Isolated Cloud specific processes or SLAs.

Determining your Isolated Cloud app's pricing

For Isolated Cloud apps, only the Standard edition is currently supported. As a Marketplace Partner, you will be able to set and upload pricing specifically for the Standard edition of your Isolated Cloud compatible app. This allows you to tailor your pricing for Isolated Cloud customers, which may differ from your cloud version.

When configuring your app's price, make sure to select Isolated Cloud as the hosting type.

Advanced editions and Multi-instance pricing is not supported for Isolated Cloud apps yet. Ensure that your pricing structure reflects this limitation.

Isolated Cloud app review process

The review process for Isolated Cloud apps is the same as for cloud apps.

After submitting your app through the Marketplace Partner Portal, it will enter the review queue. The Atlassian review team will assess your submission for compliance, accuracy, and completeness.

Monitor your email and the Partner Portal for feedback or requests for additional information. Prompt responses help avoid delays and ensure a smooth review process. Once approved, your app will be published for Isolated Cloud customers.

Licenses and transactions

Always select Isolated Cloud as the hosting type before submitting your app for review.

Key points:

When viewing licenses and transactions, filter by Isolated Cloud in the Hosting field.
Only Standard edition licensing is supported; advanced or multi-instance pricing is not available for Isolated Cloud apps.

Marketing your Isolated Cloud app

Customers can find your Isolated Cloud app by selecting Isolated Cloud from the View for dropdown on your Marketplace listing. Make sure your listing messaging clearly communicates that this version is purpose-built for the Isolated Cloud environment.

Lead with Isolated Cloud compatibility and how your app handles data. Clearly state how your Forge app manages data within the Isolated Cloud environment in the first 1–2 sentences of your app description. Isolated Cloud customers are making security-conscious decisions and need this information upfront.
Use Isolated Cloud specific search terms. Incorporate terms like "single-tenant", "data residency", "isolated", "regulated industries", and "Runs on Atlassian" in your description to improve discoverability for Isolated Cloud customers.
Highlight security and isolation as features, not footnotes. Isolated Cloud customers choose this environment because of strict compliance needs. Emphasise how your Forge app aligns with their data handling and residency requirements.
Be transparent about feature scope. If your Isolated Cloud version differs from your cloud version, say so. Customers trust apps that are upfront about limitations more than apps that don't mention them.
Promote through Atlassian Partner channels. Participate in Isolated Cloud specific campaigns and co-marketing opportunities with your Partner Manager to reach your target audience.

Frequently Asked Questions (FAQs)

Q: Can I use the same App ID for Isolated Cloud and cloud versions?

A: No. You need one App ID for your cloud hosting type and a separate App ID for Isolated Cloud hosting type. This ensures your Isolated Cloud app is properly identified and managed within the Marketplace.

Q: Where do I develop and deploy my Isolated Cloud app?

A: Isolated Cloud apps are developed and deployed through the developer console at developer.atlassian.com. Your Isolated Cloud App ID must be distinct from your cloud App ID.

Q: What Forge apps are supported in Isolated Cloud?

A: Isolated Cloud supports all Forge apps. Connect and Connect-on-Forge modules are not supported. The right approach for your Isolated Cloud app depends on your customer's specific security, residency, and egress requirements.

Q: Can I maintain a single codebase for cloud and Isolated Cloud?

A: Yes, this is the recommended approach. Maintain one codebase and use environment variables to manage any differences in platform capabilities across environments. Deploy to both cloud and Isolated Cloud using the Forge CLI with distinct App IDs. If a capability is unavailable in Isolated Cloud, delay enabling that feature in the Isolated Cloud environment rather than maintaining separate codebases.

Support

For help with publishing or technical issues, contact Atlassian Marketplace Support.
For Isolated Cloud specific questions, reach out to your Partner Manager.