Is your feature request related to a problem? Please describe.
Currently, Typebot only provides a Docker Compose setup as the official deployment method.
While Docker Compose works well for local development and small environments, it is not suitable for teams running production workloads on Kubernetes. Users who want to deploy Typebot on Kubernetes must create and maintain their own manifests or custom solutions, which increases operational complexity and leads to inconsistent setups.
There is no official, standardized way to deploy Typebot on Kubernetes today.
Describe the solution you'd like
Provide an official Helm chart for deploying Typebot on Kubernetes.
The Helm chart would:
Offer a Kubernetes-native, production-ready deployment option
Replace the need for custom manifests when running Typebot on Kubernetes
Allow configuration via values.yaml (images, replicas, resources, env vars, secrets)
Optionally support Ingress configuration and TLS
Be compatible with GitOps tools like ArgoCD and Flux
This would make Typebot easier to adopt in Kubernetes-based infrastructures while keeping Docker Compose as a valid option for local development.
Describe alternatives you've considered
Continuing to use Docker Compose only, which limits production adoption
Maintaining custom Kubernetes manifests per user or team
Community-maintained Helm charts without an official reference
An official Helm chart would reduce duplication, improve consistency, and provide a better operational experience for Kubernetes users.
Is your feature request related to a problem? Please describe.
Currently, Typebot only provides a Docker Compose setup as the official deployment method.
While Docker Compose works well for local development and small environments, it is not suitable for teams running production workloads on Kubernetes. Users who want to deploy Typebot on Kubernetes must create and maintain their own manifests or custom solutions, which increases operational complexity and leads to inconsistent setups.
There is no official, standardized way to deploy Typebot on Kubernetes today.
Describe the solution you'd like
Provide an official Helm chart for deploying Typebot on Kubernetes.
The Helm chart would:
Offer a Kubernetes-native, production-ready deployment option
Replace the need for custom manifests when running Typebot on Kubernetes
Allow configuration via values.yaml (images, replicas, resources, env vars, secrets)
Optionally support Ingress configuration and TLS
Be compatible with GitOps tools like ArgoCD and Flux
This would make Typebot easier to adopt in Kubernetes-based infrastructures while keeping Docker Compose as a valid option for local development.
Describe alternatives you've considered
Continuing to use Docker Compose only, which limits production adoption
Maintaining custom Kubernetes manifests per user or team
Community-maintained Helm charts without an official reference
An official Helm chart would reduce duplication, improve consistency, and provide a better operational experience for Kubernetes users.