Atlassian Isolated Cloud is creating a new opportunity for Marketplace Partners to serve enterprise customers that need stronger data isolation, security controls, and governance than a standard shared Cloud environment can provide.
However, supporting Isolated Cloud is not as simple as enabling another hosting option on an existing Marketplace listing.
Before adding it to your app roadmap, there are several technical, commercial, and operational requirements your team should understand.
What is Atlassian Isolated Cloud?
Atlassian Isolated Cloud is a single-customer Cloud environment operated by Atlassian on dedicated infrastructure.
It sits between two familiar deployment models:
Data Center, where the customer operates and maintains the environment
Standard Cloud, where Atlassian manages a shared Cloud infrastructure
Isolated Cloud, where Atlassian manages a private environment dedicated to one customer
This model gives customers stronger control over data isolation, encryption keys, and outbound data flows while reducing much of the infrastructure burden associated with Data Center.
It can therefore be particularly relevant to large enterprises and organizations in regulated industries that want to move toward Cloud but are not comfortable with a standard multi-tenant deployment.
Why Isolated Cloud matters for Marketplace Partners
will follow them.
This creates an opportunity for vendors to:
retain Data Center customers as they move to Cloud
reach enterprise and regulated-industry buyers
differentiate their app from competitors without Isolated Cloud support
expand their Cloud product strategy beyond the commercial Cloud market
But vendors should first evaluate whether their current application architecture is compatible.
Is your app technically eligible?
The most important requirement is that Isolated Cloud supports Forge apps.
Apps that still contain Connect or Connect-on-Forge modules are not currently eligible. For those apps, supporting Isolated Cloud first requires completing the transition to a fully Forge-based architecture.
The development effort can therefore vary significantly.
If your app is already fully Forge-based
The technical effort may be relatively limited. Most of the work is likely to involve:
confirming eligibility
preparing the Isolated Cloud listing
configuring pricing
creating the required app registration
completing Marketplace review and security documentation
validating the app in the target environment
Depending on the app, this may take from several days to around two weeks.
If your app is still built on Connect
The effort is much greater.
The app must first be rebuilt or migrated to Forge. Depending on its modules, backend architecture, data model, and external integrations, this could take several weeks or months.
In this situation, Isolated Cloud support should be treated as part of a wider Connect-to-Forge roadmap rather than a small listing update.
Key publishing requirements
Marketplace Partners should prepare for several Isolated Cloud-specific conditions.
Before publishing, the app should:
Contain no remaining Connect modules
Already have a live public Cloud version on the Marketplace
Use a separate App ID for the Isolated Cloud version
Be listed as a Standard edition with Isolated Cloud as the hosting type
Complete the relevant Marketplace review and Privacy & Security questionnaire
Partners can set pricing specifically for the Isolated Cloud listing, and that pricing may differ from the commercial Cloud version.
However, pricing decisions need to be made carefully. The selected pricing tier may become fixed after publishing, making it difficult to switch between free and paid models later.
Important limitations to consider
Isolated Cloud offers stronger controls, but it should not be positioned as a direct replacement for every Data Center environment.
Marketplace Partners should be aware of several limitations.
It does not guarantee absolute legal data sovereignty
Although the infrastructure is dedicated and data flows can be more tightly controlled, applicable laws may still allow legal access to customer data.
Customers with strict sovereign hosting requirements may still need to assess whether Isolated Cloud satisfies their legal and regulatory obligations.
The Marketplace app ecosystem is still developing
A customer’s current Data Center app portfolio may not yet be available for Isolated Cloud.
Before proposing migration, vendors and implementation partners should check the availability of every business-critical application and identify potential feature gaps.
The cost is higher than Standard Cloud
Dedicated infrastructure, additional operational requirements, and expanded security capabilities make Isolated Cloud a premium offering.
Marketplace vendors should consider how their own app pricing and support model will fit enterprise customer expectations.
Migration is still evolving
Data Center-to-Isolated Cloud migration capabilities may still be in an early-access phase for some scenarios.
Partners should avoid promising a simple or risk-free migration until the customer’s environment, data, apps, and supported migration paths have been fully assessed.
What Marketplace Partners should do now
Even if Isolated Cloud is not yet part of your immediate roadmap, it is worth evaluating your readiness.
A practical first step is to:
confirm whether your app is fully Forge-based
identify any remaining Connect dependencies
review external data flows and integrations
assess enterprise security and privacy requirements
review the Isolated Cloud publishing checklist
estimate the effort required for a separate listing and review
evaluate demand from existing Data Center and enterprise customers
For vendors with a Forge app already live on Cloud, supporting Isolated Cloud may be a relatively achievable extension.
For vendors still running Connect apps, it provides another business reason to accelerate Forge migration.
Final thoughts
Atlassian Isolated Cloud is more than a new deployment option. It represents a potential new market for Marketplace vendors serving customers that need the flexibility of Cloud with stronger isolation and control.
But entering that market requires more than changing a listing setting.
App architecture, Marketplace eligibility, security documentation, pricing, testing, and long-term support all need to be considered together.
At DS Solution Vietnam, we support Marketplace Partners with Forge app development, Connect-to-Forge migration, app architecture assessment, and preparation for new Atlassian Cloud deployment models.
If your team is evaluating Isolated Cloud support or needs additional Atlassian development capacity, we would be happy to discuss your app and possible next steps.
