---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/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


---

# Supported ServiceNow AI Platform features

# Supported ServiceNow AI Platform features in Developer Sandboxes {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Developer Sandboxes supports almost all development-related ServiceNow AI Platform features.

## Development features and apps {#dev-sbx-supported-features__section_pk3_c4r_jhc}

Supported features include the following:

* Metadata updates
* System Update Sets
* Legacy source control  
  Note:  
  Each sandbox can connect to source control with its own git branch. For more information, see [Source control and Developer Sandboxes](https://servicenow-prod.fluidtopics.net/y~WASxZ1VxWQrZAIauSFKQ "Use source control with Developer Sandboxes to enable parallel development and prevent merge conflicts.").
* ServiceNow IDE
* Workflow Studio
* App and plugin installation  
  Note:  
  Apps and plugins can be installed and upgraded in a sandbox independently.
* Outgoing integrations  
  Note:  
  Incoming integrations must be manually updated by customers to support the unique URLs of sandboxes.
{#dev-sbx-supported-features__ul_f4n_snr_jhc}

## Sandbox considerations and limitations {#dev-sbx-supported-features__section_spb_d4r_jhc}

Upgrading an instance automatically backs up update sets to the base instance and recreates the sandboxes on that instance. Sandboxes are recreated in a base state, so you must restore backed up update sets. For details, see [Cloning and upgrading considerations for Developer Sandboxes](https://servicenow-prod.fluidtopics.net/RgastIyV7MfytBs4ckus5g "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.").{#dev-sbx-supported-features__dsb-restore-update-sets}  
Note:  
Sandboxes are not automatically recreated after a clone. You should save your work from a sandbox before the clone so you can recreate it.

You can have up to 30 sandboxes per 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.