> ## 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.

# Self-Hosting Options

> Compare the three Serval self-hosting delivery models — Hybrid, Managed in Your AWS, and Self-Managed on Your Kubernetes — and learn how to get access to deployment instructions.

# Self-Hosting Options

Serval supports three delivery models when you run it in your own infrastructure. The two axes that actually differ between them are (1) **what you bring** — a Linux host, an AWS account, or a Kubernetes cluster — and (2) **who operates it** — Serval, your team, or (on AWS) either, your choice. Pick the model that matches both. This page is the starting point for evaluation; step-by-step deployment instructions are [shared with customers](/sections/self-hosting/request-access) during onboarding.

<Info>
  Most organizations should start with **Hybrid Self-Hosted** (smallest footprint, fastest setup). Choose a fully self-hosted model when regulatory, data-residency, or air-gap requirements demand that the entire application runs in your environment.
</Info>

## The three delivery models

<CardGroup cols={3}>
  <Card title="Hybrid Self-Hosted" icon="shield-check" color="#845FF2" href="/sections/self-hosting/hybrid">
    You run only the Serval **worker** in your infrastructure. Serval operates the backend in Serval Cloud. Integration credentials stay on your worker and are never shared with Serval. Smallest footprint, fastest to set up.
  </Card>

  <Card title="Managed in Your AWS" icon="sparkles" href="/sections/self-hosting/serval-managed-overview">
    The **full Serval application** runs single-tenant in an AWS account you own, operated by your team or by Serval — your choice. Your AWS credentials never leave your environment.
  </Card>

  <Card title="Self-Managed on Your Kubernetes" icon="server" color="#3D3D3D" href="/sections/self-hosting/self-managed-prerequisites">
    The **full Serval application** runs on a Kubernetes cluster your team operates. You install the public Serval Helm chart from OCI and own day-2 operations. You bring the cluster; you run it.
  </Card>
</CardGroup>

## Comparison

|                                   | Hybrid Self-Hosted                         | Managed in Your AWS                                          | Self-Managed on Your Kubernetes             |
| --------------------------------- | ------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------- |
| **What you bring**                | A Linux host for the worker                | A supported AWS account you own                              | A Kubernetes cluster (any cloud or on-prem) |
| **Who operates it**               | Serval (backend) + your team (worker host) | Your choice — your team or Serval                            | Your team                                   |
| **What runs in your environment** | Worker only                                | Full application stack                                       | Full application stack                      |
| **Where app data lives**          | Serval cloud                               | Your AWS account                                             | Your cluster                                |
| **Tenancy**                       | Shared control plane, isolated worker      | Single-tenant                                                | Single-tenant                               |
| **Upgrades**                      | Automatic                                  | Applied in your account, by your chosen operator             | Your team runs `helm upgrade`               |
| **Setup time**                    | Hours                                      | Days (onboarding)                                            | Hours to days                               |
| **Kubernetes expertise required** | Basic                                      | Minimal if Serval-managed; working knowledge if self-managed | Intermediate to advanced                    |

## Does Serval need to reach private resources?

If Serval needs to talk to systems on your internal network — on-prem Active Directory, internal LDAP, self-hosted GitLab, internal APIs, etc. — the connectivity story differs per model. The [Private Network Access](/sections/self-hosting/private-network-access) page walks through the options for each.

## Evaluating Serval self-hosting

Use these pages while you decide which model fits:

<CardGroup cols={2}>
  <Card title="Hybrid Self-Hosted — overview" icon="shield-check" href="/sections/self-hosting/hybrid">
    How Hybrid works, what runs where, prerequisites, and when to pick it over the fully self-hosted options.
  </Card>

  <Card title="Compare the fully self-hosted options" icon="route" href="/sections/self-hosting/deployment-models">
    Managed in Your AWS vs. Self-Managed on Your Kubernetes, side by side.
  </Card>

  <Card title="Managed in Your AWS — overview" icon="sparkles" href="/sections/self-hosting/serval-managed-overview">
    The operating modes (self-managed or Serval-managed) and what your team supplies either way.
  </Card>

  <Card title="Self-Managed on Your Kubernetes — prerequisites" icon="list-check" href="/sections/self-hosting/self-managed-prerequisites">
    What your Kubernetes platform must provide before you install 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 (on-prem AD, internal GitLab, etc.).
  </Card>
</CardGroup>

## Ready to deploy?

Detailed installation steps, configuration references, integration setup, and operational runbooks live in a password-protected area of this site, which we share with customers and teams working through onboarding.

<Card title="Deployment instructions" icon="book-open" href="/sections/self-hosting/request-access">
  Installation, configuration, integration setup, and day-2 operations for Serval self-hosting.
</Card>