---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Installing

# Developer Sandboxes installation {#ariaid-title1}

Release version: Australia  
Updated October 15, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Developer Sandboxes is installed on your instance with assistance from your ServiceNow account team.

## Requesting Developer Sandboxes installation {#dev-sbx-installing__section_iw5_w4h_lgc}

Check your entitlements to determine whether you have access to Developer Sandboxes. For more information, see [Developer Sandboxes entitlements](https://www.servicenow.com/docs/z44OpXdvOXuh7RBHYFqAyw "Your company's entitlements determine whether you have access to Developer Sandboxes.").  
Developer Sandboxes is a paid feature and is enabled only after procurement is complete. To install Developer Sandboxes once you're entitled, open a case with Now Support specifying the instance name and licensed number of sandboxes.  
Note:  
* If your instance is in a regulated environment, check with ServiceNow Support for more information about support for Developer Sandboxes.
* The Developer Sandboxes plugin should be installed in your production instance, or any clone source to ensure that cloning a sandbox instance correctly maintains entitlement.
{#dev-sbx-installing__ul_ecp_hcj_zjc}

## Prerequisites for installing Developer Sandboxes {#dev-sbx-installing__section_zl1_bx4_3hc}

You must have the following to install Developer Sandboxes:

* A non-production instance
* The instance is on ADCv3 (Application Delivery Controller version 3)  
  Note:  
  If a non-production instance is not on ADCv3, it is moved as part of the setup.
* Yokohama or higher
{#dev-sbx-installing__ul_fqr_hx4_3hc}

## Instances and sandboxes {#dev-sbx-installing__section_ktk_bxq_jhc}

Sandboxes are instance-specific, which means that you can't move a sandbox from one instance to another. If a new instance needs to be sandbox enabled, a new order is required.

Each sandbox is hosted in its own app-node. Therefore, a key part of the setup is adding the required number of additional nodes on the instance. For example, to support 10 sandboxes, 10 new nodes would be added to an instance.  
Developer Sandboxes are available in packs of 10. When you buy two or more packs, you can split the pack between different instances. To do so, open a request with Now Support for each instance.  
Note:  
The minimum is one pack of sandboxes (10) per instance. For example, If you buy two packs, you can't split them 5-15. Each instance must have at least 10 sandboxes.

Developer Sandboxes does not support self-hosted instances by default, though you can set up your own networking and routing changes to support sandboxes.

For more information about sandboxes and instances, see [General guidelines and use cases for Developer Sandboxes](https://www.servicenow.com/docs/xqj28So6zTrIfsa20wvtGQ "Follow some general guidelines to ensure you're optimizing your use of sandboxes.").

## Contact Now Support to finish installation {#dev-sbx-installing__section_e2s_ymv_bhc}

The number of available sandboxes on an instance is defined by the number of purchased entitlements. You must contact Now Support to open a case to finish installing and configuring Developer Sandboxes.