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

# Deployment models

> Run AgentFlow where your data and governance require: SaaS, your cloud, your VPC, or your own Kubernetes.

export const DocMeta = ({type, applies, owner}) => {
  const LABELS = {
    tutorial: "Tutorial",
    "how-to": "How-to guide",
    explanation: "Explanation",
    reference: "Reference"
  };
  return <div className="e6-meta">
      <span className={type === "how-to" || type === "tutorial" ? "e6-eyebrow" : "e6-eyebrow e6-eyebrow--quiet"}>{LABELS[type] || type}</span>
      {applies ? <span>Applies to: {applies}</span> : null}
      {owner ? <span>Owner: {owner}</span> : null}
    </div>;
};

<DocMeta type="explanation" applies="All deployments · for operators" />

AgentFlow runs where your data and your governance say it has to run. The same components deploy everywhere; identity, storage, ingress, telemetry and model-provider settings change by environment.

<Tabs>
  <Tab title="SaaS">
    e6data operates the deployment. You connect your data sources and use the product with the lowest operational burden.
  </Tab>

  <Tab title="BYOC">
    **Bring your own cloud.** The AgentFlow control plane runs in your cloud account. It can use your identity, networking, storage, telemetry and model-provider configuration.
  </Tab>

  <Tab title="In-VPC">
    AgentFlow runs inside your VPC or VNet, with ingress and egress controlled by you. Updates are delivered through the deployment process agreed for that environment.
  </Tab>

  <Tab title="On-prem">
    AgentFlow runs on private Kubernetes infrastructure, including on-premises and hybrid environments. S3-compatible storage such as MinIO can provide the object store.
  </Tab>

  <Tab title="Other clouds">
    The architecture is portable across supported Kubernetes environments, including sovereign and non-hyperscaler clouds. Storage, identity, ingress and managed-service choices vary by platform.
  </Tab>
</Tabs>

## What every deployment needs

* Kubernetes, for the API gateway, worker pods, sandbox pods and cron triggers (a local Compose profile runs without Kubernetes, but without cron triggers)
* Durable storage: S3-compatible storage, Azure Blob Storage, or PostgreSQL for product storage
* Redis, for live coordination
* At least one [model provider](/agentflow/operate/models)
* An e6data cluster

See [Architecture](/agentflow/concepts/architecture) for how these fit together, and [Before you begin](/agentflow/get-started/before-you-begin) for the setup checklist.


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