---
sourceDocument: Brazil Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# ServiceNow Arc architecture

# ServiceNow Arc architecture {#ariaid-title1}

Release version: Brazil  
Updated September 22, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
ServiceNow Arc separates the client, the agent host, and an isolated sandbox so that planning happens on the host and agent commands run inside a container with its own network policy. Arc runs on the desktop and connects to your ServiceNow instance, which governs what Arc can do.

The high level architecture has three layers: the ServiceNow instance, Arc, which governs Arc based on the policy defined, the Arc desktop application, which runs tasks; and the connected systems that Arc works with.

## ServiceNow instance {#cowork-architecture__cowork-architecture-servicenow-instance}

The ServiceNow instance governs Arc, logs its activity, and provides access to your data.

AI Control Tower manages policy and auditing, for Arc when needed. It syncs policies to Arc and registers each Arc installation. Each installation sends AI Control Tower a periodic heartbeat, so AI Control Tower can show which
installations are active and healthy. Administrators can use the kill switch in AI Control Tower to stop Arc from taking further actions. For more information, see [AI Control Tower](https://www.servicenow.com/docs/GtzcVtTj4bnKFuufQ7ld1A "Gain visibility into your organization's AI footprint, manage the lifecycle of AI investments, govern risk and compliance, and measure the business impact of AI with AI Control Tower.").

Generative AI Controller (GAIC) logs every LLM (large language model) call that Arc makes. User initiated requests consume assists and are recorded in the Generative AI Log under the feature name ServiceNow Arc Execution. Requests that Arc makes on its own, such as evaluating actions in Auto mode, don't consume assists. For more information, see [Exploring Generative AI Controller](https://www.servicenow.com/docs/uXIVGLX_mnXAPdsZCiqh3Q "Learn how Generative AI Controller works as the control and visibility layer for all generative AI requests across your ServiceNow applications, what it controls, and how it integrates with third-party LLM providers.").

Data and System of Action provides access to records, automation, and agents. Arc reaches these resources through Action Fabric, the interface that connects Arc to ServiceNow data and actions. For more information, see .

## ServiceNow Arc desktop application {#cowork-architecture__cowork-architecture-cowork}

ServiceNow Arc runs on the user's desktop and has two main parts: the Arc runtime and the secure sandbox.

The Arc runtime includes the agent loop, sub-agents, skills, and memory. The agent loop plans a task, runs each step, checks the result, and adjusts when a step
fails. Skills and connectors extend what Arc can do, and memory stores preferences, decisions, and context across sessions.

The secure sandbox is an isolated environment on the device where tool execution, connectors, and the LLM client run under policy control. The LLM client sends requests to the large language model. Connectors run only when AI
Control Tower policy allows them, so every action stays within the limits your administrator sets.

## Connected systems {#cowork-architecture__cowork-architecture-connected-systems}

Users provide a task to Arc through chat. Arc uses its connectors to gather context and take action in connected systems, including Slack, Microsoft 365, GitHub, Model Context Protocol (MCP) endpoints, and the ServiceNow instance. The same policy managed connectors handle both incoming work and outgoing actions.  
Arc runs tasks on the user's desktop. The Arc runtime, memory, and tool execution stay on the device. Some data leaves the device:

* Requests from the LLM client to the large language model, which GAIC logs
* Policy sync and registration with AI Control Tower
* Data that connectors send to connected systems
{#cowork-architecture__ul_s55_tfk_skc}