Background
The current production deployment section covers multiple approaches (Kubernetes/Helm, manual Meta Service setup, BendDeploy) without a clear recommendation. For users deploying Databend in a private/on-premises production environment, this creates decision fatigue.
Proposal
Restructure the production deployment section to position BendDeploy as the recommended path for self-hosted production deployments:
- Add a clear recommendation at the top of the production section: "For self-hosted production environments, we recommend BendDeploy"
- Move BendDeploy content earlier in the section (currently it's last)
- Reframe the Kubernetes/Helm and manual Meta Service pages as "advanced" or "alternative" options for users with specific requirements
- Update the section overview to reflect this recommendation
Motivation
BendDeploy is purpose-built for managing Databend clusters in production — it handles multi-cluster, multi-tenant deployments with a visual management interface. Surfacing it as the primary recommendation reduces complexity for new users and aligns with the product direction.
Related
Background
The current production deployment section covers multiple approaches (Kubernetes/Helm, manual Meta Service setup, BendDeploy) without a clear recommendation. For users deploying Databend in a private/on-premises production environment, this creates decision fatigue.
Proposal
Restructure the production deployment section to position BendDeploy as the recommended path for self-hosted production deployments:
Motivation
BendDeploy is purpose-built for managing Databend clusters in production — it handles multi-cluster, multi-tenant deployments with a visual management interface. Surfacing it as the primary recommendation reduces complexity for new users and aligns with the product direction.
Related