--- sourceDocument: Zurich Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Installing # Installing Developer Sandboxes {#ariaid-title1} * Release version: Zurich * * Updated July 23, 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 paid ServiceNow feature that enables developers to work in isolated, instance-specific sandbox environments. Installing Developer Sandboxes requires coordination with your ServiceNow account team and Now Support. This feature is designed to be installed on production or clone source instances to maintain entitlement consistency during cloning. Show full answer Show less ## Installation Prerequisites and Process * **Entitlement Check:** Verify you have purchased Developer Sandboxes entitlements, which come in packs of 10 sandboxes. * **Instance Requirements:** Must be a non-production instance running on ADCv3 (Application Delivery Controller version 3) or higher (Yokohama or newer). Instances not on ADCv3 will be upgraded during setup. * **Sandbox Allocation:** Sandboxes are instance-specific and hosted on separate app-nodes. Each sandbox requires an additional node, so, for example, 10 sandboxes require 10 new nodes on the instance. * **Splitting Packs:** If multiple packs are purchased, they can be allocated across different instances, but each instance must have a minimum of 10 sandboxes (one full pack). * **Self-hosted Instances:** Developer Sandboxes do not support self-hosted instances by default, though custom networking and routing can enable support. ## Post-Purchase Steps * Open a case with Now Support to request installation, specifying the instance name and licensed number of sandboxes. * For regulated environments, consult ServiceNow Support for additional guidance. * Now Support will complete the installation and configuration based on your entitlements. ## Single Sign-On (SSO) Configuration Developers can access sandboxes using either instance credentials or SSO. To enable SSO for sandboxes, set these properties in the base instance before usage: * Disable ACR (Authentication Context Class Reference): **glide.sso.acr.enable = false** * Enable multi-SSO: **glide.authenticate.multisso.enabled = true** ## Key Takeaways for ServiceNow Customers * Developer Sandboxes provide isolated development environments that require purchased entitlements and support from ServiceNow Support for installation. * Ensure your instance meets ADCv3 requirements and plan capacity for the additional app-nodes needed per sandbox. * Coordinate with Now Support to allocate sandbox packs appropriately across instances, respecting minimum pack sizes. * Configure SSO settings in your base instance to enable seamless developer access to sandboxes. 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/JLFYPzvdOg1qhalW8m6L4A "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 the 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} ## 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. 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 on sandboxes and instances, see [General guidelines and use cases for Developer Sandboxes](https://www.servicenow.com/docs/gFjzXbZFzfHsPr8Q4HBGBg "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. ## Enabling SSO {#dev-sbx-installing__section_qr2_z4h_lgc} Developers can access sandboxes using instance credentials as well as 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}