---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Deployment

# Vibe coding, AI-assisted development, and deployment {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

After you generate and expand an app on the ServiceNow AI Platform, the deployment process is tightly integrated into the workflow.

## Workflow for deploying an AI-developed app {#vc-and-deployment__section_m1h_4ch_phc}

After development, review, and testing are complete, a typical deployment workflow includes the following steps:

1. Collaborative design: Business owners and IT collaborate on requirements and ideas using their preferred tools.
2. AI-driven app development: Now Assist and Build Agent process files, chat history, and diagrams to generate and implement app updates.
3. Review and testing: Teams preview updates, make revisions, and run rounds of performance and readiness testing.
4. Developer review: A developer reviews the AI-generated changes, compares versions, and confirms the changes are ready for deployment.
5. Deployment approval: The project is handed off to a deployment manager, who initiates the deployment approval process.
6. Autonomous checks: AI agents automatically scan for issues (such as sensitive data exposure or model integrity problems) and remediate them before deployment.
7. Final deployment: After all readiness scans and approvals, the new app is deployed securely and efficiently.
{#vc-and-deployment__ol_a3z_nch_phc}

## Deployment options {#vc-and-deployment__section_iyw_y25_yhc}

Build Agent supports the following deployment methods for vibe-coded and AI-developed apps:

* Git-based source control integration with ServiceNow IDE: ServiceNow supports Git-based workflows for version control and CI/CD.
  * You can push scoped apps to Git repositories, enabling branching, merging, and automated deployments. ServiceNow IDE supports bring-your-own Git integration, such as GitHub or Bitbucket.
  * For more information, see [Integrating source control with the ServiceNow IDE](https://servicenow-prod.fluidtopics.net/QZMhQAn7azbu97bVfuiB8Q "Integrate with remote Git repositories to manage applications in source control with the ServiceNow IDE.").
  {#vc-and-deployment__ul_mpd_rch_phc}
* Update sets and application packaging: Standard ServiceNow deployment uses System Update Sets to track changes.
  * Advanced guidance includes packing update sets into scoped applications for easier transport and installation across instances, for example using Application Repository (AppRepo).
  * For more information on System Update Sets, see [System update sets](https://servicenow-prod.fluidtopics.net/2n0mjX_i1izL9pTdrKeFbQ "An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.").
  {#vc-and-deployment__ul_phq_qf5_yhc}
{#vc-and-deployment__ol_bmr_ff5_yhc}

## Workflows for moving apps through higher instances {#vc-and-deployment__section_jkf_pch_phc}

After you create an app using Build Agent, you have several options to move the app to the test instance.

1. Wrap the entire scoped application in an update set. The workflow is as follows:
   1. Go to the Custom Applications list, select an app and swap to its scope.
   2. Convert the app to AppRepo.
   3. Publish the update set with demo data.
   4. Put the update set in a deployment request for ReleaseOps, or follow your standard update set process for deployment.
   {#vc-and-deployment__ol_wjc_vp5_yhc}
2. Publish the app to AppRepo:
   * You can use a Git-based process or update sets to publish to AppRepo.
   * Scoped apps, as well as apps that are ready for testing, can be published to the AppRepo for distribution across environments.
   * After an app is in AppRepo, you can move it through a ReleaseOps pipeline. If ATF tests are included in the pipeline, they automatically run.
   * Register and entitle apps before publishing.
   * For more information on Application Repository, see [ServiceNow application repository](https://servicenow-prod.fluidtopics.net/apKZle1m7VYjJA7qSzDrAQ "After you develop and test a custom application, you can make the application available to company instances by publishing it to the ServiceNow application repository.").
   {#vc-and-deployment__ul_npd_rch_phc}
{#vc-and-deployment__ol_y4b_2g5_yhc}

## Additional deployment tools and capabilities {#vc-and-deployment__section_l4n_pq5_yhc}

The ServiceNow AI Platform has additional deployment tools that include the following tools:

* App Engine Management Center (AEMC):
  * After developing an app, submit it to AEMC for governance checks.
  * AEMC validates ACLs, roles, and compliance settings before deployment.
  * Use ReleaseOps pipelines to move apps through environments with ATF tests and approval gates.
  * AEMC provides dashboards for monitoring deployments and managing app versions throughout the lifecycle.
  * For more information on AEMC, see [Using the App Engine Management Center](https://servicenow-prod.fluidtopics.net/IqQeu4LCrHWVOfzB3mbdjA "Track and manage your requests, deployments, applications, and collaborative developers using the App Engine Management Center (AEMC) in your production instance. Additionally, AEMC allows admins to manage app development from intake through production.").
  {#vc-and-deployment__ul_m4n_pq5_yhc}
* ReleaseOps:
  * Move changes from development to production through multiple instances using customizable playbooks.
  * Automate preview, commit, and validation of update sets before deployment.
  * Run Automated Test Framework (ATF) tests as part of the pipeline to validate quality.
  * Deploy changes immediately or schedule releases for controlled rollouts.
  * Enforce checks, scans, and approvals before production deployment.
  * For more information on ReleaseOps, see [ReleaseOps](https://servicenow-prod.fluidtopics.net/al3hlKK44SVWAPJk1IOg8A "ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production.").
  {#vc-and-deployment__ul_zpy_gdh_phc}
* ServiceNow SDK:
  * Use the ServiceNow SDK to move applications to and from your instance to your local machine. You can integrate the ServiceNow SDK with your off-instance CI/CD process if you have one.
  * Install the ServiceNow SDK locally and use the command line interface (CLI).
  * Authenticate to a ServiceNow instance from the ServiceNow SDK.
  * Push to or install an application on the authenticated instance from your local environment.
  {#vc-and-deployment__ul_mwp_w3g_k3c}
* Automated Test Framework (ATF)
  * Tests can be generated by Build Agent and executed in ServiceNow Studio or ServiceNow IDE to confirm functionality after changes.
  * For more information on ATF, see [Automated Test Framework (ATF)](https://servicenow-prod.fluidtopics.net/x4Tg~gX3EeFqtF9ohWlMNQ "The Automated Test Framework (ATF) enables you to create and run automated tests to confirm that your instance works after making a change. For example, after an upgrade, during application development, or when deploying instance configurations with update sets. Review failed test results to identify the changes that caused the failure and the changes that you should review.").
  {#vc-and-deployment__ul_ppd_rch_phc}
{#vc-and-deployment__ul_mwj_rch_phc}