Multiple Sandboxes Now Generally Available!

[#1]

Hello everyone,

My name is Atul Setlur, Group Product Manager for Atlassian Cloud. I'm excited to announce that Multiple Sandboxes, which allows for the creation of multiple sandboxes per production site, will transition from an open beta to General Availability today! The ability to create multiple sandboxes per production site is available to Atlassian apps on a Premium* or Enterprise plan. With Multiple Sandboxes, you can now accelerate safe change management with isolated sandboxes linked to one site. Whether you’re testing new configurations and features or onboarding new apps, you can do it with confidence.

With the general availability of Multiple Sandboxes, we will also be introducing two additional changes that impact Premium and Enterprise plans

• Atlassian apps on an Enterprise plans will include five complimentary sandboxes that can be allocated across any site associated with the plan. (Atlassian apps on a Premium plan will continue to include only one complimentary sandbox.)

• Additional sandboxes can be purchased for annually-billed Atlassian apps on Premium and Enterprise plans for $10,000 per sandbox, per year.

*Atlassian apps on a Premium plan can get access to multiple sandboxes per production site by purchasing additional sandboxes (more-below). 

Multiple Sandboxes, Sandbox Limits, and Marketplace Apps

Reminder: Sandboxes are available for Jira, Confluence, Jira Service Management, and Jira Product Discovery. By default, our Platform Apps are included in sandboxes. Rovo can be added or removed from your sandbox at any time, based on your preferences.

Benefits of Multiple Sandboxes

Multiple Sandboxes enables organizations to scale and optimize their change management processes by running tests and staging changes against their app's production sites in parallel. Organizations can now implement either industry-standard Dev -> Test -> Prod pipelines or parallel change processes, reducing risk and eliminating development bottlenecks.

Org Admins can flexibly allocate sandboxes to any eligible site and purchase additional ones as their organization’s needs evolve, all managed from the Atlassian Administration Sandbox tab.

For more details about Sandboxes please see our support documentation.

Sandbox Limits

With the general availability of Multiple Sandboxes, Atlassian apps on Enterprise plans will include five complimentary sandboxes. These sandboxes can be assigned to any site(s) within an organization. For example, suppose a customer has a Jira Enterprise license and has four sites, with two sandboxes allocated to Site 1, two sandboxes allocated to Site 2, and one sandbox allocated to Site 3. In this scenario the sixth sandbox cannot be assigned to Site 4 as only five sandboxes can be active concurrently.

In the above scenario, Org Admins can do one of two things:

• If you don't need all sandboxes running at the same time, you can delete a sandbox from one site and reassign that allocation to Site 4, i.e.,

• If your organization needs 6 concurrent sandboxes, you can purchase an additional sandbox to expand your sandbox pool, i.e.,

How does Multiple Sandboxes work with apps purchased from the Atlassian Marketplace?

Each site with a Marketplace app can install that Marketplace app on up to five sandboxes associated with that site. If you need the Marketplace app on additional sandboxes beyond this limit, you'll need to purchase additional licenses.

Let's say a customer has two Jira Enterprise sites. Their Enterprise license includes five sandboxes, and they've purchased three additional sandboxes. If they have App A licensed for both sites, they can use App A on five of the sandboxes associated with Site 1, i.e., Sandboxes 1-5, and the two sandboxes associated with Site 2, i.e., Sandboxes 7-8. However, on Sandbox 6 associated with Site 1 they can't use App A unless they purchase an additional Marketplace app license or remove App A from other sandboxes associated with Site 1.

Additional Sandboxes

Understanding additional sandboxes

Customers can purchase additional sandboxes for Atlassian apps that are on a Premium or Enterprise plan and are being billed annually. Additional sandboxes cost $10,000 per sandbox, per app and can only be purchased if the associated app plan is billed annually. For example if you need one Jira Sandbox and one Confluence Sandbox you will need to purchase one for each.

Please note that additional sandboxes can be purchased off-cycle and they will be pro-rated from the date or purchase to the start of your next billing cycle.

How do additional sandboxes work with your license?

Atlassian Apps on an Enterprise plan

For Atlassian apps on an Enterprise plan, additional sandboxes can be allocated to any site associated with your app's Enterprise plan

Atlassian Apps on a Premium plan

Atlassian apps on a Premium plan are site specific, therefore additional sandboxes are site-specific. Each Premium site that needs an additional sandbox requires a separate purchase. Need more than two sandboxes? Upgrade to Cloud Enterprise for five sandboxes you can use across any linked site. Talk to your Account Executive to learn more.

How to purchase additional sandboxes?

You can purchase additional sandboxes through admin.atlassian.com/billing by

1. Select Subscriptions > choose app license
2. Click Add-on tab > Explore add-ons
3. Select "Additional sandboxes"
4. Enter desired number of sandboxes
5. Add payment method
6. Review and Accept legal terms

Or by contacting sales directly. Reminder, additional sandboxes can only be purchased for app plans billed annually.

The Future of enterprise Change Management

Sandboxes are essential for safe, scalable change. They provide isolated spaces to experiment, validate, and refine changes - eliminating production disruptions and costly rollbacks. Atlassian sandboxes enable admins and teams to:

• Test new workflows, automations, and integrations without impacting production

• Run parallel tests across multiple sandboxes to drive innovation safely

• Experiment with and validate AI-powered automations, workflows, and integrations

Our vision is clear: help you de-risk operational changes and navigate transformational shifts through purpose-built, enterprise-grade Sandboxes that adapt to your needs.

We're prioritizing operational change workflows first, reducing manual effort and risk when promoting changes from Sandbox to production. Our enhanced Sandboxes streamline change management, making it simpler and safer to validate and deploy updates without business disruption. 

Our Sandbox config deployment, now in closed beta, enables you to safely promote Jira configuration changes from sandboxes to production.

Share your Sandbox success stories or tell us what features you'd like to see next in the comments below!

Additional Resources:

• Open Beta: Multiple sandboxes | Atlassian Support

• What is a sandbox? | Atlassian Support

• Sandbox limits | Atlassian Support

• Copy production data to sandbox | Atlassian Support

• Manage apps for a sandbox | Atlassian Support
  

[Mathew Lederman]

@Atul Setlur this is unacceptable.

When multiple sandboxes went into Open Beta, Enterprise Cloud sites were provided, "10 sandboxes per Cloud Enterprise product license" (https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Announcing-Multiple-Sandboxes-Open-Beta-and-additional-Sandbox/ba-p/2905865). Now that's being knocked down to 5 total, not per product, and we have to pay for the others? I'm using 12 sandboxes today. 5 Jira, 5 Confluence, 2 JSM. Will 7 of these be magically disconnected unless we pay $10k each at some point?

Atlassian is encouraging it's customers to move everyone in one company under one Organization and therefore I now have 8 sites under my organization. Most of these sites have Jira, Confluence, and JSM. Now you're telling me each of those sites can no longer have it's own sandbox unless we pay the $10k per product (please stop calling them apps, it is SO unnecessarily confusing). That's $190K/year just to have appropriate change management in place.

The future of enterprise change management is an abysmal mess if this farse is allowed to proceed.

[Sebastian Wigge]

Generally speaking a great feature, too bad it's locked entirely behind enterprise.

Why couldn't you at least allow a second sandbox per app for your premium customers without charging extra? 

[ADM Thijs]

Hi @Atul Setlur 

How does this work for a hybrid setup where some apps are on Enterprise and others on Premium?

In our case, we have Jira Software and Confluence on Cloud Enterprise, but Jira Service Management on Premium, all on the same production site. From the docs and your article I understand that:

• Jira/Confluence on Enterprise get a pool of complimentary sandboxes that we can allocate across sites.
• JSM Premium still only includes one sandbox per production site, unless we buy additional JSM sandboxes.

Does that mean that, for this site, we can still only have one “full stack” sandbox (Jira + Confluence + JSM), and any extra sandbox sites we create with our Jira/Confluence Enterprise entitlement would be Jira/Confluence-only, without JSM?

If so, it feels like we’re leaving value on the table because our change-management needs are cross-product. Have you considered a model where sandbox capacity is pooled (or “credits”-based) across products, so mixed Enterprise/Premium customers could use their unused Jira/Confluence sandbox capacity to spin up a second full-stack sandbox instead of multiple partial ones?

[carl]

This is a great improvement — having multiple sandboxes available by default will really help teams test configurations safely without disrupting production. The flexibility to allocate sandboxes across sites and scale up when needed makes change management much smoother. The pricing and limits are also clearly explained. Overall, this is a solid step forward for teams running Dev → Test → Prod workflows in Atlassian Cloud.

[Robert DaSilva]

Hey @Mathew Lederman , while this might be changing, according to my current One Atlassian demo site, it should be per-app sandboxes. My demo site has a total of 10 sandboxes available to me, and I see three different counts, one for each app I have installed.

I would assume this will remain true for the reduction to 5 sandboxes, where it will really be 5 per-app. I think the main distinction is going to be "sandbox sites" instead of individual sandboxes. If this assumption is true, that would mean that multiple apps per sandbox site only count once.

I would be very curious if @Atul Setlur can confirm if this is the expected behaviour or not.

[Mathew Lederman]

@Robert DaSilva I very much hope that's the case. My concern is quoted below which makes me think otherwise. I hope you're right and we're going from 10 sandboxes per app to 5 sandboxes per app and not 5 sandboxes total. Unfortunately all of the scenarios only include 1 app, so it's difficult to decipher.

Additional sandboxes cost $10,000 per sandbox, per app and can only be purchased if the associated app plan is billed annually. For example if you need one Jira Sandbox and one Confluence Sandbox you will need to purchase one for each.

[Fernando Calvo García]

Hi, I don't see any good news anywhere. A customer who is currently using 10 sandboxes in their enterprise plan, which has a very high cost, will only have 5 sandboxes, in addition to paying $10K per additional sandbox. This seems like a very risky policy on Atlassian's part and for their competitiveness with other rival products. It is VERY difficult to defend these decisions made by Atlassian to our clients.

[Paul Pasler]

This policy suggests a direct increase in our operational cost as Forge app vendor - as multiplied sandbox usage increases our billable Forge consumption - without any corresponding revenue compensation from the customer's purchase of Enterprise or the $10,000 annual for additional sandbox licenses.

[Jaime Escribano _knowmad mood_]

@Atul Setlur 

Is this final?

Customers now have complicated hierarchies where more than one company is buying licenses in bulk and creating a big number of sites all under one organization.

Asking for only two of those companies tops (not including different sites for departments) to have the expected dev->test->prod setup is ludicrous when the future of the ecosystem is "enterprise level customers"

[Antonio Valle _G2_]

What about customers using collections? What about customers that need to spin an additional  sandbox for three months instead a full year? Why do you need a different billing profile?

Too much questions ....