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

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Managing app development using the App Engine Management Center

# Managing app development using the App Engine Management Center {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Track and manage your App Engine Studio (AES) and Creator Studio 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.
AEMC uses Pipelines and Deployments to deploy applications through different instances. Pipelines and Deployments uses the Application Repository to manage these deployments. For more information, see [ServiceNow application repository](https://www.servicenow.com/docs/4BrGoeWoYiLCQ1rB_jlz6A "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.").

Each application can either be deployed using the Application Repository or System Update Sets. If you've used Update Sets in the past, but want to switch to using the Application Repository, you can do a one-time conversion to deploy the app using the Application Repository instead. All apps don't have to follow the same deployment. For more information, see [Convert custom applications to upgrade from the application repository](https://www.servicenow.com/docs/MiuKMWTwJMqKAsIhXN8sFQ "When your applications are placed in the Custom Applications table [sys_app], you can't upgrade them directly through the Application Repository. This procedure helps you do a one-time conversion when you want to migrate deploying your applications using the Application Repository.") and [System update sets](https://www.servicenow.com/docs/uzXA7b9PTrhvUpjPOjguxw "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.").

## Additional resources for App Engine Management Center

{#monitor-requests-using-aemc__table_h24_rr5_gwb__entry__2}

| Learn more about App Engine Management Center | ServiceNow resources |
|-|-|
| Although you can use AEMC in any instance, for full functionality, you must install AEMC in the production instance. You must also set up the deployment pipelines with the controller instance in production. For more information, see [Configure Pipelines and Deployments](https://www.servicenow.com/docs/xaOwha2xJg01VCJtLzcGog "Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation."). | [Govern low-code app development at scale with App Engine Management Center](https://www.youtube.com/watch?v=G-PcrtXs6GI) |
| Although you can use AEMC in any instance, for full functionality, you must install AEMC in the production instance. You must also set up the deployment pipelines with the controller instance in production. For more information, see [Configure Pipelines and Deployments](https://www.servicenow.com/docs/xaOwha2xJg01VCJtLzcGog "Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation."). | [Creator toolbox \| App Engine Management Center](https://www.youtube.com/watch?v=fDvEqAQIHzQ) |
| Although you can use AEMC in any instance, for full functionality, you must install AEMC in the production instance. You must also set up the deployment pipelines with the controller instance in production. For more information, see [Configure Pipelines and Deployments](https://www.servicenow.com/docs/xaOwha2xJg01VCJtLzcGog "Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation."). | [Govern low-code app development at scale with App Management Center](https://www.servicenow.com/demo/demonow-detail.html?videoid=govern-lowcode-app-development) |
[ ]

{#monitor-requests-using-aemc__table_h24_rr5_gwb}

## Navigating AEMC {#monitor-requests-using-aemc__section_wrl_snj_bvb}

From the AEMC Overview screen, you can navigate to four
additional views: Requests, Pipelines, Custom apps, and Developers by selecting icons in the
primary navigation bar.  
{#monitor-requests-using-aemc__table_y5k_cl3_wtb__entry__2}

| Page | Description |
|-|-|
| Overview | High-level view of all intake, app, collaboration, and deployment requests, with a graph showing new requests of each type over the last 90 days. You can also see a high-level view of your pipelines and application metrics. |
| Requests | Full list of each request type broken down by approval status. |
| Pipelines | High-level view of the number of open deployment requests in each instance and within each pipeline. Selecting a pipeline or an environment in a pipeline displays all active deployment requests. Note: If you view deployment requests in a production instance, all Closed - Published deployment requests for that environment are listed. |
| Custom apps | Charts and graphs illustrating the status of your active applications, and a list of all custom apps in development or production. You can view details for individual apps, including usage information, deployment history, and collaborators. |
| Developers | Charts and graphs illustrating total and active developers, as well as developers by department. You can view details for individual developers, including the apps for which they are collaborators and their request history. |
[Table 1. AEMC primary navigation bar]

{#monitor-requests-using-aemc__table_y5k_cl3_wtb}
* **[Managing requests using AEMC](https://www.servicenow.com/docs/CNr38Jueu1EUjrbWYXKEog)**   
  You can track and approve or reject Intake, App, Collaboration, and Deployment requests using the App Engine Management Center (AEMC).
* **[Managing deployments using pipelines in AEMC](https://www.servicenow.com/docs/OnEht6Xjla_SvdijH3UMLQ#manage-deployments-using-aemc)**   
  Manage applications at all stages of deployment, view multiple pipelines, and approve or reject deployment requests using the App Engine Management Center (AEMC).
* **[Managing custom apps using AEMC](https://www.servicenow.com/docs/lqaI79Hiv1aDOOItXJNGJA)**   
  Review custom app metrics and manage apps through the development life cycle using the App Engine Management Center (AEMC).
* **[Managing developers using AEMC](https://www.servicenow.com/docs/c368YK2qIKdA50OimqIU~g)**   
  View details about developers working on apps in App Engine Studio and Creator Studio using App Engine Management Center (AEMC).

