--- sourceDocument: Brazil Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/application-development Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Installing # Installing Developer Sandboxes {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Installing Developer Sandboxes Developer Sandboxes is a ServiceNow feature that enables isolated development environments hosted on license-managed instances. It requires specific plugins and configurations to be installed and managed properly. These sandboxes are instance-specific, cannot be moved between instances, and are provisioned in packs of 10. They provide developers with dedicated app-nodes for development and testing without impacting production environments. Show full answer Show less ## Prerequisites and Installation * Verify Developer Sandboxes entitlement before installation. * Install the **com.glide.dsb** plugin only on the license management (controller) instance that will host sandboxes---do not install on production instances or non-hosting instances. * Install the **com.glide.dsb.licensing** plugin on the production or controller instance to manage sandbox license assignments via App Engine Management Center (AEMC). * Reconfigure the **glide.devsandbox.num.controller** property after licensing plugin installation. * The controller instance must be the license management instance and non-production instances must be on Application Delivery Controller version 3 (ADCv3) or higher (Yokohama or above). * Each sandbox requires an app-node; for example, 10 sandboxes require 10 additional nodes on the instance. * Sandbox packs come in increments of 10 sandboxes, with a minimum of one pack per instance and a maximum of three packs (30 sandboxes) per instance. * A free pack of four sandboxes is available to all organizations but can only be assigned to one non-production instance and not split across instances. * Developer Sandboxes do not support self-hosted instances by default; custom networking setup is required for those cases. ## License Assignment and Management * Sandbox licenses are assigned via AEMC, allowing admins to distribute purchased packs across non-production instances without ServiceNow support intervention. * Each license pack contains 10 sandboxes, and packs cannot be split unevenly across instances. * With the free pack and purchased packs combined, a maximum of 34 sandboxes can be hosted on a single instance. ## Single Sign-On (SSO) Configuration Developers can access sandboxes using instance credentials or via SSO. To enable SSO for sandboxes, set these system properties on the base instance: * Disable ACR: **glide.sso.acr.enable = false** * Enable SSO: **glide.authenticate.multisso.enabled = true** ## Operational Considerations * Before cloning or upgrading instances with Developer Sandboxes, back up sandbox work through update sets or source control to prevent data loss. * Domain separation is supported, allowing logical grouping of data, processes, and administrative tasks with controlled user access across domains. ## Components and Properties Installed Activating Developer Sandboxes installs essential components such as tables, user roles, and system properties that govern sandbox behavior. These configurations enable developers to optimize and manage their isolated development environments effectively. ## Support and Compliance For instances operating in regulated environments, customers should consult ServiceNow Support for specific guidance and compliance-related information regarding Developer Sandboxes. Developer Sandboxes is a installed on your instance, with licenses from a pack assigned by your admin. Review prerequisites, plugin requirements, and SSO configuration before installation begins. ## 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/DDj9mdfPwJyAdOWN1Wirtw "Your company's entitlements determine whether you have access to Developer Sandboxes."). To install Developer Sandboxes: * The com.glide.dsb plugin must be installed on each license management instance that will host sandboxes. Warning: Do not install or enable the `com.glide.dsb` plugin on a production instance or any instance where sandboxes will not be hosted. * The com.glide.dsb.licensing plugin must be installed on your production or controller instance to manage sandbox license assignment from App Engine Management Center. * After you install the com.glide.dsb.licensing plugin, you must reconfigure the `glide.dev_sandbox.num.controller` property. For more information, see [Properties installed with Developer Sandboxes](https://www.servicenow.com/docs/ujR5z8JZfFyODf5sWHowMw "The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively."). * A sandbox license admin must assign licenses. For more information, see [License assignment](https://www.servicenow.com/docs/Di~l2QZti_6mvyAH2sKy9Q "License assignment in App Engine Management Center (AEMC) lets Developer Sandboxes admins distribute purchased sandbox packs across non-production instances without opening a support case. Each pack contains 10 sandboxes, and assignments are managed from a license management instance."). * If your instance is in a regulated environment, check with ServiceNow Support for more information about support for Developer Sandboxes. {#dev-sbx-installing__ul_ecp_hcj_zjc} ## Prerequisites for installing Developer Sandboxes {#dev-sbx-installing__section_zl1_bx4_3hc} Verify the following prerequisites before installing Developer Sandboxes. The controller instance must be the license management instance. Non-production instances must be: * On ADCv3 (Application Delivery Controller version 3) Note: If a non-production instance is not on ADCv3, it will be moved it as part of the setup. * Yokohama or higher {#dev-sbx-installing__ul_fqr_hx4_3hc_subprod} ## 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, it will be a net-new order. Note: A free pack of four sandboxes is automatically available to all organizations. The free pack can be assigned to one non-production instance and can't be split across instances. 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 distribute them across instances using the self-serve license assignment UI in AEMC. Note: The minimum is one pack of sandboxes (10) per instance, and a maximum of three packs (30 sandboxes) can be assigned to a single instance. For example, if you buy two packs, you can't split them 5-15. Each instance must have at least 10 sandboxes. However, with the free pack, you can have a maximum of 34 sandboxes on one instance. For more information, see [License assignment](https://www.servicenow.com/docs/Di~l2QZti_6mvyAH2sKy9Q "License assignment in App Engine Management Center (AEMC) lets Developer Sandboxes admins distribute purchased sandbox packs across non-production instances without opening a support case. Each pack contains 10 sandboxes, and assignments are managed from a license management instance."). 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 on sandboxes and instances, see [General guidelines and use cases for Developer Sandboxes](https://www.servicenow.com/docs/oadOvrLOjaHauCx9jq1nUg "Follow some general guidelines to ensure you're optimizing your use of sandboxes."). ## Enabling SSO {#dev-sbx-installing__section_qr2_z4h_lgc} Developers can access sandboxes using instance credentials and Single Sign-On (SSO). The following properties must be set in the base instance before developers can use SSO to access sandboxes: * Disable ACR: `sys_property glide.sso.acr.enable = false` * Enable SSO: `glide.authenticate.multisso.enabled = true` {#dev-sbx-installing__ul_bjw_2ph_lgc} * **[Developer Sandboxes entitlements](https://www.servicenow.com/docs/DDj9mdfPwJyAdOWN1Wirtw)** Your company's entitlements determine whether you have access to Developer Sandboxes. * **[License assignment](https://www.servicenow.com/docs/Di~l2QZti_6mvyAH2sKy9Q)** License assignment in App Engine Management Center (AEMC) lets Developer Sandboxes admins distribute purchased sandbox packs across non-production instances without opening a support case. Each pack contains 10 sandboxes, and assignments are managed from a license management instance. * **[Cloning and upgrading considerations for Developer Sandboxes](https://www.servicenow.com/docs/Vl_W3UJexQQoYxtZKjr1fg)** You should understand how plugins and sandboxes work before you clone or upgrade an instance with Developer Sandboxes. Always back up your work in a sandbox before any clone or upgrade, either by exporting the update sets or committing to source control. * **[Developer Sandboxes domain separation](https://www.servicenow.com/docs/qEMvU3wo6nKhGGJeA8Q4~g)** Domain separation is supported for Developer Sandboxes. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data. * **[Components installed with Developer Sandboxes](https://www.servicenow.com/docs/ACkVJSOAbJPE7q5XN~1dSw)** Several types of components are installed with activation of Developer Sandboxes, including tables and user roles. * **[Properties installed with Developer Sandboxes](https://www.servicenow.com/docs/ujR5z8JZfFyODf5sWHowMw)** The system properties available in Developer Sandboxes govern application behavior, enabling developers to configure and optimize their testing environments effectively.