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

# Deployment

> Choose Checkfu-managed or customer-operated Cloudflare deployment.

Checkfu runs on Cloudflare. Choose who operates the installation:

| Deployment | Who operates it |
| - | - |
| Checkfu-managed | Checkfu operates the installation. You configure your Workspace, Agents, Environments, and Sessions. |
| Customer-operated | You operate the same product in your Cloudflare account, including installation, upgrades, recovery, and its external dependencies. |

A customer-operated installation retains PostgreSQL and explicitly selected
external dependencies. Owning the Cloudflare account does not replace those
dependencies or transfer their operation to Checkfu.

## Choose execution capabilities separately

An [Environment](/concepts/work-environments) describes execution requirements.
A [Computer](/concepts/computer-and-screens) provides a persistent machine
identity. Code, browser, desktop, and continuity capabilities depend on the
selected environment; deployment ownership alone does not select them.

## Choose an agent engine

Select a [Harness](/concepts/harnesses-and-models) explicitly; there is no default.
[Bring your own harness](/guides/bring-a-custom-harness) (BYOH) chooses the agent
engine. Bring your own key (BYOK) chooses model access. These choices are
independent of who operates the Cloudflare installation.

A supported [ConnectedRuntime](/guides/connect-a-local-agent) attaches an
operator-owned process to Checkfu. It is a separate execution choice, not a
third deployment model. BYOH does not require an arbitrary third-party sandbox
or public Runner setup.

See [Billing](/concepts/billing-and-platform-supply) for usage and charges across
these choices.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.