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

# Choose a Delivery Model

> Compare the two fully self-hosted delivery models — Managed in Your AWS and Self-Managed on Your Kubernetes — side by side.

# Choose a Delivery Model

If you want to run the full Serval application inside your own infrastructure, you have two delivery models. They differ in **what you bring**: an AWS account, or a Kubernetes cluster.

1. **Managed in Your AWS** — you provide an AWS account you own; Serval provides a standard Terraform + Helm bundle that stands up the full stack on AWS services (EKS, Aurora, ElastiCache, OpenSearch, S3). You separately choose **who operates it** — your team (self-managed) or Serval (Serval-managed); see [Managed in Your AWS](/sections/self-hosting/serval-managed-overview) for that choice. **Lower operational burden** than Kubernetes either way.
2. **Self-Managed on Your Kubernetes** — you provide a Kubernetes cluster (any cloud or on-prem) and your team installs the public Serval Helm chart directly, owning installs, upgrades, and day-2 operations. Always self-managed — there is no Serval-operated option on this path. **Highest operational burden** — intended for non-AWS, on-prem, or platform-team-mandated environments.

<Warning>
  Self-Managed on Your Kubernetes is *more* work than Managed in Your AWS, not less — regardless of which operator you'd choose on AWS. In addition to running Serval, your team is responsible for the cluster itself, ingress, PostgreSQL/Redis/Temporal, monitoring, backups, upgrades, and on-call. Pick this model only when a hard constraint (non-AWS, on-prem, or an existing platform mandate) rules out Managed in Your AWS.
</Warning>

<Info>
  This page compares the two **fully self-hosted** delivery models. If you are still deciding between Hybrid and fully self-hosted, start at [Self-Hosting Options](/sections/self-hosting/index).
</Info>

<Note>
  Regardless of which delivery model you choose, fully self-hosted deployments must provision their own OAuth apps (Slack, Microsoft, GitHub, Google Workspace, etc.) with each integration provider. See [Integrations Overview](/sections/self-hosting/deployment/integrations/index) for the full list and per-app setup guides.
</Note>

<CardGroup cols={2}>
  <Card title="Managed in Your AWS" icon="sparkles" href="/sections/self-hosting/serval-managed-overview">
    Recommended for most organizations that want the full application in their own cloud, standardized on AWS. You choose whether your team or Serval operates it — same deployment either way.
  </Card>

  <Card title="Self-Managed on Your Kubernetes" icon="server" href="/sections/self-hosting/self-managed-prerequisites">
    For non-AWS, on-prem, or platform-team-mandated environments. Highest operational burden — your team owns the cluster, datastores, ingress, monitoring, backups, upgrades, and on-call in addition to running Serval.
  </Card>
</CardGroup>

## Side-by-side comparison

|                                     | Managed in Your AWS                                                                                                                          | Self-Managed on Your Kubernetes                                    |
| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| **What you bring**                  | A supported AWS account you own                                                                                                              | A Kubernetes cluster (any cloud or on-prem)                        |
| **Who operates it**                 | Your choice — your team (self-managed) or Serval (Serval-managed); see [Managed in Your AWS](/sections/self-hosting/serval-managed-overview) | Always your team                                                   |
| **Deployment method**               | Serval's Terraform + Helm bundle, standardized on AWS services                                                                               | Public Serval Helm chart, on your own cluster                      |
| **Tenancy**                         | Single-tenant in your environment                                                                                                            | Single-tenant in your environment                                  |
| **Cloud flexibility**               | AWS only                                                                                                                                     | Any cloud or on-prem                                               |
| **Operational burden on your team** | Low if Serval-managed, moderate if self-managed — either way, less than owning a Kubernetes platform from scratch                            | High — your team owns all platform ops                             |
| **Best fit**                        | Most fully self-hosted customers                                                                                                             | Non-AWS, on-prem, or platform-team-mandated only                   |
| **Primary prerequisite**            | Supported AWS account                                                                                                                        | Existing Kubernetes cluster + Helm + a platform team to operate it |

<Tip>
  Most organizations evaluating full self-hosting should choose **Managed in Your AWS**, self-managed or Serval-managed. Self-Managed on Your Kubernetes is *more* total work, not less — only pick it when a hard requirement (non-AWS, on-prem, or an existing platform-team mandate) rules it out.
</Tip>

## Next steps

<CardGroup cols={2}>
  <Card title="Managed in Your AWS — overview" icon="sparkles" href="/sections/self-hosting/serval-managed-overview">
    Review the operating modes and what runs in your account.
  </Card>

  <Card title="Self-Managed on Your Kubernetes — prerequisites" icon="list-check" href="/sections/self-hosting/self-managed-prerequisites">
    Prepare your Kubernetes platform before installing the Helm chart.
  </Card>

  <Card title="Private network access" icon="network-wired" href="/sections/self-hosting/private-network-access">
    Options for letting Serval reach resources on your internal network.
  </Card>
</CardGroup>