---
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


---

# App Engine Studio and Build Agent feature comparison

# App Engine Studio and Build Agent feature comparison {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
App Engine Studio (AES) and Build Agent differ across interface, artifact scope, scripting access, application scope, and governance. Use this feature comparison to understand what changes when you migrate to Build Agent.
{#aes-vs-ba-feature-comparison__table_ulf_1pw_3kc__entry__3}

|   | App Engine Studio (AES) | Build Agent in ServiceNow Studio |
|-|-|-|
| Primary interface | Guided wizard interface | Conversational prompt interface inside ServiceNow Studio |
| Developer persona | Citizen and low-code developers | All developer experience levels, from citizen to pro-code |
| Artifact types | Tables, forms, flows, and workspaces within wizard constraints | Full platform set of artifacts: business rules, Script Includes, Client Scripts, flows, ACLs, UI Builder pages, packaging, and README |
| Script access | Not directly available. Requires converting to ServiceNow Fluent and opening app in an integrated development environment (IDE) | Built-in script writing and reading |
| Application scope | Scoped applications only | Scoped and global applications |
| Existing application modification | Applications you created only | Any application, including base system applications |
| Session context | Stateless | Persistent within a session and accumulates over the course of a session |
| External integrations at build time | None | Model Context Protocol Server Console (MCP) client connections. For a full list of MCP connections, see [MCP connections and Build Agent](https://www.servicenow.com/docs/XeTSglNnJJCAFVdvLp0rRA "MCP connections enable Build Agent to access external tools and resources through standardized communication. Use these connections to integrate third-party applications like Figma for accelerated design-to-development workflows.") |
| Governance | App Engine Management Center (AEMC) optional deployment path | Several deployment options, including App Engine Management Center (AEMC). See[Deploying what you built with Build Agent](https://www.servicenow.com/docs/rb~KixtWZ4aRbYjEU6knkA "Learn about deployment methods and workflows for moving applications created with Build Agent from development to production environments. Choose the right deployment approach based on your application complexity and organizational requirements.") |
| AI capability embedding | Manual post-build step | In-app AI agents and skills can be embedded in workflows at build time |
[Table 1. AES and Build Agent feature comparison]

{#aes-vs-ba-feature-comparison__table_ulf_1pw_3kc}

## What does not change {#aes-vs-ba-feature-comparison__section_what_does_not_change}

The following remain consistent across both tools:

* App files built in AES are already accessible in ServiceNow Studio. No re-creation or export is required.
* Workflow Studio flows created in AES are the same records in ServiceNow Studio.
{#aes-vs-ba-feature-comparison__ul_vlf_1pw_3kc}