> ## Documentation Index
> Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connected runtime

> How connected runtimes execute agent runs through registered services or workers.

A connected runtime is a registered service or worker.

It executes agent runs and streams events back to the control plane.

## Use this for

| Work                   | Needs                                      |
| ---------------------- | ------------------------------------------ |
| External agent service | Run agents outside managed server runtime. |
| Worker pool            | Accept agent runs from the control plane.  |
| Private runtime        | Keep execution inside your infrastructure. |

## What it reports

| Area            | Role                                   |
| --------------- | -------------------------------------- |
| Agent execution | Runs the selected agent and tools.     |
| Event streaming | Sends run events to the control plane. |
| Runtime health  | Reports whether it can accept work.    |

## How it fits

The control plane owns durable run state.

Connected runtimes execute selected runs.

They do not own run identity, lineage, replay, resume, or cancellation.

## Related concepts

| Concept                                          | Explains                                                        |
| ------------------------------------------------ | --------------------------------------------------------------- |
| [Runs and events](/cloud/runs-and-events)        | How Veryfront tracks agent, job, and workflow execution.        |
| [Server runtime](/cloud/concepts/server-runtime) | How server runtimes host app routes and agent runtime services. |