Isolated Cloud (IC) 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.

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

Because IC customers make app decisions based on their own security profile, residency requirements, and trust criteria, the architecture you choose for your IC 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 IC app on the Marketplace.

Who is eligible

Your app must meet both of the following criteria:

Have a commercial/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 IC. 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, IC 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 IC 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 commercial app live on the Marketplace. Your IC version will appear as a new hosting category alongside your existing commercial versions.
An IC-specific App ID. You need one App ID for your commercial hosting type and a separate App ID for Isolated Cloud hosting type. Create a new app in the developer console and deploy it using forge deploy -e production.
IC-specific product and support information ready. You'll need to customise your listing details and support documentation for IC customers.
Sharing enabled for your app.

Before you can list an IC 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 commercial 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:

Go to the Marketplace Partner Portal, and select your existing commercial cloud app.
Select Create version.
From the Upload app dropdown list, select Forge app for Isolated Cloud.
Select your IC app from the dropdown. A dropdown will appear showing your unpublished apps. Select the correct IC app.

For IC, 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 IC-specific information.

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

Follow the guided process to review and, if necessary, update your app details before submitting your IC 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 IC-compatible apps.

Releasing a new IC version

To release a new version of your IC 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 IC-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 IC version, your listing will appear alongside your existing commercial versions under a single Marketplace listing. To help IC customers quickly identify your app and set the right expectations, consider the following:

Clarify IC 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 IC version has any limitations compared to your commercial version (for example, features disabled due to egress restrictions), state this clearly to avoid customer confusion.
Use IC-relevant screenshots. Where possible, include screenshots that reflect the IC experience. Avoid screenshots that reference third-party integrations that are unavailable in IC.
Tailor your support details. Ensure your support documentation and contact information reflects any IC-specific processes or SLAs.

Determining your IC 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 IC-compatible app. This allows you to tailor your pricing for Isolated Cloud customers, which may differ from your commercial 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 IC apps yet. Ensure that your pricing structure reflects this limitation.

IC app review process

The review process for IC apps is the same as for commercial 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 IC 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 IC apps.

Marketing your IC app

Customers can find your IC 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 IC compatibility and how your app handles data. Clearly state how your Forge app manages data within the IC environment in the first 1–2 sentences of your app description. IC customers are making security-conscious decisions and need this information upfront.
Use IC-specific search terms. Incorporate terms like "single-tenant", "data residency", "isolated", "regulated industries", and "Runs on Atlassian" in your description to improve discoverability for IC customers.
Highlight security and isolation as features, not footnotes. IC 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 IC version differs from your commercial 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 IC-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 IC and commercial versions?

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

Q: Where do I develop and deploy my IC app?

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

Q: What Forge apps are supported in Isolated Cloud?

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

Q: Can I maintain a single codebase for commercial and IC?

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 commercial and IC using the Forge CLI with distinct App IDs. If a capability is unavailable in IC, delay enabling that feature in the IC environment rather than maintaining separate codebases.

Support

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