Skip to main content

​
Managed in Your AWS

In this delivery model, you bring an AWS account you own and the full Serval application runs single-tenant inside it. The application runtime and all customer data remain in that account, and your AWS credentials never leave your environment. The deployment is operated either by your own team (self-managed) or by Serval (Serval-managed).
Fully self-hosted and single-tenant. The application runtime and customer data live only in your AWS account. You choose whether your team operates the deployment or Serval operates it for you; the deployment is the same in both cases.

​
Operating the deployment

The operator — your team in self-managed, or Serval in Serval-managed — is responsible for:
  • Infrastructure provisioning for the supported self-hosted stack inside your AWS account
  • Application installation and upgrades
  • Baseline monitoring and operational work
  • Applying each new Serval release inside the AWS account

​
How it works

  • Versioned releases. Serval publishes each new version as a versioned release.
  • Applied in your account. The operator applies the release inside your AWS account; your AWS credentials never leave your environment.
  • Onboarding. Serval provides the deployment definition, a configuration reference, and setup scripts during onboarding.

​
Self-managed deployments

If your team operates the deployment, Serval provides a deployment bundle — Terraform intended for AWS, along with Kubernetes/Helm configuration and setup scripts — that stands up the full stack. It builds on standard AWS services, including:
  • Amazon EKS — the Kubernetes platform
  • Amazon Aurora (PostgreSQL) — application databases
  • Amazon ElastiCache and Amazon OpenSearch — cache and search
  • Amazon S3 — object storage
  • AWS Secrets Manager — application secrets
Align with the provided configuration as much as possible. Serval ships a standard bundle of Terraform, Kubernetes/Helm, and setup scripts, and can walk your team through applying it in a dedicated setup session. The deployment is designed, tested, and supported against that standard configuration.You can point the deployment at your own external services — your own PostgreSQL, Redis, Temporal, OpenSearch, or S3-compatible object storage — instead of the ones the bundle provisions, and Serval supports doing so. But every deviation from the provided configuration adds operational lift on your side and makes upgrades harder to apply cleanly, because your deployment diverges from the tested baseline. Align with the provided configuration entirely, or as much as possible, to minimize unexpected behavior and keep upgrades simple.

​
What you own

  • The AWS account and any required internal approvals
  • DNS and domain ownership
  • AI provider keys and any customer-owned credentials supplied during onboarding
  • Environment-specific policies, guardrails, and access reviews
  • Whether your team or Serval operates the deployment
  • Any networking you need to reach private internal systems (see Private Network Access)

​
When to choose this model

Choose Managed in Your AWS when you:
  • Want the application runtime and data single-tenant in an AWS account you own
  • Are standardizing on AWS for the Serval deployment

​
Next steps

Prerequisites

Review the AWS account, DNS, and AI provider requirements before onboarding.

Compare delivery models

See how the delivery models compare.

Talk to Sales

Start the onboarding process.