Skip to main content

​
Serval-Managed in Your AWS

In this delivery model, you bring an AWS account you own and Serval operates the platform inside it. During onboarding, a one-time bootstrap provisions a small operator appliance inside your AWS account. Serval publishes new releases to a controlled release plane; the appliance in your account pulls each release and applies the infrastructure changes locally. Your AWS credentials never leave your environment, and Serval engineers do not hold persistent IAM access to your account.
This is fully self-hosted and single-tenant. The application runtime and customer data live in your AWS account. The difference from Self-Managed on Your Kubernetes is that Serval owns the platform operations — executed by the operator appliance inside your account — rather than your team.

​
What Serval operates

  • Infrastructure provisioning for the supported self-hosted stack inside your AWS account
  • Application installation and upgrades
  • Baseline monitoring and operational rollout work
  • Ongoing release application inside the AWS account you own

​
How it works

  • One-time bootstrap. During onboarding you run a short bootstrap in your AWS account that provisions the operator appliance (a lightweight controller) and establishes its trust boundary.
  • Release publishing. When Serval ships a new version, Serval publishes a release to a controlled release plane that your appliance is subscribed to.
  • Local execution. The appliance pulls the release and applies infrastructure and application changes from inside your AWS account. No Serval employee holds persistent IAM credentials to your account; AWS credentials never leave your environment.

​
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
  • Any networking you need to reach private internal systems (see Private Network Access)

​
When to choose this model

Choose Serval-Managed in Your AWS when you:
  • Want the application runtime and data in your own environment
  • Are comfortable standardizing on AWS for the Serval deployment
  • Do not want to operate the Kubernetes and data platform yourself
  • Want Serval to handle installs, upgrades, and routine operational work
  • Prefer a guided onboarding flow where Serval handles installs and upgrades remotely via the operator appliance rather than your team assembling the platform by hand
Most organizations evaluating full self-hosting should start with Serval-Managed in Your AWS unless they already have a strong reason to own the Kubernetes platform themselves or need multi-cloud flexibility.

​
Next steps

Prerequisites

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

Compare delivery models

See Serval-Managed in Your AWS and Self-Managed on Your Kubernetes side by side.

Talk to Sales

Start the onboarding process.