Which Kubernetes distributions does the Helm chart support?

The Cosmo Helm chart works with any Kubernetes cluster, including Amazon EKS, Azure AKS, Google GKE, and on-premises distributions. Minikube is supported for local development.

What storage components are required?

The platform requires PostgreSQL (operational database), Keycloak (authentication), ClickHouse (analytics), Minio (object storage), and Redis (cache). These are bundled via Bitnami Helm charts but can be replaced with external services in production.

Does any data leave my cluster in self-hosted mode?

No. All data remains within your cluster unless you explicitly configure external endpoints. Routers fetch their configuration from your own CDN, not from Cosmo Cloud.

What are the prerequisites for self-hosted deployment?

Helm 3.8 or later must be installed and configured to access your cluster. The chart runs on any current Kubernetes distribution.

Can I run the platform in an air-gapped environment?

Yes. Pull container images and Helm charts into your internal registry, then deploy to your isolated cluster. All components are configured to operate without external connectivity.

Is self-hosted deployment covered under a specific plan?

Cosmo is open source under Apache 2.0, so you can self-host the full stack yourself. For production, WunderGraph offers Enterprise support, deployment assistance, and Long Term Support. Contact the sales team for those options.

Where can I find the Helm chart source?

The Helm chart is in the Cosmo open-source repository at github.com/wundergraph/cosmo/tree/main/helm/cosmo. Configuration documentation is auto-generated with every chart update.

Self-Hosted GraphQL Federation | Cosmo by WunderGraph

The problem

Cloud-only platforms block regulated industries

Many organizations cannot send API data, schema metadata, or telemetry to an external SaaS. Most federation platforms offer no alternative.

Cloud-hosted platforms violate data residency requirements

Financial services, healthcare, and government organizations often cannot allow API metadata, schema data, or telemetry to leave their network. Cloud-only platforms make this impossible.

Vendor availability controls your uptime

When the federation control plane is managed externally, any outage or maintenance window affects your ability to publish schema changes or compose the federated graph.

Air-gapped environments need fully offline operation

Government contractors and secure facilities often operate in networks with no external connectivity. Every platform dependency must be available within the isolated environment.

Our solution

The entire stack, inside your network

The Cosmo umbrella Helm chart deploys all platform components to any Kubernetes cluster. Storage components run alongside platform services. All data stays within your infrastructure.

Deployment steps

The Cosmo umbrella Helm chart packages all platform components as modular sub-charts.
Configure your values.yaml with environment-specific settings: external databases, TLS, resource limits.
Run helm install against your Kubernetes cluster—EKS, AKS, GKE, or on-premises.
All data remains inside your cluster. No traffic reaches external services unless you configure it.
Storage components (PostgreSQL, Keycloak, ClickHouse, Minio, Redis) are managed via Bitnami Helm charts.
Upgrade platform components individually using Helm lifecycle management.

All components in one chart. All data in your cluster.

Self-Hosted

Before & After

Before	With Cosmo Self-Hosted
Limited to cloud-only federation platforms	Deploy federation in any environment
Data leaves your network to reach the control plane	Full data sovereignty within your infrastructure
Dependent on vendor availability and maintenance windows	Complete control over uptime and maintenance schedules
Compliance blockers for regulated industries	Meet strict regulatory requirements on your own infrastructure

Platform components

What the chart deploys

Platform sub-charts

ControlplaneStudioGraphQL MetricsOTEL CollectorRouterCDN

Storage (Bitnami charts)

PostgreSQLKeycloakClickHouseMinioRedis

How self-hosted deployment works

01

Any Kubernetes distribution.

Prepare

Set up a Kubernetes cluster and install Helm 3.8 or later. Pull the Cosmo Helm chart from the WunderGraph repository.

02

Full configuration control.

Configure

Customize values.yaml for your environment: external databases for production durability, TLS certificates, ingress configuration, and resource limits per component.

03

Single helm install command.

Deploy

Run helm install with your values file. The umbrella chart deploys all sub-charts and configures inter-component networking. Use Minikube for development environments.

04

All data stays in your cluster.

Operate

All data remains inside your cluster. Upgrade platform components using Helm lifecycle hooks. Scale sub-charts independently based on your workload.

Key differentiators

Why self-hosted Cosmo

Full stack, no compromises, inside your network.

Full data sovereignty

All platform data—schema metadata, analytics, telemetry—stays within your infrastructure. No external dependencies unless you configure them.

Any Kubernetes cluster

EKS, AKS, GKE, Minikube, or bare-metal on-premises clusters. The umbrella Helm chart works with any Kubernetes distribution.

Auto-generated configuration docs

Every Helm chart update regenerates its README with all available configuration options and defaults. Documentation is always accurate.

Open source

Cosmo is fully open source. Inspect the Helm charts, modify components, and contribute upstream. No vendor lock-in.

Deploy federation inside your network

Production-grade Helm charts. Full data sovereignty. Contact us for deployment guidance and enterprise support.

Talk to Sales Read the Docs

Full data sovereignty, in your own cluster