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

# Deployment

> Plan an Oximy rollout around the problem you need to solve and the trust boundaries you choose.

Oximy does not require an all-at-once rollout. Products and collection sources can be introduced independently while sharing the same platform foundation.

## Choose a hosting model

<Tabs sync={false}>
  <Tab title="Oximy Cloud" icon="cloud">
    The control plane and data plane run in Oximy Cloud.
  </Tab>

  <Tab title="Customer VPC" icon="server">
    The deployment runs in a customer-controlled virtual private cloud.
  </Tab>

  <Tab title="Hybrid" icon="cloud-cog">
    The control plane runs in Oximy Cloud and the data plane runs in the customer’s cloud.
  </Tab>
</Tabs>

Continue to [Architecture](/docs/platform/architecture) for the system boundaries behind each model.

## Deployment sequence

<Steps>
  <Step title="Select the hosting boundary">
    Choose Oximy Cloud, Customer VPC, or hybrid based on where the control plane and data plane must run.
  </Step>

  <Step title="Choose products and data paths">
    Deploy the products and components required for the organization’s starting point.

    | Component               | Purpose                                                    |
    | ----------------------- | ---------------------------------------------------------- |
    | First-party integration | Official account, seat, usage, and billing data            |
    | Endpoint agent          | Organization-managed attribution across endpoint traffic   |
    | Browser extension       | Visibility into supported web AI activity                  |
    | Local collector         | Local coding, agent, skill, and MCP activity               |
    | Relay gateway           | OpenAI-compatible request routing                          |
    | Relay observe mode      | Traffic measurement without changing the request path      |
    | Relay route-only mode   | Routing decisions executed by your infrastructure          |
    | Sidekick workspace      | Shared AI threads, tools, artifacts, memory, and execution |
  </Step>

  <Step title="Connect identity and policy">
    Connect the workspace to the relevant organization structure and decide who can administer products, view activity, manage providers, approve access, and change policy.

    Review capture, content, redaction, retention, and regional requirements before expanding collection.
  </Step>

  <Step title="Roll out by scope">
    Begin with a defined team, traffic source, integration set, or product. Add departments, traffic, integrations, or products deliberately, with owners for administration, security review, data quality, and business outcomes.
  </Step>
</Steps>

<Info>
  Visibility, Sidekick, and Relay are generally available. The exact hosting and integration configuration is selected for each customer environment.
</Info>