diff --git a/content/docs/platform/v2026.7.10/CHANGELOG-v2026.6.19.md b/content/docs/platform/v2026.7.10/CHANGELOG-v2026.6.19.md
new file mode 100644
index 0000000000..00bf92e6f1
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/CHANGELOG-v2026.6.19.md
@@ -0,0 +1,107 @@
+---
+title: Changelog | ACE
+description: Changelog
+menu:
+ docs_v2026.7.10:
+ identifier: changelog-ace-v2026.6.19
+ name: Changelog-v2026.6.19
+ parent: welcome
+ weight: 20260619
+product_name: ace
+menu_name: docs_v2026.7.10
+section_menu_id: welcome
+url: /docs/v2026.7.10/welcome/changelog-v2026.6.19/
+aliases:
+- /docs/v2026.7.10/CHANGELOG-v2026.6.19/
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# ACE v2026.6.19 (2026-06-21)
+
+
+## [appscode-cloud/b3](https://github.com/appscode-cloud/b3)
+
+### [v2026.6.19](https://github.com/appscode-cloud/b3/releases/tag/v2026.6.19)
+
+
+
+
+## [appscode-cloud/installer](https://github.com/appscode-cloud/installer)
+
+### [v2026.6.19](https://github.com/appscode-cloud/installer/releases/tag/v2026.6.19)
+
+
+
+
+## [appscode-cloud/ui-wizards](https://github.com/appscode-cloud/ui-wizards)
+
+### [v0.35.0](https://github.com/appscode-cloud/ui-wizards/releases/tag/v0.35.0)
+
+- [0a9c4c10](https://github.com/appscode-cloud/ui-wizards/commit/0a9c4c104) Prepare for release v0.35.0 (#1062)
+
+
+
+## [appscode/website](https://github.com/appscode/website)
+
+### [v2026.6.19](https://github.com/appscode/website/releases/tag/v2026.6.19)
+
+- [01f7f216](https://github.com/appscode/website/commit/01f7f216) Prepare for release v2026.6.19 (#215)
+- [f184b71b](https://github.com/appscode/website/commit/f184b71b) Pin Node to 22.22.3 to fix firebase preview deploy auth (#216)
+
+
+
+## [kmodules/image-packer](https://github.com/kmodules/image-packer)
+
+### [v2026.6.19](https://github.com/kmodules/image-packer/releases/tag/v2026.6.19)
+
+- [d6091139](https://github.com/kmodules/image-packer/commit/d6091139) Prepare for release v2026.6.19 (#55)
+
+
+
+## [kmodules/resource-metadata](https://github.com/kmodules/resource-metadata)
+
+### [v0.47.0](https://github.com/kmodules/resource-metadata/releases/tag/v0.47.0)
+
+- [fcd907ae](https://github.com/kmodules/resource-metadata/commit/fcd907ae6) Prepare for release v0.47.0 (#650)
+- [85c67bcb](https://github.com/kmodules/resource-metadata/commit/85c67bcb0) Update to KubeDB and KubeStash v2026.6.19
+- [e86f70f4](https://github.com/kmodules/resource-metadata/commit/e86f70f4c) Resync kubedb & kubestash CRDs
+- [776d5e81](https://github.com/kmodules/resource-metadata/commit/776d5e816) Update KubeDB and KubeStash for v2026.6.18-rc.2
+- [25abe419](https://github.com/kmodules/resource-metadata/commit/25abe4197) Sync up missing editors
+- [a7af825c](https://github.com/kmodules/resource-metadata/commit/a7af825c9) Update kubedb & catalog CRDs
+- [4ac7c73a](https://github.com/kmodules/resource-metadata/commit/4ac7c73ae) Add `observability-cluster` clusterprofile (#646)
+- [05ae8ec7](https://github.com/kmodules/resource-metadata/commit/05ae8ec76) Fix documentdb & import kubedb crds (#648)
+- [791189ee](https://github.com/kmodules/resource-metadata/commit/791189ee6) Add documentdb in menu
+- [45589858](https://github.com/kmodules/resource-metadata/commit/455898580) Remove FerretDB support (#647)
+
+
+
+## [kubeops/installer](https://github.com/kubeops/installer)
+
+### [v2026.6.19](https://github.com/kubeops/installer/releases/tag/v2026.6.19)
+
+- [ed4648dd](https://github.com/kubeops/installer/commit/ed4648dd) Prepare for release v2026.6.19 (#490)
+
+
+
+## [kubeops/ui-server](https://github.com/kubeops/ui-server)
+
+### [v0.5.0](https://github.com/kubeops/ui-server/releases/tag/v0.5.0)
+
+
+
+
+## [kubepack/lib-app](https://github.com/kubepack/lib-app)
+
+### [v0.23.0](https://github.com/kubepack/lib-app/releases/tag/v0.23.0)
+
+- [c12c4ce7](https://github.com/kubepack/lib-app/commit/c12c4ce7b) Prepare for release v0.23.0 (#172)
+- [6840206e](https://github.com/kubepack/lib-app/commit/6840206e0) Update vulnerable dependencies (#171)
+- [6dcb8a92](https://github.com/kubepack/lib-app/commit/6dcb8a924) Remove FerretDB support (#169)
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/CHANGELOG-v2026.7.10.md b/content/docs/platform/v2026.7.10/CHANGELOG-v2026.7.10.md
new file mode 100644
index 0000000000..45d2e76a66
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/CHANGELOG-v2026.7.10.md
@@ -0,0 +1,123 @@
+---
+title: Changelog | ACE
+description: Changelog
+menu:
+ docs_v2026.7.10:
+ identifier: changelog-ace-v2026.7.10
+ name: Changelog-v2026.7.10
+ parent: welcome
+ weight: 20260710
+product_name: ace
+menu_name: docs_v2026.7.10
+section_menu_id: welcome
+url: /docs/v2026.7.10/welcome/changelog-v2026.7.10/
+aliases:
+- /docs/v2026.7.10/CHANGELOG-v2026.7.10/
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# ACE v2026.7.10 (2026-07-13)
+
+
+## [appscode-cloud/b3](https://github.com/appscode-cloud/b3)
+
+### [v2026.7.10](https://github.com/appscode-cloud/b3/releases/tag/v2026.7.10)
+
+- [f90ecc7e](https://github.com/appscode-cloud/b3/commit/f90ecc7e0d) Prepare for release v2026.7.10 (#1560)
+- [e766b5a7](https://github.com/appscode-cloud/b3/commit/e766b5a7d1) Modernize golangci-lint config, clean up all lint findings, and enable lint in CI (#1559)
+- [6c3d23d0](https://github.com/appscode-cloud/b3/commit/6c3d23d0db) Preallocate slices and close healthz response body (#1558)
+
+
+
+## [appscode-cloud/installer](https://github.com/appscode-cloud/installer)
+
+### [v2026.7.10](https://github.com/appscode-cloud/installer/releases/tag/v2026.7.10)
+
+- [ec739356](https://github.com/appscode-cloud/installer/commit/ec739356) Prepare for release v2026.7.10 (#1300)
+- [95567425](https://github.com/appscode-cloud/installer/commit/95567425) Add reproducible make targets for catalog and certified charts (#1301)
+- [46a85a85](https://github.com/appscode-cloud/installer/commit/46a85a85) Propagate chart version to regcache dependency in ace-installer (#1299)
+- [8028dd4a](https://github.com/appscode-cloud/installer/commit/8028dd4a) Modernize golangci-lint config (#1298)
+
+
+
+## [appscode-cloud/ui-wizards](https://github.com/appscode-cloud/ui-wizards)
+
+### [v0.36.0](https://github.com/appscode-cloud/ui-wizards/releases/tag/v0.36.0)
+
+- [e2b93a81](https://github.com/appscode-cloud/ui-wizards/commit/e2b93a81b) Prepare for release v0.36.0 (#1083)
+- [ca807994](https://github.com/appscode-cloud/ui-wizards/commit/ca807994c) Modernize golangci-lint config (#1082)
+- [ffa9ab38](https://github.com/appscode-cloud/ui-wizards/commit/ffa9ab383) fix resource init and validation in vertical scaling ops (#1081)
+- [5a1452d4](https://github.com/appscode-cloud/ui-wizards/commit/5a1452d44) Set storage-metrics-server chart version to v0.1.0
+- [a8a7507c](https://github.com/appscode-cloud/ui-wizards/commit/a8a7507c3) Generate editors (#1080)
+- [e44adf55](https://github.com/appscode-cloud/ui-wizards/commit/e44adf553) fix mongodb horizons conditions (#1079)
+- [82ad918d](https://github.com/appscode-cloud/ui-wizards/commit/82ad918d4) Remove ferretdb
+
+
+
+## [appscode/website](https://github.com/appscode/website)
+
+### [v2026.7.10](https://github.com/appscode/website/releases/tag/v2026.7.10)
+
+- [0b246ffe](https://github.com/appscode/website/commit/0b246ffe) Prepare for release v2026.7.10 (#217)
+
+
+
+## [kmodules/image-packer](https://github.com/kmodules/image-packer)
+
+### [v2026.7.10](https://github.com/kmodules/image-packer/releases/tag/v2026.7.10)
+
+- [18b029a2](https://github.com/kmodules/image-packer/commit/18b029a2) Prepare for release v2026.7.10 (#59)
+- [a8bd9927](https://github.com/kmodules/image-packer/commit/a8bd9927) Expand ${...} image tags using availableVersions (#58)
+- [ec36f527](https://github.com/kmodules/image-packer/commit/ec36f527) Modernize golangci-lint config (#57)
+- [ed3c452e](https://github.com/kmodules/image-packer/commit/ed3c452e) Pass ci/ci-values.yaml to helm template when present (#56)
+
+
+
+## [kmodules/resource-metadata](https://github.com/kmodules/resource-metadata)
+
+### [v0.48.0](https://github.com/kmodules/resource-metadata/releases/tag/v0.48.0)
+
+- [ae8fcd22](https://github.com/kmodules/resource-metadata/commit/ae8fcd22e) Prepare for release v0.48.0 (#658)
+- [f060724a](https://github.com/kmodules/resource-metadata/commit/f060724a6) KubeDB / KubeStash v2026.7.10
+- [cae64e5b](https://github.com/kmodules/resource-metadata/commit/cae64e5bc) Modernize golangci-lint config (#657)
+- [57e63940](https://github.com/kmodules/resource-metadata/commit/57e639408) Sync catalog bindings
+- [b5c0d799](https://github.com/kmodules/resource-metadata/commit/b5c0d799a) Update for datastore & ops
+- [9e2d67a3](https://github.com/kmodules/resource-metadata/commit/9e2d67a3f) Sync digests
+- [4e9dbd2f](https://github.com/kmodules/resource-metadata/commit/4e9dbd2f9) Grafana Dashboards -> Dashboards
+
+
+
+## [kubeops/installer](https://github.com/kubeops/installer)
+
+### [v2026.7.10](https://github.com/kubeops/installer/releases/tag/v2026.7.10)
+
+- [29761e3b](https://github.com/kubeops/installer/commit/29761e3b) Prepare for release v2026.7.10 (#505)
+- [3d2d92b0](https://github.com/kubeops/installer/commit/3d2d92b0) Modernize golangci-lint config (#504)
+- [53f65b9d](https://github.com/kubeops/installer/commit/53f65b9d) [Update SideKick ClusterRole] Add Snapshot, ServiceExport Permission (#489)
+
+
+
+## [kubeops/ui-server](https://github.com/kubeops/ui-server)
+
+### [v0.6.0](https://github.com/kubeops/ui-server/releases/tag/v0.6.0)
+
+- [57fdaa2c](https://github.com/kubeops/ui-server/commit/57fdaa2c7) Prepare for release v0.6.0 (#436)
+- [10ce260b](https://github.com/kubeops/ui-server/commit/10ce260b2) Modernize golangci-lint config and switch formatter to gofumpt (#435)
+
+
+
+## [kubepack/lib-app](https://github.com/kubepack/lib-app)
+
+### [v0.24.0](https://github.com/kubepack/lib-app/releases/tag/v0.24.0)
+
+- [7d7088f3](https://github.com/kubepack/lib-app/commit/7d7088f35) Prepare for release v0.24.0 (#179)
+- [dd9de1cc](https://github.com/kubepack/lib-app/commit/dd9de1ccd) Sync catalog bindings; Remove ferretbinding
+- [2e3a6163](https://github.com/kubepack/lib-app/commit/2e3a61639) fusion: keep full HelmRelease object in values.yaml (#177)
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/README.md b/content/docs/platform/v2026.7.10/README.md
new file mode 100644
index 0000000000..20bff32f88
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/README.md
@@ -0,0 +1,37 @@
+---
+layout: docs
+title: Welcome | KubeDB Platform
+menu:
+ docsplatform_v2026.7.10:
+ identifier: platform-readme
+ name: Welcome
+ parent: welcome
+ weight: -1
+menu_name: docsplatform_v2026.7.10
+section_menu_id: welcome
+url: /docs/platform/v2026.7.10/welcome/
+aliases:
+- /docs/platform/v2026.7.10/
+- /docs/platform/v2026.7.10/README/
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# KubeDB Platform Documentation
+
+This page is the entry point for KubeDB Platform documentation.
+
+## Core sections
+
+- [Selfhost Setup](../selfhost-setup/)
+- [Guides](../guides/)
+
+## Contributor resources
+
+- [Contributing](../contributing.md)
+- [Support](../support.md)
+
+Use [Guides](../guides/) for day-to-day workflows, then continue to [Selfhost Setup](../selfhost-setup/) for deployment-specific instructions.
diff --git a/content/docs/platform/v2026.7.10/_index.md b/content/docs/platform/v2026.7.10/_index.md
new file mode 100644
index 0000000000..89b2d0c8c0
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/_index.md
@@ -0,0 +1,16 @@
+---
+title: KubeDB Platform
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: welcome
+ name: Welcome
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/contributing.md b/content/docs/platform/v2026.7.10/contributing.md
new file mode 100644
index 0000000000..7573c12470
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/contributing.md
@@ -0,0 +1,29 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: platform-contributing
+ name: Contributing
+ parent: welcome
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: welcome
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Contribution Guidelines
+
+Want to contribute to KubeDB?
+
+## Getting Help
+To speak with us, please leave a message on [our website](https://appscode.com/contact/). To receive product announcements, follow us on [Twitter](https://twitter.com/AppsCodeHQ).
+
+## Bugs/Feature request
+If you have found a bug with or want to request for new features, please [file an issue](https://github.com/appscode/community/issues/new).
+
+## Spread the word
+If you have written blog post or tutorial on KubeDB, please share it with us on [Twitter](https://twitter.com/AppsCodeHQ).
diff --git a/content/docs/platform/v2026.7.10/guides/README.md b/content/docs/platform/v2026.7.10/guides/README.md
new file mode 100644
index 0000000000..bbbbd9376c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/README.md
@@ -0,0 +1,38 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guides-readme
+ name: Guides
+ parent: guides
+ weight: -1
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+url: /docs/platform/v2026.7.10/guides/
+aliases:
+- /docs/platform/v2026.7.10/guides/README/
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Platform Guides
+
+This section contains practical, task-oriented guides for operating and managing the platform.
+
+## Guide categories
+
+- [Account Management](../guides/account-management/manage-profile/)
+- [Billing and Usage Guide](../guides/billing-and-usage-guide/overview)
+- [License Management](../guides/license-management/overview)
+- [Cluster Management](../guides/cluster-management/cluster-overview)
+- [Database Management](../guides/database-management/overview)
+- [Get Started](../guides/get-started/architecture)
+- [Integrations](../guides/integrations/rancher-extension)
+
+
+## Recommended path
+
+For first-time users, start with [Get Started](../guides/get-started/architecture) and then move to the specific management areas relevant to your workflow.
diff --git a/content/docs/platform/v2026.7.10/guides/_index.md b/content/docs/platform/v2026.7.10/guides/_index.md
new file mode 100644
index 0000000000..1bfa5deeba
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/_index.md
@@ -0,0 +1,16 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guides
+ name: Guides
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/_index.md b/content/docs/platform/v2026.7.10/guides/account-management/_index.md
new file mode 100644
index 0000000000..9edfad2e96
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management
+ name: Account Management
+ parent: guides
+ description: Basic Account Management
+ icon: https://img.icons8.com/00994A/ios/50/database--v1.png
+ popular: true
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/access-tokens.md b/content/docs/platform/v2026.7.10/guides/account-management/access-tokens.md
new file mode 100644
index 0000000000..120e5140aa
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/access-tokens.md
@@ -0,0 +1,50 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-accesstokens
+ name: Tokens
+ parent: account-management
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Managing Tokens
+
+Manage your access and NATS tokens to securely connect external applications and services to your account.
+
+## Access and Overview
+
+
+
+Go to **USER SETTINGS > Tokens** to manage your credentials.
+
+- **Manage Access Tokens:** View existing tokens, their expiration dates, and recent activity.
+- **Actions:** Use the search bar to find tokens or click **Delete** to remove them.
+- **NATS Tokens:** Located at the bottom, these manage UI features and AppsCode licenses.
+
+## Generate a New Access Token
+
+
+
+Click **Generate Token** to create a new credential.
+
+- **Name:** Give your token a descriptive label.
+- **Expiration:** Select an **Expire Date** using the calendar icon.
+- **Generate:** Click the green **Generate** button.
+- **Note:** Tokens grant full access to your account.
+
+## Secure Your Token
+
+
+
+A success banner will confirm the token is created.
+
+- ⚠️ **Copy Immediately:** Use the **Copy Token** link to save your credential now.
+- **Privacy:** For security, the token string **will never be shown again** after you leave this page
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/delete-account.md b/content/docs/platform/v2026.7.10/guides/account-management/delete-account.md
new file mode 100644
index 0000000000..72eef069d7
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/delete-account.md
@@ -0,0 +1,47 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-deleteaccount
+ name: Delete Account
+ parent: account-management
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deleting Your KubeDB Platform Account
+
+
+
+This guide provides step-by-step instructions for permanently removing your personal account from the KubeDB Platform.
+
+1. **Navigate to Account Settings:**
+ - Log in to your account.
+ - Click on the **USER SETTINGS** tab in the main top navigation bar.
+ - In the left-hand sidebar, locate the **GENERAL** category and select **Account**.
+
+2. **Review the Permanent Deletion Warning:**
+
+ Before proceeding, please note the critical alert displayed in the **Delete Your Account** section:
+
+ > ⚠️ **This operation will permanently delete your user account. It CAN NOT be undone.**
+
+ Deleting your account will result in the permanent loss of all associated data and access.
+
+3. **Verify Your Identity:**
+
+ To prevent unauthorized deletions, the system requires password verification:
+
+ - Locate the **Password** field (marked with a red asterisk as a required field).
+ - Enter your current account password.
+ - **Optional:** You can click the **eye icon** on the right side of the password field to toggle the visibility of your characters to ensure accuracy.
+
+4. **Confirm Deletion:**
+ - Once your password is entered, click the red **Confirm Deletion** button.
+ - The account will be immediately and permanently removed from the system.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/Branding.png b/content/docs/platform/v2026.7.10/guides/account-management/images/Branding.png
new file mode 100644
index 0000000000..2ed2f44e3c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/Branding.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth1.png
new file mode 100644
index 0000000000..a9ed48906b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth2.png
new file mode 100644
index 0000000000..c63c92fb75
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth3.png b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth3.png
new file mode 100644
index 0000000000..4abb438099
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth4.png b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth4.png
new file mode 100644
index 0000000000..74657b88fb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/OAuth4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/authentication-sources.png b/content/docs/platform/v2026.7.10/guides/account-management/images/authentication-sources.png
new file mode 100644
index 0000000000..ce217ceea5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/authentication-sources.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-1.png
new file mode 100644
index 0000000000..d3b03f67ec
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-2.png
new file mode 100644
index 0000000000..4a9152f27a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-3.png b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-3.png
new file mode 100644
index 0000000000..e776d7675c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-4.png b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-4.png
new file mode 100644
index 0000000000..21ae8997a0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-5.png b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-5.png
new file mode 100644
index 0000000000..230e063361
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/client-org-5.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Hetzner.png b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Hetzner.png
new file mode 100644
index 0000000000..882ae915c9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Hetzner.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Scaleway.png b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Scaleway.png
new file mode 100644
index 0000000000..6fb47f559c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/Scaleway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/azureStorage.png b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/azureStorage.png
new file mode 100644
index 0000000000..797fb6325f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/azureStorage.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/cloudflareStorage.png b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/cloudflareStorage.png
new file mode 100644
index 0000000000..84c0c1b62a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/cloudflareStorage.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/vultr.png b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/vultr.png
new file mode 100644
index 0000000000..c5009cd337
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/credentials/vultr.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/delete-account.png b/content/docs/platform/v2026.7.10/guides/account-management/images/delete-account.png
new file mode 100644
index 0000000000..cdbbd03110
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/delete-account.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/external-authentication.png b/content/docs/platform/v2026.7.10/guides/account-management/images/external-authentication.png
new file mode 100644
index 0000000000..6200dd50fe
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/external-authentication.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-1.png
new file mode 100644
index 0000000000..388a5066be
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-2.png
new file mode 100644
index 0000000000..3f882f4d2e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/manage-profile-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-1.png
new file mode 100644
index 0000000000..70ae79f234
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-2.png
new file mode 100644
index 0000000000..db1e8f9e36
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/orgs-members-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/security-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/security-1.png
new file mode 100644
index 0000000000..176f474b6c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/security-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/security-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/security-2.png
new file mode 100644
index 0000000000..5e7ec163d9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/security-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/security-3.png b/content/docs/platform/v2026.7.10/guides/account-management/images/security-3.png
new file mode 100644
index 0000000000..05136b778e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/security-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-1.png
new file mode 100644
index 0000000000..22e071b9ca
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-2.png
new file mode 100644
index 0000000000..7b0a2c5ce3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/sign-up-config-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-dashboard.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-dashboard.png
new file mode 100644
index 0000000000..1b9c35f582
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-dashboard.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-1.png
new file mode 100644
index 0000000000..5c48ecdad4
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-2.png
new file mode 100644
index 0000000000..03fe27b769
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-deleted-account-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-1.png
new file mode 100644
index 0000000000..d207a4968f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-2.png
new file mode 100644
index 0000000000..a2d4ac76de
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-organizations-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-1.png
new file mode 100644
index 0000000000..ae4f6caa48
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-2.png
new file mode 100644
index 0000000000..2be3b219de
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/site-admin-user-account-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/token-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/token-1.png
new file mode 100644
index 0000000000..2717893cce
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/token-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/token-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/token-2.png
new file mode 100644
index 0000000000..3033888c6f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/token-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/token-3.png b/content/docs/platform/v2026.7.10/guides/account-management/images/token-3.png
new file mode 100644
index 0000000000..f6455b01e8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/token-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-1.png b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-1.png
new file mode 100644
index 0000000000..cd1d314fe0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-2.png b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-2.png
new file mode 100644
index 0000000000..43cd737e4a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-3.png b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-3.png
new file mode 100644
index 0000000000..4d0d2eacbb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-4.png b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-4.png
new file mode 100644
index 0000000000..a5796a77b1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/images/upgrade-version-4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/_index.md b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/_index.md
new file mode 100644
index 0000000000..7a0e118a01
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/_index.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-kubernetes
+ name: Kubernetes
+ weight: 100
+ parent: account-management
+ pre: dropdown
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/credentials.md b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/credentials.md
new file mode 100644
index 0000000000..64f63c408e
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/credentials.md
@@ -0,0 +1,444 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-kubernetes-creds
+ name: Credentials
+ parent: account-management-kubernetes
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Kubernetes Credentials Management
+
+In order to integrate a vendor-managed Kubernetes cluster into our system, you can either opt o `Create` a new cluster or `Import` an existing one. This process involves adding specific credentials based on your vendor.
+
+Supported Credential Types include:
+- [AWS](#aws)
+- [Azure](#azure)
+- [Azure Storage](#azure-storage)
+- [Cloudflare R2 Storage](#cloudflare-r2-storage)
+- [Digital Ocean](#digital-ocean)
+- [Google Cloud](#google-cloud)
+- [Google OAuth](#google-oauth)
+- [Hetzner](#hetzner)
+- [Linode](#linode)
+- [Rancher](#rancher)
+- [Scaleway](#scaleway)
+- [Vultr](#vultr)
+
+Visit https://appscode.com/id/{user}/user/settings/credentials to manage credential.
+
+
+## AWS
+
+To create or import EKS clusters to [Platform Console](https://console.appscode.com/), you need to create a access-key with the following policies.
+- AmazonEC2FullAccess (AWS Managed Policy)
+- AWSCloudFormationFullAccess (AWS Managed Policy)
+- EKSAllAccess
+- IamLimitedAccess
+
+Steps:
+- Create user
+- Create required policies
+- Attach the policies to the user
+- Create access key
+
+Details:
+- Create user
+ ```sh
+ aws iam create-user --user-name "eks-cluster"
+ ```
+- Create policies
+ - Export AWS Account ID
+ ```sh
+ export AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query 'Account' --output text)
+ ```
+ - Create `AmazonEC2FullAccess (AWS Managed Policy)` policy
+ ```sh
+ echo '{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Action": "ec2:*",
+ "Effect": "Allow",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "elasticloadbalancing:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "cloudwatch:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "autoscaling:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "iam:CreateServiceLinkedRole",
+ "Resource": "*",
+ "Condition": {
+ "StringEquals": {
+ "iam:AWSServiceName": [
+ "autoscaling.amazonaws.com",
+ "ec2scheduled.amazonaws.com",
+ "elasticloadbalancing.amazonaws.com",
+ "spot.amazonaws.com",
+ "spotfleet.amazonaws.com",
+ "transitgateway.amazonaws.com"
+ ]
+ }
+ }
+ }
+ ]
+ }' > ec2-policy.json
+ ```
+ ```sh
+ aws iam create-policy --policy-name ec2-policy --policy-document file://ec2-policy.json
+
+ POLICY_ARN=$(aws iam list-policies --query 'Policies[?PolicyName==`ec2-policy`].Arn' --output text)
+ aws iam attach-user-policy --user-name "eks-cluster" --policy-arn $POLICY_ARN
+ ```
+ - Create `AWSCloudFormationFullAccess (AWS Managed Policy)` policy
+
+ ```sh
+ echo '{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "cloudformation:*"
+ ],
+ "Resource": "*"
+ }
+ ]
+ }' > cloudformation-policy.json
+ ```
+
+ ```sh
+ aws iam create-policy --policy-name cloudformation-policy --policy-document file://cloudformation-policy.json
+
+ POLICY_ARN=$(aws iam list-policies --query 'Policies[?PolicyName==`cloudformation-policy`].Arn' --output text)
+ aws iam attach-user-policy --user-name "eks-cluster" --policy-arn $POLICY_ARN
+ ```
+ - Create `EKSAllAccess` policy
+ ```sh
+ echo '{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": "eks:*",
+ "Resource": "*"
+ },
+ {
+ "Action": [
+ "ssm:GetParameter",
+ "ssm:GetParameters"
+ ],
+ "Resource": [
+ "arn:aws:ssm:*:${AWS_ACCOUNT_ID}:parameter/aws/*",
+ "arn:aws:ssm:*::parameter/aws/*"
+ ],
+ "Effect": "Allow"
+ },
+ {
+ "Action": [
+ "kms:CreateGrant",
+ "kms:DescribeKey"
+ ],
+ "Resource": "*",
+ "Effect": "Allow"
+ },
+ {
+ "Action": [
+ "logs:PutRetentionPolicy"
+ ],
+ "Resource": "*",
+ "Effect": "Allow"
+ }
+ ]
+ }' > eks-policy-template.json
+
+ envsubst < eks-policy-template.json > eks-policy.json
+ ```
+ ```sh
+ aws iam create-policy --policy-name eks-policy --policy-document file://eks-policy.json
+
+ POLICY_ARN=$(aws iam list-policies --query 'Policies[?PolicyName==`eks-policy`].Arn' --output text)
+ aws iam attach-user-policy --user-name "eks-cluster" --policy-arn $POLICY_ARN
+ ```
+ - Create `IamLimitedAccess` policy
+ ```sh
+ echo '{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:CreateInstanceProfile",
+ "iam:DeleteInstanceProfile",
+ "iam:GetInstanceProfile",
+ "iam:RemoveRoleFromInstanceProfile",
+ "iam:GetRole",
+ "iam:CreateRole",
+ "iam:DeleteRole",
+ "iam:AttachRolePolicy",
+ "iam:PutRolePolicy",
+ "iam:AddRoleToInstanceProfile",
+ "iam:ListInstanceProfilesForRole",
+ "iam:PassRole",
+ "iam:DetachRolePolicy",
+ "iam:DeleteRolePolicy",
+ "iam:GetRolePolicy",
+ "iam:GetOpenIDConnectProvider",
+ "iam:CreateOpenIDConnectProvider",
+ "iam:DeleteOpenIDConnectProvider",
+ "iam:TagOpenIDConnectProvider",
+ "iam:ListAttachedRolePolicies",
+ "iam:TagRole",
+ "iam:GetPolicy",
+ "iam:CreatePolicy",
+ "iam:DeletePolicy",
+ "iam:ListPolicyVersions"
+ ],
+ "Resource": [
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:instance-profile/eksctl-*",
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:role/eksctl-*",
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:policy/eksctl-*",
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:oidc-provider/*",
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:role/aws-service-role/eks-nodegroup.amazonaws.com/AWSServiceRoleForAmazonEKSNodegroup",
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:role/eksctl-managed-*"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:GetRole"
+ ],
+ "Resource": [
+ "arn:aws:iam::${AWS_ACCOUNT_ID}:role/*"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:CreateServiceLinkedRole"
+ ],
+ "Resource": "*",
+ "Condition": {
+ "StringEquals": {
+ "iam:AWSServiceName": [
+ "eks.amazonaws.com",
+ "eks-nodegroup.amazonaws.com",
+ "eks-fargate.amazonaws.com"
+ ]
+ }
+ }
+ }
+ ]
+ }' > iam-policy-template.json
+
+ envsubst < iam-policy-template.json > iam-policy.json
+ ```
+ ```sh
+ aws iam create-policy --policy-name iam-policy --policy-document file://iam-policy.json
+
+ POLICY_ARN=$(aws iam list-policies --query 'Policies[?PolicyName==`iam-policy`].Arn' --output text)
+ aws iam attach-user-policy --user-name "eks-cluster" --policy-arn $POLICY_ARN
+ ```
+- Create Access Token for the user
+ ```sh
+ aws iam create-access-key --user-name "eks-cluster"
+ ```
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from previous step.
+
+
+
+
+
+## Azure
+
+To configure Azure credentials for accessing and managing Azure Kubernetes Service (AKS) clusters, follow these steps using the Azure CLI:
+- Set the Azure subscription ID using the following command.
+ ```sh
+ export AZURE_SUBSCRIPTION_ID=$(az account show --query id --output tsv)
+ ```
+- Create Azure Service Principal with `Contributor` role.
+ ```sh
+ az ad sp create-for-rbac --role Contributor --scopes="/subscriptions/${AZURE_SUBSCRIPTION_ID}" --sdk-auth
+ ```
+- Save Credentials
+The command will output a JSON response containing the service principal details, including clientId (Application ID), clientSecret (Client Secret), subscriptionId, tenantId, and other information. Save these credentials securely as they will be used to configure the AKS cluster.
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+
+## Digital Ocean
+To access Digital Ocean Managed clusters, you need to create a API token from Digital Ocean.
+
+Ref: [How to Create a Personal Access Token](https://docs.digitalocean.com/reference/api/create-personal-access-token/)
+
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from Digital Ocean.
+
+
+
+## Google Cloud
+
+To access GKE clusters, you need to create a GCP service account with with container.admin role.
+
+- Set Project id, service account name
+ ```sh
+ # Set the project ID where you registered your Domain
+ PROJECT_ID="myproject-id" # change it to your project id
+ GKE_SA_NAME="gke-cluster" # change it to your desired sa name
+ GKE_SA_EMAIL="$GKE_SA_NAME@${PROJECT_ID}.iam.gserviceaccount.com"
+ ```
+- Create Service account and Assign permission
+ ```sh
+ gcloud iam service-accounts create $GKE_SA_NAME --display-name $GKE_SA_NAME
+
+ # assign google service account to dns.admin role in cloud-dns project
+ gcloud projects add-iam-policy-binding $PROJECT_ID \
+ --member serviceAccount:$GKE_SA_EMAIL --role "roles/container.admin"
+ ```
+- Create a Service Account Secret
+ ```sh
+ # download static credentials
+ gcloud iam service-accounts keys create $GKE_SA_NAME-credentials.json \
+ --iam-account $GKE_SA_EMAIL
+ ```
+
+Then add the service account credentials [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+## Google OAuth
+
+Simplest way to access GKE clusters is through creating `Google OAuth` type credential.
+Just head over [here](https://appscode.com/id/{user}/user/settings/credentials/create) and
+- Choose a `Name`
+- Select Credential Type: `Google OAuth`
+- Click `Continue with Google`
+
+
+This will create a credential, you will be able to access your k8s cluster with.
+
+
+
+
+
+## Linode
+
+To access LKE clusters, you need to create a API token from Linode with the following permissions.
+- Kubernetes (Read/Write)
+
+Ref: [Manage Linode Personal Access Tokens](https://www.linode.com/docs/products/tools/api/guides/manage-api-tokens/)
+
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from Linode.
+
+
+
+
+
+## Rancher
+
+To access Rancher clusters through KubeDB Platform, you need to create an API token in your Rancher system. Follow these steps:
+
+1. In Rancher, click on the profile icon.
+2. Select `Account & API Keys`.
+3. Click `Create API Key`.
+4. Provide a name and set the expiration for the API key.
+5. Click `Create` to complete the API token creation.
+
+Reference: [Rancher API Keys](https://ranchermanager.docs.rancher.com/reference-guides/user-settings/api-keys)
+
+Copy the generated access key, secret key, and API endpoint from the `Account & API Keys` overview page.
+
+Next, add these credentials to the [KubeDB Platform user settings credentials page](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+## Azure Storage
+
+To access Azure Blob Storage, you need your Storage Account name and one of its access keys.
+
+- **Account:** Your Storage Account name, found in the Azure Portal under **Storage accounts**.
+- **Key:** One of the access keys (key1 or key2), found under **Security + networking > Access keys** in the storage account sidebar. Click **Show** to reveal the key value.
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+
+
+## Cloudflare R2 Storage
+
+To access Cloudflare R2 Object Storage, you need your Account ID and an R2 API token.
+
+- **Account ID:** Found on your Cloudflare Dashboard under **R2 > Overview** or in the sidebar.
+- **Access Key ID & Secret Access Key:** Generated by creating an R2 API token. Navigate to **R2 > Manage R2 API Tokens > Create API Token** and ensure the token has `Edit` permissions for the target bucket.
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+
+
+## Hetzner
+
+To access Hetzner Cloud resources, you need an API token and an SSH key.
+
+- **SSH Key Name:** The name of an existing SSH key registered in your Hetzner Cloud project.
+- **Token:** A Hetzner Cloud API token. Generate one under **Security > API Tokens** in your Hetzner Cloud Console. Use `Read & Write` permissions.
+
+Ref: [Hetzner Cloud API Tokens](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/)
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+
+
+## Scaleway
+
+To access Scaleway resources, you need your Organization ID and an API secret key.
+
+- **Organization:** Your Scaleway Organization ID (a UUID), found under **Organization Settings** in the Scaleway Console.
+- **Token:** Your API Secret Key. Navigate to **Identity and Access Management (IAM) > API Keys**, create a new API key, and copy the **Secret Key**.
+
+Ref: [Scaleway API Keys](https://www.scaleway.com/en/docs/iam/how-to/create-api-keys/)
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
+
+
+
+
+
+## Vultr
+
+To access Vultr resources, you need a Vultr API key.
+
+- **Token:** Your Vultr API key. Navigate to **Account > API** in the Vultr customer portal and generate a personal access token.
+
+Ref: [Vultr API](https://www.vultr.com/api/)
+
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/aws-cred.png b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/aws-cred.png
new file mode 100644
index 0000000000..0c1247ca9b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/aws-cred.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/do-cred.png b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/do-cred.png
new file mode 100644
index 0000000000..12c9fe4f26
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/do-cred.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/gcp-oauth.png b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/gcp-oauth.png
new file mode 100644
index 0000000000..d0080de9c5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/gcp-oauth.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/linode-cred.png b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/linode-cred.png
new file mode 100644
index 0000000000..ef4519bc03
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/linode-cred.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/rancher-cred.png b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/rancher-cred.png
new file mode 100644
index 0000000000..3469802039
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/account-management/kubernetes/images/rancher-cred.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/manage-profile.md b/content/docs/platform/v2026.7.10/guides/account-management/manage-profile.md
new file mode 100644
index 0000000000..8c17a1d375
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/manage-profile.md
@@ -0,0 +1,46 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-manageprofile
+ name: Manage Profile, Emails, & Avatar
+ parent: account-management
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Managing Your Profile
+
+Personalize your account details and profile picture under **USER SETTINGS > Profile**.
+
+## 1. Update Profile Info
+
+
+
+Update your public identity and contact information in the **Manage Profile** section:
+
+- **Fields:** Modify your **Username**, **Full Name**, **Email Address**, **Biography**, **Website**, and **Location**.
+- **Save:** Click **Update Profile** to apply changes.
+
+## 2. Manage Avatar
+
+You can choose between two methods for your profile picture:
+
+### Option A: Link to Gravatar
+
+- Select the **From mail** tab.
+- Enter the **Avatar Email Address** connected to your Gravatar and click **Update Gravatar Email**.
+
+### Option B: Custom Upload
+
+
+
+- Select the **Custom** tab.
+- **Upload:** Drag and drop an image or select one from storage (Max: **1MB**, Max resolution: **4096 x 3072**).
+- **Reset:** Use the **Delete Current Avatar** button to remove your current image.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/manage-security.md b/content/docs/platform/v2026.7.10/guides/account-management/manage-security.md
new file mode 100644
index 0000000000..0f68e1c2ce
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/manage-security.md
@@ -0,0 +1,47 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-security
+ name: Manage Security
+ weight: 30
+ parent: account-management
+ pre: dropdown
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Account Security
+
+Manage your account's protection under **USER SETTINGS > Security** in the left-hand sidebar.
+
+## 1. Update Password & Linked Accounts
+
+
+
+- **Change Password:** To update your credentials, provide your **Current Password**, followed by a **New Password** and a confirmation in the **Retype Password** field.
+- **Linked Accounts:** View external accounts (like Google or GitHub) used for authentication and manage their connection to your profile.
+
+## 2. Enroll in Two-Factor Authentication (2FA)
+
+
+
+Enable 2FA to require a second verification step during login for enhanced security.
+
+- **Setup:** Click **Enroll into Two-Factor Authentication** and scan the QR code or enter the secret key into an authenticator app.
+- **Verify:** Enter the 6-digit **Passcode** generated by your app and click **Verify**.
+
+## 3. Manage 2FA & Security Keys
+
+
+
+Once 2FA is active, you can manage emergency access and hardware keys.
+
+- **Scratch Token:** Copy and store your scratch token safely immediately; it is only shown once and is required if you lose access to your authentication app.
+- **Security Keys (FIDO U2F):** Add hardware security devices for a higher level of protection. Assign a **Name** to your key and click **Add Security Key** to begin the pairing process.
+- **Control:** Use the provided buttons to **Regenerate** your scratch token or **Disable 2FA** entirely.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/oauth2-apps.md b/content/docs/platform/v2026.7.10/guides/account-management/oauth2-apps.md
new file mode 100644
index 0000000000..8ee230721a
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/oauth2-apps.md
@@ -0,0 +1,53 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-oauth2apps
+ name: Setup OAuth2 Applications
+ parent: account-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Application Overview
+
+
+
+Navigate to **User Settings > Applications** to manage how third-party services interact with your account. This page is divided into two sections:
+
+- **OAuth2 Applications:** A list of applications you have created, where you can **Edit** settings or **Remove** them entirely.
+- **Authorized OAuth2 Applications:** A list showing external services you have specifically granted access to your personal account.
+- To begin, click the green **\+ Create Application** button
+
+## Create a New Application
+
+
+
+On the creation screen, you must provide the following required information:
+
+- **Application Name:** The name that will identify your application.
+- **Redirect URL:** The specific address where users are sent after they authorize the application.
+- Click **\+ Create Application** to generate your credentials
+
+## Secure Your Credentials & Customize
+
+
+
+Once the application is generated, you will see your **Client ID** and **Client Secret**.
+
+- ⚠️ **Important:** Copy your **Client Secret** immediately using the **Copy Client Secret** link; for security, it will **not be shown again**.
+- **Regenerate Secret:** If you lose your secret, use this link to create a new one.
+- **Application Icon:** You can personalize your app by dragging and dropping an image (Max size: **1MB**, Max resolution: **4096 x 3072**).
+- Click **Save Changes** to apply any updates to the name, URL, or icon
+
+## Confirmation of Success
+
+
+
+After saving your changes or creating an application, a green "Successfully updated" notification will appear at the top of the screen. Your new application will now be visible in the OAuth2 Applications list, ready for use with its assigned Client ID
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/orgs-members.md b/content/docs/platform/v2026.7.10/guides/account-management/orgs-members.md
new file mode 100644
index 0000000000..3cdb179676
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/orgs-members.md
@@ -0,0 +1,41 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-orgmembers
+ name: Manage Organizations
+ parent: account-management
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Managing Organizations
+
+Manage your collaborations and organizational structure via the **ORGANIZATIONS** tab in the top navigation menu.
+
+## 1. Viewing & Managing Organizations
+
+
+
+The main list displays all organizations you belong to as a creator or member.
+
+- **Search & View:** Use the search bar to find groups and click their names to visit their profiles.
+- **Leave:** Click the **Leave** button to remove yourself from an organization immediately.
+
+## 2. Creating a New Organization
+
+
+
+Click **+ New Organization** to establish a new group.
+
+- **Details:** Provide a required **Organization Name**, plus an optional full name, description, website, and location.
+- **Visibility:** Choose who can see your organization: **Public**, **Limited** (logged-in users only), or **Private** (members only).
+- **Origin:** Toggle **Rancher Managed?** if the organization is managed through Rancher.
+- **Avatar:** Set a profile image using a Gravatar email or by uploading a custom image (Max: 1MB, 4096 x 3072 resolution).
+- **Finalize:** Click the green **Create** button to finish.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/_index.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/_index.md
new file mode 100644
index 0000000000..888bac6255
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/_index.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin
+ name: Site Administration
+ weight: 70
+ parent: account-management
+ pre: dropdown
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/ace-upgrade.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/ace-upgrade.md
new file mode 100644
index 0000000000..a5bafd3876
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/ace-upgrade.md
@@ -0,0 +1,71 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-ace-upgrade
+ name: KubeDB Platform Upgrade
+ parent: account-management-siteadmin
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# KubeDB Platform Upgrade
+
+Site administrators can upgrade the KubeDB Platform management cluster directly from the platform UI by uploading a configuration file downloaded from the AppsCode portal.
+
+---
+
+## Prerequisites
+
+Before starting the upgrade, download the required values file from the AppsCode portal:
+
+1. Log in to [appscode.com](https://appscode.com) and switch to your organization.
+2. Locate the installer currently in use and click **View Details**, then select **Upgrade**.
+3. Click **Download** to save the archive to your local machine. It contains the `values.yaml` file needed for the upgrade.
+
+---
+
+## Step 1 — Open KubeDB Platform Upgrade
+
+
+
+Go to **SITE ADMINISTRATION > KubeDB Platform Upgrade** from the left-hand menu.
+
+The page displays the current KubeDB Platform version and the upgrade status of all platform components. Click the **Upgrade Version** button at the top right to begin.
+
+---
+
+## Step 2 — Upload the Values File
+
+
+
+On the **Upgrade KubeDB Platform** screen:
+
+- Click **Upload values file...** and select the `values.yaml` file downloaded from the AppsCode portal.
+- Click **Update Version** to start the upgrade process.
+
+---
+
+## Step 3 — Monitor Upgrade Progress
+
+
+
+The platform will upgrade individual components one by one. You can track progress directly on this page:
+
+- Components currently being updated show a **refresh icon**.
+- Completed components show a **green checkmark**.
+- The overall status displays as **Progressing** while the upgrade is running.
+
+---
+
+## Step 4 — Verify Completion
+
+
+
+Once all components have been updated, the status changes to **Updated**. Confirm that the new version number is correctly reflected at the top of the page.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/authentication-sources.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/authentication-sources.md
new file mode 100644
index 0000000000..e4f8e2ec3d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/authentication-sources.md
@@ -0,0 +1,51 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-authentication-sources
+ name: Authentication Sources
+ parent: account-management-siteadmin
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Authentication Sources
+
+Site administrators can configure external authentication backends (such as LDAP) to allow users to log in using their organization's existing credentials.
+
+## Add an Authentication Source
+
+
+
+Go to **SITE ADMINISTRATION > Authentication Sources** and configure a new source using the form below.
+
+- **Authentication Type:** Select the backend type from the dropdown. Example: `LDAP (via BindDN)`.
+- **Authentication Name:** A label to identify this source (e.g., `Corporate-LDAP`).
+- **Security Protocol:** Choose the connection security — `Unencrypted`, `LDAPS`, or `StartTLS`.
+- **Host:** The hostname or IP address of your LDAP server (e.g., `ldap.yourdomain.com`).
+- **Port:** The port your LDAP server listens on (default: `389` for unencrypted, `636` for LDAPS).
+- **Bind DN:** The distinguished name of the service account used to query the directory (e.g., `cn=readonly-user,dc=example,dc=com`).
+- **Bind Password:** The password for the Bind DN account.
+ - ⚠️ **Warning:** This password is stored in plain text. Use a read-only account if possible.
+- **User Search Base:** The directory path to search for users (e.g., `ou=Users,dc=example,dc=com`).
+- **User Filter:** An LDAP filter to match user entries (e.g., `(uid=%s)`).
+- **Admin Filter:** An optional filter to identify admin users (e.g., `(memberOf=cn=Admins,ou=Groups,dc=example,dc=com)`).
+- **Username Attribute:** The LDAP attribute mapped to the username (e.g., `uid`).
+- **Surname Attribute:** The attribute for the user's surname (e.g., `sn`).
+- **Email Attribute:** The attribute for the user's email address (e.g., `mail`).
+- **Public SSH Key Attribute:** The attribute for the user's SSH public key (e.g., `sshPublicKey`).
+
+## Options
+
+- **Use Paged Search:** Enable this to handle large directories by fetching results in pages.
+- **Fetch Attributes in Bind DN Context:** Retrieve user attributes using the Bind DN credentials.
+- **Enable User Synchronization:** Automatically sync user data from the LDAP directory.
+- **This Authentication Source is Activated:** Enable or disable this source without deleting it.
+
+Click **+ Add Authentication Source** to save the configuration.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/branding.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/branding.md
new file mode 100644
index 0000000000..0531814943
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/branding.md
@@ -0,0 +1,45 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-branding
+ name: Branding
+ parent: account-management-siteadmin
+ weight: 70
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Branding
+
+Site administrators can customize the platform's appearance and identity — including the application name, logo, and favicon — to reflect their organization's branding.
+
+## Configure Branding
+
+
+
+Go to **SITE ADMINISTRATION > Branding** to update the platform's visual identity.
+
+### App Name
+
+- Enter a name in the **App Name** field. This name appears as the title in the browser tab and across the application.
+- Example: `ByteBuilders Cloud managed for the age of Kubernetes`
+
+### Logo & Tag
+
+- Use the toggle to **enable or disable** custom branding globally across the platform.
+- Click **Choose File** to upload a logo image.
+- Accepted formats: **JPEG, PNG, SVG, and GIF**.
+
+### Favicon
+
+- Click **Choose File** to upload a favicon displayed in the browser tab.
+- For best results, use an image approximately **32x32 pixels**.
+- Accepted formats: **JPEG, PNG, SVG, and GIF**.
+
+Click **Update Branding** to save all changes.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/client-org.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/client-org.md
new file mode 100644
index 0000000000..93b93af2b0
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/client-org.md
@@ -0,0 +1,81 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-clientorg
+ name: Client Organization
+ parent: account-management-siteadmin
+ weight: 75
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Client Organization
+
+A Client Organization provides logical separation between different clients sharing the same infrastructure, ensuring that one client cannot access or create resources (like databases) belonging to another. A central administrator manages multiple environments from a Hub cluster while each client gets a dedicated Spoke cluster for their own teams, workloads, and billing.
+
+---
+
+## Prerequisites
+
+Before creating a Client Organization, make sure the following are already in place:
+
+- **A Hub cluster is set up** — See [Create Hub & Spoke](../../../cluster-management/hub-ui/create.md) for the full setup guide.
+- **A Spoke cluster is connected to the Hub** — The Spoke must be linked and accepted by the Hub administrator.
+- **The Spoke cluster is licensed** — A valid license certificate must be applied to the Spoke. Without it, database features remain in a **Warning** state and the organization cannot be created. See [License Management](../../../cluster-management/hub-ui/license-management.md) for details.
+
+> ⚠️ Always perform these steps from an **Organization/Work account**. Personal accounts do not support Hub-Spoke features.
+
+---
+
+## Creating the Client Organization
+
+Once your Hub is ready and your Spoke is licensed, you can create the organization.
+
+> **Note:** Make sure the user who will be the organization admin already exists. If not, create one first via **SITE ADMINISTRATION > User Accounts**.
+
+
+
+Go to **USER SETTINGS > Client Organizations** and click **+ Add Organization**.
+
+### Step 1 — Basic Info
+
+
+
+- **Organization Name:** Enter a display name for the organization (e.g., `test-final`).
+- **Custom Annotations:** Optionally add key-value annotations applied to the organization's namespace.
+- **Organization Admin:** Select an existing user who will own and manage this organization (e.g., `bishaw2021`).
+- **Visibility:** Choose **Public** or **Private** (members only).
+- Click **Next** to continue.
+
+### Step 2 — Select Cluster
+
+
+
+- **Hub Cluster:** Select the Hub cluster to use as the management plane.
+- **Spoke Cluster:** Select the licensed Spoke cluster where the organization's workloads will run.
+- **Configure DB Nodepool (Optional):** Add **Labels** and **Tolerations** to restrict the organization's databases to specific nodes, ensuring physical isolation from other clients.
+- Click **Next** to continue.
+
+### Step 3 — Gateway Configuration
+
+
+
+- **Use Shared Gateway:** No dedicated gateway configuration is applied. The organization shares the existing gateway.
+- **Use Dedicated Gateway:** Select from available gateway configurations to assign a dedicated gateway for this organization.
+- Click **Submit** to create the organization.
+
+---
+
+## Verification
+
+
+
+After submission, the organization is created and visible in the list. Clicking on it shows its details — including the assigned Spoke cluster and its status.
+
+The organization admin, when logged in, will only see their assigned namespaces and Spoke cluster — fully isolated from other clients on the Hub.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/dashboard.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/dashboard.md
new file mode 100644
index 0000000000..c095131d0c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/dashboard.md
@@ -0,0 +1,33 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-dashboard
+ name: Dashboard
+ parent: account-management-siteadmin
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Site Administration Dashboard
+
+The Site Admin Dashboard gives administrators a high-level overview of the entire platform — users, organizations, and system activity.
+
+## Accessing the Dashboard
+
+
+
+Navigate to **SITE ADMINISTRATION > Dashboard** from the top navigation bar.
+
+- **Users:** View the total number of registered users on the platform.
+- **Organizations:** See the total count of organizations created across the system.
+- **Recent Activity:** Monitor the latest actions taken by users and admins.
+- **System Info:** Review platform version and environment details at a glance.
+
+Use this page as your starting point for platform-wide management and monitoring.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/delete-account.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/delete-account.md
new file mode 100644
index 0000000000..938c3bb3cc
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/delete-account.md
@@ -0,0 +1,39 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-deleteaccount
+ name: Delete Account
+ parent: account-management-siteadmin
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deleted Accounts
+
+When a user account is deleted from the **User Accounts** list, it is soft-deleted and moved here. Site administrators can view all deleted accounts and reactivate them if needed.
+
+## 1. View Deleted Accounts
+
+
+
+Go to **SITE ADMINISTRATION > Deleted Accounts** to see the list of deleted user accounts.
+
+- **User Details:** Each row shows the user's ID, username, email, creation date, and last sign-in.
+- **Reactivate:** Click the **Reactive** button next to a user to restore their account.
+
+## 2. Confirm Reactivation
+
+
+
+Clicking **Reactive** opens a confirmation dialog.
+
+- The dialog asks: *"Do you want to Reactive user [username]?"*
+- Click **Yes** to restore the account, or **Cancel** to go back.
+- Once confirmed, the user account is reactivated and will reappear in the main **User Accounts** list.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/external-authentication-sources.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/external-authentication-sources.md
new file mode 100644
index 0000000000..5e588fb2fe
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/external-authentication-sources.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-external-authentication-sources
+ name: External Authentication Sources
+ parent: account-management-siteadmin
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# External Authentication Sources
+
+Site administrators can enable third-party OAuth login providers (such as GitHub, Google, or others) so users can sign in using their existing external accounts.
+
+## Add an External Authentication Source
+
+
+
+Go to **SITE ADMINISTRATION > External Authentication Sources** and fill in the form.
+
+- **Provider:** Select or enter the OAuth provider name (e.g., `GitHub`).
+- **Client ID:** The application Client ID obtained from the provider's developer settings (e.g., `0123456789abcdef0123`).
+- **Client Secret:** The Client Secret key from the provider's developer settings.
+- **Callback URL:** The redirect URL that the provider sends users back to after authentication (e.g., `https://your-system-domain.com/login/github/callback`).
+ - This URL must be registered exactly in your provider's OAuth app settings.
+
+Click **Add External Authentication** to save and activate the provider.
+
+## How to Obtain Credentials
+
+Before filling in the form, you must register an OAuth application with your chosen provider:
+
+- **GitHub:** Go to **Settings > Developer settings > OAuth Apps > New OAuth App**.
+- **Google:** Go to **Google Cloud Console > APIs & Services > Credentials > Create OAuth Client ID**.
+
+Copy the generated **Client ID** and **Client Secret** from the provider and paste them into the form above.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/organizations.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/organizations.md
new file mode 100644
index 0000000000..40f764e7e9
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/organizations.md
@@ -0,0 +1,47 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-organizations
+ name: Organizations
+ parent: account-management-siteadmin
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Managing Organizations
+
+Site administrators can view all organizations on the platform and create new ones from the **Organizations** section.
+
+## 1. View All Organizations
+
+
+
+Go to **SITE ADMINISTRATION > Organizations** to see the full list of organizations.
+
+- **Total Count:** The page header shows the total number of organizations (e.g., Total: 90).
+- **Organization Details:** Each row shows the ID, username, number of teams, number of members, and creation date.
+- **Actions:** Each organization has a **Delete** button to remove it and a **No Access** button to restrict access.
+- **Create:** Click **+ New Organization** in the top right to add a new organization.
+
+## 2. Create a New Organization
+
+
+
+Click **+ New Organization** to open the creation form.
+
+- **Organization Name:** Enter a unique name (required).
+- **Organization Full Name:** Optionally provide a display name.
+- **Description:** Add a brief description of the organization.
+- **Website URL:** Optionally link a website.
+- **Location:** Optionally specify a location.
+- **Origin:** Toggle **Rancher Managed?** if the organization is managed through Rancher.
+- **Visibility:** Choose **Public**, **Limited** (logged-in users only), or **Private** (members only).
+- **Avatar:** Upload a profile image from storage (Max: 1MB, 4096 x 3072 resolution).
+- **Create:** Click **+ Create** to finish.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/sign-up-configuration.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/sign-up-configuration.md
new file mode 100644
index 0000000000..4d128af241
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/sign-up-configuration.md
@@ -0,0 +1,48 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-signupconfig
+ name: Sign-up Configuration
+ parent: account-management-siteadmin
+ weight: 65
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Sign-up Configuration
+
+Site administrators can control who is allowed to register on the platform by managing approved domains and toggling user sign-up access.
+
+## Overview
+
+
+
+Go to **SITE ADMINISTRATION > Sign-up Configuration** to manage registration settings.
+
+## Allowed Domains
+
+Restrict sign-ups to users with email addresses from specific approved domains.
+
+- **List:** All currently allowed domains are shown in the table under **Name**.
+- **Search:** Use the search bar to filter existing domains.
+- **Delete:** Click the **Delete** button next to a domain to remove it from the allowed list.
+- **Add:** Click **+ Add Domains** to add a new allowed domain.
+
+## Registration Options
+
+- **Disable user sign-up?** — Toggle this on to prevent new users from registering on the platform entirely.
+
+## Add a New Allowed Domain
+
+
+
+Click **+ Add Domains** to open the form.
+
+- **Domain Name:** Enter the domain you want to allow (e.g., `example.com`). Only users with email addresses from this domain will be permitted to sign up.
+- Click **+ Add Domains** to save the entry.
diff --git a/content/docs/platform/v2026.7.10/guides/account-management/site-administration/user-account.md b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/user-account.md
new file mode 100644
index 0000000000..75a12342ae
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/account-management/site-administration/user-account.md
@@ -0,0 +1,45 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: account-management-siteadmin-useraccount
+ name: User Accounts
+ parent: account-management-siteadmin
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Managing User Accounts
+
+As a site administrator, you can view all registered user accounts and create new ones from the **User Accounts** section.
+
+## 1. View All Users
+
+
+
+Go to **SITE ADMINISTRATION > User Accounts** to see the full list of registered accounts.
+
+- **Total Count:** The page header shows the total number of registered users (e.g., Total: 97).
+- **User Details:** Each row shows the user's ID, username, email, activation status, admin status, creation date, and last sign-in.
+- **Actions:** Each user has **Edit** and **Delete** buttons. Use **Delete** to permanently remove a user, or **Edit** to update their details.
+- **Create:** Click **Create User Account** in the top right to add a new user.
+
+## 2. Create a New User Account
+
+
+
+Click **Create User Account** to open the new user form.
+
+- **Authentication Source:** Select the login method (e.g., local).
+- **Username:** Enter a unique username.
+- **Full Name:** Provide the user's full name.
+- **Rescue Email:** Enter an email address for account recovery.
+- **Password:** Set an initial password for the account.
+- **Require Password Change:** Check this option (recommended) to prompt the user to change their password on first login.
+- **Create:** Click **Create User Account** to finish.
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/_index.md b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/_index.md
new file mode 100644
index 0000000000..eb119ff7d1
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: billing-and-usage-guide
+ name: Billing and Usage Guide
+ parent: guides
+ description: Billing and Usage Guide for AppsCode's products
+ icon: https://img.icons8.com/external-anggara-basic-outline-anggara-putra/96/external-stats-ui-anggara-basic-outline-anggara-putra.png
+ popular: true
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/cost-management.md b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/cost-management.md
new file mode 100644
index 0000000000..fd0a748a94
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/cost-management.md
@@ -0,0 +1,80 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: billing-and-usage-guide-cost-management
+ name: Cost Management
+ parent: billing-and-usage-guide
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## **Cluster and Namespace Configuration for Cost Management**
+
+For effective cost management, users can configure their clusters and namespaces. This section covers how to set a cluster's mode to **PROD** or **NON-PROD** for different billing rates, and how to enable a one-month free trial for KubeDB resources in a specific namespace.
+
+### **Configuring Cluster Mode (PROD vs. NON-PROD)**
+
+We offer different billing rates for production (**PROD**) and non-production (**NON-PROD**) environments. To distinguish between these, the user must set an annotation on the kube-system namespace of the cluster. The system considers a cluster as **PROD** only if the mode is explicitly set to `prod`. All other modes (`qa`, `staging`, `dev`) are treated as **NON-PROD**.
+
+**To set the cluster mode:**
+
+1. Identify the kube-system namespace in the cluster.
+2. Apply the following annotation: `cluster.appscode.com/mode`.
+
+Here are the possible values for the annotation:
+
+| Value | Cluster Mode Interpretation |
+| :---- | :---- |
+| prod | **PROD** (Production) |
+| qa | **NON-PROD** (Quality Assurance) |
+| staging | **NON-PROD** (Staging) |
+| dev | **NON-PROD** (Development) |
+
+**Example using kubectl:**
+
+To set a cluster to **PROD** mode, run the following command:
+
+```shell
+kubectl annotate namespace kube-system cluster.appscode.com/mode=prod --overwrite
+```
+
+To set it to a **NON-PROD** mode like staging, run:
+
+```shell
+kubectl annotate namespace kube-system cluster.appscode.com/mode=staging --overwrite
+```
+
+### **Enabling the First One-Month Free Resource Trial**
+
+Users can get a one-month free trial for every KubeDB database running within a specific namespace. This allows for evaluation of the service without incurring costs during the trial period.
+
+To enable the free trial, the user needs to add a specific annotation to the desired namespace.
+
+- **Who applies this:** In a DBaaS setup, downstream users typically do not have direct access to the cluster. The annotation must be applied by the cluster/infra administrator who manages the cluster.
+- **Where it can be used:** The trial can be enabled in namespaces on both **PROD** and **NON-PROD** clusters. While the trial is active, eligible database usage is counted as **free usage** (not billed and reported as Free usage in the Billable section), regardless of cluster mode. After the trial ends for a database, subsequent usage follows the cluster's pricing mode (**PROD** or **NON-PROD**) and your contract status (paid contract vs. the 30‑day free contract when no paid contract exists).
+
+**To enable the trial:**
+
+1. Select the namespace that contains your KubeDB databases. The trial behavior depends on when databases are created relative to when the annotation is applied:
+ - **Existing databases:** If a database is still within its first month from creation, it will receive free trial usage for the remaining portion of that first month (starting from when the annotation is applied). Databases that have already completed their first month are not eligible for the trial.
+ - **New databases:** Any databases created after the annotation is applied will receive a full one-month free trial from their creation timestamp, as long as the namespace remains annotated.
+ - **Trial eligibility:** Each database is eligible for a one-month free trial only once during its lifetime.
+2. Apply the annotation `ace.appscode.com/enable-resource-trial` with the value `true`.
+
+**Example using kubectl:**
+
+To enable the free trial for a namespace named `my-app-ns`, run the following command:
+
+```shell
+kubectl annotate namespace my-app-ns ace.appscode.com/enable-resource-trial=true --overwrite
+```
+
+Once this annotation is applied, eligible KubeDB resources in this namespace will receive trial benefits as described above.
+
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/dbaas-client-billing.md b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/dbaas-client-billing.md
new file mode 100644
index 0000000000..a994250389
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/dbaas-client-billing.md
@@ -0,0 +1,118 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: billing-and-usage-guide-dbaas-client-billing
+ name: DBaaS Client Billing
+ parent: billing-and-usage-guide
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+### **DBaaS Provider Billing APIs**
+
+This section is intended for DBaaS providers (self-hosted administrators) who manage the platform for end-users. To help providers monitor the resource consumption of their clients, we expose a set of APIs that deliver detailed usage reports for specific namespaces. This is particularly useful for billing, resource planning, and gaining insights into how end-users are utilizing the KubeDB resources within their assigned namespaces.
+
+#### **Prerequisites: Enabling Client Billing**
+
+Before these APIs can be used, the **Client Billing** feature must be enabled in your contract with us. This is a digital agreement that activates the necessary backend services to collect and expose usage data for your clients' namespaces from our central system.
+
+For more information on how to view or modify your contract, please refer to the [official contract management documentation](https://appscode.com/docs/en/guides/license-management/contract.html) or contact [AppsCode administrators](https://appscode.com/contact/). Once **Client Billing** is enabled in your contract, you can proceed to use the API endpoints detailed below.
+
+### **Authentication**
+
+To use these APIs, you must authenticate your requests. Usage information is collected and stored in our central system, and accessing it requires a secure token.
+
+1. **Generate an Access Token:** Create a user-scoped API token from your account.
+ - Go to User Settings and open the `Tokens` tab, then click on `Generate Token`.
+ 
+ - Provide a token name and (optionally) an expiry, then click on `Generate`.
+ 
+ - Copy the token and store it securely. It’s shown only once.
+ 
+2. **Use as a Bearer Token:** This token must be included in the Authorization header of your API requests as a Bearer token.
+
+**Example Header:** Authorization: Bearer
+
+**Note:** Treat this access token as a confidential credential. Do not expose it in client-side code or public repositories.
+
+### **Information Available for Client-Side Billing**
+
+The billing reports expose the following information for use in customer invoicing and internal chargeback. This section describes what you can expect to see; the next section explains how to query it via APIs.
+
+1) Namespace Level
+ - **Database Information:** Identifies the type of database deployed in each namespace (for example, MongoDB, PostgreSQL, MySQL), along with the database name as visible to the platform.
+
+2) Database Level
+ - **Pod Details:**
+ - **Flavor:** CPU and Memory allocation for each pod.
+ - **Age of Pod:** Duration since pod creation.
+ - **Number of Pods:** Total pod count, including autoscaling pods.
+ - Volume Details:
+ - **Volume Name:** Name of the persistent volume.
+ - **Initial Size:** Initial size of the volume at creation.
+ - **Expanded Sizes:** Any volume size increases, including the size and timestamp of each expansion.
+ - **Volume Created At:** Timestamp when the volume was created.
+ - **Volume Age:** Duration since the volume was created.
+ - **Volume Expansion History:** Record of any expansion events, with size and timestamp.
+ - **Volume Deleted At:** Timestamp when the volume was deleted (if applicable).
+
+**Notes:** Timestamps are reported in UNIX time. Sizes are returned as strings with Gi units (for example, '10Gi').
+
+### **API Endpoints**
+
+The following APIs are available to retrieve billing and usage reports.
+
+#### **1. Get Usage Reports for All Namespaces**
+
+This endpoint retrieves a consolidated usage report for all namespaces that are bound to your client organizations. It is ideal for generating auditing reports and getting a high-level overview of resource consumption.
+
+* **Endpoint:**
+> GET https://appscode.com/api/v1/dbaas/billing/reports/namespaces
+* **Description:** Returns a list of usage reports, with each report corresponding to a namespace managed under your DBaaS platform. This endpoint is particularly useful for auditing, billing reconciliation, and high‑level usage analysis.
+* **Query Parameters:**
+ * **org** (string, optional): The organization name in the central **appscode.com** platform that owns your billing contract and receives usage from your self-hosted installation. The authenticated user must be a member of this organization. Use this to restrict results to namespaces reported under that org.
+* **Limitations:**
+ * The current implementation does not support pagination. As a result, the endpoint returns all available namespaces, which may lead to large response sizes over time.
+ * Resources (including namespaces, pods, and volumes) that were deleted more than six months ago are automatically excluded from the response.
+* **Example Response:** The response will contain a list of namespace reports. Each report includes cluster information, namespace details, and a breakdown of the databases running within that namespace. Please see the [Additional Resources](#additional-resources) section below for detailed response schema and example.
+
+#### **2. Get Usage Report for a Specific Namespace**
+
+This endpoint allows you to drill down and retrieve a detailed usage report for a single, specific namespace within a given cluster. This is useful for generating invoices or analyzing the consumption of a particular client.
+
+* **Endpoint:**
+> GET https://appscode.com/api/v1/dbaas/billing/reports/clusters/{clusterID}/namespaces/{namespace}
+* **Description:** Returns a detailed usage report for the specified namespace, including information about the cluster, the namespace itself, and all KubeDB resources deployed within it.
+* **Path Parameters:**
+ * **clusterID** (string, required): The unique identifier of the spoke cluster where the namespace is located.
+ * **namespace** (string, required): The name of the namespace for which the report is being requested.
+* **Query Parameters:**
+ * **org** (string, optional): The organization name in the central **appscode.com** platform that owns your billing contract and to which your self-hosted app reports usage. The authenticated user must be a member of this organization. Provide the org created for your DBaaS customer to target the correct data.
+* **Cautions:**
+ * The namespace name provided in the path should be unique within the specified cluster, or unique across all clusters if you need to ensure you are targeting the correct one.
+ * In the self-hosted platform, each **client organization** (client-org) name must be unique because the DBaaS namespace is created with exactly the same name as that client-org. This one-to-one mapping means duplicate client-org names will cause namespace conflicts.
+ * You can optionally add an annotation to the namespace to tag the downstream end-user (for example, a customer ID or external reference) so you can map reports back to your own user records.
+* **Response Breakdown:** The JSON response for a single namespace provides granular details:
+ * **clusterInfo**: Contains metadata about the cluster, such as its name, Kubernetes version, provider, and resource capacity.
+ * **namespaceInfo**: Includes the namespace's labels, annotations, and creation timestamp.
+ * **databases**: An array of objects, where each object represents a KubeDB instance and contains:
+ * **databaseInfo**: Basic details like the database kind, product, and resource name.
+ * **podDetails**: Information about the pods, including CPU and memory resources allocated.
+ * **volumeDetails**: Details about the persistent volumes, including their initial size and any expansion history.
+
+For full field-by-field schemas, sample payloads, and screenshots, see the [Additional Resources](#additional-resources) section below.
+
+### **General API Cautions**
+
+- **Time Format:** All time-related values in the API responses (e.g., createdAt, lastReceivedAt) are represented in the **UNIX time format**.
+- **Data Retention:** The API response does not include resources (namespaces, pods, volumes, etc.) that were deleted more than **six months ago**.
+
+### **Additional Resources**
+- **Document Files:** For related document files, please access the following shared drive: [DBaaS Billing API Documents](https://drive.google.com/drive/u/1/folders/14ccceVuJQCKLvi9iSswnz86LqvB3Dfeq)
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-options.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-options.png
new file mode 100644
index 0000000000..6eeaf25e0e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-options.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-ui-navigation.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-ui-navigation.png
new file mode 100644
index 0000000000..33730acfc9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/create-token-ui-navigation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/created-token-result.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/created-token-result.png
new file mode 100644
index 0000000000..061af18140
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/created-token-result.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-billable-usage-home.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-billable-usage-home.png
new file mode 100644
index 0000000000..005edcbcdb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-billable-usage-home.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-home.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-home.png
new file mode 100644
index 0000000000..682e2ad547
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-home.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-prod-nonprod-usage-home.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-prod-nonprod-usage-home.png
new file mode 100644
index 0000000000..449550ec07
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-prod-nonprod-usage-home.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-product-dropdown.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-product-dropdown.png
new file mode 100644
index 0000000000..db77879428
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-product-dropdown.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-select-month.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-select-month.png
new file mode 100644
index 0000000000..fd053dd4a6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-select-month.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-usage-type-dropdown.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-usage-type-dropdown.png
new file mode 100644
index 0000000000..f8e490ba3a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-usage-type-dropdown.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-view-by-dropdown.png b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-view-by-dropdown.png
new file mode 100644
index 0000000000..a08302a079
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/images/usage-section-view-by-dropdown.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/overview.md b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/overview.md
new file mode 100644
index 0000000000..25862c1b62
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/billing-and-usage-guide/overview.md
@@ -0,0 +1,65 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: billing-and-usage-guide-overview
+ name: Overview
+ parent: billing-and-usage-guide
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# **Billing and Usage Guide**
+
+This document provides a detailed overview of the **Usage** section within our billing system. It explains how to navigate the user interface, monitor resource consumption, and configure **clusters** and **namespaces** for effective cost management.
+
+## **AppsCode Billing Console — Usage**
+
+The AppsCode Billing Console is a web-based hub at [AppsCode Billing Console](https://appscode.com/billing) where you can manage contracts, link clusters, generate license-proxyserver installers, track licensed clusters, and **monitor usage—all in one place**.
+
+This section focuses on the **Usage** dashboard, which shows the resources consumed by downstream AppsCode services like KubeDB running in your clusters.
+
+
+
+### **Billing View (Month, Product, Usage, View By)**
+
+* **Month:** Our billing is month-specific. Pick the month to review and the dashboard refreshes all charts and tables to that month.
+
+* **Product:** Use the Product dropdown to scope data to one product (KubeDB, KubeStash, Voyager, KubeVault).
+
+* **Usage Types:**
+ * **Total Usage**: total consumption for the selected scope, measured primarily in `Core-Minute` and `GiB-Minute`.
+ * **Billable Usage**: the portion that is billable, measured primarily in `Core-Month` and `GiB-Month`. Billable is computed only if your organization has a paid contract for the selected product. If there’s no paid contract, a 30‑day free contract is applied and usage during this period is counted as `free usage`. See the [Contract docs](http://appscode.com/docs/en/guides/license-management/contract.html) for details.
+
+* **View By:**
+ * Choose how data is grouped. For Database view, you can drill down **Kinds → Clusters → Deployments** (for example, `kubedb.com/Postgres` → `clusters running Postgres` → `individual database deployments`).
+
+
+Additional View By filters
+- **View By: Cluster** — Start at clusters to see per‑cluster usage, then drill down **Clusters → Kinds → Deployments** (for example, `cluster-prod` → `kubedb.com/Postgres` → `individual postgres database deployments in cluster-prod`).
+- **View By: Namespace** — Start at namespaces to see per‑namespace usage, then drill down **Namespaces → Deployments** (for example, `namespace-client-org-1` → `individual database deployments in that namespace`).
+
+### **Billable Usage and Cost Management**
+
+Billable shows the chargeable portion of usage for the selected month and product, reported in `Core-Month` and `GiB-Month`.
+
+
+What you’ll see in the Billable table
+- **Billable Usage:** total chargeable usage for the month after applying contracts and rules.
+- **PROD/NON-PROD usage:** billable usage split by cluster mode—clusters marked `prod` are priced at the `PROD` rate; clusters marked `qa`, `staging`, or `dev` are priced at the `NON‑PROD` rate.
+
+- **Free usage:** usage that isn’t billed. This includes:
+ - **Trial usage** from namespaces annotated `ace.appscode.com/enable-resource-trial=true` (`first one‑month` free per database starting from its creation in that namespace).
+ - Usage covered by the **30‑day free contract** when there’s no paid contract for the selected product.
+
+**How to influence these numbers:**
+ - Cluster mode (`PROD` vs `NON‑PROD`) and namespace trials are configured in Cost Management: [Cost Management](../cost-management.md)
+ - Contract behavior (`paid` vs. `30‑day free` when none exists) is described here: [Contract docs](http://appscode.com/docs/en/guides/license-management/contract.html)
+
+**For more details, please contact** [AppsCode administrators](https://appscode.com/contact/).
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/_index.md b/content/docs/platform/v2026.7.10/guides/client-organization/_index.md
new file mode 100644
index 0000000000..58cb21b233
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/client-organization/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: client-organization
+ name: Client Organization
+ parent: guides
+ description: Manage client organizations on KubeDB Platform
+ icon: https://img.icons8.com/?size=100&id=80695&format=png&color=000000
+ popular: true
+ weight: 25
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/add-cluster-to-existing-client-organization.md b/content/docs/platform/v2026.7.10/guides/client-organization/add-cluster-to-existing-client-organization.md
new file mode 100644
index 0000000000..89b503d058
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/client-organization/add-cluster-to-existing-client-organization.md
@@ -0,0 +1,56 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: client-organization-add-cluster
+ name: Add a Cluster
+ parent: client-organization
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Add a Cluster to an Existing Client Organization
+
+You can assign additional clusters to a client organization after it has been created. The **Add Cluster** wizard reuses the same **Gateway Configuration** and **Telemetry Configuration** steps as the [Create Client Organization](../create-client-organization.md) wizard.
+
+## Open the Client Organization
+
+Go to **Site Administration → Client Organizations** and click the organization's **Name** in the list to open its details.
+
+
+
+## Find the Add Cluster option
+
+On the organization's details page, the **Clusters** section lists the clusters already assigned to the organization. Click **Add Cluster** in the top-right of that section to start the wizard.
+
+
+
+## Step 1: Select Cluster
+
+In the first step of the **Add Cluster** wizard, choose the cluster to assign and optionally tune where its database workloads are scheduled.
+
+
+
+- **Hub Cluster** *(required)* — the management (hub) cluster for this assignment.
+- **Spoke Cluster** *(required)* — the spoke cluster where the organization's databases run.
+- **Configure DB Nodepool** *(optional)* — key/value labels used to target specific nodes for database workloads.
+- **Tolerations** *(optional)* — add tolerations so workloads can be scheduled onto tainted nodes. Each toleration takes an **Effect**, **Key**, **Operator**, and **Value**.
+
+
+
+Click **Next** to continue.
+
+## Remaining Steps
+
+After selecting the cluster, the wizard continues with the same **Gateway Configuration** and **Telemetry Configuration** steps used when creating a client organization:
+
+- [Gateway Configuration](../create-client-organization/#step-3-gateway-configuration) — choose a shared or dedicated gateway.
+- [Telemetry Configuration](../create-client-organization/#step-4-telemetry-configuration) — configure log and metrics retention.
+
+Configure them as needed, then finish to add the cluster to the organization. The new cluster then appears in the **Clusters** section of the organization's details page.
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/create-client-organization.md b/content/docs/platform/v2026.7.10/guides/client-organization/create-client-organization.md
new file mode 100644
index 0000000000..59398cf232
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/client-organization/create-client-organization.md
@@ -0,0 +1,114 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: client-organization-create
+ name: Create a Client Organization
+ parent: client-organization
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Create a Client Organization
+
+This guide walks through the **Create Client Organization** wizard. To open it, go to **Site Administration → Client Organizations** and start a new organization.
+
+The wizard has four steps, shown on the right side of the form:
+
+1. **User Information** — organization and admin details.
+2. **Select Cluster** — hub and spoke cluster assignment.
+3. **Gateway Configuration** — how the organization exposes its workloads.
+4. **Telemetry Configuration** — review the monitoring setup and finish.
+
+## Step 1: User Information
+
+Enter the organization details and choose its administrator.
+
+
+
+- **Organization Name** *(required)* — used to provision the three namespaces (`orgName`, `orgName-gw`, and `orgName-monitoring`).
+- **Organization Display Name** — a friendly name shown in the UI.
+- **Custom Annotations** — optional key/value pairs added to the client organization namespace. Click **Add Annotations** to add more.
+- **Organization Admin** — choose **Existing User** to assign an existing account, or **Create New User** to provision a new admin by entering a **Username** and **Email**.
+- **Visibility** — controls who can see the organization:
+ - **Public** — visible to everyone.
+ - **Limited** — visible to logged-in users only.
+ - **Private** — visible only to organization members.
+
+Click **Next** to continue.
+
+## Step 2: Select Cluster
+
+Assign the organization to a hub and spoke cluster, and optionally tune where its database workloads are scheduled.
+
+
+
+- **Hub Cluster** *(required)* — the management (hub) cluster for this organization.
+- **Spoke Cluster** *(required)* — the spoke cluster where the organization's databases run.
+- **Configure DB Nodepool** *(optional)* — key/value labels used to target specific nodes for database workloads. Click **Add Annotations** to add more.
+- **Tolerations** *(optional)* — add tolerations so workloads can be scheduled onto tainted nodes. Each toleration takes an **Effect**, **Key**, **Operator** (for example, `Exists`), and **Value**.
+
+Click **Next** to continue, or **Previous** to go back.
+
+## Step 3: Gateway Configuration
+
+Choose how the organization exposes its workloads. There are two top-level options.
+
+### Use Shared Gateway
+
+Select **Use Shared Gateway** to reuse the platform's shared gateway. No additional gateway configuration is required.
+
+
+
+### Use Dedicated Gateway
+
+Select **Use Dedicated Gateway** to give the organization its own gateway. Then pick a **Dedicated Gateway Type**.
+
+
+
+#### Use Existing Gateway
+
+Choose **Use Existing Gateway** and select a **Gateway Preset Config** to reuse an already-defined gateway configuration.
+
+
+
+#### Use Custom Gateway
+
+Choose **Use Custom Gateway** to define the gateway yourself. Use **Can it be used as a shared Gateway?** to pick a starting point.
+
+**Preload From Existing One** — start from an existing **Gateway Preset Config**, then edit the pre-filled fields across the **In Cluster** (certificates and keys), **Envoy Service** (service type, external IP, traffic policy, ports, provisioner type), and **Infra** (DNS provider, host type, host/domain, TLS issuer) sections.
+
+
+
+**Create New From Start** — build the gateway from scratch by filling in the same **In Cluster**, **Envoy Service**, and **Infra** sections with your own values.
+
+
+
+Click **Next** to continue.
+
+## Step 4: Telemetry Configuration
+
+In the final step, configure the telemetry settings that will be applied to the organization's `orgName-monitoring` namespace, then finish to create the client organization.
+
+
+
+- **Select Monitoring Cluster** — the observability cluster that will store this organization's telemetry. Its `tenant-operator` provisions a `Tenant` on the cluster's TelemetryStack, isolating the organization's data within the shared stack. See [OpenTelemetry Monitoring](../../cluster-management/otel-monitoring.md) for how the monitoring cluster is set up.
+- **Logs** — set the **Retention Period** for collected logs.
+- **Metrics** — set the retention periods for collected metrics:
+ - **Yearly Retention** — how long aggregated yearly metrics are kept.
+ - **Five Minute Retention** — how long five-minute resolution metrics are kept.
+ - **One Hour Retention** — how long one-hour resolution metrics are kept.
+
+Click **Submit** to create the client organization, or **Previous** to go back.
+
+Once created, the organization appears in the **Client Organizations** list and its admin can sign in to begin using it.
+
+## Next steps
+
+- [Add a Cluster to an Existing Client Organization](../add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org-2.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org-2.png
new file mode 100644
index 0000000000..6cebb2b9f6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org.png
new file mode 100644
index 0000000000..fa8db1b5b2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/add-cluster-to-existing-client-org.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-details.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-details.png
new file mode 100644
index 0000000000..722a48fed7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-details.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-overview.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-overview.png
new file mode 100644
index 0000000000..d620988638
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/client-org-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization-2.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization-2.png
new file mode 100644
index 0000000000..546bf36534
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization.png
new file mode 100644
index 0000000000..0e2fc6413b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-client-organization.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/create-new-custom-gateway.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-new-custom-gateway.png
new file mode 100644
index 0000000000..f3baa0aace
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/create-new-custom-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/preload-existing-gateway.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/preload-existing-gateway.png
new file mode 100644
index 0000000000..11de628e0c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/preload-existing-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/telemetry-configuration.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/telemetry-configuration.png
new file mode 100644
index 0000000000..de54c3fd06
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/telemetry-configuration.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/use-dedicated-gateway.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-dedicated-gateway.png
new file mode 100644
index 0000000000..58217460e3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-dedicated-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/use-existing-gateway.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-existing-gateway.png
new file mode 100644
index 0000000000..8b5577f49d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-existing-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/images/use-shared-gateway.png b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-shared-gateway.png
new file mode 100644
index 0000000000..6efaa5ddff
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/client-organization/images/use-shared-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/client-organization/overview.md b/content/docs/platform/v2026.7.10/guides/client-organization/overview.md
new file mode 100644
index 0000000000..68d41b2c27
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/client-organization/overview.md
@@ -0,0 +1,44 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: client-organization-overview
+ name: Overview
+ parent: client-organization
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Client Organizations
+
+A **Client Organization** is an isolated tenant that a platform administrator provisions from **Site Administration**. It lets you give a team or customer their own organization on KubeDB Platform, scoped to a specific cluster, gateway, and monitoring setup.
+
+When you create a client organization, the platform provisions three namespaces from the organization name (`orgName`):
+
+| Namespace | Purpose |
+| --- | --- |
+| `orgName` | The organization's primary workload namespace. |
+| `orgName-gw` | Holds the organization's gateway resources. |
+| `orgName-monitoring` | Holds the organization's telemetry and monitoring resources. |
+
+Each client organization is created with:
+
+- An **organization admin** — either an existing user or a newly created one.
+- An assigned **hub** and **spoke** cluster.
+- A **gateway** configuration (shared or dedicated).
+- A **telemetry** configuration applied to the monitoring namespace.
+
+## Where to find it
+
+Client organizations are managed from **Site Administration → Client Organizations**, under the **ADMINISTRATION** group in the left sidebar. You need site administration access to view and use this section.
+
+## Next steps
+
+- [Create a Client Organization](../create-client-organization.md) — a step-by-step walkthrough of the creation wizard.
+- [Add a Cluster to an Existing Client Organization](../add-cluster-to-existing-client-organization.md) — assign additional clusters after the organization is created.
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/_index.md b/content/docs/platform/v2026.7.10/guides/cluster-management/_index.md
new file mode 100644
index 0000000000..c00980b76d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/_index.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management
+ name: Cluster Management
+ parent: guides
+ popular: true
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/_index.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/_index.md
new file mode 100644
index 0000000000..8ee086f8fc
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/_index.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add
+ name: Adding a Cluster
+ weight: 10
+ parent: cluster-management
+ pre: dropdown
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/create-vendor-managed.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/create-vendor-managed.md
new file mode 100644
index 0000000000..d53d2d825b
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/create-vendor-managed.md
@@ -0,0 +1,22 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-createvendormanaged
+ name: Create Vendor Managed Clusters
+ parent: cluster-management-add
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Create Vendor Managed Clusters
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-observability-cluster.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-observability-cluster.md
new file mode 100644
index 0000000000..13b94a985f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-observability-cluster.md
@@ -0,0 +1,64 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-observability
+ name: Import Observability Cluster
+ parent: cluster-management-add
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Importing an Observability Cluster
+
+The Platform Console can run a dedicated **observability cluster** that collects
+telemetry (metrics, logs, and traces) from your spoke clusters through
+OpenTelemetry. This guide covers the two import-time tasks:
+
+1. Importing the observability cluster itself.
+2. Enabling the OpenTelemetry feature on the spoke clusters you want to monitor.
+
+For the full end-to-end setup — MinIO, the `telemetry` bucket, and the
+TelemetryStack — see [OpenTelemetry Monitoring](../../otel-monitoring.md).
+
+## Import the Observability Cluster
+
+Import the cluster as a spoke as you normally would (see
+[Adding a Cluster](overview.md)). During the import flow, select the
+**Observability Cluster** cluster profile. This provisions the components
+required to receive and store telemetry from other clusters.
+
+## Enable the OpenTelemetry Feature on a Spoke Cluster
+
+Once the observability cluster is ready, enable the OpenTelemetry feature on
+each spoke cluster you want it to monitor. There are two ways to do this.
+
+### Option A: During Cluster Import
+
+When importing a new cluster, select the destination observability cluster from
+the **Monitoring Cluster** drop-down in the import flow. This automatically
+enables the OpenTelemetry feature on the new spoke and routes its telemetry to
+the chosen monitoring cluster.
+
+
+
+### Option B: On an Existing Spoke Cluster
+
+1. Import the cluster as a spoke (if it is not already imported).
+2. Install the Perses dashboards on the cluster:
+
+ ```bash
+ helm upgrade -i kubedb-perses-dashboards \
+ oci://ghcr.io/appscode-charts/kubedb-perses-dashboards \
+ -n monitoring --create-namespace \
+ --version=v2026.4.27
+ ```
+
+3. Navigate to the cluster's **Observability** feature set.
+4. Enable the **`appscode-otel-stack`** feature.
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-rancher-cluster.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-rancher-cluster.md
new file mode 100644
index 0000000000..84f484749a
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-rancher-cluster.md
@@ -0,0 +1,37 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-rancher
+ name: Import Rancher Managed Clusters
+ parent: cluster-management-add
+ weight: 15
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Rancher Managed Cluster to Platform Console
+
+Importing a `Rancher-Managed` cluster requires a Rancher Type Credential and a Rancher Managed Organization.
+
+## Create Rancher Type Credential
+
+Add a credential of type "Rancher" — see [Credentials Management](../../../account-management/kubernetes/credentials/#rancher).
+
+## Create a Rancher Managed Organization
+
+Rancher clusters belong to Rancher Managed organizations, not personal accounts. Follow [Create a New Organization](../../../account-management/orgs-members/#create-a-new-organization) with these settings:
+
+1. Set the organization's Origin to `Rancher Managed`.
+2. Provide the Rancher `API Endpoint` (found on the `Account & API Keys` page).
+3. Click `Create`.
+
+## Import the Cluster
+
+1. Switch to the Rancher organization: in the [AppsCode Console](https://console.appscode.com), click your profile, choose `Switch Account`, and select the Rancher organization.
+2. Follow the standard import process in [Import Vendor Managed Clusters](../import-vendor-managed.md).
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-vendor-managed.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-vendor-managed.md
new file mode 100644
index 0000000000..664b0ae432
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/import-vendor-managed.md
@@ -0,0 +1,52 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-vendormanaged
+ name: Import Vendor Managed Clusters
+ parent: cluster-management-add
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Vendor-Managed Cluster to Platform Console
+
+1. Go to the [Platform Console](https://console.appscode.com/) and click `Add Cluster`.
+
+### Choose Provider
+
+2. In the `Vendor Managed` section, select the provider hosting your cluster.
+
+### Select Credential
+
+3. Choose a credential with permission to access and import the cluster, then click `Next`. To create one, use the `+Create Credential` button (see [Credentials](../../../account-management/kubernetes/credentials.md)).
+
+
+
+
+
+
+
+
+
+
+
+
+
+### Select Cluster
+
+4. Selection depends on the provider:
+ - `Linode` / `Digital Ocean`: select the cluster directly.
+ - `AKS` / `EKS` / `GKE`: choose the `Resource Group`, `Region`, or `Project`, then select the cluster.
+
+
+
+### Customize Features and Import
+
+5. Click `Import` to bring the cluster into the Platform Console, then explore it in the dashboard.
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/overview.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/overview.md
new file mode 100644
index 0000000000..a5f26d2158
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/overview.md
@@ -0,0 +1,30 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-overview
+ name: Overview
+ parent: cluster-management-add
+ weight: 1
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Cluster to Platform Console
+
+Adding a Kubernetes cluster to the Platform Console takes two steps:
+
+## Step 1: Select the Cluster
+
+- **Vendor-Managed:** [Import Vendor Managed Clusters](../import-vendor-managed.md)
+- **Rancher-Managed:** [Import Rancher Managed Clusters](../import-rancher-cluster.md)
+- **Self-Managed:** [Import Self-Managed Clusters](../self-managed/import-self-managed.md)
+
+## Step 2: Customize Features
+
+Choose the features to install during import. The selected features are deployed into the cluster as part of the import process.
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/_index.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/_index.md
new file mode 100644
index 0000000000..06353a15a5
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/_index.md
@@ -0,0 +1,17 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-selfmanaged
+ name: Import Self-Managed Clusters
+ parent: cluster-management-add
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-private.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-private.md
new file mode 100644
index 0000000000..ef2619de2b
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-private.md
@@ -0,0 +1,37 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-importprivatecluster
+ name: Import Private Clusters
+ parent: cluster-management-add-selfmanaged
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Private Self-Managed Cluster to Platform Console
+
+1. Go to the [Platform Console](https://console.appscode.com/) and click `Add Cluster`.
+
+### Select Cluster Type
+
+2. In the `Self Managed` section, choose the private/air-gapped cluster option.
+
+### Provide Kubeconfig and Get Import Link
+
+3. Provide the kubeconfig for your cluster and click `Get Import Link`. Run either of the two returned commands inside your cluster.
+
+### Customize Features
+
+4. The UI then moves to the feature customization step.
+
+### Explore
+
+5. Once imported, explore the cluster in the Platform Console.
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-public.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-public.md
new file mode 100644
index 0000000000..b5b7526342
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-public.md
@@ -0,0 +1,41 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-importpubliccluster
+ name: Import Public Clusters
+ parent: cluster-management-add-selfmanaged
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Public Self-Managed Cluster to Platform Console
+
+1. Go to the [Platform Console](https://console.appscode.com/) and click `Add Cluster`.
+
+### Select Cluster Type
+
+2. In the `Self Managed` section, choose the public cluster option.
+
+
+
+### Provide Kubeconfig
+
+3. Provide the kubeconfig for your cluster.
+
+
+
+### Customize Features
+
+4. Proceed to the feature customization step.
+
+### Explore
+
+5. Once imported, explore the cluster in the Platform Console.
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-self-managed.md b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-self-managed.md
new file mode 100644
index 0000000000..22b49810d6
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/add-cluster/self-managed/import-self-managed.md
@@ -0,0 +1,32 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-add-selfmanaged-overview
+ name: Overview
+ parent: cluster-management-add-selfmanaged
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Adding a Self-Managed Cluster to Platform Console
+
+A self-managed cluster is any cluster you have a kubeconfig for — public or air-gapped. Use the guides below to import it into the Platform Console:
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-features.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-features.md
new file mode 100644
index 0000000000..c476abf09f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-features.md
@@ -0,0 +1,200 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-feature
+ name: Manage Feature Sets
+ parent: cluster-management
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Manage Feature Sets
+
+**Feature Sets** are groups of AppsCode product capabilities that you can install or remove on any connected cluster. This page covers all 19 available Feature Sets and shows the enable flow for two common ones: **Backup & Recovery** and **Databases**.
+
+> For a per-feature breakdown of every Feature Set — what each feature does, why you'd enable it, and its prerequisites — see the [Feature Set Reference](../feature-reference.md).
+
+---
+
+## Available Feature Sets at a Glance
+
+The Feature Sets grid on the Cluster Overview page shows all available product modules and their current installation status.
+
+
+
+| Feature Set | Description |
+|---|---|
+| **Opscenter Core** *(Required)* | Core platform capabilities — must be installed first. All other Feature Sets depend on it. |
+| **Backup & Recovery** | Scheduled backup and recovery for Kubernetes-native applications using KubeStash (Stash 2.0). |
+| **Cluster API AWS (CAPA)** | Lifecycle management tools for clusters running on AWS via the Cluster API. |
+| **Cluster API GCP (CAPG)** | Lifecycle management tools for clusters running on GCP via the Cluster API. |
+| **Cluster Management** | Cluster provisioning and management tools. |
+| **Cost Management** | Measure and allocate infrastructure and container resource costs. |
+| **Crossplane** | The cloud-native control plane framework for infrastructure as code. |
+| **Databases** | Production-grade database management powered by KubeDB — supports Elasticsearch, Kafka, MongoDB, MySQL, Postgres, Redis, and more. |
+| **Kubernetes Native Service** | Components for building Kubernetes-native service patterns. |
+| **Multicluster Hub** | Deploy and manage a central hub for a fleet of clusters. |
+| **Multicluster Spoke** | Connect this cluster as a spoke to an existing Multicluster Hub. |
+| **Networking Addons** | Various networking plugins and extensions for Kubernetes. |
+| **Observability** | Cluster monitoring, metrics, and dashboards using Prometheus and Grafana. |
+| **Opscenter Tools** | DevOps tooling and management utilities for KubeDB Platform. |
+| **Policy Management** | Platform-level policy enforcement tools. |
+| **Secret Management** | Tools for secure secret storage and distribution across namespaces. |
+| **Security** | TLS certificate management, secret scanning, and image vulnerability tooling. |
+| **Storage Addons** | Additional storage drivers and integrations for Kubernetes. |
+
+> **Tip:** Feature Sets marked **Required** must be installed before enabling any others. **Opscenter Core** is always required first.
+
+Once you have enabled some Feature Sets, the Cluster Overview grid reflects the updated statuses — cards previously showing **Not Installed** will update to **Ready**.
+
+
+
+---
+
+## Feature Set: Backup & Recovery
+
+**Backup & Recovery** enables scheduled backup and recovery for Kubernetes-native applications using KubeStash (formerly Stash). It consists of three components: **Stash 2.0** (aka KubeStash), **Stash Presets**, and **Stash**.
+
+### Step 1 — Open the Backup & Recovery Feature Set Page
+
+From the Cluster Overview, click the **Backup & Recovery** card. The Feature Set page opens, showing:
+- A blue info banner: *"No feature enabled yet for this feature set."*
+- A **Components** section with three cards: **Stash 2.0** *(Recommended)*, **Stash Presets** *(Recommended)*, and **Stash**
+- A green **Enable** button on each component card, and a master **Enable** button at the top-right
+
+
+
+### Step 2 — Select Components and Configure the Preset
+
+Click the top-right **Enable** button to open the **Enable Feature Set modal**. The modal shows:
+
+- A checklist of available components — select the ones you want to enable (e.g., **Stash 2.0** and **Stash Presets** are pre-checked as Recommended)
+- A **Preset Configuration** section with required fields:
+ - **Backend Provider** — the storage backend (e.g., AWS S3, GCS, Azure)
+ - **Bucket** — the bucket or container name
+ - **End Point** — the storage endpoint URL
+ - **Insecure TLS** — toggle if using insecure TLS
+ - **Prefix** — optional path prefix inside the bucket
+ - **Region** — the storage region (e.g., `us-east-1`)
+
+> **Note:** Enabling a feature auto-enables any prerequisite features — a blue banner at the top of the modal confirms this.
+
+Fill in all required fields and click **Preview** to advance.
+
+
+
+### Step 3 — Review the Generated Helm Values
+
+The modal advances to the **Values Preview** step:
+
+- The **left panel** lists each generated Helm release file (e.g., `kubestash.yaml`, `stash_presets.yaml`)
+- The **right panel** shows the full YAML values for the selected file
+- Switch between **Edit** and **Preview Changes** tabs to review or compare against defaults
+- Click **Compare default values** to diff against the out-of-the-box configuration
+- Click **← Previous** to go back, or **Deploy** to apply
+
+
+
+### Step 4 — Deploy and Monitor Progress
+
+After clicking **Deploy**, the modal shows a **live deploy log**. You will see output like:
+
+```
+Enabling FeatureSet `opscenter-backup` started!
+```
+
+Wait for the log stream to complete, then close the modal.
+
+
+
+### Step 5 — Verify the Feature Set Status
+
+After deployment, the Feature Set page shows the updated component statuses. If a dependency is still being pulled, a banner reads: *"Feature 'stash-presets' is enabled but not ready."* The affected component cards show a ⚠️ warning icon with a tooltip *"Required workload does not exist."*
+
+
+
+Once all components are running, all cards show a green ✓ checkmark and both **Configure** and **Disable** buttons appear at the top-right — confirming the Feature Set is fully **Ready**.
+
+
+
+---
+
+## Feature Set: Databases
+
+**Databases** enables production-grade database management powered by **KubeDB**. It supports a wide range of database engines and is managed by a single component: **KubeDB** (with sub-components KubeDB Opscenter and KubeDB UI Presets).
+
+### Step 1 — Open the Databases Feature Set Page
+
+Click the **Databases** card on the Cluster Overview. The Feature Set page opens, showing:
+- A blue info banner: *"No feature enabled yet for this feature set."*
+- A single **KubeDB** component card *(Recommended)* with sub-components: `KubeDB`, `KubeDB Opscenter`, `KubeDB UI Presets`, and **More**
+- A green **Enable** button on the component card and at the top-right
+
+
+
+### Step 2 — Select Database Types
+
+Click the **Enable** button to open the **Enable Feature Set modal**. The modal shows:
+
+- A checklist of **KubeDB components**: KubeDB, KubeDB Opscenter, KubeDB UI Presets, and Prepare Cluster
+- A **Select Database Types** multi-select field — choose which database engines to enable:
+ - Elasticsearch, Kafka, MariaDB, MongoDB, MySQL, Postgres, Redis, Cassandra, ClickHouse, Druid, FerretDB, Hazelcast, Ignite, Oracle, PerconaXtraDB, PgBouncer, Pgpool, ProxySQL, RabbitMQ, Singlestore, Solr, ZooKeeper
+- A blue note: *"Enabling a feature auto enables any prerequisite features."*
+
+Select your required database types and click **Preview**.
+
+
+
+### Step 3 — Review the Generated Helm Values
+
+The modal advances to the YAML values preview. Three Helm release files are listed on the left:
+- `kubedb.yaml`
+- `kubedb_opscenter.yaml`
+- `kubedb_ui_presets.yaml`
+
+The YAML editor on the right shows the `featureGates` configuration — each selected database type is set to `true`, others to `false`. Use **Edit / Preview Changes** tabs to review, then click **Deploy**.
+
+
+
+### Step 4 — Deploy and Monitor Progress
+
+After clicking **Deploy**, the live deploy log shows:
+
+```
+Enabling FeatureSet `opscenter-datastore` started!
+Deploying resources for FeatureSet `opscenter-datastore` started!
+```
+
+Wait for the log to complete, then close the modal.
+
+
+
+### Step 5 — Verify the Feature Set Status
+
+After deployment, the Databases page shows the KubeDB component status. While resources are still initializing, the banner reads: *"Feature 'kubedb' is enabled but not ready."* The component card shows a ⚠️ warning icon and tooltip *"Required workload does not exist."*
+
+
+
+Once KubeDB is fully running, the component card shows a green ✓ checkmark and the page header shows **Configure** and **Disable** buttons — confirming the Feature Set is fully **Ready**.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| View all Feature Sets | Cluster Overview → Feature Sets grid |
+| Open a Feature Set | Click any Feature Set card |
+| Enable a Feature Set | Click **Enable** → select components → configure → **Preview** → **Deploy** |
+| Check component status | ✓ = Ready, ⚠️ = Not Ready, **Enable** button = Not Installed |
+| Disable a Feature Set | Open Feature Set page → click **Disable** (top-right) |
+| Reconfigure a Feature Set | Open Feature Set page → click **Configure** (top-right) |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-helm-charts.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-helm-charts.md
new file mode 100644
index 0000000000..65a3fc8219
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-helm-charts.md
@@ -0,0 +1,74 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-helmcharts
+ name: Manage Cluster Helm Charts
+ parent: cluster-management
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Helm Chart Management
+
+The **Helm** group in the Cluster UI sidebar gives you full visibility into your cluster's Helm ecosystem. It has three pages — Releases, HelmRelease, and HelmChart — covering deployed releases, FluxCD-managed releases, and chart sources respectively.
+
+## Open the Helm Section
+
+1. Navigate to the [Platform Console](https://console.appscode.com).
+2. Click on your imported cluster to open its Cluster Overview page.
+3. In the left sidebar, click **Helm** to expand it.
+
+---
+
+## Releases
+
+The Releases page lists all Helm v3 releases currently deployed in your cluster — everything installed via `helm install`, regardless of how it got there. This is the primary page to check what is running, what version is deployed, and whether the release is in a healthy state.
+
+Use this page to get a quick overview of all deployed charts, check release status, or install a new chart using the **+ Install Chart** button.
+
+Lists every release with its **Name**, **Namespace**, **Status** (e.g. deployed, failed), **Version**, and **Age**. Use the **Select All** and **All Namespaces** dropdowns to filter the list.
+
+
+
+---
+
+## HelmRelease
+
+A HelmRelease is a FluxCD resource that declaratively manages a Helm chart installation. The Platform Console tracks every HelmRelease and shows its reconciliation state, so you can see whether a GitOps-driven installation or upgrade succeeded or is still in progress.
+
+Use this page to check FluxCD-managed release health, spot failed reconciliations, or create a new HelmRelease from the UI.
+
+Lists every HelmRelease with its **Namespace**, **Age**, **Ready** status, and a **Status** message showing the last Helm operation result. Click **+ Create HelmRelease** to define a new one.
+
+
+
+---
+
+## HelmChart
+
+A HelmChart is a FluxCD resource that sources a specific chart and version from a HelmRepository. Each HelmRelease references a HelmChart behind the scenes. This page tells you which charts are being pulled, from where, and whether the source is reachable and up to date.
+
+Use this page to verify chart versions in use, check that chart sources are resolving correctly, or create a new HelmChart resource.
+
+Lists every HelmChart with its **Namespace**, **Annotations**, **Age**, **Chart** name, **Version**, **Source Kind**, **Source Name**, **Ready** state, and **Status**. Click **+ Create HelmChart** to add a new chart source.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| View all deployed releases | Click **Releases** under the Helm group |
+| Install a new chart | Click **+ Install Chart** on the Releases page |
+| Check FluxCD-managed release health | Click **HelmRelease** under the Helm group |
+| View chart sources | Click **HelmChart** under the Helm group |
+| Create a new FluxCD release | Click **+ Create HelmRelease** on the HelmRelease page |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-overview.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-overview.md
new file mode 100644
index 0000000000..db25327c20
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-overview.md
@@ -0,0 +1,167 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-overview
+ name: Cluster Overview
+ parent: cluster-management
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Cluster Overview
+
+The **Cluster Overview** page is your primary dashboard for a connected Kubernetes cluster. It shows cluster identity, status, installed Feature Sets, and live node information — all in one place.
+
+---
+
+## Step 1 — Open Your Cluster
+
+From the **KubeDB Platform Console UI** home screen, you will see the **ALL CLUSTERS** grid. Each cluster card shows its name, status badge (e.g., **Active**), Kubernetes version, provider, number of nodes, and age.
+
+Click on any cluster card to open its Overview page.
+
+
+
+> The **+ Add Cluster** tile lets you import a new cluster at any time.
+
+---
+
+## Step 2 — Read the Cluster Overview Page
+
+After clicking your cluster, you land on the **Cluster Overview** page. The page is organized into three sections: **Basic**, **Feature Sets**, and **Nodes**.
+
+### Basic Information
+
+The **Basic** section at the top displays the cluster's core identity:
+
+| Field | Description |
+|---|---|
+| **Name** | The cluster name as registered in KubeDB Platform |
+| **Endpoint** | The Kubernetes API server address |
+| **UID** | The unique identifier of this cluster |
+| **Provider** | Cloud or infrastructure provider (e.g., Generic, AWS, GCP) |
+| **Zone** | Deployment zone (if applicable) |
+| **Status** | Connection state — **Active** means the cluster is reachable |
+| **Kubernetes Version** | The version of Kubernetes running on this cluster |
+
+Two action buttons appear top-right inside this section:
+- **Connect** — Downloads a KubeConfig for direct `kubectl` access
+- **Remove** — Disconnects and removes the cluster from KubeDB Platform
+
+
+
+---
+
+## Step 3 — Download the KubeConfig
+
+Click the **Connect** button to open the **Kube Config** modal. This dialog shows the full kubeconfig YAML for your cluster with two action buttons:
+
+- **⬇ Download** — Saves the kubeconfig file to your local machine
+- **Copy** — Copies the content to your clipboard
+
+You can use this kubeconfig with `kubectl` to interact directly with the cluster from your terminal.
+
+
+
+---
+
+## Step 4 — Review Feature Sets
+
+Scroll down past the **Basic** section to see the **Feature Sets** grid. Each card represents a product module from AppsCode that can be installed on your cluster.
+
+### Available Feature Sets
+
+| Feature Set | Description |
+|---|---|
+| **Opscenter Core** *(Required)* | Core management capabilities — must be installed first |
+| **Backup & Recovery** | Scheduled backup & recovery using KubeStash |
+| **Cluster API AWS (CAPA)** | Lifecycle tools for AWS-provisioned clusters |
+| **Cluster API GCP (CAPG)** | Lifecycle tools for GCP-provisioned clusters |
+| **Cluster Management** | Cluster provisioning & management tools |
+| **Cost Management** | Measure and allocate infrastructure and container costs |
+| **Crossplane** | The cloud-native control plane framework |
+| **Databases** | Production-grade database management via KubeDB |
+| **Kubernetes Native Service** | Components for Kubernetes Native Service patterns |
+| **Multicluster Hub** | Deploy and manage a multicluster hub |
+| **Multicluster Spoke** | Connect this cluster as a spoke to a hub |
+| **Networking Addons** | Various networking addons for Kubernetes |
+| **Observability** | Cluster monitoring with Prometheus and Grafana |
+| **Opscenter Tools** | DevOps tools for KubeDB Platform |
+| **Policy Management** | Platform policy management tools |
+| **Secret Management** | Tools for secret management |
+| **Security** | TLS, secret scanning, and vulnerability tools |
+| **Storage Addons** | Various storage addons for Kubernetes |
+
+### Status Badges
+
+Each Feature Set card shows a status badge:
+- **Ready** *(green)* — Installed and fully operational
+- **Not Ready** *(yellow)* — Installed but not fully operational
+- **Not Installed** *(red)* — Available but not yet enabled on this cluster
+
+Hover over any **Not Installed** card to see a tooltip like *"No feature enabled yet for this feature set."*
+
+
+
+Click any Feature Set card to open the **Feature Set Management** page where you can enable or configure its components. See [Feature Management](../cluster-features.md) for a full walkthrough.
+
+---
+
+## Step 5 — View Nodes
+
+Scroll past the **Feature Sets** grid to the **Nodes** section. Each registered cluster node is shown as a card with:
+
+- Node **Name** and **Status** (e.g., `Ready`)
+- Kubernetes version, architecture, and OS labels
+- **Role** (e.g., `control-plane`)
+- **CPU** cores, **Memory** (GiB), and active **Pods** count
+- **Pod CIDR** and **Internal IP**
+- **Age**
+
+Click **Nodes** in the left sidebar to open the dedicated **Nodes list page**, which shows all nodes with their labels and annotations in a table format.
+
+
+
+---
+
+## Step 6 — View Node Details
+
+Click on a node's name in the Nodes list to open the **Node Detail** page. This page shows:
+
+- **Name**, **Namespace**, **Labels**, and **Annotations** in the **Basic** tab
+- Sub-pages accessible from the left panel: **Security**, **Events**, **Graph**, **Manifest**
+
+Use the **Edit** button (top-right) to modify the node spec, or **Delete** to remove the node from the cluster.
+
+
+
+### Editing a Node
+
+Clicking **Edit** opens a structured form where you can modify:
+- **Pod CIDRs** — Network ranges assigned to the node
+- **Taints** — Taint key/value pairs and effects for scheduling control
+- **Unschedulable** toggle — Mark the node as unschedulable
+
+Switch between **Form**, **YAML**, and **JSON** views using the tabs at the top-right of the editor.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| Open a cluster | Click the cluster card on the home screen |
+| Download kubeconfig | Click **Connect** in the Basic section → **Download** |
+| Check Feature Set status | Scroll to the Feature Sets grid — green = Ready, red = Not Installed |
+| Manage a Feature Set | Click the Feature Set card → Feature Management page |
+| View all nodes | Click **Nodes** in the left sidebar |
+| Edit a node | Open node detail → **Edit** button |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-presets.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-presets.md
new file mode 100644
index 0000000000..b144a34afd
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-presets.md
@@ -0,0 +1,162 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-preset
+ name: Manage Presets
+ parent: cluster-management
+ weight: 70
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Manage Cluster Presets
+
+**Cluster Presets** are reusable configuration templates that are automatically created when you enable certain Feature Sets (for example, **Backup & Recovery** creates a `stash-presets` preset). They define default values — such as backup schedule, storage references, and retention policies — that can be applied uniformly across multiple namespaces.
+
+---
+
+## Step 1 — Open the Preset List
+
+In the left sidebar, navigate to **Preset** (under **Cluster Settings**). The **Cluster Presets** page lists all presets available in your cluster.
+
+Each row shows:
+- **Name** — The preset's name (clickable to open its detail page)
+- **Namespace** — The namespace the preset belongs to (or `-` for cluster-scoped)
+- **Annotations** — Key labels attached to the preset (e.g., `ace.appscode.com/managed: true`, `app.kubernetes.io/managed-by`)
+- **Age** — How long ago the preset was created
+
+
+
+> Presets are automatically created when you enable a Feature Set that requires preset configuration (such as Backup & Recovery). After enabling a Feature Set, you may see a new preset appear in this list.
+>
+> 
+
+
+
+---
+
+## Step 2 — Open a Preset's Detail Page
+
+Click on a preset name (e.g., `stash-presets`) to open the **Preset Detail** page. This page has two tabs in the left panel:
+
+- **Basic Info** — Lists the preset's name, UID, and any namespace-scoped copies (Namespace Presets)
+- **Edit Values** — Lets you modify the preset's configuration values
+
+The **Basic Info** tab also shows a **Namespace Presets** table with all namespace-level copies of this preset. If no copies exist yet, it shows *"No Data Available."*
+
+A green **Extend to Namespace** button (top-right) creates a namespace-scoped copy of this preset.
+
+
+
+---
+
+## Step 3 — Edit Preset Values
+
+Click the **Edit Values** tab in the left panel to modify the preset's default configuration.
+
+The edit form presents each configurable section as a collapsible card. For example, the `stash-presets` preset exposes:
+
+| Section | Fields |
+|---|---|
+| **Encryption Secret** | Namespace, Name |
+| **Retention Policy** | Namespace, Name |
+| **Storage Ref** | Namespace, Name |
+| **Schedule** | A cron expression (e.g., `*/15 * * * *`) |
+
+Update the values as needed and click **Preview** to advance to the review step.
+
+
+
+### Preview the Generated YAML
+
+After clicking **Preview**, the page displays the full generated `stash-presets` specification in YAML (or JSON) format on the right. You can directly edit this YAML or JSON.
+
+
+Click **Submit** to apply the updated preset values to the cluster.
+
+
+
+---
+
+## Step 4 — Edit KubeDB Presets
+
+Click on the `kubedb-ui-presets` preset to open its detail page. Click the **Edit Values** tab in the left panel to modify the general KubeDB configuration.
+
+The KubeDB preset configuration is organized into four main sections:
+
+1. **Machine specifics** — Configure deployment type (Shared/Dedicated), cluster tiers, and node topologies.
+2. **Database specifics** — Manage versions and modes for supported databases (Postgres, Redis, MongoDB, etc.), storage classes, and TLS settings.
+3. **Monitoring & Backups specifics** — Configure monitoring agents and default backup settings.
+4. **Extras** — Additional configuration fields.
+
+
+
+### Machine Specifics
+
+In this section, you can define if users are allowed to modify the deployment type, cluster tier, and node placement. You can also specify the available options and default values for these fields.
+
+
+
+### Database Specifics
+
+The **Database Specifics** section is where you manage settings for different database engines. You can enable or disable specific versions and modes for each database type.
+
+
+
+For example, in the **Postgres** subsection, you can toggle which versions (e.g., 13.x, 14.x) and modes (Standalone, Cluster) are available to users.
+
+
+
+You can also configure default **Auth Credentials**, **Storage Classes**, and **TLS** settings that will be applied to new database instances.
+
+
+
+### Monitoring & Backup Specifics
+
+Configure the default monitoring agent and resources (CPU/Memory). You can also enable or disable backups by default and specify if they should be managed via `BackupConfiguration` or `BackupBlueprint`.
+
+
+
+
+
+### Preview and Submit
+
+After completing your changes, click **Preview** to review the generated YAML specification.
+
+
+
+Click **Submit** to update the `kubedb-ui-presets` configuration in your cluster.
+
+---
+
+## Step 5 — Extend a Preset to a Namespace
+
+Presets can be scoped to specific namespaces so that workloads in those namespaces inherit the preset's configuration. To do this, click the **Extend to Namespace** button (top-right on the Preset Detail page).
+
+A **Presetless Namespace** dropdown appears, listing all namespaces in the cluster that do not yet have a copy of this preset (e.g., `default`, `kubedb`, `flux-system`, `kube-system`, `monitoring`, etc.).
+
+Select the target namespace from the list.
+
+
+
+After selecting the namespace, a **Preset Values** editor appears (YAML/JSON). You can customize the values specifically for this namespace before applying. Click **Apply** to create the namespace-scoped preset copy.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| View all presets | Left sidebar → **Preset** |
+| Open a preset | Click the preset name in the list |
+| Edit preset values | Preset detail → **Edit Values** tab → update fields → **Preview** → **Submit** |
+| Apply to a namespace | Preset detail → **Extend to Namespace** → pick namespace → **Apply** |
+| Check namespace copies | Preset detail → **Basic Info** → Namespace Presets table |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-sidebar.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-sidebar.md
new file mode 100644
index 0000000000..f9ba475c53
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-sidebar.md
@@ -0,0 +1,97 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-sidebar
+ name: Customize Cluster Sidebar
+ parent: cluster-management
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Customize the Cluster Sidebar
+
+The **Cluster Sidebar** is the navigation panel inside a connected cluster. By default it shows a set of Kubernetes workloads and AppsCode custom resources. The **Sidebar Settings** page lets you customize which menu items appear.
+
+---
+
+## Step 1 — Open the Cluster Overview
+
+From the platform console, click on your cluster (e.g., `default`) to open the **Cluster Overview** page. The left sidebar shows the default set of sections: **Kubernetes**, **Workloads**, **Helm**, **Datastore**, **Service & Discovery**, **Config**, **Storage**, **Monitoring**, **Security**, and **Admin**.
+
+
+
+> **Tip:** The default sidebar already covers the most common resources. You only need to open Sidebar Settings if you want to add, remove, or rearrange menu items.
+
+---
+
+## Step 2 — Open Sidebar Settings
+
+Click the **⚙ Gear icon** in the top-right navbar to enter the cluster's **Settings** area. In the left settings menu, click **Sidebar**.
+
+You will land on the **Sidebar Settings** page, which has two main panels:
+
+| Panel | Description |
+|---|---|
+| **All Available Menus** (left) | Every resource group and kind available to add to your sidebar |
+| **Updated List** (right) | The current sidebar layout that is live on your cluster |
+
+At the top-right of the page are two action buttons:
+- **Default** — Resets the sidebar back to the original default layout
+- **Save** — Saves your current changes
+
+
+
+---
+
+## Step 3 — Search for a Resource (Optional)
+
+The **All Available Menus** panel lists hundreds of resource types grouped by API category. To quickly find what you need, use the **search box** (🔍) at the top of that panel.
+
+For example, typing `cert` instantly filters the list and highlights all matches — such as **Cert Manager → Certificate**, **Certificate → CertificateSigningRequest**, and so on. A result counter (e.g., *Found 4 Search Results for 'cert'*) and pagination controls help you navigate through matches.
+
+
+
+> **Note:** The search is case-insensitive. Matched groups and items are highlighted in green so they stand out clearly.
+
+---
+
+## Step 4 — Add or Rearrange Items (Drag & Drop)
+
+To add a resource to your sidebar, **drag** it from the **All Available Menus** panel on the left and **drop** it into the **Updated List** panel on the right at the position you prefer.
+
+In the example below, the user is dragging **Appscode K8s Management → ProjectQuota** into the current sidebar layout. You can see it appearing as a floating drag indicator (`⠿`) in the left panel.
+
+
+
+You can also drag existing items within the **Updated List** panel to reorder them according to your workflow preferences.
+
+---
+
+## Step 5 — Save and Verify
+
+Once you are satisfied with your layout, click the green **Save** button in the top-right corner.
+
+The sidebar of the cluster will immediately reflect your changes. In the example below, after saving, the **Appscode K8s Management** group with **ProjectQuota** now appears in the cluster sidebar on the left.
+
+
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Open Sidebar Settings | Click the ⚙ icon in the top-right navbar → **Sidebar** |
+| Find a resource | Use the 🔍 search box in the **All Available Menus** panel |
+| Add a resource to sidebar | Drag it from the left panel into the right panel |
+| Remove a resource | Drag it back from the right panel to the left panel |
+| Reorder sidebar items | Drag items within the right panel |
+| Reset to defaults | Click the **Default** button |
+| Apply changes | Click the **Save** button |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-upgrade.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-upgrade.md
new file mode 100644
index 0000000000..06c5aa2cbc
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-upgrade.md
@@ -0,0 +1,212 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-upgrade
+ name: Upgrade Cluster
+ parent: cluster-management
+ weight: 80
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Upgrading Your KubeDB Platform: Management, Imported, and Spoke Clusters
+
+## Overview
+
+Upgrade a **KubeDB Platform** deployment across all cluster tiers: the base management cluster, the KubeDB Platform cluster, general imported clusters, and spoke clusters. The example below upgrades from release `2025.5.16` to `2025.6.x`.
+
+---
+
+## Architecture
+
+```
+ ┌─────────────────────────────────┐
+ │ Management Cluster │
+ │ (KubeDB Platform control plane) │
+ └────────────────┬────────────────┘
+ │
+ ┌──────────────────┼──────────────────┐
+ │ │ │
+ ┌──────────────▼──────┐ ┌────────▼────────┐ ┌─────▼──────────┐
+ │ KubeDB Platform │ │ Imported Cluster │ │ Spoke Cluster │
+ │ Cluster (management)│ │ (generic import) │ │ (generic import│
+ └─────────────────────┘ └─────────────────┘ └────────────────┘
+```
+
+Each tier is upgraded separately; the order matters.
+
+---
+
+## Pre-checks
+
+Before starting, verify your current installer version and target release.
+
+1. Log in to [appscode.com](https://appscode.com) and switch to your organization.
+2. Navigate to your installer and click **View Details**.
+3. Note the **current version** (e.g., `2025.5.16`) and confirm the **target version**
+ (e.g., `2025.6.x`).
+
+```bash
+# Confirm current Helm release versions on the management cluster
+helm list -A | grep opscenter-features
+
+# Watch releases during upgrade
+kubectl get helmreleases -A -w
+```
+
+---
+
+## Upgrade Flow
+
+### Step 1 — Download the new installer archive
+
+1. On the installer page, click **Upgrade to **.
+2. Click **Download** to get the updated `.values` (val) file.
+3. The downloaded archive lands in your local archive folder (e.g., `archive2/`).
+
+```bash
+# Optional: inspect the downloaded values file before applying
+cat ~/Downloads/.values.yaml
+```
+
+---
+
+### Step 2 — Apply the upgrade via Platform UI
+
+1. Switch from the **Console UI** to the **Platform UI**.
+2. Go to **User Settings → Upgrade**.
+3. Select the val file downloaded in Step 1.
+4. Click **Update Version**.
+
+The platform creates a background job that updates Helm releases one by one.
+
+```bash
+# Monitor the upgrade job on the management cluster
+kubectl get jobs -n ace -w
+
+# Watch Helm releases roll forward
+kubectl get helmreleases -A -w
+```
+
+> **Expected state:** `current version: 5.16 → update in progress: 6.16`
+
+Once the job completes, verify the op-center feature set reflects the new version.
+
+---
+
+### Step 3 — Upgrade spoke clusters
+
+Spoke clusters are imported as **generic DBaaS** generally. Update them individually before
+updating the cluster set.
+
+1. In the Console, go to **Your Organization → Hub Cluster → KubeDB Platform**.
+2. Select the correct **Cluster set** (how you imported). For example, Generic DBaaS.
+3. Select your spoke cluster.
+4. Click **Update KubeDB Platform Resources → Update Version → Yes**.
+
+
+
+```bash
+# After triggering, watch the QB operator start the upgrade on the spoke
+kubectl get helmreleases -A -w --context
+
+# Wait for all pods to return to Running
+kubectl get pods -A --context
+```
+
+The cluster set manifest (which holds metadata about all spoke clusters) updates
+almost instantly. The underlying Helm releases take longer — wait for them to
+reconcile before moving on.
+
+---
+
+### Step 4 — Upgrade general imported clusters
+
+1. In the Console, select the **General Imported Cluster**.
+2. Open its **Settings** page and click **Update Version**.
+
+```bash
+# Verify on the imported cluster
+kubectl get helmreleases -A --context
+```
+
+This path updates Helm releases directly (not via a cluster set), so progress is
+visible immediately.
+
+---
+
+### Step 5 — Update the cluster set
+
+After **all** individual clusters are on the new version:
+
+1. In the Console, go to **Your Organization → Hub Cluster → KubeDB Platform**.
+2. Select the correct **Cluster set** (how you imported). For example, Generic DBaaS.
+3. Click **Update Cluster Set**.
+
+```bash
+# Confirm cluster set version
+kubectl get clusterset -A
+```
+
+> Before clicking **Update Cluster Set**, you will see the cluster set still shows the old version (e.g., `5.6`).
+> After the update it will be marked as **unaligned** briefly, then reconcile.
+
+---
+
+### Step 6 — Verify
+
+```bash
+# Check every Helm release is at the new version across all clusters
+for ctx in management spoke imported; do
+ echo "=== $ctx ==="
+ helm list -A --kube-context $ctx | grep -v DEPLOYED
+done
+
+# Spot-check the search manager (may self-update from the cluster side)
+kubectl get deployment search-manager -n ace -o jsonpath='{.spec.template.spec.containers[0].image}'
+```
+
+All clusters should report version `6.6.16` (or your target release).
+
+---
+
+## Lessons Learned
+
+| Observation | Takeaway |
+|---|---|
+| One Helm release failed to update via the job | It had already reconciled from the cluster side — not always an error |
+| Cluster set update is near-instant | It only patches a manifest, not the releases themselves — releases follow async |
+| Search manager self-updated | Some components pull their version from the cluster operator, not the installer job |
+| Upgrade order matters | Always update individual clusters **before** the cluster set |
+| Ports need time after upgrade | Wait for all pods to reach `Running` before declaring success |
+
+---
+
+## Quick Reference
+
+```
+appscode.com → Download val file
+ ↓
+Platform UI → Update Version (Management / Platform cluster)
+ ↓
+Console → Generic DBaaS → Update KubeDB Platform Resources (each spoke)
+ ↓
+Console → Generic DBaaS → Update Cluster Set
+ ↓
+Console → Imported Cluster → Settings → Update Version
+ ↓
+Verify: helm list -A across all contexts
+```
+
+No downtime during upgrade procedure — the platform performs rolling Helm release updates and
+most workloads stay running throughout.
+
+---
+Here is a sample video on how you can setup the full platform:
+
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-workload.md b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-workload.md
new file mode 100644
index 0000000000..0279d83491
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/cluster-workload.md
@@ -0,0 +1,119 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-k8sworkloads
+ name: Kubernetes Workload Management
+ parent: cluster-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Kubernetes Workload Management
+
+The **Workloads** group in the Cluster UI sidebar is where you browse and manage everything that runs application containers — Deployments, Pods, Jobs, and the other standard Kubernetes workload types.
+
+## Open the Workloads Section
+
+1. Navigate to the [Platform Console](https://console.appscode.com).
+2. Click on your imported cluster to open its Cluster Overview page.
+3. In the left sidebar, click **Workloads** to expand it.
+
+Every list page in this group follows the same layout: a 🔍 search box, an **All Namespaces** filter dropdown, and a green **+ Create** button top-right.
+
+---
+
+## Deployments
+
+A Deployment keeps a set number of identical app copies running and handles rolling updates — it's the standard way to run and update a stateless app. Use this page when you need to check rollout status, scale an app up/down, or push a new image version.
+
+Lists every Deployment with its Namespace, Pods (ready count), Images, and Age. Click a row to view or edit it; use **+ Create** to deploy a new one.
+
+
+
+---
+
+## Replica Sets
+
+A Replica Set's only job is to keep a fixed number of Pod copies alive. You rarely create these by hand — a Deployment creates and manages one for you behind the scenes. Check this page when troubleshooting why a Deployment isn't scaling the way you expect.
+
+Lists every Replica Set with its Namespace, Pods, Images, and Age.
+
+
+
+---
+
+## Replication Controllers
+
+The older, legacy way to keep a fixed number of Pod copies running — same idea as a Replica Set, kept for backward compatibility. New workloads should use Deployments instead; you'd only see entries here on older setups.
+
+Lists every Replication Controller with its Namespace, Pods, Images, and Age. Click **+ Create ReplicationController** to add one.
+
+
+
+---
+
+## Stateful Sets
+
+For apps where each Pod needs a stable identity and its own storage — databases, queues, anything that can't just be swapped for an identical copy. Use this when running stateful services that care about pod order or persistent data.
+
+Lists every Stateful Set with its Namespace, Pods, Images, and Age.
+
+
+
+---
+
+## Daemon Sets
+
+Runs one copy of a Pod on every node automatically — typically used for cluster-wide infrastructure like log collectors or monitoring agents that need to run everywhere. Check this page to confirm a node-wide agent has rolled out to all nodes.
+
+Lists every Daemon Set with its Namespace, Pods, Dsired, Current-Scheduled, Up-to-date, Node Selector, Images, and Age — the Desired/Current/Up-to-date columns show rollout progress at a glance.
+
+
+
+---
+
+## Jobs
+
+A Job runs a task once until it completes — a backup, a migration script, a one-off batch process — then stops, unlike a Deployment which runs forever. Use this page to check whether a one-off task finished and how long it took.
+
+Lists every Job with its Namespace, Annotations, Completions, Duration, Images, and Age.
+
+
+
+---
+
+## Cron Jobs
+
+A Cron Job runs a Job on a repeating schedule — like a nightly backup or a recurring cleanup task — so you don't have to trigger it manually each time. Use the **Suspend** state here to pause a recurring task without deleting it.
+
+Lists every Cron Job with its Namespace, Annotations, Schedule, Suspend, Active, Last Schedule, Images, and Age — the Schedule column shows the cron expression.
+
+
+
+---
+
+## Pods
+
+A Pod is the actual running container(s) — the smallest unit in Kubernetes. Every Deployment, StatefulSet, Job, etc. above ultimately creates Pods to do the real work. This is the page to check when you need to see real-time container health or debug a crash.
+
+Lists every Pod with its Namespace, Ready, Status, Restarts, IP, Images, and Age — the only Workloads item with these extra live-state columns, useful for spotting crashing or restarting containers.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| Open the Workloads view | Click your cluster on the Platform Console → click **Workloads** in the left sidebar |
+| List a workload type | Click its name under the Workloads group (e.g. Deployments, Pods) |
+| Filter by namespace | Use the **All Namespaces** dropdown on any list page |
+| Create a new workload | Click **+ Create** on the resource's list page |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/feature-reference.md b/content/docs/platform/v2026.7.10/guides/cluster-management/feature-reference.md
new file mode 100644
index 0000000000..967ecfaeac
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/feature-reference.md
@@ -0,0 +1,326 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-feature-reference
+ name: Feature Set Reference
+ parent: cluster-management
+ weight: 31
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Feature Set Reference
+
+This page lists every feature available in each Feature Set, why you would enable it, and the features it depends on. Use it to decide what to turn on and to understand what gets pulled in automatically.
+
+> **Prerequisites auto-enable.** When you enable a feature, every feature in its **Prerequisites** column is enabled for you if not already present. The chain is transitive — a prerequisite's own prerequisites are pulled in too.
+
+---
+
+## Opscenter Core *(Required)*
+
+Core platform capabilities. Must be installed before any other Feature Set.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Kube UI Server** *(Required)* | The core Server that renders the UI of this particular cluster | — |
+| **License Proxyserver** *(Recommended)* | Fetches and serves AppsCode product licenses. Required by KubeDB, KubeStash, Panopticon, KubeVault, Scanner. | — |
+| **FluxCD** *(Recommended)* | GitOps engine for declaratively syncing manifests from Git. All features are actually deployed in the cluster via flux HelmRelease. | — |
+| **OpenShift Adapter** | Adapts the platform to OpenShift. Enable only on OpenShift clusters. | — |
+| **Opscenter Features** *(Required)* | Internal configurator that renders feature definitions. Platform-managed. | — |
+
+Note: If you are an ArgoCD user, AppsCode provides a way to convert the flux HelmRelease to an Argo Application via a custom operator called FargoCD. This is configurable in the [selfhost](../../../selfhost-setup/install/_index.md) page.
+
+
+
+---
+
+## Backup & Recovery
+
+Scheduled backup and recovery for Kubernetes applications and databases.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Stash 2.0** *(Recommended)* | Backup and restore of apps and databases via KubeStash. The current backup engine. | License Proxyserver |
+| **Stash Presets** *(Recommended)* | Ready-made backup storage and retention policy configurations. | — |
+| **Stash** | Legacy backup operator (Stash 1.0). Enable only to keep existing Stash 1.0 setups working. | License Proxyserver |
+| **Stash Opscenter** | UI and Grafana monitoring for Stash. | Stash, Panopticon, Grafana Operator |
+
+
+
+---
+
+## Databases
+
+Production-grade database management powered by KubeDB.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **KubeDB** *(Recommended)* | Operator to provision and manage production databases (MongoDB, Postgres, MySQL, Redis, Kafka, etc.). | License Proxyserver |
+| **KubeDB Opscenter** *(Recommended)* | UI and monitoring dashboards for KubeDB. | KubeDB, Panopticon, Grafana Operator |
+| **KubeDB UI Presets** *(Recommended)* | Default presets for the database creation forms. | — |
+| **Prepare Cluster** | Pre-pulls images and prepares nodes for KubeDB. | — |
+
+
+
+---
+
+## Observability
+
+Cluster monitoring, metrics, and dashboards.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Monitoring Operator** *(Recommended)* | Foundation operator that wires up cluster monitoring. Prerequisite for most observability features. | — |
+| **Kube Prometheus Stack** *(Recommended)* | Prometheus, Grafana, and alerting bundle for Kubernetes-native monitoring. | Monitoring Operator |
+| **Grafana Operator** *(Recommended)* | Manage Grafana dashboards as Kubernetes resources. | Monitoring Operator |
+| **Panopticon** *(Recommended)* | Generates metrics from any Kubernetes resource (generic kube-state-metrics). | License Proxyserver |
+| **Kubernetes Metrics Server** | Container CPU/memory metrics for `kubectl top` and built-in autoscaling. | — |
+| **Prometheus Metrics Adapter** *(Recommended)* | Exposes Prometheus metrics to the Kubernetes custom-metrics API. | Kube Prometheus Stack |
+| **Kubernetes Grafana Dashboards** *(Recommended)* | Prebuilt Kubernetes Grafana dashboards. | Grafana Operator |
+| **AppsCode OTEL Stack** *(Recommended)* | OpenTelemetry collectors and pipelines for traces, metrics, and logs. | Monitoring Operator |
+| **Thanos Operator** *(Recommended)* | Long-term, highly available Prometheus storage and global querying. | — |
+| **Prometheus Label Proxy** *(Recommended)* | Enforces label-based tenant isolation on Prometheus queries. | Thanos Operator, Gateway API, Service Catalog |
+| **Tenant Operator** *(Recommended)* | Isolates monitoring resources and access per tenant. | Prometheus Label Proxy, Thanos Operator |
+| **Inbox Agent / Server / UI** *(ALPHA)* | Cluster event inbox components. | — |
+
+
+
+---
+
+## Cost Management
+
+Measure and allocate infrastructure and container costs.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Keda** *(Recommended)* | Event-driven autoscaling of workloads. | — |
+| **Keda HTTP Addon** *(Recommended)* | Scale workloads based on HTTP traffic. | Keda |
+| **Opencost** *(ALPHA)* | Measure and allocate infrastructure and container costs. | Kube Prometheus Stack, Monitoring Operator |
+| **OpenCost Grafana Dashboards** | Cost visualization dashboards. | Opencost, Grafana Operator |
+
+
+
+---
+
+## Security
+
+TLS certificates, runtime security, and image scanning.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Scanner** *(Recommended)* | Scans image vulnerabilities and generates security reports. | License Proxyserver, Grafana Operator |
+| **Cert Manager** | X.509 certificate issuance and renewal. | Gateway API |
+| **CA Cert CSI Driver** | CSI driver that adds CA certificates to the OS trusted certificate issuers | Cert Manager |
+| **Falco** | Container-native runtime threat detection. | — |
+| **Falco UI Server** | UI for Falco runtime alerts. | Falco, Grafana Operator |
+
+
+
+---
+
+## Secret Management
+
+Secure secret storage, syncing, and distribution.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **External Secrets** | Sync secrets from external managers (AWS/GCP/Azure/Vault) into Kubernetes Secrets. | — |
+| **Kubevault** | Operator to run and manage HashiCorp Vault. | License Proxyserver |
+| **Kubevault Opscenter** | UI and monitoring for KubeVault. | Kubevault, Grafana Operator |
+| **Config Syncer** | Sync ConfigMaps and Secrets across namespaces and clusters. | License Proxyserver |
+| **Reloader** | Roll workloads automatically on ConfigMap/Secret changes. | — |
+| **Sealed Secrets** | One-way encrypted Secrets safe to store in Git. | — |
+| **Vault Secrets Operator** | Consume Vault secrets natively as Kubernetes Secrets. | — |
+| **Secrets Store CSI Driver** | Mount secrets from external stores as CSI volumes. | — |
+| **Azure Key Vault provider** | Azure Key Vault backend for the CSI driver. | Secrets Store CSI Driver |
+| **AWS provider** | AWS Secrets Manager / SSM Parameter Store backend for the CSI driver. | Secrets Store CSI Driver |
+| **Google Secret Manager provider** | Google Secret Manager backend for the CSI driver. | Secrets Store CSI Driver |
+| **HashiCorp Vault provider** | HashiCorp Vault backend for the CSI driver. | Secrets Store CSI Driver |
+| **Virtual Secrets** *(ALPHA)* | Virtual Secrets server for not to actually keep the secrets in k8s level. | — |
+| **Virtual Secrets provider** *(ALPHA)* | Virtual Secrets backend for the CSI driver. | Virtual Secrets, Secrets Store CSI Driver |
+
+
+
+---
+
+## Policy Management
+
+Platform-level policy enforcement.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Gatekeeper** | OPA-based policy controller. | — |
+| **Gatekeeper Templates** | OPA Gatekeeper policy template library. | Gatekeeper |
+| **Gatekeeper Constraints** | OPA Gatekeeper policy constraint library. | Gatekeeper, Gatekeeper Templates |
+| **GateKeeper Policy Grafana Dashboards** | Policy compliance dashboards. | Gatekeeper, Grafana Operator |
+| **Kyverno** | Kubernetes-native policy management. | — |
+| **Kyverno Policies** | Pod Security Standards implemented as Kyverno policies. | Kyverno |
+
+
+
+---
+
+## Storage Addons
+
+Additional storage drivers and integrations.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **NFS CSI driver** | Access NFS servers as Kubernetes volumes. | — |
+| **Longhorn** | Cloud-native distributed block storage. | — |
+| **CSI Volume Snapshotter** | Snapshot controller and validation webhook for CSI volumes. | — |
+| **TopoLVM** | Local LVM-backed CSI storage. | — |
+
+
+
+---
+
+## Networking Addons
+
+Networking plugins and extensions.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Kubernetes Gateway API** *(Recommended)* | Installs the Gateway API CRDs and controller. | — |
+| **External DNS Operator** | Manage external DNS records for Services and Ingresses. | — |
+| **Voyager Ingress** | HAProxy-based ingress controller. | — |
+| **Voyager Gateway** | Envoy-based gateway distro by AppsCode. | — |
+
+
+
+---
+
+## Opscenter Tools
+
+DevOps tooling and management utilities.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Supervisor** *(Recommended)* | Day-2 operations — upgrade recommendations and maintenance windows. | — |
+| **Sidekick** *(Recommended)* | Run a one-off container as a pod (sidecar-as-a-pod). | — |
+| **Operator Shard Manager** *(Recommended)* | Scale operators by sharding responsibility across instances. | — |
+
+
+
+---
+
+## Cluster Management
+
+Cluster provisioning and management tools (Cluster API core).
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **CAPI Catalog** | Catalog of Cluster API cluster templates. | — |
+| **CAPI Ops Manager** | Day-2 operations for Cluster API clusters. | — |
+| **Cluster Presets** | Preset configurations for cluster provisioning. Work with cloud NodePools | — |
+
+
+
+---
+
+## Cluster API AWS (CAPA)
+
+Lifecycle management for clusters running on AWS.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **AWS Credential Manager** *(Recommended)* | Manage AWS credentials used by CAPA. | — |
+| **AWS EBS CSI Driver** *(Recommended)* | EBS-backed storage for provisioned clusters. | — |
+| **AWS Load Balancer Controller** *(Recommended)* | Provision AWS load balancers for EKS clusters. | — |
+| **AWS VPC Peering Operator** *(Recommended)* | Manage AWS VPC peering connections. | — |
+| **Cluster Autoscaler** *(Recommended)* | Node autoscaling for Cluster API clusters. | — |
+
+
+
+---
+
+## Cluster API GCP (CAPG)
+
+Lifecycle management for clusters running on GCP.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **GCP Credential Manager** *(Recommended)* | Manage GCP credentials used by CAPG. | — |
+
+
+
+---
+
+## Cluster API Azure (CAPZ)
+
+Lifecycle management for clusters running on Azure.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Azure Credential Manager** *(Recommended)* | Manage Azure credentials used by CAPZ. | — |
+
+
+
+---
+
+## Crossplane
+
+Control-plane framework for infrastructure as code.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Crossplane** *(Recommended)* | The cloud-native control plane for provisioning infrastructure via Kubernetes APIs. | — |
+| **KubeDB AWS Provider** | Provision KubeDB databases on AWS through Crossplane. | Crossplane |
+| **KubeDB Azure Provider** | Provision KubeDB databases on Azure through Crossplane. | Crossplane |
+| **KubeDB GCP Provider** | Provision KubeDB databases on GCP through Crossplane. | Crossplane |
+
+
+
+---
+
+## Multicluster Hub
+
+Central hub for managing a fleet of clusters.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Multicluster Hub** *(Recommended)* | Core hub components. Foundation for all other hub features. | — |
+| **Managed ServiceAccount Manager** *(Recommended)* | Manage service accounts on spoke clusters. | Multicluster Hub |
+| **Cluster Auth Manager** *(Recommended)* | Authentication and authorization across the fleet. | Multicluster Hub, Managed ServiceAccount Manager |
+| **Cluster Profile Manager** *(Recommended)* | Manage cluster profiles across the fleet. | Multicluster Hub, Cluster Auth Manager |
+| **Cluster Proxy Manager** *(Recommended)* | Proxy traffic to spoke clusters. | Multicluster Hub, Cluster Profile Manager |
+| **Cluster Gateway Manager** *(Recommended)* | API gateway for reaching spoke clusters. | Multicluster Hub, Cluster Profile Manager, Managed ServiceAccount Manager, Cluster Proxy Manager |
+| **FluxCD Manager** *(Recommended)* | GitOps delivery across the fleet. | Multicluster Hub, Cluster Profile Manager |
+| **License Proxyserver Manager** *(Recommended)* | Distribute AppsCode licenses to spoke clusters. | Multicluster Hub, Cluster Profile Manager |
+| **Hub Cluster Robot** *(Recommended)* | Automation account for hub-driven operations. | Multicluster Hub, Cluster Auth Manager |
+
+
+
+---
+
+## Multicluster Spoke
+
+Connect this cluster as a spoke to an existing hub.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Multicluster Spoke** *(Recommended)* | Register this cluster as a spoke of a Multicluster Hub. | — |
+
+
+
+---
+
+## Kubernetes Native Service
+
+Components for Kubernetes-native service patterns.
+
+| Feature | Why enable | Prerequisites |
+|---|---|---|
+| **Service Catalog** *(Recommended)* | Exposes the Databases with gateway. Controls all the gw component provisioning for all modes including client orgs | Cert Manager, KubeDB |
+| **Service Gateway Presets** *(Recommended)* | A preset that holds the root 'ace' gateway configurations | Cert Manager, External DNS Operator |
+| **Service Connector Backend** | Backend for the service connector. | — |
+| **Service Provider** | Service provider component. | — |
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/_index.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/_index.md
new file mode 100644
index 0000000000..678c05d847
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui
+ name: Hub UI
+ parent: cluster-management
+ description: Know how to use Hub UI
+ icon: https://img.icons8.com/external-anggara-basic-outline-anggara-putra/96/external-stats-ui-anggara-basic-outline-anggara-putra.png
+ popular: true
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/cluster-and-clusterset.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/cluster-and-clusterset.md
new file mode 100644
index 0000000000..9a9bab749d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/cluster-and-clusterset.md
@@ -0,0 +1,84 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-cluster
+ name: Cluster & Clusterset
+ parent: hub-ui
+ weight: 70
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Important Note
+
+⚠️ Spoke users **should NOT manage feature sets directly**
+
+* Feature updates must be handled from the **Hub**
+* Hub must stay in sync
+
+---
+
+# ClusterSets
+
+ClusterSets group multiple clusters together.
+
+## Create ClusterSet
+
+1. Go to **ClusterSets**
+2. Click **Add ClusterSet**
+
+
+
+3. Provide a name
+
+
+
+---
+
+## Feature Sets
+
+* Select any feature you want to change in all of your connected spokes
+
+
+
+
+
+
+* Apply configurations across all clusters
+* Centralized feature management
+
+## Unaligned and Out of sync cluster
+
+### Unaligned cluster: If any spoke cluster has extra features enabled than hub that's unaligned
+
+
+
+Like in the image secret management have 1 unaligned cluster
+
+
+
+You can see config-syncer is enabled in spoke but not in hub
+
+### Similarly if any hub update does not get applied in spoke that becomes out of sync
+
+---
+
+## Add Clusters
+
+You can add cluster from another clusterset if you want
+
+
+
+
+1. Select cluster(s)
+
+
+
+2. Add to ClusterSet
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/create.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/create.md
new file mode 100644
index 0000000000..e0b31a3bae
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/create.md
@@ -0,0 +1,53 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-create
+ name: Create Hub Cluster
+ parent: hub-ui
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Hub Cluster
+
+> ⚠️ Recommended: Use an organizational account for full functionality
+
+### Steps
+
+1. Go to import cluster and choose your preferred method
+
+2. After filling up necessary steps for your preferred method Choose Generic as cluster profile
+
+3. Open **Cluster Details**
+You won't see the hub UI button initially
+
+
+
+4. Go to **Feature Set Settings**
+5. Select **OCM Hub Feature Set**
+
+All the features will be white leveled if you are enabling it for the first time.
+
+
+
+In the top right corner there will be enable button.
+1. Click in the enable button
+2. Select all features ( will be auto-selected)
+3. Click Preview then Deploy
+
+
+
+
+
+✅ Wait a bit Your Hub Cluster is ready
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/introduction.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/introduction.md
new file mode 100644
index 0000000000..101cea1a2c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/introduction.md
@@ -0,0 +1,82 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-introduction
+ name: Introduction
+ parent: hub-ui
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Hub UI
+
+Hub UI lets you manage multiple clusters from a single point.
+
+
+
+### What is OCM?
+
+**Open Cluster Management (OCM)** is a platform for managing multiple Kubernetes clusters from a single control point.
+
+Think of it like this:
+
+* You run multiple stores across different cities (**clusters**)
+* You manage them from a central office (**hub cluster**)
+
+OCM acts as that central office, allowing you to:
+
+* Monitor clusters
+* Apply configurations
+* Manage workloads
+* Enforce policies across environments
+
+---
+
+## Core Terminology
+
+### Hub Cluster
+
+The **central control plane** that:
+
+* Manages other clusters
+* Stores cluster states
+* Distributes applications and policies
+
+---
+
+### Spoke Cluster
+
+A **cluster connected to a hub**
+
+**Analogy:**
+
+* Hub = center of a wheel
+* Spokes = connected clusters
+
+Spoke clusters:
+
+* Run workloads
+* Receive policies/configurations from the hub
+
+---
+
+### Subscription
+
+Defines what applications/configurations should be deployed to clusters.
+
+---
+
+### Policy
+
+Rules enforced across clusters, such as:
+
+* Security settings
+* Network configurations
+* Compliance rules
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/license-management.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/license-management.md
new file mode 100644
index 0000000000..d48815e853
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/license-management.md
@@ -0,0 +1,44 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-license
+ name: License Management
+ parent: hub-ui
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# License Management
+
+From **Cluster Settings → License**
+
+You can:
+
+* Add licenses
+
+
+
+
+
+* Upon clicking on the link you will redirected to billing UI
+
+
+
+* After selecting a contract add your cluster there
+
+
+
+
+
+* Copy and paste your license
+* Assign to namespaces
+* Track usage
+* Access billing (if permitted)
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/permission.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/permission.md
new file mode 100644
index 0000000000..72a1087579
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/permission.md
@@ -0,0 +1,74 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-permission
+ name: User Permission
+ parent: hub-ui
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# User Access Management
+
+
+
+Here you can assign a user one cluster or many cluster (clusterset) and grant access of different level
+
+## Scenario Example
+
+| User | Cluster | Access Level |
+| -------- | ------- | ------------ |
+| user-1 | spoke-1 | View Only |
+| user-2 | spoke-2 | Edit Access |
+
+---
+
+## Method 1: Assign via Organization Team
+
+### Steps
+
+1. Go to **Platform UI**
+
+
+
+2. Create a **Team**
+
+
+
+3. Add members
+
+
+
+4. Go to Hub → **Access**
+5. Click **Assign Permission**
+
+
+
+
+### Fields Explained
+
+* **User** → Organization member
+* **Level**
+
+ * Cluster
+ * ClusterSet
+* **Cluster/ClusterSet** → Target
+* **Role Type**
+
+ * ClusterRole
+ * Role (namespace-specific)
+* **Roles Available**
+
+ * `cluster-admin`
+ * `admin`
+ * `create`
+ * `view`
+* **Namespace** → Scope (if applicable)
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/spoke.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/spoke.md
new file mode 100644
index 0000000000..104231f5e8
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/spoke.md
@@ -0,0 +1,78 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-spoke
+ name: Connect Spoke Cluster
+ parent: hub-ui
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Spoke Cluster
+
+## Method 1 (Recommended): Import with Hub Connection
+
+### Steps
+
+1. Go to **Import Cluster** and complete the necessary steps
+2. Select an existing hub cluster before importing
+
+
+
+3. Complete import
+
+✅ Spoke cluster is created and linked
+
+
+
+This method can also be started from the Hub cluster:
+
+1. Go to Hub → **Cluster List**
+2. Click **Import Managed Cluster**
+
+
+
+
+3. Follow import steps
+
+✅ Hub auto-selected during import
+
+
+---
+
+## Method 2: Enable OCM Spoke Feature
+
+1. Go to cluster → Feature Set
+2. Enable **OCM Spoke** (initially your features will be white leveled)
+
+
+
+3. Select Hub Cluster
+
+
+
+4. Provide a name
+5. Enable
+
+Then:
+
+* Enter into your hub cluster then Click Go to Hub
+
+
+
+* Click **Accept Spoke** The select the spoke from which the connection request was sent before
+
+
+
+* Approve the request
+
+✅ Cluster becomes a managed spoke
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/upgrade.md b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/upgrade.md
new file mode 100644
index 0000000000..28c1075471
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/hub-ui/upgrade.md
@@ -0,0 +1,34 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: hub-ui-upgrade
+ name: Upgrade Spoke
+ parent: hub-ui
+ weight: 80
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Upgrade spoke cluster
+
+1. Go to clusterset of the cluster that you want to upgrade to latest version
+
+
+
+2. You will see the spoke featureset inside the hub
+
+
+
+To give a spoke different features than the hub, configure them here.
+
+3. Go to **Upgrade Version** from the sidebar. If a latest version is available, click the upgrade button.
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-05-53.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-05-53.png
new file mode 100644
index 0000000000..0136437956
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-05-53.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-06-49.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-06-49.png
new file mode 100644
index 0000000000..c5e3558b8d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-06-49.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-22.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-22.png
new file mode 100644
index 0000000000..08a62202a0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-22.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-30.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-30.png
new file mode 100644
index 0000000000..8b92260ecf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-10-30.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-22.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-22.png
new file mode 100644
index 0000000000..c9a25d7215
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-22.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-26.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-26.png
new file mode 100644
index 0000000000..3399b8db3d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-26.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-38.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-38.png
new file mode 100644
index 0000000000..6a91d19e88
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-38.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-49.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-49.png
new file mode 100644
index 0000000000..705161ea16
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-49.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-53.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-53.png
new file mode 100644
index 0000000000..9539a4d963
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-19-53.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-27.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-27.png
new file mode 100644
index 0000000000..e56bbe8e8e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-27.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-34.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-34.png
new file mode 100644
index 0000000000..383818b873
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-34.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-39.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-39.png
new file mode 100644
index 0000000000..78eddde646
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-39.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-43.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-43.png
new file mode 100644
index 0000000000..f47127bfb1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-43.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-47.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-47.png
new file mode 100644
index 0000000000..6dc7659587
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-47.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-51.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-51.png
new file mode 100644
index 0000000000..74baeaf88c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-51.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-55.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-55.png
new file mode 100644
index 0000000000..8b9db7b712
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-55.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-57.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-57.png
new file mode 100644
index 0000000000..0ea72ff6ca
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-20-57.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-05.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-05.png
new file mode 100644
index 0000000000..4192149ba1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-05.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-18.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-18.png
new file mode 100644
index 0000000000..309eeb0f14
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-18.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-22.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-22.png
new file mode 100644
index 0000000000..f9e9602295
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-22.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-25.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-25.png
new file mode 100644
index 0000000000..886bca0bb3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-25.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-29.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-29.png
new file mode 100644
index 0000000000..a4abc7d411
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/Screenshot from 2026-06-16 15-22-29.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/delete_cluster.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/delete_cluster.png
new file mode 100644
index 0000000000..acb50e47a2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/delete_cluster.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/helm-release.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/helm-release.png
new file mode 100644
index 0000000000..a00f6fd76d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/helm-release.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/removeAndDelete.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/removeAndDelete.png
new file mode 100644
index 0000000000..86c348933f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/removeAndDelete.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/remove_cluster.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/remove_cluster.png
new file mode 100644
index 0000000000..8baedb9619
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/remove_cluster.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-09.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-09.png
new file mode 100644
index 0000000000..4addef7bb6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-09.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-20.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-20.png
new file mode 100644
index 0000000000..2983bd90e3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-20.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-41.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-41.png
new file mode 100644
index 0000000000..bb0069fa9e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/Cluster_management/resource_management/Screenshot from 2026-06-16 15-49-41.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/add-cluster-select-provider.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/add-cluster-select-provider.png
new file mode 100644
index 0000000000..102b31816b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/add-cluster-select-provider.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-form.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-form.png
new file mode 100644
index 0000000000..3ba4c5c729
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-form.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-progress.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-progress.png
new file mode 100644
index 0000000000..27edabcebf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/create-cluster-progress.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-aws.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-aws.png
new file mode 100644
index 0000000000..b98aeb47d3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-aws.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-azure.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-azure.png
new file mode 100644
index 0000000000..8e95ace4e3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-azure.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-digitalocean.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-digitalocean.png
new file mode 100644
index 0000000000..ccfac815d0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-digitalocean.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-gcp.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-gcp.png
new file mode 100644
index 0000000000..812def589c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-gcp.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-hetzner.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-hetzner.png
new file mode 100644
index 0000000000..d08d7972f8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-hetzner.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-kubevirt.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-kubevirt.png
new file mode 100644
index 0000000000..cf0c900ac9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/credential-kubevirt.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/public-cluster-kubeconfig.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/public-cluster-kubeconfig.png
new file mode 100644
index 0000000000..32238cd49d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/public-cluster-kubeconfig.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/select-cluster-eks.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/select-cluster-eks.png
new file mode 100644
index 0000000000..95fdb21f1a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/add_cluster/select-cluster-eks.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases1.png
new file mode 100644
index 0000000000..63cbd54c67
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases2.png
new file mode 100644
index 0000000000..2951066b89
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases3.png
new file mode 100644
index 0000000000..e22117b2ae
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases4.png
new file mode 100644
index 0000000000..5c1669e543
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases5.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases5.png
new file mode 100644
index 0000000000..e860acb406
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases5.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases6.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases6.png
new file mode 100644
index 0000000000..9228c892fb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/feature-databases6.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-after-enable-some-features.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-after-enable-some-features.png
new file mode 100644
index 0000000000..a48c3e6f45
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-after-enable-some-features.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup1.png
new file mode 100644
index 0000000000..abd1816304
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup2.png
new file mode 100644
index 0000000000..540ad5e70c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup3.png
new file mode 100644
index 0000000000..187904143c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup4.png
new file mode 100644
index 0000000000..0e1f0f8dcb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup5.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup5.png
new file mode 100644
index 0000000000..e7f3cf32dd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup5.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup6.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup6.png
new file mode 100644
index 0000000000..7063521097
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features-backup6.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features.png
new file mode 100644
index 0000000000..20963e9efc
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-features/features.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-charts-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-charts-list.png
new file mode 100644
index 0000000000..8b92260ecf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-charts-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-deployed.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-deployed.png
new file mode 100644
index 0000000000..a00f6fd76d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-deployed.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-list.png
new file mode 100644
index 0000000000..08a62202a0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-helm-charts/helm-releases-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-1.png
new file mode 100644
index 0000000000..3c6175cc3b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-2.png
new file mode 100644
index 0000000000..b25f64c2fe
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-3.png
new file mode 100644
index 0000000000..452785ce08
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-4.png
new file mode 100644
index 0000000000..de4a66cdcf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-1.png
new file mode 100644
index 0000000000..4be29be88f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-2.png
new file mode 100644
index 0000000000..2118df71ec
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-3.png
new file mode 100644
index 0000000000..682befcc92
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-nodes-edit-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-1.png
new file mode 100644
index 0000000000..aecbf5ddec
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-2.png
new file mode 100644
index 0000000000..4a8ed2cfba
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-3.png
new file mode 100644
index 0000000000..8d2b4eaefc
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-4.png
new file mode 100644
index 0000000000..6942ea7826
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-overview/cluster-overview-4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values1.png
new file mode 100644
index 0000000000..43c2d97a9c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values2.png
new file mode 100644
index 0000000000..5dcb08d117
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values3.png
new file mode 100644
index 0000000000..e4bffdc291
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values4.png
new file mode 100644
index 0000000000..2a071c8288
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values5.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values5.png
new file mode 100644
index 0000000000..7d294d8f29
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values5.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values6.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values6.png
new file mode 100644
index 0000000000..aea49b1b1a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values6.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values7.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values7.png
new file mode 100644
index 0000000000..6c5d146995
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values7.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values8.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values8.png
new file mode 100644
index 0000000000..9eeac3b9ed
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/db-preset-edit-values8.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/present-basic-info.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/present-basic-info.png
new file mode 100644
index 0000000000..acc12a820f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/present-basic-info.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-enable.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-enable.png
new file mode 100644
index 0000000000..9fd7f7a6f0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-enable.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace1.png
new file mode 100644
index 0000000000..8794cbeba6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace2.png
new file mode 100644
index 0000000000..5e0f490b7f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset-extend-to-namespace2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset.png
new file mode 100644
index 0000000000..d2ab03b69e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/preset.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/presets-after-feature-enable.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/presets-after-feature-enable.png
new file mode 100644
index 0000000000..850b9f7c7d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/presets-after-feature-enable.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values1.png
new file mode 100644
index 0000000000..752c723bc6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values2.png
new file mode 100644
index 0000000000..5da4debed8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-presets/stash-preset-edit-values2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-1.png
new file mode 100644
index 0000000000..c2253595f3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-after-update.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-after-update.png
new file mode 100644
index 0000000000..25cde62557
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-after-update.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-before-update.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-before-update.png
new file mode 100644
index 0000000000..7792f47d4a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-before-update.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-search-menu.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-search-menu.png
new file mode 100644
index 0000000000..de8025c699
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-search-menu.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-updating.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-updating.png
new file mode 100644
index 0000000000..8a5f114320
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-sidebar/sidebar-updating.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/cron-jobs-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/cron-jobs-list.png
new file mode 100644
index 0000000000..d4efeebc1f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/cron-jobs-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/daemon-sets-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/daemon-sets-list.png
new file mode 100644
index 0000000000..ece1b4bd2a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/daemon-sets-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/deployments-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/deployments-list.png
new file mode 100644
index 0000000000..c9dcd41cdd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/deployments-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/jobs-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/jobs-list.png
new file mode 100644
index 0000000000..02851408a4
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/jobs-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/pods-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/pods-list.png
new file mode 100644
index 0000000000..68ce55f15d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/pods-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replica-sets-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replica-sets-list.png
new file mode 100644
index 0000000000..cdccf6c802
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replica-sets-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replication-controllers-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replication-controllers-list.png
new file mode 100644
index 0000000000..f5c85e9237
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/replication-controllers-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/stateful-sets-list.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/stateful-sets-list.png
new file mode 100644
index 0000000000..361e9d532b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster-workload/stateful-sets-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_1.png
new file mode 100644
index 0000000000..09c45a3a68
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_2.png
new file mode 100644
index 0000000000..54480d7aab
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/add_cluster_2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset.png
new file mode 100644
index 0000000000..35cdc752d0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_1.png
new file mode 100644
index 0000000000..0846d87381
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_2.png
new file mode 100644
index 0000000000..70a750c21c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/clusterset_feature_2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned.png
new file mode 100644
index 0000000000..a6ff007846
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned_2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned_2.png
new file mode 100644
index 0000000000..1bb329e2b1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/cluster_and_clusterset/unaligned_2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-backup-recovery.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-backup-recovery.png
new file mode 100644
index 0000000000..3ca47e53c5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-backup-recovery.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-aws.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-aws.png
new file mode 100644
index 0000000000..404c2c8bae
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-aws.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-azure.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-azure.png
new file mode 100644
index 0000000000..7a56e1ae55
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-azure.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-gcp.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-gcp.png
new file mode 100644
index 0000000000..d2f41ead2a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-capi-gcp.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cluster-management.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cluster-management.png
new file mode 100644
index 0000000000..f6741fad6b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cluster-management.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cost-management.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cost-management.png
new file mode 100644
index 0000000000..5f35ed5118
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-cost-management.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-crossplane.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-crossplane.png
new file mode 100644
index 0000000000..dd31b8bc84
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-crossplane.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-databases.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-databases.png
new file mode 100644
index 0000000000..c4ca2ecc87
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-databases.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-kubernetes-native-service.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-kubernetes-native-service.png
new file mode 100644
index 0000000000..cda767ee13
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-kubernetes-native-service.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-hub.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-hub.png
new file mode 100644
index 0000000000..2b5b11afdf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-hub.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-spoke.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-spoke.png
new file mode 100644
index 0000000000..d3995d8646
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-multicluster-spoke.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-networking-addons.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-networking-addons.png
new file mode 100644
index 0000000000..5f49dd6174
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-networking-addons.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-observability.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-observability.png
new file mode 100644
index 0000000000..c2bd0de3a1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-observability.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-core.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-core.png
new file mode 100644
index 0000000000..a6604b04f7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-core.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-tools.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-tools.png
new file mode 100644
index 0000000000..0893d5b34f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-opscenter-tools.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-policy-management.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-policy-management.png
new file mode 100644
index 0000000000..b0bedfd6ea
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-policy-management.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-secret-management.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-secret-management.png
new file mode 100644
index 0000000000..cf5309b890
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-secret-management.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-security.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-security.png
new file mode 100644
index 0000000000..edda00c4bb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-security.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-storage-addons.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-storage-addons.png
new file mode 100644
index 0000000000..80d9bcbfa1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/feature-reference-images/featureset-storage-addons.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-details.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-details.png
new file mode 100644
index 0000000000..44dfa26d71
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-details.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-profile.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-profile.png
new file mode 100644
index 0000000000..425efe93f0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/cluster-profile.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/deploy.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/deploy.png
new file mode 100644
index 0000000000..44e2cc041a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/deploy.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/feature-set.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/feature-set.png
new file mode 100644
index 0000000000..ad06ac4c9f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/feature-set.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/select-cluster.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/select-cluster.png
new file mode 100644
index 0000000000..47dba03fa5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/import/select-cluster.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/introduction/hub-spoke-model.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/introduction/hub-spoke-model.png
new file mode 100644
index 0000000000..ce014031b3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/introduction/hub-spoke-model.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/add_license.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/add_license.png
new file mode 100644
index 0000000000..96da550c71
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/add_license.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract.png
new file mode 100644
index 0000000000..a93ef3b1dc
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_1.png
new file mode 100644
index 0000000000..9e1e47e825
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_2.png
new file mode 100644
index 0000000000..858f678b26
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/contract_2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/license_modal.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/license_modal.png
new file mode 100644
index 0000000000..24b18a1c6f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/license/license_modal.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/import-select-monitoring-cluster.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/import-select-monitoring-cluster.png
new file mode 100644
index 0000000000..1691936fe2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/import-select-monitoring-cluster.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-1.png
new file mode 100644
index 0000000000..9a97222824
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-2.png
new file mode 100644
index 0000000000..a4c1b33e07
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-3.png
new file mode 100644
index 0000000000..8f3e662871
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/otel-monitoring/telemetrystack-3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/add_member.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/add_member.png
new file mode 100644
index 0000000000..5b9281af7c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/add_member.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/create_team.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/create_team.png
new file mode 100644
index 0000000000..2c2c7d5db0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/create_team.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/go_to_platform.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/go_to_platform.png
new file mode 100644
index 0000000000..1e5cbbdb55
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/go_to_platform.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/grant_permission.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/grant_permission.png
new file mode 100644
index 0000000000..3d22fc08c3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/grant_permission.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/permission.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/permission.png
new file mode 100644
index 0000000000..47f8620f76
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/permission/permission.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create1.png
new file mode 100644
index 0000000000..c382a83261
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create2.png
new file mode 100644
index 0000000000..e465215976
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create3.png
new file mode 100644
index 0000000000..08cd39ca0f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create4.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create4.png
new file mode 100644
index 0000000000..ca40f69101
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-create4.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-details.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-details.png
new file mode 100644
index 0000000000..b5736e76ab
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-details.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-edit.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-edit.png
new file mode 100644
index 0000000000..d15849392b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota-edit.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota.png
new file mode 100644
index 0000000000..bdee8ad1ee
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/project-quota/project-quota.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/cluster-options-menu.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/cluster-options-menu.png
new file mode 100644
index 0000000000..86c348933f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/cluster-options-menu.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/delete-cluster-modal.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/delete-cluster-modal.png
new file mode 100644
index 0000000000..acb50e47a2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/delete-cluster-modal.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/remove-cluster-modal.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/remove-cluster-modal.png
new file mode 100644
index 0000000000..8baedb9619
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/remove-cluster/remove-cluster-modal.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/accept.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/accept.png
new file mode 100644
index 0000000000..61d9a38855
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/accept.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/featureset.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/featureset.png
new file mode 100644
index 0000000000..b9300f8d29
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/featureset.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/homepage.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/homepage.png
new file mode 100644
index 0000000000..efdd158639
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/homepage.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/import_spoke.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/import_spoke.png
new file mode 100644
index 0000000000..a2bca815fe
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/import_spoke.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/request.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/request.png
new file mode 100644
index 0000000000..8d766ff5d2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/request.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/select.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/select.png
new file mode 100644
index 0000000000..d8034820cb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/spoke.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/spoke.png
new file mode 100644
index 0000000000..3934c82be0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/spoke/spoke.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_1.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_1.png
new file mode 100644
index 0000000000..517524a098
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_2.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_2.png
new file mode 100644
index 0000000000..7198b89ce7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_3.png b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_3.png
new file mode 100644
index 0000000000..0944e7e2f5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/cluster-management/images/upgrade/upgrade_3.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/otel-monitoring.md b/content/docs/platform/v2026.7.10/guides/cluster-management/otel-monitoring.md
new file mode 100644
index 0000000000..2cd9e01a26
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/otel-monitoring.md
@@ -0,0 +1,200 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-otel-monitoring
+ name: OpenTelemetry Monitoring
+ parent: cluster-management
+ weight: 90
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# OpenTelemetry Monitoring
+
+This guide walks through setting up an observability stack that collects
+telemetry from your spoke clusters using OpenTelemetry, stores it in an
+object-storage bucket, and exposes it through a TelemetryStack.
+
+## Architecture
+
+The setup involves three kinds of clusters:
+
+- **Hub cluster** — the central Platform Console (ACE). This is where you
+ operate clusters, manage organizations, and view dashboards. It is the
+ management plane; it does not store telemetry itself.
+- **Monitoring cluster** — a dedicated observability cluster that runs the
+ TelemetryStack and stores all telemetry: metrics (Thanos + object storage),
+ and logs and traces (ClickHouse). It serves multi-tenant queries back to the
+ hub. This is the cluster imported with the **Observability Cluster** profile.
+- **Spoke / imported clusters** — the clusters you actually want to observe.
+ Once the OpenTelemetry feature (`appscode-otel-stack`) is enabled on them,
+ their collectors ship metrics, logs, and traces to the monitoring cluster.
+
+In short: spoke clusters produce telemetry, the monitoring cluster stores and
+serves it, and the hub is where you view it.
+
+## The Monitoring Cluster's Special Features
+
+Beyond a normal spoke, the monitoring cluster runs three components (in the
+`monitoring` namespace) that make multi-tenant telemetry storage work:
+
+- **`thanos-operator`** — reconciles the Thanos custom resources
+ (`ThanosReceive`, `ThanosStore`, `ThanosQuery`, `ThanosCompact`,
+ `ThanosRuler`) that the TelemetryStack generates into running workloads. It
+ is the controller that turns your TelemetryStack spec into an actual Thanos
+ deployment.
+- **`tenant-operator`** — manages `Tenant` custom resources. Each client
+ organization / monitored cluster gets a `Tenant` that references the
+ TelemetryStack and defines its retention and ingest/query endpoints, giving
+ every tenant an isolated slice of the shared stack.
+- **`prom-label-proxy`** — the multi-tenant gateway on the ingest and query
+ paths. It enforces per-tenant label filtering (via the tenant ID / label)
+ so each tenant can only write to and read back its own data. The `Tenant`
+ endpoints point at this proxy.
+
+## Overview
+
+The end-to-end flow is:
+
+1. Create a self-hosted installer.
+2. Create the observability cluster.
+3. Install MinIO.
+4. Create the `telemetry` bucket.
+5. Create a TelemetryStack.
+6. Enable OpenTelemetry on the spoke clusters to be monitored.
+7. Create a client organization.
+
+## Step 1: Create the Self-Hosted Installer
+
+Set up a self-hosted installer for your environment.
+
+## Step 2: Create the Observability Cluster
+
+Create a new cluster and import it as a spoke, choosing the **Observability
+Cluster** cluster profile during import. See
+[Import Observability Cluster](add-cluster/import-observability-cluster.md) for
+details.
+
+## Step 3: Install MinIO
+
+The TelemetryStack can be backed by any S3-compatible object storage — MinIO is
+used here only as an example. Substitute your own storage solution (AWS S3, GCS,
+Ceph, etc.) as needed.
+
+Install MinIO on the observability cluster to provide the object storage that
+backs the TelemetryStack:
+
+```bash
+kubectl create ns minio
+
+kubectl create secret generic tls-ssl-minio -n minio \
+ --from-file=private.key \
+ --from-file=public.crt
+
+kubectl create secret generic tls-ssl-minio -n monitoring \
+ --from-file=private.key \
+ --from-file=public.crt
+
+helm repo add minio-comm https://charts.min.io/
+
+helm upgrade -i minio \
+ --namespace minio \
+ --create-namespace \
+ --set rootUser=rootuser,rootPassword=rootpass123 \
+ minio-comm/minio \
+ -f ./minio/minio-values.yaml
+```
+
+The `tls-ssl-minio` secret is created in both the `minio` and `monitoring`
+namespaces so that MinIO and the telemetry components can serve and consume TLS
+using the same certificate pair (`private.key` / `public.crt`).
+
+## Step 4: Create the `telemetry` Bucket
+
+Port-forward the MinIO console and create the bucket through the UI:
+
+```bash
+kubectl port-forward -n minio svc/minio-console 9001:9001
+```
+
+Open `https://localhost:9001` and log in:
+
+| Field | Value |
+|----------|----------------|
+| Username | `rootuser` |
+| Password | `rootpass123` |
+
+Create a bucket named **`telemetry`**.
+
+## Step 5: Create a TelemetryStack
+
+In the observability cluster, navigate to:
+
+**Settings → TelemetryStack → Create a new Telemetry stack**
+
+Fill in the configuration sections as shown below.
+
+Configure Metrics (Compact, Store, Query, Router, Ingester):
+
+
+
+Ruler, Additional Config, and Configure Clickhouse:
+
+
+
+Configure Clickhouse (Standalone / Create Topology), Configure S3, and Configure ID:
+
+
+
+### Resources Created by the TelemetryStack
+
+Once the TelemetryStack is created, the operators reconcile it into a set of
+resources in the `monitoring` namespace. You can find everything the stack owns
+by looking for resources whose owner is the TelemetryStack:
+
+```bash
+# The Thanos and ClickHouse custom resources generated from the stack
+kubectl get thanosreceives,thanosstores,thanosqueries,thanoscompacts,thanosrulers.monitoring.thanos.io,clickhouse -n monitoring
+
+# Any resource owned by the telemetry-stack (children carry it in ownerReferences)
+kubectl get all -n monitoring -o json | \
+ jq -r '.items[] | select(.metadata.ownerReferences[]?.kind=="TelemetryStack") | "\(.kind)/\(.metadata.name)"'
+```
+
+For the **metrics** pipeline, `thanos-operator` produces:
+
+- **`ThanosReceive`** → a receive-router deployment plus a receive-ingester
+ StatefulSet — the remote-write ingestion endpoint for incoming metrics.
+- **`ThanosStore`** → a store StatefulSet that serves historical blocks from
+ object storage.
+- **`ThanosQuery`** → query and query-frontend deployments that fan out reads
+ across the receivers and store.
+- **`ThanosCompact`** → one StatefulSet per retention tier that downsamples and
+ compacts blocks in object storage.
+- **`ThanosRuler`** → a ruler StatefulSet that evaluates recording/alerting
+ rules and forwards alerts to Alertmanager.
+
+For the **logs / traces** pipeline, a KubeDB **`ClickHouse`** database
+(`telemetry-stack-clickhouse`) is provisioned, along with the supporting
+secrets (`telemetry-stack-object-storage`,
+`telemetry-stack-clickhouse-storage-config`).
+
+## Step 6: Enable OpenTelemetry on a Spoke Cluster
+
+Enable the OpenTelemetry feature on each spoke cluster you want to monitor —
+either during import or on an existing spoke. See
+[Import Observability Cluster](add-cluster/import-observability-cluster.md#enable-the-opentelemetry-feature-on-a-spoke-cluster).
+
+## Step 7: Create a Client Organization
+
+Create a client organization and point it at the monitoring cluster so its
+telemetry is stored in the shared TelemetryStack. See
+[Create a Client Organization](../../client-organization/create-client-organization.md)
+— the **Telemetry Configuration** step is where you select the monitoring
+cluster and set retention.
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/project-quota.md b/content/docs/platform/v2026.7.10/guides/cluster-management/project-quota.md
new file mode 100644
index 0000000000..bd72d527fb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/project-quota.md
@@ -0,0 +1,117 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-project-quota
+ name: Project Quota
+ parent: cluster-management
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Project Quota Management
+
+**Project Quota** lets you set resource limits — CPU and Memory — for specific Kubernetes resource types within a namespace. This prevents any single workload from consuming more than its fair share of cluster resources.
+
+---
+
+## Step 1 — Open the Project Quota Page
+
+In the left sidebar, navigate to **Project Quota** (under **Cluster Settings** or **Appscode K8s Management**, depending on your sidebar layout).
+
+The **Project Quota** page lists all existing quotas. Each row shows the **Name** (the namespace the quota applies to) and the **Age** (when it was created). Use the 🔍 search icon at the top right to filter the list.
+
+To delete an existing quota, click the red **Delete** button next to it.
+
+
+
+---
+
+## Step 2 — Start Creating a New Quota
+
+Click the green **+ Create Quota** button in the top-right corner of the page to open the **Create Project Quota** form.
+
+### Select a Namespace
+
+The first field is **Namespace** (required). Click the field to open a dropdown listing all namespaces in your cluster. Select the namespace you want to apply the quota to (for example, `kubeops`).
+
+
+
+---
+
+## Step 3 — Configure the Quota Rule
+
+After selecting a namespace, a **New Quota** section appears. Here you define the rule to enforce.
+
+### Select the API Group
+
+Click the **Group** dropdown. Choose the API group of the resource you want to limit. For example:
+- `apps` — for standard Kubernetes workloads (Deployments, StatefulSets, etc.)
+- `kubedb.com` — for KubeDB-managed databases
+
+
+
+### Select the Resource Kind
+
+After choosing a group, click the **Kind** dropdown. The list is filtered to show only the resource types available under the selected group.
+
+For example, with `kubedb.com` selected, you can choose from: **Elasticsearch**, **Kafka**, **MariaDB**, **MongoDB**, **MySQL**, **Postgres**, **Redis**, **RedisSentinel**, and more.
+
+
+
+### Set CPU and Memory Limits
+
+Once the Kind is selected, fill in the resource limits:
+
+| Field | Description | Example |
+|---|---|---|
+| **CPU Limit** | Maximum CPU cores allowed for this resource kind in the namespace | `8` |
+| **Memory Limit** | Maximum memory allowed for this resource kind in the namespace | `24Gi` |
+
+
+
+Click the green **Save** button (within the New Quota section) to stage this rule.
+
+---
+
+## Step 4 — Review Staged Quotas & Save
+
+After staging a rule, it appears in the **Quotas** table below, showing the **Group**, **Kind**, **CPU Limit**, **Memory Limit**, and **Actions** (edit ✏ / delete 🗑).
+
+A green toast notification confirms: **"Quota created successfully!"**
+
+You can click **+ Add Quota** to add more rules for other resource types in the same namespace.
+
+
+
+Once you have added all your rules, click the main **Save** button to permanently apply the project quota to the selected namespace.
+
+---
+
+## Step 5 — Edit an Existing Quota
+
+To modify a quota rule, click the ✏ **edit icon** in the **Actions** column of the Quotas table.
+
+An **Edit Quotas** inline form expands below the table. The **Group** and **Kind** fields are pre-filled and locked (greyed out) since they identify the rule. You can see the current **CPU Used** and **Memory Used** values alongside the editable **CPU Limit** and **Memory Limit** fields.
+
+Update the limits as needed and click **Save** to apply the changes.
+
+
+
+---
+
+## Quick Reference
+
+| Task | How to do it |
+|---|---|
+| View all quotas | Open **Project Quota** in the left sidebar |
+| Create a new quota | Click **+ Create Quota**, select namespace → group → kind → limits → **Save** |
+| Add more rules to a quota | Click **+ Add Quota** in the Quotas table |
+| Edit a quota rule | Click the ✏ icon in the Actions column → adjust limits → **Save** |
+| Delete a quota | Click the 🗑 icon in the Actions column (or **Delete** on the list page) |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/remove-cluster.md b/content/docs/platform/v2026.7.10/guides/cluster-management/remove-cluster.md
new file mode 100644
index 0000000000..83620a3a21
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/remove-cluster.md
@@ -0,0 +1,60 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-deletecluster
+ name: Remove / Delete Cluster
+ parent: cluster-management
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Remove / Delete Cluster
+
+From the cluster list, click the **⋮** (three-dot) menu on any cluster card to access two actions: **Remove** and **Delete**.
+
+
+
+---
+
+## Remove
+
+**Remove** unregisters the cluster from the Cluster UI. The actual Kubernetes cluster and its workloads are left untouched.
+
+1. Click **⋮** on your cluster card.
+2. Click **Remove**.
+3. A confirmation modal opens. Optionally check any cleanup actions to run before removal:
+ - **Remove FluxCD** — uninstalls FluxCD from the cluster.
+ - **Remove All Features** — uninstalls all installed feature-sets from the cluster.
+4. Click **Yes, Remove**.
+
+
+
+---
+
+## Delete
+
+**Delete** permanently destroys the cluster and its underlying infrastructure. This action is irreversible.
+
+1. Click **⋮** on your cluster card.
+2. Click **Delete**.
+3. Confirm in the modal by clicking **Yes, Delete**.
+
+
+
+> **Warning:** Delete tears down the actual infrastructure. Use **Remove** if you only want to unregister the cluster from the UI.
+
+---
+
+## Quick Reference
+
+| Action | What happens | Cluster destroyed? |
+|---|---|---|
+| **Remove** | Unregisters cluster from Cluster UI | No |
+| **Delete** | Destroys cluster + infrastructure | Yes |
diff --git a/content/docs/platform/v2026.7.10/guides/cluster-management/security-report.md b/content/docs/platform/v2026.7.10/guides/cluster-management/security-report.md
new file mode 100644
index 0000000000..4afa9cfdcc
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/cluster-management/security-report.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: cluster-management-securityreport
+ name: Security Report
+ parent: cluster-management
+ weight: 80
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Security Report
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/_index.md b/content/docs/platform/v2026.7.10/guides/database-management/_index.md
new file mode 100644
index 0000000000..e99edea152
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management
+ name: Database Management
+ parent: guides
+ description: Basic database information description
+ icon: https://img.icons8.com/00994A/ios/50/database--v1.png
+ popular: true
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/backup-configuration.md b/content/docs/platform/v2026.7.10/guides/database-management/backup-configuration.md
new file mode 100644
index 0000000000..1beec04ab2
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/backup-configuration.md
@@ -0,0 +1,266 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-backup-configuration
+ name: Backup Configuration
+ parent: database-management
+ weight: 120
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Backup Configuration
+
+This guide explains how to view and create **BackupConfiguration** resources using the platform console. A BackupConfiguration defines a complete backup policy for a database — including the storage backend, retention policy, backup sessions with their schedules and tasks, and the target database to back up.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **Backup Configuration**. This opens the BackupConfiguration list page showing all existing configurations in your cluster.
+
+---
+
+## 2. BackupConfiguration List
+
+The list page shows all BackupConfigurations across namespaces. Use the **Select Namespace** dropdown in the top-right to filter by namespace, or click **Create New Instance** to create a new one.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The name of the BackupConfiguration resource. |
+| **Namespace** | The namespace where it is deployed. |
+| **Schedule** | The cron expression defining the backup frequency. |
+| **Paused** | Whether the backup schedule is currently paused. |
+| **Repository** | The repository used to store backup snapshots. |
+| **BackupStorage** | The underlying storage backend. |
+| **Target** | The database resource being backed up. |
+| **Task** | The backup task type (e.g., `logical-backup`). |
+| **RetentionPolicy** | The policy controlling how long backups are kept. |
+| **Phase** | The current status of the BackupConfiguration (e.g., `Ready`). |
+| **Age** | How long ago the resource was created. |
+
+---
+
+## 3. Viewing a BackupConfiguration
+
+Click on any BackupConfiguration name in the list to open its detail page.
+
+### 3.1 - Overview
+
+The detail page opens on the **Overview** tab, which shows the following sections:
+
+
+
+**Basic** — Core metadata for the resource:
+
+| Field | Description |
+|---|---|
+| **Name** | The BackupConfiguration resource name. |
+| **Namespace** | The namespace it belongs to. |
+| **Labels** | Key-value labels attached to the resource. |
+| **Annotations** | Key-value annotations including managed-by and apply-configuration references. |
+| **UID** | The unique Kubernetes identifier for this resource. |
+| **Phase** | Current lifecycle phase (e.g., `Ready`). |
+| **Paused** | Whether the backup schedule is paused (`true` / `false`). |
+
+**Backup Sessions** — Lists all active backup sessions linked to this configuration:
+
+| Column | Description |
+|---|---|
+| **Name** | The name of the BackupSession resource. |
+| **Namespace** | Namespace of the BackupSession. |
+| **Invoker Kind** | The resource type that triggered the session (e.g., `BackupConfiguration`). |
+| **Invoker Name** | The name of the invoker resource. |
+| **Session** | The session name within the configuration (e.g., `full-backup`). |
+| **Total snapshots** | Number of snapshots created in this session. |
+| **Phase** | Current status of the session (e.g., `Succeeded`, `Running`). |
+| **Duration** | Time taken to complete the session. |
+| **Age** | How long ago the session was created. |
+
+**Retention Policies** — Lists the RetentionPolicy resources linked to this configuration:
+
+| Column | Description |
+|---|---|
+| **Name** | The RetentionPolicy resource name. |
+| **Annotations** | Annotations referencing the linked namespace and name. |
+| **Age** | Age of the RetentionPolicy resource. |
+| **Max Retention Period** | How long backups are kept before being pruned. |
+| **Default** | Whether this is the default retention policy. |
+
+**Target** — Identifies the database resource being backed up. Shown as "No data available" if the target database has been removed or is not yet bound.
+
+### 3.2 - Repository, BackupStorage and CronJobs
+
+Scroll down on the detail page to view the linked infrastructure resources.
+
+
+
+**Repository** — The backup repository storing snapshots for this configuration:
+
+| Column | Description |
+|---|---|
+| **Name** | The repository resource name. |
+| **Namespace** | Namespace of the repository. |
+| **Size** | Total size of all stored snapshots (e.g., `71.001 KiB`). |
+| **Snapshot Count** | Number of snapshots currently stored. |
+| **Target** | The database this repository backs up (e.g., `MongoDB demo/mongodb`). |
+| **Last-Successful-Backup** | Time elapsed since the last successful backup. |
+| **Integrity** | Whether the repository integrity check passed (`TRUE` / `FALSE`). |
+| **Age** | Age of the repository resource. |
+
+**BackupStorage** — The underlying storage backend connected to this configuration:
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupStorage resource name. |
+| **Namespace** | Namespace of the BackupStorage. |
+| **Provider** | Storage provider (e.g., `s3`). |
+| **Size** | Total data stored across all connected repositories. |
+| **No. of Connected Repositories** | Number of repositories using this storage. |
+| **Status** | Current state of the storage backend (e.g., `Ready`). |
+| **Age** | Age of the BackupStorage resource. |
+
+**CronJobs** — The Kubernetes CronJob resources created to run backup sessions on schedule:
+
+| Column | Description |
+|---|---|
+| **Name** | The CronJob resource name (e.g., `trigger-mongodb-full-backup`). |
+| **Namespace** | Namespace of the CronJob. |
+| **Annotations** | Annotations linking the CronJob to the BackupConfiguration instance. |
+| **Schedule** | The cron expression driving the backup schedule (e.g., `*/15 * * * *`). |
+| **Suspend** | Whether the CronJob is currently suspended (`true` / `false`). |
+| **Active** | Number of currently active job runs. |
+| **Last Schedule** | Time elapsed since the CronJob last triggered. |
+| **Age** | Age of the CronJob resource. |
+
+---
+
+## 4. Creating a BackupConfiguration
+
+To create a new BackupConfiguration, click **Create New Instance** from the list page. The **Create BackupConfiguration** form will open containing the following sections:
+
+- **Namespace / Name / Storage Ref / Retention Policy** — Core identity and storage fields.
+- **Labels & Annotations** — Optional metadata for the resource.
+- **Sessions** — One or more backup sessions defining schedule, addon, and tasks.
+- **Target** — The database resource this BackupConfiguration applies to.
+
+
+
+### 4.1 - Basic Information
+
+The top section captures the core identity and storage references for the BackupConfiguration.
+
+
+
+| Field | Description |
+|---|---|
+| **Namespace** | The Kubernetes namespace where the BackupConfiguration will be created. Required. |
+| **Name** | A unique name for this BackupConfiguration (e.g., `test-name`). Required. |
+| **Storage Ref** | Reference to the BackupStorage resource that defines where backups are stored (e.g., `stash/default`). Required. |
+| **Retention Policy** | Reference to the RetentionPolicy resource that controls how long backups are kept (e.g., `stash/default`). Required. |
+
+> **Note:** All four fields are required (marked with a red asterisk). The Storage Ref and Retention Policy dropdowns list existing resources available in your cluster.
+
+### 4.2 - Labels & Annotations
+
+Expand the **Labels & Annotations** panel to attach custom metadata to the BackupConfiguration resource.
+
+
+
+- Use **+ Add new** under **Labels** to add key-value label pairs.
+- Use **+ Add new** under **Annotations** to add key-value annotation pairs.
+- Use the delete icon on any row to remove an entry.
+
+### 4.3 - Sessions
+
+The **Sessions** section defines one or more backup sessions. Each session specifies when the backup runs, which addon to use, and what tasks to execute. Click **+ Add new** to add a session entry.
+
+
+
+| Field | Description |
+|---|---|
+| **Session Name** | A unique name for this backup session (e.g., `full-backup`). |
+| **Schedule** | A cron expression defining when this session runs (e.g., `*/30 * * * *` for every 30 minutes). |
+| **Security Context (runAsUser)** | The UID the backup job container runs as. |
+| **Addon Name** | The backup addon to use for this session. Select from the dropdown. |
+
+Use the **Delete** button at the bottom of a session entry to remove it.
+
+#### 4.3.1 - Session Tasks
+
+Each session must have at least one **Task** defined. Tasks describe the actual backup operation to perform. Click **Add new** inside the Tasks section to add a task entry.
+
+
+
+| Field | Description |
+|---|---|
+| **Task Name** | The name of the backup task to execute. Select from the dropdown. Required. |
+| **Encryption Secret Namespace** | The namespace of the Kubernetes Secret holding the encryption key. |
+| **Encryption Secret Name** | The name of the Kubernetes Secret holding the encryption key. |
+| **Repo Name** | The name of the repository within the storage backend where this task writes backups. |
+| **Params** | Optional task-specific parameters in YAML format entered in the code editor. |
+
+> **Note:** **Task Name** is required. Use the **Delete** button at the bottom of a task entry to remove it. Multiple tasks can be added to a single session using **Add new**.
+
+### 4.4 - Target
+
+The **Target** section identifies the database resource that this BackupConfiguration will back up.
+
+
+
+| Field | Description |
+|---|---|
+| **Api Group** | The API group of the target resource (e.g., `kubedb.com`). Required. |
+| **Kind** | The resource kind of the target database (e.g., `MongoDB`). Required. |
+| **Namespace** | The namespace where the target database resides (e.g., `demo`). Required. |
+| **Name** | The name of the target database instance (e.g., `mongodb`). Required. |
+
+> **Note:** All four Target fields are required. If any are missing, the form will display an "Error in fields" warning on the Target panel header.
+
+---
+
+## 5. Preview and Submit
+
+Once all required fields are filled, click **Preview** to review the generated `BackupConfiguration` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to create the BackupConfiguration in your cluster.
+
+> **Note:** After submitting, the BackupConfiguration will immediately begin scheduling backup sessions according to the cron expressions you defined.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all BackupConfigurations | **Backups** → **Backup Configuration** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View detail of a config | Click on the BackupConfiguration name in the list |
+| Check backup session status | Detail page → **Backup Sessions** table |
+| Check repository integrity | Detail page → **Repository** table → **Integrity** column |
+| View linked CronJobs | Detail page → **CronJobs** table |
+| Open the create form | List page → **Create New Instance** |
+| Set storage backend | **Storage Ref** dropdown → select a BackupStorage resource |
+| Set retention policy | **Retention Policy** dropdown → select a RetentionPolicy resource |
+| Add labels or annotations | **Labels & Annotations** → **+ Add new** → enter Key and Value |
+| Add a backup session | **Sessions** → **+ Add new** → fill Session Name, Schedule, Addon Name |
+| Add a task to a session | **Tasks** → **Add new** → select Task Name → optionally add Params |
+| Encrypt backup data | **Tasks** → set Encryption Secret Namespace and Encryption Secret Name |
+| Set the backup target | **Target** → fill Api Group, Kind, Namespace, and Name |
+| Review before creating | Click **Preview** |
+| Edit manifest directly | Use the **YAML** / **JSON** toggle on the Preview page |
+| Create the configuration | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/backup-storage.md b/content/docs/platform/v2026.7.10/guides/database-management/backup-storage.md
new file mode 100644
index 0000000000..2c4de50d2e
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/backup-storage.md
@@ -0,0 +1,200 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-backup-storage
+ name: Backup Storage
+ parent: database-management
+ weight: 130
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Backup Storage
+
+This guide explains how to view and create **BackupStorage** resources using the platform console. A BackupStorage defines the storage backend (cloud provider, credentials, bucket, and connection settings) where database backups are stored and can be retrieved for restoration.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **BackupStorage**. This opens the BackupStorage list page showing all configured storage backends in your cluster.
+
+---
+
+## 2. BackupStorage List
+
+The list page displays all BackupStorage resources configured in your cluster. Use the **Select Namespace** dropdown to filter by namespace, or click **Create New Instance** to add a new storage backend.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupStorage resource name. |
+| **Namespace** | The namespace where it is deployed. |
+| **Provider** | The cloud storage provider (e.g., `s3`, `azure`, `gcs`). |
+| **Size** | Total data stored across all connected repositories. |
+| **No. of Connected Repositories** | Number of Repository resources using this storage backend. |
+| **Status** | Current state of the storage connection (e.g., `Ready`, `Failed`). |
+| **Age** | How long ago the BackupStorage was created. |
+
+---
+
+## 3. Viewing a BackupStorage
+
+Click on any BackupStorage name in the list to open its detail page. The detail page shows storage connection details and linked repositories.
+
+### 3.1 - Overview
+
+The detail page shows all relevant information about the storage backend:
+
+
+
+**Basic** — Core metadata for the storage:
+
+| Field | Description |
+|---|---|
+| **Name** | The BackupStorage resource name. |
+| **Namespace** | The namespace it belongs to. |
+| **Labels** | Key-value labels for organization and filtering. |
+| **Annotations** | Key-value annotations including provider and secret references. |
+| **UID** | The unique Kubernetes identifier. |
+| **Provider** | The cloud storage provider (e.g., `azure`, `s3`, `gcs`). |
+| **Status** | Current connection status. |
+
+**Repositories** — All Repository resources using this storage backend:
+
+| Column | Description |
+|---|---|
+| **Name** | The Repository resource name. |
+| **Namespace** | Namespace of the repository. |
+| **Size** | Total size of snapshots stored in this repository. |
+| **Snapshots** | Number of snapshots contained. |
+| **Target** | The database being backed up. |
+| **Retention Policy** | The RetentionPolicy controlling snapshot cleanup. |
+| **Status** | Repository status (e.g., `Ready`). |
+| **Age** | Age of the Repository resource. |
+
+**BackupConfigurations** — All BackupConfigurations using this storage:
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupConfiguration resource name. |
+| **Namespace** | Namespace of the configuration. |
+| **Schedule** | The cron expression for scheduled backups. |
+| **Target** | The database being backed up. |
+| **Session** | The session name within the configuration. |
+| **Invoker Kind** | Always `BackupConfiguration`. |
+| **Task** | The backup task type (e.g., `logical-backup`). |
+| **Paused** | Whether backups are paused. |
+| **Status** | Configuration status. |
+
+---
+
+## 4. Creating a BackupStorage
+
+To add a new storage backend, click **Create New Instance** from the BackupStorage list page. The **Create BackupStorage** form will open.
+
+### 4.1 - Basic Information
+
+The form starts with basic identity fields:
+
+
+
+| Field | Description |
+|---|---|
+| **Namespace** | The Kubernetes namespace where the BackupStorage will be created. Required. |
+| **Name** | A unique name for this BackupStorage (e.g., `s3-backup`). Required. |
+| **Deletion Policy** | Controls what happens when the BackupStorage is deleted. Default: `Delete (Keep only database Secrets and backed up data)`. Required. |
+| **Security Context** | Optional pod security context for backup operations (e.g., run-as user). |
+
+### 4.2 - Labels & Annotations
+
+Expand the **Labels & Annotations** section to attach custom metadata:
+
+
+
+- Use **+ Add new** under **Labels** to add key-value label pairs.
+- Use **+ Add new** under **Annotations** to add key-value annotation pairs.
+- Use the delete icon on any row to remove an entry.
+
+### 4.3 - Backend Configuration
+
+The **Backend** section defines the storage provider and its credentials.
+
+
+
+#### Backend Provider
+
+1. **Provider** — Select the cloud storage provider from the dropdown. Available options include:
+ - `s3` — Amazon S3 or S3-compatible storage
+ - `azure` — Microsoft Azure Blob Storage
+ - `gcs` — Google Cloud Storage
+ - Others depending on your cluster's backup addon
+
+#### Provider-Specific Configuration
+
+Once a provider is selected, provider-specific sub-panels appear for authentication and storage specification.
+
+**For Azure (example shown):**
+
+**Auth** — Authentication credentials:
+
+| Field | Description |
+|---|---|
+| **Account Key** | Azure Storage Account access key. Required. |
+| **Account Name** | Azure Storage Account name. Required. |
+
+**Spec** — Storage specifications:
+
+| Field | Description |
+|---|---|
+| **Container** | Azure Blob Storage container name where backups are stored. Required. |
+| **Max Connections** | Maximum concurrent connections to the storage backend. Optional. |
+| **Prefix** | Prefix for all backup objects (e.g., `db-backups/`). Optional. |
+
+> **Note:** Provider-specific fields vary. Refer to your backup addon documentation for S3, GCS, or other providers.
+
+---
+
+## 5. Preview and Submit
+
+Once all required fields are filled, click **Preview** to review the generated `BackupStorage` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to create the BackupStorage in your cluster.
+
+> **Note:** After submitting, the BackupStorage resource will be created and validated. Once `Status` shows `Ready`, it can be referenced by BackupConfigurations and RetentionPolicies.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all BackupStorages | **Backups** → **BackupStorage** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View storage detail | Click on the BackupStorage name in the list |
+| Check repository count | Detail page → **Repositories** table |
+| Check linked configurations | Detail page → **BackupConfigurations** table |
+| Check storage status | Detail page → **Basic** section → **Status** field |
+| Open the create form | List page → **Create New Instance** |
+| Add labels or annotations | **Labels & Annotations** → **+ Add new** → enter Key and Value |
+| Set deletion policy | **Deletion Policy** dropdown → select policy |
+| Configure storage provider | **Backend** → **Provider** dropdown → select cloud provider |
+| Set Azure storage account | **Backend** → **Auth** → enter Account Key and Account Name |
+| Set Azure container | **Backend** → **Spec** → enter Container name |
+| Set storage prefix | **Backend** → **Spec** → **Prefix** → optional path prefix |
+| Review before creating | Click **Preview** |
+| Edit manifest directly | Use the **YAML** / **JSON** toggle on the Preview page |
+| Create the storage backend | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/backup.md b/content/docs/platform/v2026.7.10/guides/database-management/backup.md
new file mode 100644
index 0000000000..1b5ee91b5f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/backup.md
@@ -0,0 +1,105 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-backup
+ name: Configure Backups
+ parent: database-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Configure Backups
+
+This guide covers how to use the **Configure Backup** interface to manage data protection via individual configurations (**BackupConfig**) or broader templates (**BackupBlueprint**).
+
+---
+
+## 1. Getting Started
+
+Select **Configure Backup** from the left sidebar. This selection determines the available settings and workflow.
+
+- **BackupConfig:** Use this to create, delete, or modify specific backup tasks.
+- **BackupBlueprint:** Use this to manage high-level templates for enabling or disabling backups across multiple resources.
+
+
+
+---
+
+## 2. Managing Backup Configurations (BackupConfig)
+
+When **BackupConfig** is selected, define the **Select Context** to indicate the specific action you wish to perform.
+
+### 2.1 - Creating a New Configuration
+
+Use this context to set up a new automated backup schedule.
+
+
+
+1. **Select Context:** Choose **Create** from the dropdown menu.
+1. **Schedule:** Enter a cron expression to define the backup frequency. For example, `*/15 * * * *` triggers a backup every 15 minutes.
+1. **Preview:** Click **Preview** to review your settings.
+1. **Submit:** Once satisfied, click **Submit** to apply the new configuration.
+
+> **Tip:** The Schedule field is mandatory (marked with a red asterisk). Ensure your cron expression is valid before proceeding.
+
+### 2.2 - Modifying an Existing Configuration
+
+Use this context to update the settings or status of an active backup.
+
+
+
+1. **Select Context:** Choose **Modify**.
+1. **Select BackupConfig:** Pick the specific configuration you want to edit (e.g., `mongodb`) from the dropdown list.
+1. **Update Schedule:** Change the cron expression if the backup needs to run more or less frequently.
+1. **Paused Toggle:** Use this switch to temporarily stop the schedule without deleting the configuration.
+ - Toggle **on** to pause (inactive). Toggle **off** to resume — the backup will run according to the schedule.
+1. **Preview:** Click **Preview** to see how the changes will impact your system.
+1. **Submit:** Once satisfied, click **Submit** to apply the changes.
+
+
+
+> **Note:** After every **Preview**, you must click **Submit** to save your changes. This applies across all backup operations.
+
+> **Tip:** On the Preview page, you can also switch to **YAML** or **JSON** view to edit your configuration directly before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+### 2.3 - Deleting a Configuration
+
+Use this context to permanently remove a backup configuration.
+
+
+
+1. **Select Context:** Choose **Delete**.
+1. **Select BackupConfig:** Select the configuration you wish to remove (e.g., `mongodb`).
+1. **Finalize:** Click **Deploy** to execute the deletion.
+
+> **Warning:** Unlike other contexts, this button says **Deploy** — clicking it will immediately apply the removal with no further confirmation.
+
+---
+
+## 3. Managing Backup Blueprints (BackupBlueprint)
+
+Selecting the **BackupBlueprint** type allows you to toggle predefined backup templates for your environment.
+
+
+
+1. **Enable Backup Blueprint Toggle:** Switching on activates the selected blueprint, applying its settings to the relevant resources. Switching off deactivates it.
+1. **Preview:** Click **Preview** to confirm which configurations will be affected before the change takes effect.
+1. **Submit:** Once satisfied, click **Submit** to apply the blueprint change.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Create a backup schedule | **BackupConfig** → **Create** → set Schedule → **Preview** → **Submit** |
+| Modify an existing backup | **BackupConfig** → **Modify** → choose config → update settings → **Preview** → **Submit** |
+| Delete a backup config | **BackupConfig** → **Delete** → choose config → **Deploy** |
+| Enable/disable a blueprint | **BackupBlueprint** → toggle **Enable Backup Blueprint** → **Preview** → **Submit** |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/contraint-violations.md b/content/docs/platform/v2026.7.10/guides/database-management/contraint-violations.md
new file mode 100644
index 0000000000..b26e6421c6
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/contraint-violations.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-gatekeeper
+ name: Database Contraint Violations
+ parent: database-management
+ weight: 100
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Database Contraint Violations
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/_index.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/_index.md
new file mode 100644
index 0000000000..2cdae9b5f8
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/_index.md
@@ -0,0 +1,79 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create
+ name: Creating a Database
+ parent: database-management
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Database
+
+Creating a database is a multi-step wizard: select a database engine, set a name and
+namespace, configure topology and resources, and enable optional features like
+monitoring, TLS, and backups.
+
+The overall flow is the same for every engine and is documented once in
+[**Common Steps**](../common-steps.md). Where it differs is the **Database Mode** (topology)
+and a handful of engine-specific settings — pick your engine below for a guide tailored to
+it, then follow the common steps for everything else.
+
+---
+
+## Supported Engines
+
+### Relational
+- [IBM Db2](../db2.md)
+- [MariaDB](../mariadb.md)
+- [Microsoft SQL Server](../mssqlserver.md)
+- [MySQL](../mysql.md)
+- [Oracle](../oracle.md)
+- [Percona XtraDB](../perconaxtradb.md)
+- [PostgreSQL](../postgres.md)
+- [SAP HANA](../hanadb.md)
+- [SingleStore](../singlestore.md)
+
+### Document & Search
+- [DocumentDB](../documentdb.md)
+- [Elasticsearch](../elasticsearch.md)
+- [MongoDB](../mongodb.md)
+- [Solr](../solr.md)
+
+### Key-Value & Cache
+- [Hazelcast](../hazelcast.md)
+- [Ignite](../ignite.md)
+- [Memcached](../memcached.md)
+- [Redis](../redis.md)
+
+### Vector
+- [Milvus](../milvus.md)
+- [Qdrant](../qdrant.md)
+- [Weaviate](../weaviate.md)
+
+### Wide-column & Time-series
+- [Cassandra](../cassandra.md)
+- [ClickHouse](../clickhouse.md)
+- [Druid](../druid.md)
+
+### Streaming & Messaging
+- [Kafka](../kafka.md)
+- [RabbitMQ](../rabbitmq.md)
+
+### Graph
+- [Neo4j](../neo4j.md)
+
+### Coordination
+- [ZooKeeper](../zookeeper.md)
+
+### Connection Poolers & Proxies
+- [PgBouncer](../pgbouncer.md)
+- [Pgpool](../pgpool.md)
+- [ProxySQL](../proxysql.md)
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/cassandra.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/cassandra.md
new file mode 100644
index 0000000000..6be7f92cbb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/cassandra.md
@@ -0,0 +1,44 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-cassandra
+ name: Cassandra
+ parent: database-management-create
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Cassandra Database
+
+This page covers the configuration specific to **Cassandra** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node Cassandra instance for development or testing.
+- **Topology** — A multi-node Cassandra cluster, optionally organized into named **Racks** for rack-aware replication.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of Cassandra nodes (e.g., `3`). Required. |
+| **Racks** | Optional list of rack names to spread nodes across for fault tolerance. |
+
+## Create a Cassandra Database
+
+1. Open the wizard and select **Cassandra** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/clickhouse.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/clickhouse.md
new file mode 100644
index 0000000000..3adc57dd2d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/clickhouse.md
@@ -0,0 +1,48 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-clickhouse
+ name: ClickHouse
+ parent: database-management-create
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a ClickHouse Database
+
+This page covers the configuration specific to **ClickHouse** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node ClickHouse instance.
+- **Topology** — A distributed ClickHouse cluster with sharding/replication, coordinated by ClickHouse Keeper.
+
+
+
+**Cluster**
+
+| Field | Description |
+|---|---|
+| **Shards** | Number of shard partitions. Required. |
+| **Replicas** | Number of replicas per shard. Required. |
+
+**ClickHouse Keeper** — Provides coordination/metadata for the cluster (the ClickHouse-native alternative to ZooKeeper). Configure its node count and resources.
+
+## Create a ClickHouse Database
+
+1. Open the wizard and select **ClickHouse** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/common-steps.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/common-steps.md
new file mode 100644
index 0000000000..fade07df22
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/common-steps.md
@@ -0,0 +1,193 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-common
+ name: Common Steps
+ parent: database-management-create
+ weight: 5
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Common Steps for Creating a Database
+
+These steps are the same for every database engine. Each engine's own page covers only
+the engine-specific **Database Mode**; everything else — opening the wizard, naming,
+versions, resources, and optional features — is described here.
+
+> Start on your engine's page (e.g. [PostgreSQL](../postgres.md), [Redis](../redis.md)) for the
+> Database Mode, and refer back to this page for the surrounding steps.
+
+---
+
+## 1. Getting Started
+
+Navigate to the **Datastore** section in the left sidebar. The **Datastore Overview** page lists all existing database instances across your connected engines.
+
+To create a new database, click the green **+ Create New Instance** button in the top-right corner of the page.
+
+
+
+---
+
+## 2. Select a Database Type
+
+You will be presented with a grid of all supported database engines. Click the engine you want to provision.
+
+
+
+> **Tip:** Supported engines include relational, document, key-value, search, vector, and time-series databases.
+
+---
+
+## 3. Choose Namespace and Name
+
+After selecting the database type, choose a namespace and provide a name for the new instance.
+
+
+
+1. **Select Namespace:** The Kubernetes namespace where the database will be deployed. If the namespace has resource quotas, available CPU and memory are shown.
+1. **Name:** A unique name that starts with a lowercase letter and contains only letters, numbers, or dashes.
+
+Click **Next** to proceed to the configuration step.
+
+> **Note:** Both fields are required. The name cannot be changed after creation.
+
+---
+
+## 4. Configure the Database
+
+The configuration page shows all settings for the new database, with the chosen namespace and name displayed as a breadcrumb (e.g., `demo / mongo-test`).
+
+### 4.1 - Database Version
+
+Select the engine version from the **Database Version** dropdown. The version determines engine features, compatibility, and runtime behaviour.
+
+### 4.2 - Database Mode
+
+The available topologies depend on the engine. See your engine's page for its **Database Mode** options and fields — for example [MongoDB](../mongodb.md) (Standalone / Replicaset / Sharded) or [PostgreSQL](../postgres.md) (Standalone / Cluster / RemoteReplica).
+
+### 4.3 - Machine Profile
+
+The **Machine Profile** dropdown selects a preset CPU and memory configuration for your database nodes. Choose `custom` to enter CPU and memory values manually.
+
+
+
+> **Tip:** Preset profiles are named by size (e.g., `db.t4large`). Use `custom` when your workload requires resources that do not match any preset.
+
+### 4.4 - Storage Class and Size
+
+Select the Kubernetes **Storage Class** that backs the persistent volumes and enter the required **Storage size**.
+
+
+
+| Field | Description |
+|---|---|
+| **Storage Class** | The Kubernetes StorageClass for persistent volumes (e.g., `longhorn`). Required. |
+| **Storage size** | The disk capacity per node (e.g., `2Gi`). Required. |
+
+---
+
+## 5. Advanced Configuration
+
+Expand the **Advanced Configuration** panel (*Configure Credentials, Deployment Mode etc.*) for additional settings.
+
+### 5.1 - Labels & Annotations
+
+Add custom Kubernetes labels and annotations to the database resources.
+
+
+
+- Use **+ Add new** under **Labels** / **Annotations** to attach key-value pairs.
+- Use the delete icon on any row to remove it.
+
+### 5.2 - Deletion Policy
+
+The **Deletion Policy** dropdown controls what happens to the resources when the database object is deleted.
+
+
+
+| Option | Behaviour |
+|---|---|
+| **Delete** | Deletes pods and services but retains the PersistentVolumeClaims. |
+| **Halt** | Stops the database without deleting resources. Can be resumed later. |
+| **WipeOut** | Deletes all resources including PersistentVolumeClaims. All data is permanently removed. |
+| **DoNotTerminate** | Prevents deletion until the policy is changed. |
+
+> **Warning:** **WipeOut** permanently destroys all data. Ensure you have a valid backup before selecting this policy.
+
+### 5.3 - Authentication Credentials
+
+Configure how the database credentials are managed.
+
+
+
+| Field | Description |
+|---|---|
+| **Provide Authentication Credentials** | Toggle on to supply custom credentials instead of auto-generating them. |
+| **Refer existing Secret** | Toggle on to reference an existing Kubernetes Secret. Select it from the dropdown. |
+| **Password** | Manually enter a password if not using an existing Secret. |
+| **Configure Database** | Toggle on to provide a custom database configuration in the **Configuration** textarea. |
+
+### 5.4 - Point in-time Recovery
+
+For engines that support continuous archiving (e.g. **PostgreSQL**, **MySQL**), enable **Point in-time Recovery** to restore the new database from a previous backup to an exact timestamp.
+
+
+
+1. **Namespace:** The namespace where the source backup resides. Required.
+1. **Name:** The name of the source database to recover from. Required.
+1. **Recovery Timestamp:** The exact date and time to restore to (`mm/dd/yyyy, hh:mm`). Required.
+
+> **Note:** All three fields are required when Point in-time Recovery is enabled.
+
+---
+
+## 6. Additional Options
+
+Expand the **Additional Options** panel (*Enable Backup, Monitoring, TLS etc.*) to enable integrated platform features.
+
+
+
+| Option | Description |
+|---|---|
+| **Enable Monitoring** | Enables Prometheus metrics collection. Select an **Alert Options** level (`critical`, `warning`, `info`). |
+| **Enable Backup** | Registers the database with the backup system so scheduled backups can be configured after creation. |
+| **Enable TLS** | Enables TLS encryption. Select a **Cluster Issuer** from the dropdown (e.g., `ace-incluster`). |
+| **Expose via Gateway** | Toggles external access through the configured gateway endpoint. |
+
+---
+
+## 7. Deploy
+
+Once all required fields are filled and options are configured, click the green **Deploy** button at the bottom-right of the form to create the database.
+
+> **Note:** Required fields are marked with a red asterisk. The **Deploy** button is active only when all required fields are valid. If any field has an error, a validation summary will appear above the button.
+
+---
+
+## Quick Reference
+
+| Action | Where / How |
+|---|---|
+| Start creating a database | **Datastore Overview** → **+ Create New Instance** |
+| Select database engine | Click the desired engine from the type grid |
+| Set namespace and name | **Choose Namespace and Name** → fill both → **Next** |
+| Choose topology | **Database Mode** → see your engine's page |
+| Set CPU and memory | **Machine Profile** → select preset or `custom` |
+| Set storage | **Storage Class** → select class → set **Storage size** |
+| Add labels or annotations | **Advanced Configuration** → **Labels & Annotations** → **+ Add new** |
+| Control deletion behaviour | **Advanced Configuration** → **Deletion Policy** |
+| Provide custom credentials | **Advanced Configuration** → toggle **Provide Authentication Credentials** |
+| Restore to a point in time | **Advanced Configuration** → toggle **Point in-time Recovery** |
+| Enable monitoring | **Additional Options** → **Enable Monitoring** → set Alert Options |
+| Enable backup at creation | **Additional Options** → **Enable Backup** |
+| Enable TLS at creation | **Additional Options** → **Enable TLS** → select Cluster Issuer |
+| Expose via gateway | **Additional Options** → **Expose via Gateway** |
+| Apply and create | Click **Deploy** |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/db2.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/db2.md
new file mode 100644
index 0000000000..6afe060a7a
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/db2.md
@@ -0,0 +1,38 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-db2
+ name: IBM Db2
+ parent: database-management-create
+ weight: 80
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a IBM Db2 Database
+
+This page covers the configuration specific to **IBM Db2** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+IBM Db2 is deployed as a single logical instance. Set the **Number of Replicas** to control how many nodes back the instance for availability.
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes for the instance (e.g., `1` for a single node, `3` for high availability). |
+
+## Create a IBM Db2 Database
+
+1. Open the wizard and select **IBM Db2** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/documentdb.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/documentdb.md
new file mode 100644
index 0000000000..9ab72bfbc9
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/documentdb.md
@@ -0,0 +1,40 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-documentdb
+ name: DocumentDB
+ parent: database-management-create
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a DocumentDB Database
+
+This page covers the configuration specific to **DocumentDB** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+DocumentDB is deployed as a single logical instance. Set the **Number of Replicas** to control how many nodes back the instance for availability.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes for the instance (e.g., `1` for a single node, `3` for high availability). |
+
+## Create a DocumentDB Database
+
+1. Open the wizard and select **DocumentDB** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/druid.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/druid.md
new file mode 100644
index 0000000000..9a39dc4bdf
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/druid.md
@@ -0,0 +1,73 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-druid
+ name: Druid
+ parent: database-management-create
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Druid Database
+
+This page covers the configuration specific to **Druid** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Druid is always deployed as a **Topology** of role-separated process tiers. Configure each tier's node count and resources independently.
+
+
+
+
+
+| Node | Description |
+|---|---|
+| **Coordinators** | Manage data availability, segment balancing, and cluster coordination. |
+| **MiddleManagers** | Run ingestion tasks and index new data. |
+| **Historicals** | Store and serve queryable historical segments. |
+| **Brokers** | Receive queries and route them to the appropriate Historicals/MiddleManagers. |
+
+Each tier has its own **Number of Replicas**, **Storage size**, **Machine**, **CPU**, and **Memory** fields. Druid also requires dependent metadata storage and deep storage, configured by the platform.
+
+## Druid Dependencies
+
+Druid relies on external dependencies for metadata, deep storage, and coordination. Each can be provisioned by the platform or pointed at an existing, externally-managed instance.
+
+**Deep Storage** — Durable storage for Druid segments.
+
+| Field | Description |
+|---|---|
+| **Type** | Deep storage backend: `s3`, `google`, `azure`, or `hdfs`. |
+| **Config Secret** | Secret holding the credentials/configuration for the chosen backend. |
+
+**Metadata Storage** — Relational database holding Druid metadata.
+
+| Field | Description |
+|---|---|
+| **Type** | `MySQL` or `Postgres`. |
+| **Externally Managed** | Toggle on to reference an existing database instead of provisioning one. |
+| **Namespace / Name** | Reference to the metadata database when externally managed. |
+
+**ZooKeeper** — Coordination service for the Druid cluster.
+
+| Field | Description |
+|---|---|
+| **Externally Managed** | Toggle on to reference an existing ZooKeeper instead of provisioning one. |
+| **Namespace / Name** | Reference to the ZooKeeper instance when externally managed. |
+
+## Create a Druid Database
+
+1. Open the wizard and select **Druid** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/elasticsearch.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/elasticsearch.md
new file mode 100644
index 0000000000..895d94bef1
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/elasticsearch.md
@@ -0,0 +1,56 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-elasticsearch
+ name: Elasticsearch
+ parent: database-management-create
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Elasticsearch Database
+
+This page covers the configuration specific to **Elasticsearch** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Combined** — A single pool of nodes that perform all roles (master, data, ingest). Simpler; best for smaller deployments.
+- **Topology** — Role-separated nodes split into **Master**, **Data**, and **Ingest** tiers, each scaled and resourced independently.
+
+
+
+| Node | Description |
+|---|---|
+| **Master** | Manages cluster state and coordination. |
+| **Data** | Stores shards and serves indexing/search traffic. |
+| **Ingest** | Pre-processes documents via ingest pipelines before indexing. |
+
+Each tier has its own **Number of Replicas**, **Storage size**, **Machine**, **CPU**, and **Memory** fields. You may also select the security **Auth Plugin** (e.g., `X-Pack`, `OpenSearch`, `OpenDistro`, `SearchGuard`).
+
+## Elasticsearch Settings
+
+
+
+| Field | Description |
+|---|---|
+| **Auth Plugin** | The security plugin / distribution: `X-Pack`, `OpenSearch`, `OpenDistro`, or `SearchGuard`. Determines the security implementation. |
+| **Disable Kernel Defaults** | Skip the default `vm.max_map_count` and related kernel tuning applied via an init container. |
+
+## Create a Elasticsearch Database
+
+1. Open the wizard and select **Elasticsearch** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/hanadb.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/hanadb.md
new file mode 100644
index 0000000000..00721937bc
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/hanadb.md
@@ -0,0 +1,47 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-hanadb
+ name: SAP HANA
+ parent: database-management-create
+ weight: 270
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a SAP HANA Database
+
+This page covers the configuration specific to **SAP HANA** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node SAP HANA instance.
+- **SystemReplication** — A HANA System Replication setup with a primary and secondary site for high availability.
+
+
+
+When **SystemReplication** is selected:
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of HANA nodes. Required. |
+| **Replication Mode** | `logreplay`, `delta_datashipping`, or `logreplay_readaccess`. |
+| **Operation Mode** | The system replication operation mode. |
+
+## Create a SAP HANA Database
+
+1. Open the wizard and select **SAP HANA** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/hazelcast.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/hazelcast.md
new file mode 100644
index 0000000000..03ca8dc412
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/hazelcast.md
@@ -0,0 +1,51 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-hazelcast
+ name: Hazelcast
+ parent: database-management-create
+ weight: 70
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Hazelcast Database
+
+This page covers the configuration specific to **Hazelcast** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Combined** — A single pool of members forming one Hazelcast cluster. Best for most deployments.
+- **Topology** — Role-separated member tiers, each scaled and resourced independently.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of Hazelcast members in the cluster. Required. |
+
+## License
+
+Hazelcast Enterprise features require a license.
+
+| Field | Description |
+|---|---|
+| **License Secret** | Name of the Kubernetes Secret containing your Hazelcast license key. |
+
+## Create a Hazelcast Database
+
+1. Open the wizard and select **Hazelcast** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/ignite.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/ignite.md
new file mode 100644
index 0000000000..445110c1a3
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/ignite.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-ignite
+ name: Ignite
+ parent: database-management-create
+ weight: 90
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Ignite Database
+
+This page covers the configuration specific to **Ignite** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Create a Ignite Database
+
+1. Open the wizard and select **Ignite** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/kafka.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/kafka.md
new file mode 100644
index 0000000000..32c3897cb4
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/kafka.md
@@ -0,0 +1,46 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-kafka
+ name: Kafka
+ parent: database-management-create
+ weight: 100
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Kafka Database
+
+This page covers the configuration specific to **Kafka** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Combined** — Nodes act as both controller and broker. Simpler; best for smaller deployments.
+- **Topology** — Role-separated **Controller** and **Broker** node tiers (KRaft), each scaled and resourced independently.
+
+
+
+| Node | Description |
+|---|---|
+| **Controller** | Manages cluster metadata and the KRaft quorum. |
+| **Broker** | Handles produce/consume traffic and stores partition data. |
+
+Each tier has its own **Number of Replicas**, **Storage size**, **Machine**, **CPU**, and **Memory** fields.
+
+## Create a Kafka Database
+
+1. Open the wizard and select **Kafka** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/mariadb.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mariadb.md
new file mode 100644
index 0000000000..ada7feb300
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mariadb.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-mariadb
+ name: MariaDB
+ parent: database-management-create
+ weight: 110
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a MariaDB Database
+
+This page covers the configuration specific to **MariaDB** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Create a MariaDB Database
+
+1. Open the wizard and select **MariaDB** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/memcached.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/memcached.md
new file mode 100644
index 0000000000..0ddce27a49
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/memcached.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-memcached
+ name: Memcached
+ parent: database-management-create
+ weight: 120
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Memcached Database
+
+This page covers the configuration specific to **Memcached** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Create a Memcached Database
+
+1. Open the wizard and select **Memcached** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/milvus.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/milvus.md
new file mode 100644
index 0000000000..9a1d6c1ca3
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/milvus.md
@@ -0,0 +1,71 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-milvus
+ name: Milvus
+ parent: database-management-create
+ weight: 140
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Milvus Database
+
+This page covers the configuration specific to **Milvus** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node Milvus instance.
+- **Distributed** — A multi-node Milvus deployment with separated components for scale and availability.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes/components in the distributed deployment. Required for Distributed. |
+
+## Milvus Dependencies & Settings
+
+Milvus depends on a metadata store (etcd) and object storage, and exposes a few instance-level toggles.
+
+
+
+**Meta Storage (etcd)**
+
+| Field | Description |
+|---|---|
+| **Externally Managed** | Toggle on to use an existing etcd instead of provisioning one. |
+| **Endpoints** | etcd endpoints to connect to when externally managed. |
+| **Size** | Number of etcd nodes when provisioned by the platform. |
+
+**Object Storage**
+
+| Field | Description |
+|---|---|
+| **Config Secret Name** | Secret holding the object storage (e.g. S3/MinIO) configuration. |
+
+**Other Settings**
+
+| Field | Description |
+|---|---|
+| **Disable Security** | Run without authentication (development only). |
+| **Halted** | Create the instance in a halted (stopped) state. |
+| **Configuration Secret / Inline** | Provide engine configuration via a referenced Secret or inline key-value pairs. |
+
+## Create a Milvus Database
+
+1. Open the wizard and select **Milvus** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/mongodb.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mongodb.md
new file mode 100644
index 0000000000..9dbcba2344
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mongodb.md
@@ -0,0 +1,133 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-mongodb
+ name: MongoDB
+ parent: database-management-create
+ weight: 150
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a MongoDB Database
+
+This page covers the configuration specific to **MongoDB** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Three modes are available:
+
+- **Standalone** — A single-node database without high availability or sharding. Best for development or low-traffic workloads.
+- **Replicated Cluster** — A MongoDB ReplicaSet for high availability.
+- **Sharded Cluster** — A fully sharded MongoDB cluster for high performance and high availability.
+
+#### Replicated Cluster
+
+When **Replicated Cluster** is selected, two additional fields appear:
+
+
+
+| Field | Description |
+|---|---|
+| **Replicaset Name** | The name for the replica set (e.g., `rs0`). Required. |
+| **Replicaset Number** | The number of replica members (e.g., `3`). Required. |
+| **mongodb+srv style DNS** | Toggle on to advertise externally reachable per-pod endpoints so clients can connect with a `mongodb+srv` connection string. Available only for **Replicated Cluster** mode, and only when the database has TLS and gateway exposure enabled — see [mongodb+srv Style DNS](#mongodbsrv-style-dns-replicated-cluster-only). |
+
+#### Sharded Cluster
+
+When **Sharded Cluster** is selected, three subsections appear — **Shard Nodes**, **Config Server**, and **Mongos** — each configurable independently.
+
+
+
+**Shard Nodes** — Configure how MongoDB data is partitioned, replicated, and resourced across your cluster.
+
+
+
+| Field | Description |
+|---|---|
+| **Shards** | Number of shard partitions (e.g., `2`). Required. |
+| **Replicaset Number** | Number of replicas per shard (e.g., `3`). Required. |
+| **Storage size** | Disk size per shard node (e.g., `2Gi`). Required. |
+| **Machine** | Preset machine profile or `custom` for manual CPU/memory. |
+| **CPU** | CPU request per shard node (e.g., `900m`). |
+| **Memory** | Memory request per shard node (e.g., `1Gi`). |
+
+**Config Server** — Stores metadata about the sharded cluster including chunk distribution and shard configuration. Must run as a replica set.
+
+
+
+| Field | Description |
+|---|---|
+| **Replicaset Number** | Number of config server replicas (e.g., `3`). Required. |
+| **Storage size** | Disk size per config server node (e.g., `2Gi`). Required. |
+| **Machine** | Preset machine profile or `custom`. |
+| **CPU** | CPU request (e.g., `800m`). |
+| **Memory** | Memory request (e.g., `1Gi`). |
+
+**Mongos** — Acts as the query router for the sharded cluster, directing client requests to the appropriate shards based on metadata from Config Servers.
+
+
+
+| Field | Description |
+|---|---|
+| **Replicaset number** | Number of Mongos router instances (e.g., `2`). Required. |
+| **Machine** | Preset machine profile or `custom`. |
+| **CPU** | CPU request (e.g., `500m`). |
+| **Memory** | Memory request (e.g., `1Gi`). |
+
+## mongodb+srv Style DNS (Replicated Cluster Only)
+
+> **What this is for.** A `mongodb+srv://` connection string lets a client discover every replica set member from a single DNS SRV record instead of listing each host. To make that work from outside the cluster, every member must advertise an externally reachable address (this is MongoDB's *horizon* mechanism). The **mongodb+srv style DNS** toggle on the **Replicated Cluster** form configures those per-pod addresses.
+
+This applies **only** when you intend to reach a **Replicated Cluster** MongoDB from outside Kubernetes with a `mongodb+srv` connection string. If you only connect from within the cluster, use **Standalone**/**Sharded Cluster** mode, or connect with a standard `mongodb://` string, leave it off.
+
+**Prerequisites** — the toggle only takes effect when both are enabled (see [Additional Options](../common-steps/#6-additional-options)):
+
+- **TLS** on the database (upstream TLS). MongoDB requires TLS for SRV-based horizon connections.
+- **Expose via Gateway**, so the members are reachable from outside the cluster.
+
+Turn on **mongodb+srv style DNS** to reveal the endpoints panel:
+
+
+
+| Field | Description |
+|---|---|
+| **SRV DNS Endpoints** | One entry per replica set member, in pod order (member 0, member 1, …). Each entry is the externally reachable endpoint that pod should advertise. The number of entries must match the **Replicaset Number** set above. Use **+ Add new** to add an entry. |
+
+The endpoints you enter must resolve to the externally reachable address of the exposed database and must be covered by the TLS certificate's SANs.
+
+### DNS records you must create
+
+The `mongodb+srv://` scheme is pure DNS discovery — the platform advertises the endpoints, but you must create the matching records in your DNS zone (for a replica set `rs0` on domain `example.com`):
+
+| Record | Example | Why it's needed |
+|---|---|---|
+| **A** / **CNAME** — one per member | `mongo-0.example.com → ` (repeat for each member) | Each **SRV DNS Endpoint** you entered must resolve to the member's externally reachable address. Use **A** for a fixed IP, **CNAME** to alias a managed hostname. |
+| **SRV** — one per member, same name | `_mongodb._tcp.example.com IN SRV 0 0 mongo-0.example.com.` | This is what the driver queries first: connecting to `mongodb+srv://example.com` returns all members (host + port) so the client discovers the full replica set from one name. |
+| **TXT** — one, same name | `example.com IN TXT "replicaSet=rs0&authSource=admin"` | The SRV scheme requires a TXT record alongside the SRV to carry options that don't fit in SRV fields; the driver auto-appends `replicaSet`/`authSource` so the app never hardcodes them. |
+
+Verify before relying on it: `dig SRV _mongodb._tcp.example.com` and `dig TXT example.com`.
+
+## Additional MongoDB Options
+
+| Field | Description |
+|---|---|
+| **Arbiter** | Toggle on to add an arbiter member (votes in elections but stores no data). Configure its pod resources. |
+| **Hidden Node** | Toggle on to add hidden replica members (replicate data but are invisible to clients). Set **Replicas**, resources, and storage. |
+| **HostName / IP** | Optional host name and IP used to build the connection string and certificate SANs. |
+
+## Create a MongoDB Database
+
+1. Open the wizard and select **MongoDB** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database). For **Replicated Cluster** mode, configure [mongodb+srv style DNS](#mongodbsrv-style-dns-replicated-cluster-only) if you'll connect with a `mongodb+srv` string from outside the cluster.
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/mssqlserver.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mssqlserver.md
new file mode 100644
index 0000000000..e9bc8c5f7d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mssqlserver.md
@@ -0,0 +1,58 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-mssqlserver
+ name: Microsoft SQL Server
+ parent: database-management-create
+ weight: 130
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Microsoft SQL Server Database
+
+This page covers the configuration specific to **Microsoft SQL Server** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node SQL Server instance.
+- **Topology** — A high-availability deployment using an **Availability Group**.
+
+
+
+**Availability Group**
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of replicas participating in the availability group (e.g., `3`). Required. |
+
+## SQL Server Settings
+
+Microsoft SQL Server requires you to accept the licensing terms and choose a product edition.
+
+
+
+| Field | Description |
+|---|---|
+| **Accept EULA** | You must accept the SQL Server End-User License Agreement before the database can be deployed. Required. |
+| **PID (Edition)** | The SQL Server product edition: `Developer`, `Express`, `Standard`, `Evaluation`, `Enterprise`, `EnterpriseCore`, or `Custom`. |
+
+When **Topology** mode is used, you may also list the **Databases** to include in the Availability Group.
+
+## Create a Microsoft SQL Server Database
+
+1. Open the wizard and select **Microsoft SQL Server** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/mysql.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mysql.md
new file mode 100644
index 0000000000..8ca4309feb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/mysql.md
@@ -0,0 +1,49 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-mysql
+ name: MySQL
+ parent: database-management-create
+ weight: 160
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a MySQL Database
+
+This page covers the configuration specific to **MySQL** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Available modes:
+
+- **Standalone** — A single-node MySQL instance.
+- **GroupReplication** — A MySQL Group Replication cluster. Choose a group **Mode**: `Single-Primary` or `Multi-Primary`.
+- **InnoDBCluster** — A MySQL InnoDB Cluster fronted by MySQL Router. Choose `Single-Primary` or `Multi-Primary`.
+- **SemiSync** — A semi-synchronous replication topology with configurable acknowledgement.
+- **RemoteReplica** — A replica that streams from an external/primary MySQL.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for clustered modes. |
+| **Mode** (Group/InnoDB) | `Single-Primary` or `Multi-Primary`. |
+| **SemiSync** | `Source Wait For Replica Count`, `Source Timeout`, and `Errant Transaction Recovery Policy` (`Clone` or `PseudoTransaction`). |
+| **Router** (InnoDB) | MySQL Router instance count and resources. |
+
+## Create a MySQL Database
+
+1. Open the wizard and select **MySQL** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/neo4j.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/neo4j.md
new file mode 100644
index 0000000000..e4cb1d060d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/neo4j.md
@@ -0,0 +1,51 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-neo4j
+ name: Neo4j
+ parent: database-management-create
+ weight: 170
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Neo4j Database
+
+This page covers the configuration specific to **Neo4j** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Neo4j Settings
+
+| Field | Description |
+|---|---|
+| **Storage Type** | `Durable` (persistent volumes) or `Ephemeral` (no persistence). |
+| **Disable Security** | Run without authentication (development only). |
+| **TLS** | Configure TLS per protocol — **Bolt**, **HTTP**, and **Cluster** — each signed by the selected **Issuer**. |
+
+## Create a Neo4j Database
+
+1. Open the wizard and select **Neo4j** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/oracle.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/oracle.md
new file mode 100644
index 0000000000..beb814c49a
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/oracle.md
@@ -0,0 +1,49 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-oracle
+ name: Oracle
+ parent: database-management-create
+ weight: 180
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Oracle Database
+
+This page covers the configuration specific to **Oracle** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node Oracle instance.
+- **DataGuard** — An Oracle Data Guard configuration with a primary and standby database for disaster recovery.
+
+
+
+When **DataGuard** is selected:
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of database nodes. Required. |
+| **Protection Mode** | `MaximumAvailability`, `MaximumPerformance`, or `MaximumProtection`. |
+| **Sync Mode** | `SYNC` or `ASYNC` redo transport. |
+| **Standby Type** | `PHYSICAL` or `LOGICAL` standby. |
+| **Apply Lag Threshold** | Optional threshold for the observer to act on apply lag. |
+
+## Create a Oracle Database
+
+1. Open the wizard and select **Oracle** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/perconaxtradb.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/perconaxtradb.md
new file mode 100644
index 0000000000..7edcebc1e0
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/perconaxtradb.md
@@ -0,0 +1,40 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-perconaxtradb
+ name: Percona XtraDB
+ parent: database-management-create
+ weight: 190
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Percona XtraDB Database
+
+This page covers the configuration specific to **Percona XtraDB** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Percona XtraDB is deployed as a single logical instance. Set the **Number of Replicas** to control how many nodes back the instance for availability.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes for the instance (e.g., `1` for a single node, `3` for high availability). |
+
+## Create a Percona XtraDB Database
+
+1. Open the wizard and select **Percona XtraDB** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgbouncer.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgbouncer.md
new file mode 100644
index 0000000000..6761c55457
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgbouncer.md
@@ -0,0 +1,53 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-pgbouncer
+ name: PgBouncer
+ parent: database-management-create
+ weight: 200
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a PgBouncer Database
+
+This page covers the configuration specific to **PgBouncer** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Backend Database
+
+PgBouncer pools connections to a backend PostgreSQL database.
+
+| Field | Description |
+|---|---|
+| **Database Ref (Namespace / Name)** | Reference to the backend PostgreSQL instance to pool connections for. |
+| **Database Name** | The database name PgBouncer exposes to clients. |
+| **Sync Users** | Toggle on to synchronize users from the backend PostgreSQL. |
+
+## Create a PgBouncer Database
+
+1. Open the wizard and select **PgBouncer** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgpool.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgpool.md
new file mode 100644
index 0000000000..341ab41349
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/pgpool.md
@@ -0,0 +1,52 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-pgpool
+ name: Pgpool
+ parent: database-management-create
+ weight: 210
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Pgpool Database
+
+This page covers the configuration specific to **Pgpool** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Backend Database
+
+Pgpool sits in front of a PostgreSQL instance for connection pooling and load balancing.
+
+| Field | Description |
+|---|---|
+| **Postgres Ref (Namespace / Name)** | Reference to the backend PostgreSQL instance. Required. |
+| **Sync Users** | Toggle on to synchronize users from the backend PostgreSQL. |
+
+## Create a Pgpool Database
+
+1. Open the wizard and select **Pgpool** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/postgres.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/postgres.md
new file mode 100644
index 0000000000..772ba39c26
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/postgres.md
@@ -0,0 +1,48 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-postgres
+ name: PostgreSQL
+ parent: database-management-create
+ weight: 220
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a PostgreSQL Database
+
+This page covers the configuration specific to **PostgreSQL** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Three modes are available:
+
+- **Standalone** — A single-node PostgreSQL instance.
+- **Cluster** — A primary with one or more streaming replicas for high availability. Set the **Number of Replicas**.
+- **RemoteReplica** — A replica that streams from an external/primary PostgreSQL for cross-cluster replication.
+
+
+
+When **Cluster** is selected, configure replication behaviour:
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of standby replicas (e.g., `3`). Required. |
+| **Standby Mode** | `Hot` (replicas accept read queries) or `Warm` (replicas stay in standby, no reads). |
+| **Streaming Mode** | `Synchronous` (commit waits for replica acknowledgement) or `Asynchronous` (commit does not wait). |
+
+## Create a PostgreSQL Database
+
+1. Open the wizard and select **PostgreSQL** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/proxysql.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/proxysql.md
new file mode 100644
index 0000000000..5215c4becb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/proxysql.md
@@ -0,0 +1,52 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-proxysql
+ name: ProxySQL
+ parent: database-management-create
+ weight: 230
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a ProxySQL Database
+
+This page covers the configuration specific to **ProxySQL** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Backend
+
+ProxySQL proxies traffic to a backend MySQL-family cluster.
+
+| Field | Description |
+|---|---|
+| **Backend** | Reference to the backend database the proxy fronts. |
+| **Sync Users** | Toggle on to synchronize users from the backend. |
+
+## Create a ProxySQL Database
+
+1. Open the wizard and select **ProxySQL** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/qdrant.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/qdrant.md
new file mode 100644
index 0000000000..ef21975338
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/qdrant.md
@@ -0,0 +1,52 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-qdrant
+ name: Qdrant
+ parent: database-management-create
+ weight: 240
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Qdrant Database
+
+This page covers the configuration specific to **Qdrant** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node Qdrant instance.
+- **Distributed** — A multi-node Qdrant cluster that shards collections across nodes for scale and availability.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the distributed cluster (e.g., `3`). Required for Distributed. |
+
+## Qdrant Settings
+
+| Field | Description |
+|---|---|
+| **Storage Type** | `Durable` (persistent volumes) or `Ephemeral` (no persistence). |
+| **Disable Security** | Run without API-key authentication (development only). |
+| **Halted** | Create the instance in a halted (stopped) state. |
+| **TLS** | Enable TLS for **Client** and/or **P2P** (inter-node) traffic, signed by the selected **Issuer**. |
+
+## Create a Qdrant Database
+
+1. Open the wizard and select **Qdrant** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/rabbitmq.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/rabbitmq.md
new file mode 100644
index 0000000000..1653b0e631
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/rabbitmq.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-rabbitmq
+ name: RabbitMQ
+ parent: database-management-create
+ weight: 250
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a RabbitMQ Database
+
+This page covers the configuration specific to **RabbitMQ** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Create a RabbitMQ Database
+
+1. Open the wizard and select **RabbitMQ** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/redis.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/redis.md
new file mode 100644
index 0000000000..a8b3bbfb85
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/redis.md
@@ -0,0 +1,68 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-redis
+ name: Redis
+ parent: database-management-create
+ weight: 260
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Redis Database
+
+This page covers the configuration specific to **Redis** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Three modes are available:
+
+- **Standalone** — A single-node Redis instance. Best for development or low-traffic workloads.
+- **Cluster** — A sharded Redis Cluster for horizontal scaling and high availability.
+- **Sentinel** — A primary/replica setup monitored by Redis Sentinel for automatic failover.
+
+
+
+| Mode | Key fields |
+|---|---|
+| **Cluster** | **Master** count and **Replicas** per master. |
+| **Sentinel** | **Number of Replicas** and the referenced **Sentinel** instance. |
+
+## Announce Redis Endpoints (Cluster Mode Only)
+
+> **Important — required if you plan to expose a Cluster-mode Redis externally.** The default external endpoint (via **Expose via Gateway**, see [Additional Options](../common-steps/#6-additional-options)) is a single Kubernetes Service that load-balances across *all* pods in *all* shards. Redis Cluster clients don't work well with that: a client's request is only served correctly if the pod it happens to connect to owns the requested key's slot — otherwise Redis replies with a redirect to the internal pod IP, which the external client cannot reach and the connection times out.
+>
+> Toggling on **Announce Redis Endpoints** tells each Redis node to advertise its externally reachable address instead of its internal IP, so redirects point somewhere the client can actually connect to.
+
+If **Database Mode** is **Cluster**, an **Announce Redis Endpoints ?** toggle appears below **Storage Size**. Turn it on to reveal the **Announce** panel:
+
+
+
+| Field | Description |
+|---|---|
+| **Type** | How the endpoint is advertised to clients — `hostname` or `ip`. Ask your cluster administrator which one your externally reachable Redis endpoints use. |
+| **Shards** | One row per shard, in the same order the shards are provisioned (shard 0, shard 1, …). Each row's **Shard Endpoints** field takes a comma-separated list of the externally reachable endpoints for every node (master + replicas) in that shard. Use **+ Add new** to add a row if you have more shards than rows shown. |
+
+The number of shard rows must match the **Shards** count you set above, and each row must list one endpoint per node in that shard (master + replicas).
+
+Whatever the **Type** (`hostname` or `ip`), the values you enter must ultimately resolve to the envoy service's external IP. For `hostname`, point a DNS **A** or **CNAME** record at that IP; for `ip`, enter the envoy service's IP directly. When exposure is enabled, envoy opens a set of ports on its external IP — one per Redis pod — and clients reach each pod through its assigned port.
+
+> **Note:** This only applies when you intend to connect to a **Cluster**-mode Redis from outside Kubernetes. If you only access it from within the cluster, or you're using **Standalone**/**Sentinel** mode, leave this off.
+
+For the underlying mechanism, see the [Redis External Connections guide](https://kubedb.com/docs/v2026.6.19/guides/redis/external-connections/exposure/).
+
+## Create a Redis Database
+
+1. Open the wizard and select **Redis** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database). For **Cluster** mode, configure [Announce Redis Endpoints](#announce-redis-endpoints-cluster-mode-only) if you'll expose it externally.
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/singlestore.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/singlestore.md
new file mode 100644
index 0000000000..cfb97d0060
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/singlestore.md
@@ -0,0 +1,61 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-singlestore
+ name: SingleStore
+ parent: database-management-create
+ weight: 280
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a SingleStore Database
+
+This page covers the configuration specific to **SingleStore** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**:
+
+- **Standalone** — A single-node SingleStore instance.
+- **Topology** — A distributed cluster split into **Aggregator** and **Leaf** node tiers.
+
+
+
+**Aggregator** — Routes queries and aggregates results.
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of aggregator nodes. Required. |
+| **Storage size**, **Machine**, **CPU**, **Memory** | Resources per aggregator node. |
+
+**Leaf** — Stores and processes the partitioned data.
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of leaf nodes. Required. |
+| **Storage size**, **Machine**, **CPU**, **Memory** | Resources per leaf node. |
+
+## License
+
+SingleStore is commercial software and requires a license.
+
+| Field | Description |
+|---|---|
+| **License Secret** | Name of the Kubernetes Secret containing your SingleStore license key. Required. |
+
+## Create a SingleStore Database
+
+1. Open the wizard and select **SingleStore** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/solr.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/solr.md
new file mode 100644
index 0000000000..9ee7a996a4
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/solr.md
@@ -0,0 +1,59 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-solr
+ name: Solr
+ parent: database-management-create
+ weight: 290
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Solr Database
+
+This page covers the configuration specific to **Solr** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Three modes are available:
+
+- **Standalone** — A single-node Solr instance.
+- **Replicaset** — A multi-node Solr cluster. Set the **Number of Replicas**.
+- **Topology** — A role-separated cluster with dedicated **Overseer**, **Data**, and **Coordinator** node tiers.
+
+
+
+| Node | Description |
+|---|---|
+| **Overseer** | Cluster-management nodes that handle cluster state and coordination. |
+| **Data** | Nodes that host collections/shards and serve indexing and query traffic. |
+| **Coordinator** | Query-routing nodes that distribute requests across data nodes. |
+
+Each tier has its own **Number of Replicas**, **Storage size**, **Machine**, **CPU**, and **Memory** fields.
+
+## ZooKeeper
+
+SolrCloud requires ZooKeeper for coordination.
+
+| Field | Description |
+|---|---|
+| **ZooKeeper Ref (Namespace / Name)** | Reference to the ZooKeeper instance Solr uses for coordination. |
+
+
+
+
+## Create a Solr Database
+
+1. Open the wizard and select **Solr** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/weaviate.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/weaviate.md
new file mode 100644
index 0000000000..cd80dd06a8
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/weaviate.md
@@ -0,0 +1,49 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-weaviate
+ name: Weaviate
+ parent: database-management-create
+ weight: 300
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a Weaviate Database
+
+This page covers the configuration specific to **Weaviate** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Weaviate is deployed as a single logical instance. Set the **Number of Replicas** to control how many nodes back the instance for availability.
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes for the instance (e.g., `1` for a single node, `3` for high availability). |
+
+> **Note:** Weaviate exposes a **Disable Security** toggle to run without authentication (development only).
+
+## Weaviate Settings
+
+| Field | Description |
+|---|---|
+| **Disable Security** | Run without authentication (development only). |
+| **Health Checker** | Tune the health probe: **Period (s)**, **Timeout (s)**, and **Failure Threshold**. |
+
+## Create a Weaviate Database
+
+1. Open the wizard and select **Weaviate** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/create-database/zookeeper.md b/content/docs/platform/v2026.7.10/guides/database-management/create-database/zookeeper.md
new file mode 100644
index 0000000000..a9c126ce49
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/create-database/zookeeper.md
@@ -0,0 +1,43 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-create-zookeeper
+ name: ZooKeeper
+ parent: database-management-create
+ weight: 310
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Creating a ZooKeeper Database
+
+This page covers the configuration specific to **ZooKeeper** — its **Database Mode** and any engine-specific settings shown below. The rest of the creation flow —
+opening the wizard, namespace and name, version, machine profile, storage, and optional
+features — is the same for every engine and is documented in [Common Steps](../common-steps.md).
+
+## Database Mode
+
+Select the topology under **Database Mode**. Two modes are available:
+
+- **Standalone** — A single-node instance. Best for development or low-traffic workloads.
+- **Replicaset** — A multi-node cluster for high availability. Set the **Number of Replicas** (e.g., `3`).
+
+
+
+| Field | Description |
+|---|---|
+| **Number of Replicas** | Number of nodes in the cluster (e.g., `3`). Required for Replicaset. |
+
+## Create a ZooKeeper Database
+
+1. Open the wizard and select **ZooKeeper** — see [Getting Started](../common-steps/#1-getting-started) and [Select a Database Type](../common-steps/#2-select-a-database-type).
+1. Set the [namespace and name](../common-steps/#3-choose-namespace-and-name).
+1. Pick the database version and the **Database Mode** described above, then set the machine profile and storage — see [Configure the Database](../common-steps/#4-configure-the-database).
+1. Optionally configure [Advanced Configuration](../common-steps/#5-advanced-configuration) (labels, deletion policy, credentials, point-in-time recovery) and [Additional Options](../common-steps/#6-additional-options) (monitoring, backup, TLS, gateway).
+1. Click [**Deploy**](../common-steps/#7-deploy).
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/database-usage-insight.md b/content/docs/platform/v2026.7.10/guides/database-management/database-usage-insight.md
new file mode 100644
index 0000000000..669fa50aeb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/database-usage-insight.md
@@ -0,0 +1,180 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-insights
+ name: Database Usage & Insights
+ parent: database-management
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Database Usage & Insights
+
+Every database detail page has **Overview**, **Insights**, and **Users** pages. They give a live view of the database's connection details, performance metrics, query analytics, and access control bindings.
+
+---
+
+## 1. Getting Started
+
+From the **Datastore** section in the left sidebar, click on any database engine (e.g., **MongoDB**) and then click on a database instance name to open its detail page. The top of the page shows three main tabs:
+
+- **Overview** — Connection details and a high-level insights summary.
+- **Insights** — Detailed metrics, Grafana dashboards, slow queries, and top collections.
+- **Users** — Root user credentials, AppBindings, and KubeVault-managed access.
+
+---
+
+## 2. Overview
+
+The **Overview** tab has two panels — **Connection Details** and **Insights** — and a **Nodes** table at the bottom.
+
+
+
+### 2.1 - Connection Details
+
+The **Connection Details** panel provides everything needed to connect to the database:
+
+- **Basic tab** — Shows the primary connection string and quick-copy flags for connecting with the CLI or client libraries.
+- **Connection Parameters tab** — Breaks down individual connection parameters (host, port, username, database name) so you can assemble a custom connection string.
+
+> **Note:** After clicking the link, please wait a few moments for it to process. You may need to refresh the page to see the updated data.
+
+### 2.2 - Insights Summary
+
+The **Insights** panel on the right gives a live snapshot of key database statistics:
+
+| Metric | Description |
+|---|---|
+| **Current Connections** | Number of active client connections at this moment |
+| **Total Connections** | Cumulative connections since the database started |
+| **Available Connections** | Remaining connections before the limit is reached |
+| **Active Connections** | Connections currently executing an operation |
+| **Total Indexes** | Total number of indexes across all collections |
+| **Index Size** | Total disk space used by all indexes |
+| **Total Collections** | Total number of collections in the database |
+| **Data Size** | Total size of all documents stored |
+| **Replicas Per Shards** | Number of replicas in each shard |
+| **Number Of Shards** | Total number of shards in the cluster |
+| **Number Of Chunks** | Total number of chunks across all shards |
+| **Chunks Balanced** | Whether chunks are evenly distributed across shards |
+
+### 2.3 - Nodes
+
+The **Nodes** table at the bottom lists every pod in the database cluster with its role, CPU and memory usage, storage, status, age, and links to its dashboard and connect shell.
+
+---
+
+## 3. Insights
+
+The **Insights** tab provides Grafana dashboards, slow query analysis, and collection-level storage metrics.
+
+
+
+### 3.1 - Insights Summary Row
+
+A condensed stat row at the top mirrors the key metrics from the Overview panel for quick reference without switching tabs.
+
+### 3.2 - Grafana Dashboards
+
+The **Grafana Dashboards** section embeds pre-built dashboards for your database directly in the console. If Grafana integration is not yet configured, an error message will indicate that the dashboard link is missing and provide instructions to set it up.
+
+> **Tip:** To enable Grafana dashboards, ensure the Grafana datasource is configured in your cluster and the correct dashboard URL is registered in your KubeDB Platform settings.
+
+### 3.3 - Slow Queries
+
+The **Slow Queries** table lists database operations that exceeded a performance threshold. Each row contains:
+
+| Column | Description |
+|---|---|
+| **Operation** | The type of database operation (e.g., `find`, `update`) |
+| **Database Name** | The database where the slow query ran |
+| **Collection Name** | The collection targeted by the query |
+| **Command** | The raw command document |
+| **Count** | How many times this query pattern was recorded |
+| **Avg Execution Time (ms)** | Average time the query took to execute |
+| **Min Execution Time (ms)** | Fastest recorded execution for this query pattern |
+| **Max Execution Time (ms)** | Slowest recorded execution for this query pattern |
+
+Use the pagination controls at the bottom-right to navigate through results.
+
+### 3.4 - Top Collections
+
+The **Top Collections** table lists collections ranked by total storage size, helping you identify which collections consume the most disk space.
+
+| Column | Description |
+|---|---|
+| **Name** | The fully qualified collection name (e.g., `health.check`) |
+| **Total Size** | Combined size of documents and indexes in the collection |
+
+---
+
+## 4. Users
+
+The **Users** tab shows all access credentials, bindings, and KubeVault-managed secrets associated with the database instance.
+
+
+
+### 4.1 - Root User
+
+The **Root User** section lists the primary database credentials created by KubeDB. Each entry shows:
+
+| Column | Description |
+|---|---|
+| **Name** | The Kubernetes Secret name holding the credentials |
+| **Namespace** | The namespace where the Secret resides |
+| **Annotations** | Key annotations applied to the Secret (e.g., managed-by, instance) |
+| **Type** | The Secret type (e.g., `kubernetes.io/basic-auth`) |
+| **Date** | Creation date of the Secret |
+| **Age** | Age of the Secret |
+
+### 4.2 - AppBinding
+
+The **AppBinding** section lists `AppBinding` resources that expose this database to other applications in the cluster. Each entry shows:
+
+| Column | Description |
+|---|---|
+| **Name** | The AppBinding resource name |
+| **Namespace** | The namespace where the AppBinding resides |
+| **Type** | The AppBinding type (e.g., `kubedb.com/mongodb`) |
+| **Version** | The database engine version |
+| **Genres** | The genre classification of the binding |
+| **Secret** | The Secret referenced by this AppBinding for credentials |
+| **Age** | Age of the AppBinding resource |
+
+### 4.3 - VaultServers, SecretEngines, MongoDBRoles & SecretAccessRequests
+
+The lower sections of the **Users** tab are powered by **KubeVault** and provide dynamic secret management for your database.
+
+
+
+| Section | Description |
+|---|---|
+| **VaultServers** | Lists Vault server instances managing secrets for this database |
+| **SecretEngines** | Lists configured secret engines that generate dynamic database credentials |
+| **MongoDBRoles** | Lists KubeVault roles that define credential policies for this database |
+| **SecretAccessRequests** | Lists requests made by applications for dynamic credentials |
+
+> **Note:** These sections require the **kubevault** feature to be enabled in your cluster. If not yet enabled, each section will show a prompt with a link to enable the feature.
+
+---
+
+## Quick Reference
+
+| Action | Where to find it |
+|---|---|
+| Get the database connection string | **Overview** → **Connection Details** → Basic tab |
+| View live connection and storage stats | **Overview** → **Insights** panel |
+| Check pod-level resource usage | **Overview** → **Nodes** table |
+| View Grafana performance dashboards | **Insights** → **Grafana Dashboards** |
+| Identify slow queries | **Insights** → **Slow Queries** table |
+| Find largest collections | **Insights** → **Top Collections** table |
+| Access root credentials | **Users** → **Root User** |
+| View AppBindings for this database | **Users** → **AppBinding** |
+| Manage dynamic secrets via KubeVault | **Users** → VaultServers / SecretEngines / MongoDBRoles / SecretAccessRequests |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/delete-database.md b/content/docs/platform/v2026.7.10/guides/database-management/delete-database.md
new file mode 100644
index 0000000000..3e0d62ebf2
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/delete-database.md
@@ -0,0 +1,70 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-delete
+ name: Delete Database
+ parent: database-management
+ weight: 110
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Delete Database
+
+There are two ways to delete a database — from the **Datastore Overview** page (bulk or single) or from inside the **individual database page**. Both lead to the same confirmation step.
+
+> **Warning:** Deleting a database is a permanent and irreversible action. Ensure you have a valid backup before proceeding.
+
+---
+
+## 1. Getting Started
+
+Navigate to the **Datastore** section from the left sidebar and select your database engine (e.g., **MongoDB**). This opens the **Datastore Overview** page, which lists all database instances in the selected namespace.
+
+---
+
+## 2. Deleting from the Datastore Overview
+
+Use this method to delete one or more databases at once from the instance list.
+
+
+
+1. **Select Namespace:** Use the **Select Namespace** dropdown in the top-right to filter instances by namespace if needed.
+1. **Select Instance(s):** Check the checkbox next to each database instance you want to delete (e.g., `mongodb demo`).
+1. **Delete Selected:** Click the red **Delete Selected** button that appears in the top-right of the Overview table.
+1. **Confirm:** A confirmation modal will appear asking *"Are you sure you want to delete the selected databases?"* Click **Yes** to proceed, or **Cancel** to abort.
+
+
+
+---
+
+## 3. Deleting from the Database Detail Page
+
+Use this method to delete a specific database from its detail page.
+
+
+
+1. From the **Datastore Overview**, click on the name of the database instance you want to delete to open its detail page.
+1. **Delete:** Click the red **Delete** button in the top-right corner of the page.
+1. **Confirm:** A confirmation modal will appear showing the name of the database. Click **Yes** to permanently delete it, or **Cancel** to abort.
+
+
+
+> **Warning:** Clicking **Yes** immediately and permanently removes the database. There is no undo. Confirm you have a backup before proceeding.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Delete one or more databases at once | **Datastore Overview** → check instance(s) → **Delete Selected** |
+| Delete a specific database | Open the database detail page → click **Delete** (top-right) |
+| Confirm deletion | Confirmation modal → click **Yes** |
+| Abort deletion | Confirmation modal → click **Cancel** or **✕** |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/expose-via-gateway.md b/content/docs/platform/v2026.7.10/guides/database-management/expose-via-gateway.md
new file mode 100644
index 0000000000..efee21660f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/expose-via-gateway.md
@@ -0,0 +1,55 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-expose-via-gateway
+ name: Expose via Gateway
+ parent: database-management
+ weight: 77
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Expose via Gateway
+
+Control whether your database is exposed externally through the gateway. Enabling this makes your database accessible outside the cluster via the configured gateway endpoint.
+
+---
+
+## 1. Getting Started
+
+Select **Expose via Gateway** from the **Operations** section in the left sidebar. The form has a single toggle that controls the gateway exposure state of your database.
+
+
+
+---
+
+## 2. Exposing the Database
+
+1. **Expose Database:** Toggle this switch to enable or disable external access to your database through the gateway.
+ - Toggle **on** — The database will be exposed and accessible via the gateway endpoint.
+ - Toggle **off** — The database will be unexposed and gateway access will be removed.
+
+> **Warning:** Exposing your database through the gateway makes it accessible from outside the cluster. Ensure TLS and authentication are properly configured before enabling this option.
+
+---
+
+## 3. Applying the Change
+
+1. **Deploy:** Once you have set the toggle to the desired state, click **Deploy** to apply the change immediately.
+
+> **Note:** Unlike other operations, this action does not have a Preview step — the change is applied as soon as you click **Deploy**. Verify your toggle state before proceeding.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Expose database via gateway | Toggle **Expose Database** on → **Deploy** |
+| Remove gateway exposure | Toggle **Expose Database** off → **Deploy** |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-nodetopology.png b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-nodetopology.png
new file mode 100644
index 0000000000..9b4d12af88
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-nodetopology.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-readiness.png b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-readiness.png
new file mode 100644
index 0000000000..0cfa789f6b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-readiness.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-standalone.png b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-standalone.png
new file mode 100644
index 0000000000..94b3c254c8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling-standalone.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling.png b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling.png
new file mode 100644
index 0000000000..ff986cafbd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/auto-scaling.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-blueprint.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-blueprint.png
new file mode 100644
index 0000000000..208d3f34e1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-blueprint.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-create.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-create.png
new file mode 100644
index 0000000000..88c25e1a7c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-create.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-delete.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-delete.png
new file mode 100644
index 0000000000..580262e857
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-delete.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-modify.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-modify.png
new file mode 100644
index 0000000000..0977600d16
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-modify.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-submit.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-submit.png
new file mode 100644
index 0000000000..8d0cb37d9c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config-submit.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config.png
new file mode 100644
index 0000000000..aa3af68e87
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup-config.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-overview.png
new file mode 100644
index 0000000000..a549ba3e6d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-repository.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-repository.png
new file mode 100644
index 0000000000..7920f53469
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-db-repository.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-dbs-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-dbs-overview.png
new file mode 100644
index 0000000000..dbc625a14b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-dbs-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-label-annotation.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-label-annotation.png
new file mode 100644
index 0000000000..31dff63075
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-label-annotation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-name-namespace.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-name-namespace.png
new file mode 100644
index 0000000000..0da15ae5eb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-name-namespace.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-session-task.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-session-task.png
new file mode 100644
index 0000000000..ad5b4b5877
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-session-task.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-sessions.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-sessions.png
new file mode 100644
index 0000000000..a9d319cb9f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-sessions.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-target.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-target.png
new file mode 100644
index 0000000000..eb0a32742a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/config-target.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/configuration-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/configuration-overview.png
new file mode 100644
index 0000000000..b640444f63
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/configuration-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-create.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-create.png
new file mode 100644
index 0000000000..39d527b8a0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-create.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-overview.png
new file mode 100644
index 0000000000..ac5c43be88
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-backup-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-create-form.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-create-form.png
new file mode 100644
index 0000000000..43d25ce5f6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-create-form.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-db-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-db-overview.png
new file mode 100644
index 0000000000..c21a983cff
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/recent-db-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-app-ref.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-app-ref.png
new file mode 100644
index 0000000000..23772ca814
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-app-ref.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-create-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-create-overview.png
new file mode 100644
index 0000000000..02f5259710
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-create-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-overview.png
new file mode 100644
index 0000000000..26e415f655
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-snapshot.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-snapshot.png
new file mode 100644
index 0000000000..9b3c47ae85
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-db-snapshot.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-label-annotation.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-label-annotation.png
new file mode 100644
index 0000000000..8e4992fbf9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-label-annotation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-overview.png
new file mode 100644
index 0000000000..21b4168e53
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-ref-secret.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-ref-secret.png
new file mode 100644
index 0000000000..04a72afbc6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/repository-ref-secret.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-config.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-config.png
new file mode 100644
index 0000000000..16e8e55920
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-config.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-create-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-create-overview.png
new file mode 100644
index 0000000000..9d53ca510d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-create-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-overview.png
new file mode 100644
index 0000000000..432d2822d1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-target.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-target.png
new file mode 100644
index 0000000000..dd2cd2feca
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/restore-target.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-delete.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-delete.png
new file mode 100644
index 0000000000..8a571e2a69
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-delete.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-operation-view.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-operation-view.png
new file mode 100644
index 0000000000..44a7e6c352
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-operation-view.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-overview.png
new file mode 100644
index 0000000000..ea90dce306
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/snapshot-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-backend.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-backend.png
new file mode 100644
index 0000000000..5b2a8dbecb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-backend.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-overview.png
new file mode 100644
index 0000000000..35c409b633
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-create-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-db-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-db-overview.png
new file mode 100644
index 0000000000..a33b7ea499
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-db-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-label-annotation.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-label-annotation.png
new file mode 100644
index 0000000000..b724ee9b55
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-label-annotation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-overview.png
new file mode 100644
index 0000000000..4d6bc4a60c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/backup/storage-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/cassandra/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/cassandra/topology-mode.png
new file mode 100644
index 0000000000..ca60728e97
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/cassandra/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/clickhouse/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/clickhouse/topology-mode.png
new file mode 100644
index 0000000000..6fd31d84cd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/clickhouse/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/documentdb/replicas.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/documentdb/replicas.png
new file mode 100644
index 0000000000..597a461cd7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/documentdb/replicas.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-1.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-1.png
new file mode 100644
index 0000000000..f43f748ffe
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-1.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-2.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-2.png
new file mode 100644
index 0000000000..a97c2247cf
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/druid/topology-mode-2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/settings.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/settings.png
new file mode 100644
index 0000000000..353b07f3c6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/settings.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/topology-mode.png
new file mode 100644
index 0000000000..60dceb1f43
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/elasticsearch/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hanadb/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hanadb/mode-select.png
new file mode 100644
index 0000000000..6728254f95
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hanadb/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hazelcast/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hazelcast/topology-mode.png
new file mode 100644
index 0000000000..546f081fe8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/hazelcast/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/ignite/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/ignite/replicaset-mode.png
new file mode 100644
index 0000000000..8b88e70a5d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/ignite/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/kafka/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/kafka/topology-mode.png
new file mode 100644
index 0000000000..2abf366f60
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/kafka/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mariadb/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mariadb/replicaset-mode.png
new file mode 100644
index 0000000000..c5f412d2cc
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mariadb/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/memcached/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/memcached/replicaset-mode.png
new file mode 100644
index 0000000000..e06f5de64b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/memcached/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/dependencies.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/dependencies.png
new file mode 100644
index 0000000000..f1418f04d2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/dependencies.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/mode-select.png
new file mode 100644
index 0000000000..62526af72d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/milvus/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/config-server.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/config-server.png
new file mode 100644
index 0000000000..897672c340
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/config-server.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/create-overview-page.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/create-overview-page.png
new file mode 100644
index 0000000000..f2057d68fa
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/create-overview-page.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/horizon.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/horizon.png
new file mode 100644
index 0000000000..82af5ddad0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/horizon.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/mongos-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/mongos-mode.png
new file mode 100644
index 0000000000..02ccb61424
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/mongos-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/replicaset-mode.png
new file mode 100644
index 0000000000..1b391064ea
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-mode.png
new file mode 100644
index 0000000000..b26f735bc2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-nodes.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-nodes.png
new file mode 100644
index 0000000000..77e5096682
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mongodb/shard-nodes.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/settings.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/settings.png
new file mode 100644
index 0000000000..c677515ade
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/settings.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/topology-mode.png
new file mode 100644
index 0000000000..6bc5927496
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mssqlserver/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mysql/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mysql/mode-select.png
new file mode 100644
index 0000000000..abafee170a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/mysql/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/neo4j/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/neo4j/replicaset-mode.png
new file mode 100644
index 0000000000..7a3c39e45f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/neo4j/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/oracle/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/oracle/mode-select.png
new file mode 100644
index 0000000000..28fe26c742
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/oracle/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/perconaxtradb/replicas.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/perconaxtradb/replicas.png
new file mode 100644
index 0000000000..ed7e2ec829
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/perconaxtradb/replicas.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgbouncer/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgbouncer/replicaset-mode.png
new file mode 100644
index 0000000000..2f8f2d3c3a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgbouncer/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgpool/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgpool/replicaset-mode.png
new file mode 100644
index 0000000000..57bffae9b9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/pgpool/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/postgres/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/postgres/mode-select.png
new file mode 100644
index 0000000000..603a3ff6c7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/postgres/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/proxysql/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/proxysql/replicaset-mode.png
new file mode 100644
index 0000000000..bd352e39ab
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/proxysql/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/qdrant/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/qdrant/mode-select.png
new file mode 100644
index 0000000000..734ce0361f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/qdrant/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/rabbitmq/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/rabbitmq/replicaset-mode.png
new file mode 100644
index 0000000000..7614067986
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/rabbitmq/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/announce.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/announce.png
new file mode 100644
index 0000000000..78bd1d1f6f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/announce.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/mode-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/mode-select.png
new file mode 100644
index 0000000000..e887554d71
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/redis/mode-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/Additional-option.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/Additional-option.png
new file mode 100644
index 0000000000..ee3d271270
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/Additional-option.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/advance-lavel-annotation.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/advance-lavel-annotation.png
new file mode 100644
index 0000000000..fe70496875
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/advance-lavel-annotation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/auth-creds.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/auth-creds.png
new file mode 100644
index 0000000000..2481e9b151
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/auth-creds.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/db-type-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/db-type-select.png
new file mode 100644
index 0000000000..c9e4b92c36
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/db-type-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/deletion-policy.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/deletion-policy.png
new file mode 100644
index 0000000000..ea05ee9cce
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/deletion-policy.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/machine-profile.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/machine-profile.png
new file mode 100644
index 0000000000..8afb9b444b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/machine-profile.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/name-namespace-select.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/name-namespace-select.png
new file mode 100644
index 0000000000..a2768618e5
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/name-namespace-select.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/overview-create.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/overview-create.png
new file mode 100644
index 0000000000..8d0e3660a7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/overview-create.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/point-in-time-recovery.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/point-in-time-recovery.png
new file mode 100644
index 0000000000..c32e35fd84
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/point-in-time-recovery.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/storage-class.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/storage-class.png
new file mode 100644
index 0000000000..68fae2174d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/shared/storage-class.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/singlestore/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/singlestore/topology-mode.png
new file mode 100644
index 0000000000..86d3426739
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/singlestore/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/fields.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/fields.png
new file mode 100644
index 0000000000..9c73355533
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/fields.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/topology-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/topology-mode.png
new file mode 100644
index 0000000000..0c5217b881
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/solr/topology-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/weaviate/replicas.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/weaviate/replicas.png
new file mode 100644
index 0000000000..96100bdf96
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/weaviate/replicas.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/zookeeper/replicaset-mode.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/zookeeper/replicaset-mode.png
new file mode 100644
index 0000000000..e3eda5e1ef
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-create/zookeeper/replicaset-mode.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-insights.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-insights.png
new file mode 100644
index 0000000000..50266b96a1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-insights.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-overview.png
new file mode 100644
index 0000000000..c4df90f4a2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-users-kubevault.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-users-kubevault.png
new file mode 100644
index 0000000000..21ebb644c7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-users-kubevault.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/db-users.png b/content/docs/platform/v2026.7.10/guides/database-management/images/db-users.png
new file mode 100644
index 0000000000..346c78bb44
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/db-users.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/delete-modal.png b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-modal.png
new file mode 100644
index 0000000000..d95b5cadcb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-modal.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview-modal.png b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview-modal.png
new file mode 100644
index 0000000000..67bd6dc67f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview-modal.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview.png
new file mode 100644
index 0000000000..127e1eec3a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/delete-overview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/delete.png b/content/docs/platform/v2026.7.10/guides/database-management/images/delete.png
new file mode 100644
index 0000000000..c44038ecb9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/delete.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/expose-via-gateway.png b/content/docs/platform/v2026.7.10/guides/database-management/images/expose-via-gateway.png
new file mode 100644
index 0000000000..11b0aa22de
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/expose-via-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/horizontal-scale-form.png b/content/docs/platform/v2026.7.10/guides/database-management/images/horizontal-scale-form.png
new file mode 100644
index 0000000000..bda4840c15
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/horizontal-scale-form.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup-form.png b/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup-form.png
new file mode 100644
index 0000000000..6a6f6cba4c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup-form.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup.png b/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup.png
new file mode 100644
index 0000000000..93798233ff
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/instant-backup.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-config.png b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-config.png
new file mode 100644
index 0000000000..76f3b6ea34
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-config.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-secret.png b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-secret.png
new file mode 100644
index 0000000000..ddb92d26e8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-env-secret.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-exporter.png b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-exporter.png
new file mode 100644
index 0000000000..0ea7293c9a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-exporter.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-scrapper.png b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-scrapper.png
new file mode 100644
index 0000000000..2d5b02a23f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring-scrapper.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring.png b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring.png
new file mode 100644
index 0000000000..f684e72663
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/monitoring.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-prometheus.png b/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-prometheus.png
new file mode 100644
index 0000000000..5c94ddf447
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-prometheus.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-service-monitor.png b/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-service-monitor.png
new file mode 100644
index 0000000000..2cbd297e0a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/motoring-service-monitor.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-apply.png b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-apply.png
new file mode 100644
index 0000000000..be43b89638
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-apply.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-create-secret.png b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-create-secret.png
new file mode 100644
index 0000000000..86844d067e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-create-secret.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-new-secret.png b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-new-secret.png
new file mode 100644
index 0000000000..50ac8585a7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-new-secret.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-remove.png b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-remove.png
new file mode 100644
index 0000000000..16f055907d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure-remove.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure.png b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure.png
new file mode 100644
index 0000000000..e77b32848e
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/reconfigure.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/restart-preview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/restart-preview.png
new file mode 100644
index 0000000000..b6c0d3889b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/restart-preview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/restart-submit.png b/content/docs/platform/v2026.7.10/guides/database-management/images/restart-submit.png
new file mode 100644
index 0000000000..1a4f039ed8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/restart-submit.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/restart.png b/content/docs/platform/v2026.7.10/guides/database-management/images/restart.png
new file mode 100644
index 0000000000..b199fd83fa
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/restart.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/restore-config.png b/content/docs/platform/v2026.7.10/guides/database-management/images/restore-config.png
new file mode 100644
index 0000000000..58851380d6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/restore-config.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/restore.png b/content/docs/platform/v2026.7.10/guides/database-management/images/restore.png
new file mode 100644
index 0000000000..0953ad3837
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/restore.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/storage-autoscaling.png b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-autoscaling.png
new file mode 100644
index 0000000000..7e1e79adf2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-autoscaling.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-readiness.png b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-readiness.png
new file mode 100644
index 0000000000..1fbdfa0ef0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-readiness.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-standalone.png b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-standalone.png
new file mode 100644
index 0000000000..13da38acb0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-standalone.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-volume.png b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-volume.png
new file mode 100644
index 0000000000..45eca35df0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale-volume.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale.png b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale.png
new file mode 100644
index 0000000000..033b50f03a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/storage-scale.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate-details.png b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate-details.png
new file mode 100644
index 0000000000..1eb0cd55ff
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate-details.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate.png b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate.png
new file mode 100644
index 0000000000..4c849a7e14
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-certificate.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/tls-operation.png b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-operation.png
new file mode 100644
index 0000000000..1bc282c3ca
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/tls-operation.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/tls.png b/content/docs/platform/v2026.7.10/guides/database-management/images/tls.png
new file mode 100644
index 0000000000..fdc3dd0e12
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/tls.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-preview.png b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-preview.png
new file mode 100644
index 0000000000..85aecc3cd9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-preview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-submit.png b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-submit.png
new file mode 100644
index 0000000000..d71979a3d6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version-submit.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/update-version.png b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version.png
new file mode 100644
index 0000000000..1fa1e07bf6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/update-version.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-exporter.png b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-exporter.png
new file mode 100644
index 0000000000..eae523d072
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-exporter.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile.png b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile.png
new file mode 100644
index 0000000000..252ebe6c4d
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile2.png b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile2.png
new file mode 100644
index 0000000000..2bcd0e97f3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-machine-profile2.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-node-selection.png b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-node-selection.png
new file mode 100644
index 0000000000..d5ca844f54
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-node-selection.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-scaling.png b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-scaling.png
new file mode 100644
index 0000000000..bf836e9eeb
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/database-management/images/vertical-scaling.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/instant-backup-restore.md b/content/docs/platform/v2026.7.10/guides/database-management/instant-backup-restore.md
new file mode 100644
index 0000000000..0defb321c6
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/instant-backup-restore.md
@@ -0,0 +1,80 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-instant-backup-restore
+ name: Instant Backup & Restore
+ parent: database-management
+ weight: 45
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Instant Backup & Restore
+
+This guide covers two workflows: using the **Instant Backup** interface to trigger an on-demand backup immediately against an existing backup configuration, and using the **Restore** interface to recover data from a specific backup snapshot.
+
+---
+
+## 1. Getting Started
+
+Select **Instant Backup** or **Restore** from the left sidebar under **Operations**.
+
+- **Instant Backup:** Use this to immediately trigger a backup using an existing backup configuration and session.
+- **Restore:** Use this to recover data from a specific backup snapshot.
+
+---
+
+## 2. Instant Backup
+
+The **Instant Backup** form triggers an on-demand backup by selecting an existing backup configuration and one or more backup sessions.
+
+
+
+### 2.1 - Selecting a Backup Configuration
+
+1. **Backup Configuration:** Select the backup configuration that defines the storage backend and policy for this backup (e.g., `demo/mongodb`). This field is required.
+
+### 2.2 - Selecting Backup Sessions
+
+1. **Backup Sessions:** Select one or more backup sessions to trigger (e.g., `full-backup`). Sessions are defined within the chosen backup configuration. This field is required.
+
+
+
+> **Tip:** You can select multiple backup sessions from the dropdown if your configuration defines more than one session type (e.g., `full-backup`, `incremental-backup`).
+
+1. **Deploy:** Once your selections are made, click **Deploy** to trigger the instant backup immediately.
+
+> **Warning:** The backup starts as soon as you click **Deploy**. There is no Preview step — ensure your selections are correct before proceeding.
+
+---
+
+## 3. Configuring a Restore
+
+The **Restore Configuration** form defines which data to recover and its source.
+
+
+
+1. **Repository:** Select the backup repository that contains your data (e.g., **demo/mongodb**).
+1. **Select Snapshot:** Choose the specific point-in-time backup you wish to restore.
+1. **Additional Parameters:** Provide any specific configuration flags or advanced parameters.
+1. **Preview:** Click **Preview** to review the restore configuration.
+1. **Submit:** Once satisfied, click **Submit** to begin the restore.
+
+> **Note:** Fields marked with a red asterisk are required. If left empty, the system will display an "Error in 1 field" warning.
+
+> **Tip:** On the Preview page, you can switch to **YAML** or **JSON** view to edit the configuration directly before submitting.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Trigger an instant backup | **Instant Backup** → select Backup Configuration → select Backup Sessions → **Deploy** |
+| Restore from a snapshot | **Restore** → choose Repository and Snapshot → **Preview** → **Submit** |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/manage-recommendations.md b/content/docs/platform/v2026.7.10/guides/database-management/manage-recommendations.md
new file mode 100644
index 0000000000..7897d1f67b
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/manage-recommendations.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-recommendation
+ name: Manage Recommendations
+ parent: database-management
+ weight: 80
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Manage Recommendations
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/monitoring.md b/content/docs/platform/v2026.7.10/guides/database-management/monitoring.md
new file mode 100644
index 0000000000..2fdef386e2
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/monitoring.md
@@ -0,0 +1,164 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-monitoring
+ name: Configure Monitoring
+ parent: database-management
+ weight: 75
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Configure Monitoring
+
+This guide explains how to use the **Monitoring** interface to enable and configure Prometheus-based monitoring for your database. You can choose from three monitoring methods and optionally customize the metrics exporter sidecar injected alongside your database.
+
+---
+
+## 1. Getting Started
+
+Select **Monitoring** from the left sidebar. The **Monitoring** form is divided into the following sections:
+
+- **Enable Monitoring** — Master toggle to turn monitoring on or off.
+- **Select a Monitoring Method** — Choose how Prometheus scrapes your database metrics.
+- **Exporter Configuration** — Optionally customize the metrics exporter sidecar container.
+
+
+
+> **Note:** To update the Exporter Resource section, click on **Create OpsRequest** at the top of the page.
+
+---
+
+## 2. Enabling Monitoring
+
+Toggle **Enable Monitoring** to the on position to activate the monitoring configuration for your database. When disabled, all monitoring settings below are inactive.
+
+---
+
+## 3. Selecting a Monitoring Method
+
+Three monitoring methods are available. Select the one that fits your Prometheus setup.
+
+### 3.1 - Prometheus Operator
+
+**Prometheus Operator** injects a metrics exporter sidecar into your database pod and automatically creates a `ServiceMonitor` resource that Prometheus Operator picks up for scraping.
+
+Selecting this method expands the **ServiceMonitor Configuration** panel:
+
+- **Scrapping Interval:** How frequently Prometheus scrapes metrics from the database (e.g., `30s`). Defaults to `30s` if left unchanged.
+
+
+
+> **Tip:** Use **Prometheus Operator** if you already have the Prometheus Operator installed in your cluster — it handles `ServiceMonitor` creation automatically.
+
+### 3.2 - Custom ServiceMonitor
+
+**Custom ServiceMonitor** injects the metrics exporter sidecar but lets you fully customize the `ServiceMonitor` resource rather than using the auto-generated one.
+
+Selecting this method expands an **Endpoints** panel and a **Labels** panel for fine-grained control:
+
+| Field | Description |
+|---|---|
+| **Honor Labels** | Toggle to preserve labels from the scraped target when there are conflicts. |
+| **Interval** | Scraping interval for this endpoint (e.g., `30s`). |
+| **Path** | The HTTP path to scrape metrics from (e.g., `/metrics`). |
+| **Port** | The port name or number to scrape. |
+
+Use **+ Add new** in the **Labels** panel to attach additional key-value labels to the `ServiceMonitor`. You can also add multiple endpoints using **+ Add new** button in **Endpoints** panel.
+
+
+
+> **Note:** `Interval`, `Path` and `Port` fields are mandatory in **Endpoints** section.
+
+### 3.3 - Custom Scrapper
+
+**Custom Scrapper** injects the metrics exporter sidecar and adds Prometheus scraping annotations directly to the stats `Service`, instead of creating a `ServiceMonitor`. Use this method with setups that rely on annotation-based service discovery rather than the Prometheus Operator.
+
+
+
+---
+
+## 4. Configuring the Exporter Sidecar
+
+The **Exporter Configuration** section allows you to customize the metrics exporter sidecar container that is injected into your database pod. Toggle **Customize Exporter Sidecar** to expand the configuration options.
+
+
+
+### 4.1 - Security Context
+
+| Field | Description |
+|---|---|
+| **Run as User** | UID the exporter container runs as (e.g., `999`). |
+| **Run as Group** | GID the exporter container runs as. |
+| **Port** | The port the exporter listens on (e.g., `56790`). |
+
+### 4.2 - Args
+
+Use the **Args** section to pass additional command-line arguments to the exporter binary. Click **+ Add new** to add an argument (e.g., `--compatible-mode`). Use the delete icon next to an entry to remove it.
+
+### 4.3 - Environment Variables
+
+Use the **Environment Variables** section to inject environment variables into the exporter sidecar. Click **+ Add new** to add a variable. Each entry requires:
+
+- **Name** — The environment variable name (required).
+- **Value From** — The source of the value. Three options are available:
+
+**Input** — Provide the value directly in the **Value** field.
+
+**Secret** — Pull the value from a Kubernetes Secret:
+
+
+
+| Field | Description |
+|---|---|
+| **Secret Name** | The name of the Kubernetes Secret to read from (required). |
+| **Secret Key** | The key within the Secret whose value will be used. |
+
+**ConfigMap** — Pull the value from a Kubernetes ConfigMap:
+
+
+
+| Field | Description |
+|---|---|
+| **ConfigMap Name** | The name of the Kubernetes ConfigMap to read from (required). |
+| **ConfigMap Key** | The key within the ConfigMap whose value will be used. |
+
+Use the **Delete** button at the bottom of an environment variable entry to remove it.
+
+---
+
+## 5. Review and Submit
+
+Once all sections are configured, click **Preview** to review the generated manifest before applying it if preview is enabled. Then:
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to apply the monitoring configuration to your database.
+
+> **Note:** After submitting, the monitoring configuration will be applied to your cluster. You can verify the created `ServiceMonitor` or annotations from the **Monitoring** section in the sidebar.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Enable monitoring | Toggle **Enable Monitoring** to on |
+| Use Prometheus Operator | Select **Prometheus Operator** → set Scrapping Interval → **Preview** → **Submit** |
+| Use a custom ServiceMonitor | Select **Custom ServiceMonitor** → configure Endpoints and Labels → **Preview** → **Submit** |
+| Use annotation-based scraping | Select **Custom Scrapper** → **Preview** → **Submit** |
+| Customize the exporter sidecar | Toggle **Customize Exporter Sidecar** → configure Security Context, Args, and Environment Variables |
+| Add an env var from a Secret | **Environment Variables** → **+ Add new** → select **Secret** → provide Secret Name and Key |
+| Add an env var from a ConfigMap | **Environment Variables** → **+ Add new** → select **ConfigMap** → provide ConfigMap Name and Key |
+| Edit manifest before applying | Use the **YAML** / **JSON** toggle on the Preview page |
+| Apply the monitoring config | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/overview.md b/content/docs/platform/v2026.7.10/guides/database-management/overview.md
new file mode 100644
index 0000000000..27b68f0294
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/overview.md
@@ -0,0 +1,36 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-overview
+ name: Overview
+ parent: database-management
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## Overview
+
+**Database Management** is where you operate the databases provisioned through KubeDB Platform after they've been created. It brings the day-2 operational tasks — scaling, backup, restore, version upgrades, reconfiguration, TLS, monitoring, and more — into a single, per-database console so you don't need to reach for `kubectl` or hand-craft custom resources for routine work.
+
+**Target Audience:** This guide is intended for `database administrators` and `operators` responsible for the ongoing health, availability, and data protection of databases running on KubeDB Platform.
+
+
+
+### Key Sections
+
+- **[Database Usage & Insights](../database-usage-insight):** Monitor resource consumption and get at-a-glance health information for a database.
+- **[Scaling Databases](../scaling) / [Scaling Storages](../scaling-storage):** Adjust CPU, memory, replica count, or storage size — manually or through autoscaling policies.
+- **[Configure Backups](../backup), [Instant Backup & Restore](../instant-backup-restore), [Backup Restore](../restore):** Set up scheduled backups, trigger on-demand backups, and restore data when needed.
+- **[Upgrade Database Version](../upgrade-version), [Database Restarts](../restart-database), [Reconfigure Databases](../reconfigure-database):** Perform version upgrades, restarts, and configuration changes with minimal disruption.
+- **[Configure TLS](../tls), [Configure Monitoring](../monitoring), [Expose via Gateway](../expose-via-gateway):** Secure connections, enable Prometheus-based monitoring, and expose databases outside the cluster.
+- **[Manage Recommendations](../manage-recommendations), [Database Security Report](../security-report), [Database Constraint Violations](../contraint-violations):** Review platform-generated recommendations and compliance findings for a database.
+- **[Delete Database](../delete-database):** Safely remove a database and its associated resources.
+
+Each operation is exposed as a dedicated form or panel in the left sidebar of a database's detail page. Under the hood, most actions are translated into Kubernetes `OpsRequest` custom resources, so every change is applied declaratively and can be tracked through its lifecycle — giving you the convenience of a UI with the auditability of GitOps-style operations.
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/recent-backups.md b/content/docs/platform/v2026.7.10/guides/database-management/recent-backups.md
new file mode 100644
index 0000000000..6b9c140019
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/recent-backups.md
@@ -0,0 +1,168 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-recent-backups
+ name: Recent Backups
+ parent: database-management
+ weight: 125
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Recent Backups
+
+A **BackupSession** is a single backup job execution — triggered by a BackupConfiguration or created manually on-demand — that produces a point-in-time snapshot of your database. This guide explains how to view and manage BackupSessions.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **Recent Backups**. This opens the BackupSession list page showing all backup executions across your cluster.
+
+---
+
+## 2. BackupSession List
+
+The list page displays all BackupSessions in your cluster, both scheduled (from BackupConfigurations) and on-demand. Use the **Select Namespace** dropdown to filter by namespace.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupSession resource name. |
+| **Namespace** | The namespace where it is deployed. |
+| **BackupConfiguration** | The BackupConfiguration that created this session (if applicable). |
+| **Invoker Kind** | The resource type that triggered the session (`BackupConfiguration` or manual). |
+| **Invoker Name** | The name of the invoker resource. |
+| **Session** | The session name within the configuration (e.g., `full-backup`). |
+| **Timeout** | Maximum time allowed for the session to complete. |
+| **Phase** | Current status (e.g., `Succeeded`, `Running`, `Failed`). |
+| **Duration** | Elapsed time for the session operation. |
+| **Age** | How long ago the session was created. |
+
+---
+
+## 3. Viewing a BackupSession
+
+Click on any BackupSession name in the list to open its detail page.
+
+### 3.1 - Overview
+
+The detail page opens on the **Overview** tab showing the session's metadata, linked configuration, and all snapshots created:
+
+
+
+**Basic** — Core metadata for the session:
+
+| Field | Description |
+|---|---|
+| **Name** | The BackupSession resource name. |
+| **Namespace** | The namespace it belongs to. |
+| **Labels** | Key-value labels attached to the resource. |
+| **Annotations** | Key-value annotations linking to invoker and configuration. |
+| **UID** | The unique Kubernetes identifier. |
+| **Phase** | Current lifecycle phase (e.g., `Succeeded`, `Running`, `Failed`). |
+| **Timeout** | Maximum time allowed for the session. |
+| **Session** | The session name within the BackupConfiguration. |
+
+**Backup Configuration** — Reference to the BackupConfiguration that created this session:
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupConfiguration resource name. |
+| **Namespace** | Namespace of the BackupConfiguration. |
+| **Invoker Kind** | Always `BackupConfiguration` for scheduled sessions. |
+| **Invoker Name** | Name of the BackupConfiguration invoker. |
+| **Target** | The database being backed up. |
+| **Task** | The backup task executed (e.g., `logical-backup`). |
+| **Repository** | Where the backup snapshots are stored. |
+| **Status** | Current status of the linked configuration. |
+| **Age** | Age of the BackupConfiguration resource. |
+
+**Snapshots** — Individual snapshots created during this session:
+
+| Column | Description |
+|---|---|
+| **Name** | The snapshot resource name. |
+| **Namespace** | Namespace of the snapshot. |
+| **Repository** | The repository storing this snapshot. |
+| **Size** | Size of the snapshot data. |
+| **Phase** | Status of the snapshot (e.g., `Succeeded`, `Failed`). |
+| **Creation Timestamp** | When the snapshot was created. |
+| **Status** | Verification status (`OK` or error message). |
+
+---
+
+## 4. Creating a BackupSession
+
+To manually trigger an on-demand backup (without waiting for a scheduled BackupConfiguration), click **Create New Instance** from the Recent Backups list page.
+
+The **Create BackupSession** form will open with the following fields:
+
+
+
+### 4.1 - Basic Fields
+
+
+
+| Field | Description |
+|---|---|
+| **Namespace** | The Kubernetes namespace where the BackupSession will be created. Required. |
+| **Labels & Annotations** | Optional metadata key-value pairs for organization and filtering. |
+| **Invoker Kind** | The type of resource triggering this session. For manual backups, set to `BackupConfiguration`. Required. |
+| **Invoker Name** | The name of the BackupConfiguration resource to use for this on-demand backup. Required. |
+| **Session** | The session name within the BackupConfiguration (e.g., `full-backup`). Required. |
+| **Timeout** | Maximum time allowed for the backup to complete (e.g., `2h`). Optional; defaults to the BackupConfiguration's timeout. |
+
+> **Note:** The **Invoker Kind** and **Invoker Name** determine which BackupConfiguration's settings (storage backend, addon, tasks) are used for the on-demand backup.
+
+### 4.2 - Labels & Annotations
+
+Use the **Labels & Annotations** section to attach custom metadata:
+
+- Use **+ Add new** under **Labels** to add key-value label pairs.
+- Use **+ Add new** under **Annotations** to add key-value annotation pairs.
+- Use the delete icon on any row to remove an entry.
+
+---
+
+## 5. Preview and Submit
+
+Once all required fields are filled, click **Preview** to review the generated `BackupSession` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to create the BackupSession in your cluster.
+
+> **Note:** After submitting, the backup job will begin immediately using the configuration and settings from the specified BackupConfiguration and Session.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all BackupSessions | **Backups** → **Recent Backups** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View session detail | Click on the BackupSession name in the list |
+| Check snapshot status | Detail page → **Snapshots** table |
+| View linked configuration | Detail page → **Backup Configuration** table |
+| Check session phase | Detail page → **Basic** section → **Phase** field |
+| Open the create form | List page → **Create New Instance** |
+| Add labels or annotations | **Labels & Annotations** → **+ Add new** → enter Key and Value |
+| Select a configuration | **Invoker Name** dropdown → choose a BackupConfiguration |
+| Select a session | **Session** dropdown → choose session from the configuration |
+| Set operation timeout | **Timeout** field → enter duration (e.g., `2h`) |
+| Review before creating | Click **Preview** |
+| Edit manifest directly | Use the **YAML** / **JSON** toggle on the Preview page |
+| Trigger an on-demand backup | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/reconfigure-database.md b/content/docs/platform/v2026.7.10/guides/database-management/reconfigure-database.md
new file mode 100644
index 0000000000..c889952c4e
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/reconfigure-database.md
@@ -0,0 +1,120 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-reconfigure
+ name: Reconfigure Databases
+ parent: database-management
+ weight: 65
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Reconfigure Databases
+
+The **Reconfigure** interface updates your database configuration. You can select a new configuration secret, apply a custom configuration directly, or remove an existing configuration — all through a `MongoDBOpsRequest` that is tracked in your cluster.
+
+---
+
+## 1. Getting Started
+
+Select **Reconfigure** from the **Operations** section in the left sidebar. The **Reconfigure** form provides three operation modes via tabs:
+
+- **New Config Secret** — Select an existing Kubernetes secret or create a new one to use as your database configuration.
+- **Apply Config** — Define custom configuration key-value pairs inline, without needing a pre-existing secret.
+- **Remove** — Remove an existing configuration secret from your database.
+
+
+
+---
+
+## 2. New Config Secret
+
+The **New Config Secret** tab attaches a Kubernetes secret containing your database configuration. Use this when you already have a configuration secret in your cluster or want to create one from scratch.
+
+
+
+1. **Config Secret:** Click the **Config Secret** dropdown to select an existing secret from the list.
+ - Use the **refresh** icon to reload the available secrets if your list is stale.
+ - If no suitable secret exists, click **+ Create a new Secret** to open the secret creation form.
+2. The manifest preview on the right will update to reflect the selected secret. Use the **YAML** / **JSON** toggle to switch the view, and the **Copy** button to copy it to your clipboard.
+
+### Creating a New Config Secret
+
+If you choose **+ Create a new Secret**, a form will expand below the dropdown:
+
+
+
+1. **Secret Name\*:** Enter a name for the new Kubernetes secret (e.g., `secret_name`).
+2. **String Data\*:** Add one or more key-value pairs that define your configuration:
+ - **Key** — The configuration file name (e.g., `mongod.conf`).
+ - **Value** — The configuration content to apply (e.g., `example_value`).
+ - Click **+ Add key** to add additional key-value pairs.
+ - Click **Delete** next to a row to remove an unwanted entry.
+3. Click **Save** to create the secret, or **Cancel** to discard the form.
+
+> **Tip:** For MongoDB, the key is typically `mongod.conf` and the value is the content of the configuration file in YAML format.
+
+---
+
+## 3. Apply Config
+
+The **Apply Config** tab defines custom database configuration parameters directly as key-value pairs, without needing a pre-existing secret. These parameters will overwrite the current settings.
+
+
+
+1. **Configuration:** Click the **Configuration** dropdown to select an existing configuration or leave it unselected to start from scratch.
+2. Enter the configuration parameters you want to apply (e.g., `max_connections`). Each parameter is defined as a key-value pair and will directly overwrite the corresponding existing setting.
+3. The manifest preview on the right reflects the current configuration. Use the **YAML** / **JSON** toggle to inspect it, and the **Copy** button to save it to your clipboard.
+
+> **Note:** Parameters defined here will overwrite existing values in the current configuration. Review the preview carefully before submitting.
+
+---
+
+## 4. Remove
+
+The **Remove** tab detaches an existing configuration secret from your database, reverting it to its default settings.
+
+
+
+1. **Configuration:** Click the **Configuration** dropdown and select the configuration secret you want to remove.
+2. Review the generated manifest in the preview panel on the right to confirm the correct secret is being targeted.
+3. Once satisfied, proceed to submit the operation.
+
+> **Warning:** Removing a configuration secret will cause your database to revert to its default configuration on the next restart. Ensure this is the intended behavior before submitting.
+
+---
+
+## 5. Review and Submit
+
+After configuring any of the three tabs, click **Preview** to review the generated `MongoDBOpsRequest` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch formats.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+Once satisfied, click **Submit** to apply the reconfiguration.
+
+> **Note:** After submitting, a `MongoDBOpsRequest` of type `Reconfigure` will be created in your cluster. You can monitor its progress from the **OpsRequests** section in the sidebar.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Open the Reconfigure form | **Operations** → **Reconfigure** in the left sidebar |
+| Use an existing config secret | **New Config Secret** tab → select from **Config Secret** dropdown |
+| Create a new config secret | **New Config Secret** tab → **+ Create a new Secret** → fill in name and key-value pairs |
+| Apply inline configuration | **Apply Config** tab → select or define parameters in the **Configuration** dropdown |
+| Remove a configuration secret | **Remove** tab → select the secret from the **Configuration** dropdown |
+| Review the generated manifest | Click **Preview** |
+| Edit as YAML/JSON before applying | Use the **YAML** / **JSON** toggle on the Preview page |
+| Apply the reconfiguration | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/repository.md b/content/docs/platform/v2026.7.10/guides/database-management/repository.md
new file mode 100644
index 0000000000..be032dc2d7
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/repository.md
@@ -0,0 +1,220 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-repository
+ name: Backup Repository
+ parent: database-management
+ weight: 135
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Repository
+
+A **Repository** is the logical backup repository that stores individual snapshots of a database within a BackupStorage backend, acting as the bridge between BackupConfigurations and the cloud storage. This guide explains how to view and create Repository resources using the platform console.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **Repository**. This opens the Repository list page showing all backup repositories in your cluster.
+
+---
+
+## 2. Repository List
+
+The list page displays all Repository resources configured across your cluster. Use the **Select Namespace** dropdown to filter by namespace, or click **Create New Instance** to add a new repository.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The Repository resource name. |
+| **Namespace** | The namespace where it is deployed. |
+| **BackupStorage** | The BackupStorage backend this repository uses. |
+| **Target** | The database this repository backs up. |
+| **Size** | Total size of all snapshots in this repository. |
+| **Phase** | Current state of the repository (e.g., `Ready`, `Failed`). |
+| **Age** | How long ago the Repository was created. |
+
+---
+
+## 3. Viewing a Repository
+
+Click on any Repository name in the list to open its detail page.
+
+### 3.1 - Overview
+
+The detail page displays repository metadata and all snapshots stored within it:
+
+
+
+**Basic** — Core metadata for the repository:
+
+| Field | Description |
+|---|---|
+| **Name** | The Repository resource name. |
+| **Namespace** | The namespace it belongs to. |
+| **Labels** | Key-value labels for organization and filtering. |
+| **Annotations** | Key-value annotations including references and management info. |
+| **UID** | The unique Kubernetes identifier. |
+| **Phase** | Current lifecycle phase (e.g., `Ready`). |
+| **Integrity Status** | Whether the repository passed integrity validation (e.g., `OK`). |
+| **Last Integrity Check Time** | Timestamp of the most recent integrity verification. |
+
+**Backup Storage** — Reference to the underlying storage backend:
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupStorage resource name. |
+| **Namespace** | Namespace of the BackupStorage. |
+| **Provider** | The cloud provider (e.g., `s3`, `azure`). |
+| **Size** | Total data stored across all repositories in this backend. |
+| **No. of Connected Repositories** | Number of repositories using this storage. |
+| **Status** | Storage backend status. |
+| **Age** | Age of the BackupStorage resource. |
+
+**Snapshots** — Individual backup snapshots stored in this repository:
+
+
+
+**Backup Configuration** — BackupConfigurations using this repository:
+
+| Column | Description |
+|---|---|
+| **Name** | The BackupConfiguration resource name. |
+| **Namespace** | Namespace of the configuration. |
+| **Schedule** | The cron expression for backups. |
+| **Paused** | Whether backups are currently paused. |
+| **Target** | The database being backed up. |
+| **Session** | The session name within the configuration. |
+| **Status** | Configuration status. |
+| **Age** | Age of the BackupConfiguration resource. |
+
+**Snapshots** — All snapshots (backup snapshots) stored in this repository:
+
+| Column | Description |
+|---|---|
+| **Name** | The Snapshot resource name (e.g., `snapshot-20240115-143022`). |
+| **Namespace** | Namespace of the snapshot. |
+| **Repository** | The repository containing this snapshot. |
+| **Invoker Kind** | Type of resource that created the snapshot (e.g., `BackupSession`). |
+| **Invoker Name** | Name of the invoker resource. |
+| **Backend Repository** | The backend-level repository path. |
+| **Creation Timestamp** | When the snapshot was created. |
+| **Deletion Policy** | What happens when the snapshot is deleted. |
+| **Phase** | Status of the snapshot (e.g., `Ready`, `Failed`). |
+| **Verification Status** | Whether the snapshot data is valid (e.g., `OK`). |
+| **Age** | Age of the Snapshot resource. |
+
+---
+
+## 4. Creating a Repository
+
+To create a new Repository, click **Create New Instance** from the Repository list page. The **Create Repository** form will open.
+
+### 4.1 - Basic Information
+
+The form starts with identity and deletion policy fields:
+
+
+
+| Field | Description |
+|---|---|
+| **Namespace** | The Kubernetes namespace where the Repository will be created. Required. |
+| **Repository Name** | A unique name for this Repository (e.g., `mongodb-backups`). Required. |
+| **Deletion Policy** | Controls what happens when the Repository is deleted. Default: `Delete`. Required. |
+
+### 4.2 - Labels & Annotations
+
+Expand the **Labels & Annotations** section to attach custom metadata:
+
+
+
+- Use **+ Add new** under **Labels** to add key-value label pairs.
+- Use **+ Add new** under **Annotations** to add key-value annotation pairs.
+- Use the delete icon on any row to remove an entry.
+
+### 4.3 - Storage and Encryption Configuration
+
+The **Storage Ref**, **Encryption Secret**, and **Path** sections configure where and how snapshots are stored.
+
+
+
+**Storage Ref** — Reference to the BackupStorage backend:
+
+| Field | Description |
+|---|---|
+| **Namespace** | The namespace of the BackupStorage resource. Required. |
+| **Name** | The name of the BackupStorage resource. Required. |
+
+**Encryption Secret** — Optional Kubernetes Secret containing encryption keys:
+
+| Field | Description |
+|---|---|
+| **Namespace** | The namespace of the encryption Secret. Optional. |
+| **Name** | The name of the Kubernetes Secret holding encryption keys. Optional. |
+
+**Path** — The path prefix within the BackupStorage backend:
+
+| Field | Description |
+|---|---|
+| **Path** | The directory path where snapshots are stored (e.g., `mongodb/demo-db`). Required. |
+
+### 4.4 - App Reference
+
+The **App Ref** section identifies the database resource this repository backs up.
+
+
+
+| Field | Description |
+|---|---|
+| **Api Group** | The API group of the target resource (e.g., `kubedb.com`). Required. |
+| **Kind** | The resource kind of the target database (e.g., `MongoDB`). Required. |
+| **Namespace** | The namespace where the target database resides. Required. |
+| **Name** | The name of the target database instance. Required. |
+
+---
+
+## 5. Preview and Submit
+
+Once all required fields are filled, click **Preview** to review the generated `Repository` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to create the Repository in your cluster.
+
+> **Note:** After submitting, the Repository will be created and validated. Once `Phase` shows `Ready`, BackupConfigurations can reference it for storing snapshots.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all Repositories | **Backups** → **Repository** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View repository detail | Click on the Repository name in the list |
+| Check snapshots stored | Detail page → **Snapshots** table |
+| Check linked configurations | Detail page → **Backup Configuration** table |
+| Check repository status | Detail page → **Basic** section → **Phase** field |
+| Check integrity status | Detail page → **Basic** section → **Integrity Status** field |
+| Open the create form | List page → **Create New Instance** |
+| Add labels or annotations | **Labels & Annotations** → **+ Add new** → enter Key and Value |
+| Reference a BackupStorage | **Storage Ref** → set Namespace and Name |
+| Set encryption for backups | **Encryption Secret** → optionally set Namespace and Name |
+| Set storage path | **Path** field → enter directory path for snapshots |
+| Set the database target | **App Ref** → fill Api Group, Kind, Namespace, and Name |
+| Review before creating | Click **Preview** |
+| Edit manifest directly | Use the **YAML** / **JSON** toggle on the Preview page |
+| Create the repository | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/restart-database.md b/content/docs/platform/v2026.7.10/guides/database-management/restart-database.md
new file mode 100644
index 0000000000..b4d285922c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/restart-database.md
@@ -0,0 +1,78 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-restart
+ name: Database Restarts
+ parent: database-management
+ weight: 60
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Database Restarts
+
+The **Restart** interface performs a rolling restart of your database. The operation is managed through a `MongoDBOpsRequest`, which carries out the restart safely and tracks it in your cluster.
+
+---
+
+## 1. Getting Started
+
+Select **Restart** from the **Operations** section in the left sidebar. The **Restart** form contains one main section:
+
+- **OpsRequest Options** — Configure how the restart operation is executed, including timeout and apply policy.
+
+
+
+---
+
+## 2. Configuring the Restart
+
+Expand the **OpsRequest Options** panel to configure the restart operation.
+
+1. **Timeout:** Specify the maximum time allowed for the restart to complete. Use formats like `30sec`, `1min`, or `2h`. Defaults to `1h` if left unchanged.
+1. **Apply:** Choose when the OpsRequest should be applied:
+ - **IfReady** — The restart will only be applied if the database is in a ready state. This is the recommended option.
+ - **Always** — The OpsRequest will be applied regardless of the database's current state.
+
+
+
+> **Tip:** Use **IfReady** to avoid triggering a restart on an already unhealthy database, which could worsen its state.
+
+1. **Preview:** Once your settings are configured, click **Preview** to review the generated OpsRequest before applying it.
+
+---
+
+## 3. Review and Submit
+
+The Preview page displays the full `MongoDBOpsRequest` manifest that will be applied to your cluster.
+
+
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on this page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to trigger the restart on your database.
+
+> **Note:** After submitting, a `MongoDBOpsRequest` of type `Restart` will be created in your cluster. You can monitor its progress from the **OpsRequests** section in the sidebar.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Open the Restart form | **Operations** → **Restart** in the left sidebar |
+| Set operation timeout | **OpsRequest Options** → enter a value in the **Timeout** field |
+| Control when restart applies | **OpsRequest Options** → select **IfReady** or **Always** under **Apply** |
+| Review the generated manifest | Click **Preview** |
+| Edit as YAML/JSON before applying | Use the **YAML** / **JSON** toggle on the Preview page |
+| Apply the restart | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/restore.md b/content/docs/platform/v2026.7.10/guides/database-management/restore.md
new file mode 100644
index 0000000000..791c647ce1
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/restore.md
@@ -0,0 +1,137 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-restore
+ name: Backup Restore
+ parent: database-management
+ weight: 140
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Restore
+
+This guide explains how to view and create **Restore** resources using the platform console. A Restore represents a database recovery operation that restores data from a previously captured snapshot or backup to a target database instance.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **Restore**. This opens the Restore list page showing all restore operations across your cluster.
+
+---
+
+## 2. Restore List
+
+The list page displays all Restore resources in your cluster, including both scheduled and manually triggered restores. Use the **Select Namespace** dropdown to filter by namespace.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The Restore resource name. |
+| **Namespace** | The namespace where it is deployed. |
+| **Target** | The target database instance being restored to. |
+| **Task** | The restore task type executed (e.g., `logical-restore`). |
+| **Repository** | The repository containing the source snapshot. |
+| **Snapshot** | The snapshot being restored from. |
+| **Total components** | Number of database components being restored. |
+| **Duration** | Elapsed time for the restore operation. |
+| **Phase** | Current status (e.g., `Succeeded`, `Running`, `Failed`). |
+| **Age** | How long ago the Restore was created. |
+
+---
+
+## 3. Creating a Restore
+
+To manually trigger a restore operation, click **Create New Instance** from the Restore list page.
+
+The **Create Restore** form will open with the following fields:
+
+
+
+### 3.1 - Basic Fields
+
+| Field | Description |
+|---|---|
+| **Namespace** | The Kubernetes namespace where the Restore resource will be created. Required. |
+| **Labels & Annotations** | Optional metadata key-value pairs for organization and filtering. |
+| **Restore Name** | A unique name for this Restore operation (e.g., `mongodb-restore-001`). Required. |
+
+### 3.2 - Labels & Annotations
+
+Use the **Labels & Annotations** section to attach custom metadata:
+
+- Use **+ Add new** under **Labels** to add key-value label pairs.
+- Use **+ Add new** under **Annotations** to add key-value annotation pairs.
+- Use the delete icon on any row to remove an entry.
+
+### 3.3 - Source Snapshot Configuration
+
+The **Source Snapshot** section specifies which backup snapshot to restore from.
+
+
+
+| Field | Description |
+|---|---|
+| **Repository Namespace** | The namespace of the Repository resource. Required. |
+| **Repository Name** | The name of the Repository containing the snapshot. Required. |
+| **Snapshot Name** | The name of the Snapshot to restore from. Required. |
+
+### 3.4 - Target Database Configuration
+
+The **Target Database** section identifies where the data will be restored.
+
+
+
+| Field | Description |
+|---|---|
+| **Api Group** | The API group of the target resource (e.g., `kubedb.com`). Required. |
+| **Kind** | The resource kind of the target database (e.g., `MongoDB`). Required. |
+| **Namespace** | The namespace where the target database resides. Required. |
+| **Name** | The name of the target database instance. Required. |
+
+> **Note:** All four Target fields are required. The target database must exist and be in a ready state before the restore begins.
+
+---
+
+## 4. Preview and Submit
+
+Once all required fields are filled, click **Preview** to review the generated `Restore` manifest before applying it.
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to create the Restore and begin the restoration process.
+
+> **Note:** After submitting, the restore operation begins immediately. Monitor the status on the detail page; the target database is updated with the restored data once the operation completes successfully.
+
+---
+
+## 5. Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all Restores | **Backups** → **Restore** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View restore detail | Click on the Restore name in the list |
+| Check restore phase | Detail page → **Basic** section → **Phase** field |
+| Check restore duration | Detail page → **Basic** section → **Duration** field |
+| View source snapshot | Detail page → **Source Snapshot** table |
+| View target database | Detail page → **Target Database** table |
+| Open the create form | List page → **Create New Instance** |
+| Add labels or annotations | **Labels & Annotations** → **+ Add new** → enter Key and Value |
+| Select source snapshot | **Source Snapshot** → set Repository Namespace, Name, and Snapshot Name |
+| Set restore target | **Target Database** → fill Api Group, Kind, Namespace, and Name |
+| Review before creating | Click **Preview** |
+| Edit manifest directly | Use the **YAML** / **JSON** toggle on the Preview page |
+| Start a restore operation | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/scaling-storage.md b/content/docs/platform/v2026.7.10/guides/database-management/scaling-storage.md
new file mode 100644
index 0000000000..ea6423a550
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/scaling-storage.md
@@ -0,0 +1,132 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-scaling-storage
+ name: Scaling Storages
+ parent: database-management
+ weight: 35
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Scaling Storages
+
+Increase the storage capacity of your database. Two approaches are available — a manual **Expand Volume** operation for an immediate one-time resize, and **Storage Autoscaling** which automatically expands storage based on usage thresholds.
+
+---
+
+## 1. Getting Started
+
+Select **Scale Storage** from the **Operations** section in the left sidebar. The **Expand Volume** form contains two method cards at the top:
+
+- **Expand Volume** — Manually increase the database storage volume to a specified size.
+- **Storage Autoscaling** — Automatically scale storage capacity based on configurable usage thresholds.
+
+
+
+---
+
+## 2. Expand Volume
+
+Use this method to perform an immediate, one-time expansion of your database storage to a specific size.
+
+
+
+### 2.1 - Selecting the Mode
+
+The **Mode** dropdown controls how the volume expansion is applied to the database nodes:
+
+- **Online** — Expands storage while the database remains operational, with minimal disruption.
+- **Offline** — The database is briefly stopped during expansion. Use this if your storage provider does not support online resizing.
+
+> **Tip:** Use **Online** mode wherever possible to avoid downtime. Choose **Offline** mode only if your storage class does not support live volume expansion.
+
+### 2.2 - Configuring Standalone Storage
+
+The **Standalone** panel specifies how much storage to allocate:
+
+1. **Current Storage:** Displays the current storage size of the database (read-only, shown for reference).
+1. **New Standalone:** Enter the new target storage size (e.g., `5Gi`). The value must be larger than the current size.
+
+1. **Preview:** Click **Preview** to review the generated OpsRequest before applying it.
+1. **Submit:** Once satisfied, click **Submit** to apply the storage expansion.
+
+> **Note:** After every **Preview**, you must click **Submit** to save your changes.
+
+> **Tip:** On the Preview page, you can also switch to **YAML** or **JSON** view to edit the configuration directly before submitting.
+
+---
+
+## 3. Storage Autoscaling
+
+Use this method to configure automatic storage expansion. The system monitors storage usage and expands capacity automatically when defined thresholds are crossed.
+
+
+
+### 3.1 - Trigger
+
+Toggle **Trigger** to enable or disable the autoscaling policy. When enabled, the autoscaler monitors storage usage and acts according to the rules defined below.
+
+### 3.2 - Expansion Mode (Online/Offline)
+
+Choose how the autoscaler expands storage when a threshold is triggered:
+
+- **Online** — Expands storage while the database remains operational and serves requests.
+- **Offline** — Pauses the database during expansion. Suitable for storage classes that do not support live resizing.
+
+### 3.3 - Standalone Autoscaling Rules
+
+The **Standalone** panel defines the usage threshold and scaling rules for standalone database nodes.
+
+
+
+| Field | Description |
+|---|---|
+| **UsageThreshold (%)** | The storage usage percentage at which autoscaling is triggered. Adjust using the slider or enter a value directly (0–100%). |
+| **Scaling Rules — Initial Storage** | The starting storage size from which scaling steps are calculated (e.g., `1Gi`). |
+| **Scaling Rules — Step** | The percentage by which storage is increased at each scaling step (e.g., `20%` after the threshold is reached for `1Gi` storage). |
+| **UpperBound** | The maximum storage size the autoscaler is allowed to provision. Expansion stops once this limit is reached. |
+
+Use **Add New Rule** to define additional scaling steps for different storage size ranges.
+
+### 3.4 - Readiness Criteria
+
+The **Readiness Criteria** panel defines conditions that must be met before the autoscaler considers the database ready to accept a storage expansion.
+
+
+
+| Field | Description |
+|---|---|
+| **Objects Count Diff Percentage** | The maximum acceptable difference (%) in object counts between primary and secondaries before expansion is allowed. Adjust using the slider (0–100%). |
+| **Oplog Max Lag Seconds** | The maximum acceptable oplog replication lag (in seconds) before expansion is allowed (e.g., `10`). |
+
+> **Note:** These criteria ensure storage is only expanded when the database is in a healthy, consistent state — preventing expansion during replication lag or data inconsistency.
+
+### 3.5 - Timeout and Apply
+
+1. **Timeout:** Specify the maximum time allowed for the autoscaling operation to complete. Use formats like `30sec`, `1min`, or `2h`.
+1. **Apply:** Choose when the OpsRequest should be applied:
+ - **IfReady** — The operation will only be applied if the database is in a ready state. This is the recommended option.
+ - **Always** — The OpsRequest will be applied regardless of the database's current state.
+
+1. **Preview:** Click **Preview** to review the generated autoscaling manifest.
+1. **Submit:** Once satisfied, click **Submit** to activate the autoscaling policy.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Manually expand storage | Select **Expand Volume** → set Mode → enter new size in **Standalone** → **Preview** → **Submit** |
+| Enable storage autoscaling | Select **Storage Autoscaling** → enable **Trigger** → set thresholds and rules → **Preview** → **Submit** |
+| Set expansion mode | **Mode** dropdown → choose **Online** or **Offline** |
+| Define scaling rules | **Standalone** → set UsageThreshold, Scaling Rules, and UpperBound |
+| Set readiness conditions | **Readiness Criteria** → set Objects Count Diff % and Oplog Max Lag Seconds |
+| Edit manifest before applying | Use the **YAML** / **JSON** toggle on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/scaling.md b/content/docs/platform/v2026.7.10/guides/database-management/scaling.md
new file mode 100644
index 0000000000..db981121ca
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/scaling.md
@@ -0,0 +1,178 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-scale
+ name: Scaling Databases
+ parent: database-management
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Scaling Databases
+
+Adjust the computational resources and replica count of your database. Three scaling approaches are available — **Vertical Scaling** for manual CPU and memory adjustments, **Compute Autoscaling** for policy-driven automatic resource management, and **Horizontal Scaling** for changing the number of database replicas.
+
+---
+
+## 1. Getting Started
+
+Select **Scale Vertically** from the **Operations** section in the left sidebar. The scaling form shows two method cards at the top:
+
+- **Vertical Scaling** — Manually adjust CPU and memory allocated to your database nodes.
+- **Compute Autoscaling** — Automatically scale CPU and memory in response to workload demands using predefined policies.
+
+Below the method cards, the form contains sections for **Configure Your Machine Profile**, **Node Selection**, **Exporter**, and **OpsRequest Options**.
+
+
+
+---
+
+## 2. Vertical Scaling
+
+Use this method to manually set the CPU and memory resources for your database nodes.
+
+### 2.1 - Configure Your Machine Profile
+
+The **Configure Your Machine Profile** panel lets you compare your current resource allocation with the proposed new configuration before applying it.
+
+
+
+- **Current Machine Profile** — Displays the existing CPU and memory allocation (read-only, shown for reference).
+- **New Machine Profile** — Select a preset resource profile from the **Resources** dropdown, or choose **custom** to enter CPU and Memory values manually.
+
+
+
+> **Tip:** Use a preset profile for common workload sizes. Switch to **custom** if you need precise control over CPU and memory values beyond the available presets.
+
+### 2.2 - Node Selection
+
+The **Node Selection** panel controls which Kubernetes nodes the database pods are scheduled onto after scaling.
+
+
+
+| Field | Description |
+|---|---|
+| **Node Selection Policy** | Choose a policy to control node targeting — use **Label Selector** to match nodes by key-value labels, or **Taints** to define tolerations that allow pods to run on tainted nodes. |
+| **Topology - Key** | The node label key used to define a topology domain (e.g., `zone`). |
+| **Topology - Value** | The value for the topology key (e.g., `us-central1-a`). Workloads will be deployed in nodes matching this topology. |
+
+### 2.3 - Exporter
+
+The **Exporter** panel sets the CPU and memory resources allocated to the metrics exporter sidecar container.
+
+
+
+| Field | Description |
+|---|---|
+| **CPU** | CPU request for the exporter sidecar (e.g., `100m`). |
+| **Memory** | Memory request for the exporter sidecar (e.g., `256Mi`). |
+
+### 2.4 - OpsRequest Options and Apply
+
+Expand **OpsRequest Options** to configure the timeout and apply policy for the vertical scaling operation.
+
+1. **Timeout:** Maximum time allowed for the operation (e.g., `30sec`, `1min`, `2h`).
+1. **Apply:** Choose **IfReady** to apply only when the database is healthy, or **Always** to apply unconditionally.
+1. **Preview:** Click **Preview** to review the generated OpsRequest manifest.
+1. **Submit:** Once satisfied, click **Submit** to apply the vertical scaling changes.
+
+> **Tip:** On the Preview page, you can switch to **YAML** or **JSON** view to edit the manifest directly before submitting.
+
+---
+
+## 3. Compute Autoscaling
+
+Use this method to automatically adjust CPU and memory based on actual workload demands. The autoscaler monitors resource usage and applies changes according to the policies you configure.
+
+
+
+### 3.1 - Trigger and Pod Lifetime Threshold
+
+1. **Trigger:** Toggle to enable or disable the autoscaling policy. When enabled, the autoscaler actively monitors and adjusts resources.
+1. **Pod Lifetime Threshold:** Specifies the minimum duration a pod must have been running before it is considered for autoscaling decisions. This prevents scaling actions on freshly started pods that have not yet stabilised.
+
+### 3.2 - Standalone Resource Configuration
+
+The **Standalone** panel defines the resource boundaries and scaling sensitivity for standalone database nodes.
+
+
+
+| Field | Description |
+|---|---|
+| **ResourceDiff Percentage** | The minimum percentage difference between the current and recommended resource values required to trigger a scaling action. Adjust using the slider (0-100%). |
+| **Min Allowed - CPU** | The minimum CPU the autoscaler is allowed to set (e.g., `400m`). |
+| **Min Allowed - Memory** | The minimum memory the autoscaler is allowed to set (e.g., `400Mi`). |
+| **Max Allowed - CPU** | The maximum CPU the autoscaler is allowed to set (e.g., `1`). |
+| **Max Allowed - Memory** | The maximum memory the autoscaler is allowed to set (e.g., `2Gi`). |
+| **Controlled Resources** | The resource types the autoscaler manages — typically `cpu` and `memory`. |
+| **Container Controlled Values** | Determines whether the autoscaler adjusts `RequestsAndLimits`, `RequestsOnly`, or `LimitsOnly`. |
+
+### 3.3 - NodeTopology
+
+The **NodeTopology** panel lets you constrain autoscaling decisions to a specific node topology group, ensuring recommendations stay within the resource limits of a particular node class.
+
+
+
+1. **Select NodeTopology:** Choose a node topology from the dropdown to scope the autoscaler's resource recommendations to the capacity of nodes in that topology.
+
+### 3.4 - Readiness Criteria
+
+The **Readiness Criteria** panel defines conditions that must be met before the autoscaler applies a scaling recommendation.
+
+
+
+| Field | Description |
+|---|---|
+| **Objects Count Diff Percentage** | Maximum acceptable difference (%) in object counts between primary and secondaries before scaling is allowed (0-100%, e.g., `50`). |
+| **Oplog Max Lag Seconds** | Maximum acceptable replication lag in seconds before scaling is allowed (e.g., `10`). |
+
+> **Note:** These criteria ensure autoscaling only occurs when the database is in a consistent, healthy state — preventing resource changes during replication lag or data inconsistency.
+
+### 3.5 - OpsRequest Options and Apply
+
+Expand **OpsRequest Options** to configure how the autoscaling OpsRequest is applied.
+
+1. **Timeout:** Maximum time allowed for the autoscaling operation.
+1. **Apply:** Choose **IfReady** (recommended) or **Always**.
+1. **Preview:** Click **Preview** to review the generated autoscaling manifest.
+1. **Submit:** Once satisfied, click **Submit** to activate the autoscaling policy.
+
+---
+
+## 4. Horizontal Scaling
+
+Use **Horizontal Scale** to increase or decrease the number of database replicas. More replicas improve fault tolerance and distribute read load; fewer replicas conserve cluster resources.
+
+
+
+1. **Current Replicas:** Displays the current replica count (read-only, shown for reference).
+1. **New Replicas:** Enter the desired replica count using the spinner or by typing directly. Each replica is an independent copy of your database — for example, setting this to `3` creates three copies for improved availability.
+1. **Preview:** Click **Preview** to review the generated OpsRequest manifest.
+1. **Submit:** Once satisfied, click **Submit** to apply the replica change.
+
+> **Note:** After every **Preview**, you must click **Submit** to save your changes.
+
+> **Tip:** On the Preview page, you can switch to **YAML** or **JSON** view to edit the manifest directly before submitting.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Manually set CPU and memory | Select **Vertical Scaling** → configure Machine Profile → **Preview** → **Submit** |
+| Choose a node preset profile | **Configure Your Machine Profile** → select from **Resources** dropdown |
+| Pin database to specific nodes | **Node Selection** → set Node Selection Policy and Topology |
+| Set exporter sidecar resources | **Exporter** → enter CPU and Memory values |
+| Enable compute autoscaling | Select **Compute Autoscaling** → enable **Trigger** → configure Standalone bounds → **Preview** → **Submit** |
+| Scope autoscaling to a node class | **NodeTopology** → select a topology from the dropdown |
+| Set autoscaling readiness gates | **Readiness Criteria** → set Objects Count Diff % and Oplog Max Lag Seconds |
+| Change the number of replicas | Select **Horizontal Scaling** → set New Replicas → **Preview** → **Submit** |
+| Edit manifest before applying | Use the **YAML** / **JSON** toggle on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/security-report.md b/content/docs/platform/v2026.7.10/guides/database-management/security-report.md
new file mode 100644
index 0000000000..1faafb60b0
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/security-report.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-security
+ name: Database Security Report
+ parent: database-management
+ weight: 90
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Database Security Report
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/snapshot.md b/content/docs/platform/v2026.7.10/guides/database-management/snapshot.md
new file mode 100644
index 0000000000..18476a61bb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/snapshot.md
@@ -0,0 +1,129 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-snapshot
+ name: Backup Snapshot
+ parent: database-management
+ weight: 145
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Snapshot
+
+A **Snapshot** is a point-in-time backup of a database stored in a backup repository. This guide explains how to view and manage Snapshot resources using the platform console.
+
+---
+
+## 1. Getting Started
+
+Navigate to **Backups** in the left sidebar and select **Snapshot**. This opens the Snapshot list page showing all database snapshots across your cluster.
+
+---
+
+## 2. Snapshot List
+
+The list page displays all Snapshot resources in your cluster. Use the **Select Namespace** dropdown to filter by namespace, or view detailed information about stored snapshots.
+
+
+
+| Column | Description |
+|---|---|
+| **Name** | The Snapshot resource name (e.g., `snapshot-20240115-143022`). |
+| **Namespace** | The namespace where it is deployed. |
+| **Repository** | The Repository resource storing this snapshot. |
+| **Invoker Kind** | The type of resource that created the snapshot (e.g., `BackupSession`). |
+| **Invoker Name** | The name of the invoker resource. |
+| **Backend Repository** | The backend-level repository path where snapshot data is stored. |
+| **Creation Timestamp** | The exact date and time when the snapshot was created. |
+| **Deletion Policy** | Controls what happens when the snapshot is deleted (e.g., `Delete`, `Retain`). |
+| **Phase** | Current status of the snapshot (e.g., `Ready`, `Failed`). |
+| **Verification Status** | Whether the snapshot data passed integrity verification (e.g., `OK`). |
+| **Age** | How long ago the Snapshot was created. |
+
+---
+
+## 3. Viewing a Snapshot
+
+Click on any Snapshot name in the list to open its detail page.
+
+### 3.1 - Overview
+
+The detail page shows snapshot metadata, verification status, and the repository it belongs to:
+
+
+
+**Basic** — Core metadata for the snapshot:
+
+| Field | Description |
+|---|---|
+| **Name** | The Snapshot resource name. |
+| **Namespace** | The namespace it belongs to. |
+| **Labels** | Key-value labels attached to the resource. |
+| **Annotations** | Key-value annotations including references to invoker and repository. |
+| **UID** | The unique Kubernetes identifier. |
+| **Phase** | Current lifecycle phase (e.g., `Ready`, `Failed`, `Pending`). |
+| **Verification Status** | Integrity verification result (e.g., `OK` or error message). |
+| **Deletion Policy** | What happens when this snapshot is deleted. |
+
+**Repository** — The backup repository storing this snapshot:
+
+| Column | Description |
+|---|---|
+| **Name** | The Repository resource name. |
+| **Namespace** | Namespace of the repository. |
+| **BackupStorage** | The storage backend used by this repository. |
+| **Size** | Total size of all snapshots in this repository. |
+| **Target** | The database this repository backs up. |
+| **Status** | Current state of the repository. |
+| **Age** | Age of the Repository resource. |
+
+**Invoker** — The resource that triggered this snapshot's creation:
+
+| Column | Description |
+|---|---|
+| **Kind** | The type of invoker (e.g., `BackupSession`). |
+| **Name** | Name of the invoker resource. |
+| **Namespace** | Namespace of the invoker. |
+
+---
+
+## 4. Deleting a Snapshot
+
+To delete a snapshot, click on the snapshot name to open its detail page, then locate the delete action.
+
+### 4.1 - Delete Confirmation
+
+When initiating a delete operation, a confirmation dialog appears:
+
+
+
+| Field | Description |
+|---|---|
+| **Deletion Policy** | Displays the configured deletion policy (e.g., `Delete` to remove from storage, `Retain` to keep data). |
+| **Confirm** | Check the confirmation checkbox to acknowledge deletion. |
+
+> **Warning:** Deleting a snapshot is permanent if the deletion policy is `Delete`. Ensure you have other backups of your data before proceeding.
+
+---
+
+## 5. Quick Reference
+
+| Action | How to do it |
+|---|---|
+| View all Snapshots | **Backups** → **Snapshot** |
+| Filter by namespace | Use the **Select Namespace** dropdown on the list page |
+| View snapshot detail | Click on the Snapshot name in the list |
+| Check snapshot phase | Detail page → **Basic** section → **Phase** field |
+| Check verification status | Detail page → **Basic** section → **Verification Status** field |
+| View repository information | Detail page → **Repository** table |
+| Check deletion policy | Detail page → **Basic** section → **Deletion Policy** field |
+| View snapshot invoker | Detail page → **Invoker** table |
+| Delete a snapshot | Click snapshot name → locate delete action → confirm deletion |
+| Review deletion policy | Detail page before deleting to confirm snapshot data handling |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/tls.md b/content/docs/platform/v2026.7.10/guides/database-management/tls.md
new file mode 100644
index 0000000000..16a468a2f3
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/tls.md
@@ -0,0 +1,128 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-tls
+ name: Configure TLS
+ parent: database-management
+ weight: 70
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Configure TLS
+
+Manage TLS settings for your database. You can update TLS certificates, rotate existing ones, or remove TLS entirely — all managed through a `OpsRequest` applied to your cluster.
+
+---
+
+## 1. Getting Started
+
+Select **TLS Configure** from the **Operations** section in the left sidebar. The **TLS Configure** form is divided into the following sections:
+
+- **TLS Operation** — Choose the type of TLS action to perform.
+- **Remove TLS** — Toggle to strip TLS from the database entirely.
+- **Rotate Certificates** — Toggle to force certificate rotation.
+- **Issuer Reference** — Specify the cert-manager issuer to use.
+- **Certificates** — Define one or more certificates with custom subject and SAN details.
+- **OpsRequest Options** — Configure timeout and apply policy for the operation.
+
+
+
+---
+
+## 2. Configuring the TLS Operation
+
+### 2.1 - Select a TLS Operation
+
+Under **TLS Operation**, choose the action you want to perform:
+
+- **Update** — Add or update TLS configuration on the database. Use this to enable TLS for the first time or to change existing certificate settings.
+- **Rotate** — Force a rotation of the current TLS certificates without changing the configuration.
+- **Remove** — Strip TLS from the database entirely.
+
+The **Remove TLS** and **Rotate Certificates** toggles act as quick shortcuts for those specific operations without changing any other settings.
+
+### 2.2 - Configure the Issuer Reference
+
+Expand the **Issuer Reference** panel to specify which cert-manager issuer should sign the certificates.
+
+1. **API Group:** The cert-manager API group (e.g., Defaults to `cert-manager.io`).
+1. **Kind:** Select the type of issuer — typically `ClusterIssuer` for cluster-wide issuers or `Issuer` for namespace-scoped ones.
+1. **Name:** Enter the name of the issuer (e.g., `ace-incluster`).
+
+
+
+> **Note:** The Issuer Reference is required when the **Update** operation is selected. Ensure the issuer exists in your cluster before proceeding.
+
+---
+
+## 3. Adding Certificates
+
+The **Certificates** section allows you to define one or more certificates that will be managed by the TLS configuration. Click **+ Add new** to add a certificate entry.
+
+
+
+Each certificate entry contains the following fields:
+
+| Field | Description |
+|---|---|
+| **Alias** | The role of the certificate. Required — select from the dropdown. |
+| **Secret Name** | The Kubernetes secret where the certificate will be stored. |
+| **Duration** | The validity period of the certificate (e.g., `8760h` for one year). |
+| **Renew Before** | How long before expiry the certificate should be renewed (e.g., `360h`). |
+| **Organizations** | One or more organization names for the certificate subject. |
+| **Countries** | One or more country codes for the certificate subject. |
+| **Organizational Units** | Organizational unit names for the certificate subject. |
+| **Provinces** | Province or state names for the certificate subject. |
+| **DNS Names** | Subject Alternative Names (SANs) as DNS hostnames. |
+| **IP Addresses** | Subject Alternative Names (SANs) as IP addresses. |
+
+Use the **+ Add new** button next to each subject field to add multiple values. Use the **Delete** button at the bottom of an entry to remove a certificate.
+
+### 3.1 - Selecting the Certificate Alias
+
+The **Alias** dropdown identifies the role of the certificate within the database. The available options are:
+
+- **server** — The certificate used by the database server for incoming TLS connections.
+- **client** — The certificate used by clients connecting to the database.
+- **metrics-exporter** — The certificate used by the metrics exporter for secure scraping.
+
+
+
+> **Note:** Fields marked with a red asterisk are required. The filed with `+ Add new` button validates entries on input — leaving an added row empty will show an "Item cannot be empty" warning. Also You can add multiple instance of them.
+
+---
+
+## 4. Review and Submit
+
+Once all sections are configured, click **Preview** to review the generated `OpsRequest` manifest before applying it if preview is enabled. Then:
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on the Preview page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to apply the TLS configuration to your database.
+
+> **Note:** After submitting, a `OpsRequest` of type `ReconfigureTLS` will be created in your cluster.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Enable or update TLS | Select **Update** under **TLS Operation** → configure Issuer Reference → add Certificates → **Preview** → **Submit** |
+| Rotate existing certificates | Select **Rotate** under **TLS Operation** (or toggle **Rotate Certificates**) → **Preview** → **Submit** |
+| Remove TLS from the database | Select **Remove** under **TLS Operation** (or toggle **Remove TLS**) → **Preview** → **Submit** |
+| Add a certificate | **Certificates** → **+ Add new** → fill in Alias, fields, and SANs |
+| Remove a certificate entry | Click **Delete** at the bottom of the certificate entry |
+| Edit manifest before applying | Use the **YAML** / **JSON** toggle on the Preview page |
+| Apply the TLS change | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/database-management/upgrade-version.md b/content/docs/platform/v2026.7.10/guides/database-management/upgrade-version.md
new file mode 100644
index 0000000000..a6f0e5dbb9
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/database-management/upgrade-version.md
@@ -0,0 +1,90 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: database-management-update
+ name: Upgrade Database Version
+ parent: database-management
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Upgrade Database Version
+
+Upgrade your database to a newer version. The operation is managed through a `MongoDBOpsRequest`, which handles the upgrade process and tracks its status in your cluster.
+
+---
+
+## 1. Getting Started
+
+Select **Update Version** from the **Operations** section in the left sidebar. The **Update Version** form has two main sections:
+
+- **Version** — Select the target version you want to upgrade your database to.
+- **OpsRequest Options** — Configure advanced settings such as timeout and apply policy.
+
+
+
+---
+
+## 2. Configuring the Update
+
+### 2.1 - Selecting the Target Version
+
+The **Version** section shows your database's **Current** version and a **Target Version** dropdown.
+
+1. **Target Version:** Select the desired version from the dropdown. The current version is displayed on the left for reference.
+
+> **Note:** Only versions compatible with your current database engine are listed in the dropdown.
+
+### 2.2 - Setting OpsRequest Options
+
+Expand the **OpsRequest Options** panel to configure how the upgrade operation is executed.
+
+1. **Timeout:** Specify the maximum time allowed for the upgrade to complete. Use formats like `30sec`, `1min`, or `2h`. Defaults to `2h` if left unchanged.
+1. **Apply:** Choose when the OpsRequest should be applied:
+ - **IfReady** — The upgrade will only be applied if the database is in a ready state. This is the recommended option.
+ - **Always** — The OpsRequest will be applied regardless of the database's current state.
+
+
+
+> **Tip:** Use **IfReady** unless you have a specific reason to force the operation, as it prevents upgrades from running on an unhealthy database.
+
+1. **Preview:** Once your settings are configured, click **Preview** to review the generated OpsRequest before applying it.
+
+---
+
+## 3. Review and Submit
+
+The Preview page displays the full `MongoDBOpsRequest` manifest that will be applied to your cluster.
+
+
+
+- The manifest is shown in **YAML** view by default. Use the **JSON** button to switch to JSON format if preferred.
+- Use the **Copy** button to copy the manifest to your clipboard.
+- Click **Previous** to go back and adjust your settings if needed.
+
+> **Tip:** You can directly edit the YAML or JSON on this page before submitting. This is useful for making precise adjustments beyond what the form fields expose.
+
+1. **Submit:** Once satisfied, click **Submit** to apply the version upgrade to your database.
+
+> **Note:** After submitting, a `MongoDBOpsRequest` of type `UpdateVersion` will be created in your cluster. You can monitor its progress from the **OpsRequests** section in the sidebar.
+
+---
+
+## Quick Reference
+
+| Action | How to do it |
+|---|---|
+| Open the Update Version form | **Operations** → **Update Version** in the left sidebar |
+| Select the target version | **Version** → choose from the **Target Version** dropdown |
+| Set operation timeout | **OpsRequest Options** → enter a value in the **Timeout** field |
+| Control when upgrade applies | **OpsRequest Options** → select **IfReady** or **Always** under **Apply** |
+| Review the generated manifest | Click **Preview** |
+| Edit as YAML/JSON before applying | Use the **YAML** / **JSON** toggle on the Preview page |
+| Apply the upgrade | Click **Submit** on the Preview page |
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/_index.md b/content/docs/platform/v2026.7.10/guides/get-started/_index.md
new file mode 100644
index 0000000000..d600b6a3dd
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start
+ name: Get Started
+ parent: guides
+ description: Basic information and instructions for first-time users of KubeDB Platform
+ icon: https://img.icons8.com/00994A/ios/50/rocket--v1.png
+ popular: true
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/add-cluster.md b/content/docs/platform/v2026.7.10/guides/get-started/add-cluster.md
new file mode 100644
index 0000000000..fdc65b8459
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/add-cluster.md
@@ -0,0 +1,32 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start-cluster
+ name: Add a Kubernetes Cluster
+ parent: guide-start
+ weight: 30
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Add a Kubernetes Cluster
+
+With your credentials in place, it's time to connect your Kubernetes cluster to the Platform Console. This step allows KubeDB Platform to seamlessly manage and provide insights into your cluster.
+
+Follow these steps to import your Kubernetes cluster:
+
+1. Visit the [Platform Console](https://console.appscode.com/).
+2. Click on the `Add Cluster` button.
+3. Choose your cluster type and provider.
+4. Select the credentials you added in the previous step.
+5. Follow the provider-specific instructions to complete the import process.
+
+For detailed instructions and troubleshooting tips, refer to our comprehensive [Import Kubernetes Cluster Guide](../../cluster-management/add-cluster/overview.md).
+
+Once your cluster is imported, you can explore its details and capabilities directly from the Platform Console.
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/add-credential.md b/content/docs/platform/v2026.7.10/guides/get-started/add-credential.md
new file mode 100644
index 0000000000..0efa1ba53d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/add-credential.md
@@ -0,0 +1,30 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start-credential
+ name: Add a Credential
+ parent: guide-start
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Add Credential
+
+Now that you have successfully registered and logged in to the Platform Console, let's take the next step in setting up your environment. The first crucial task is to add credentials for your Kubernetes clusters. This ensures a secure connection and allows KubeDB Platform to seamlessly manage your clusters.
+
+Follow these steps to add your credentials:
+
+1. Navigate to the [Add Credential Page](https://appscode.com/id/{user}/user/settings/credentials/create).
+2. Choose your `Credential Type` or authentication method and enter the required details.
+3. Click on the `Done` button to securely save your credentials.
+
+For detailed documentation refer to [Credential Management](../../account-management/kubernetes/credentials.md)
+
+After adding your credentials, you'll be ready to import your Kubernetes cluster and unlock a world of possibilities within the platform.
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/architecture.md b/content/docs/platform/v2026.7.10/guides/get-started/architecture.md
new file mode 100644
index 0000000000..d1283c8c89
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/architecture.md
@@ -0,0 +1,40 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-architecture
+ name: Architecture
+ parent: guide-start
+ weight: 12
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Architecture
+Let's first discuss some basic terminologies, those will be repeated many times throughout the whole docs. The below picture will help in describing the terminologies:
+
+
+
+### KubeDB Platform
+KubeDB Platform is the central management cluster where we will deploy all the ui-components. Namely the `backend server(ace-platform-api)`, `kubedb-ui`, `cluster-ui`, `billing-ui`, `platform-ui`, `grafana-ui`, ingresses etc. This will be mainly used by the administrators & devops engineers.
+As this is the central point of management, we call it `Management cluster`. As all the UI-components installed in this, we sometimes call `UI cluster`.
+
+We also have native-integration of [OCM hub-spoke model](https://open-cluster-management.io/docs/concepts/architecture/). This is by-default enabled. This integration enables the cluster-manager to easily do similar changes(for example: installing a feature) centrally.
+KubeDB Platform is used as the hub of OCM mode. Thats why we call this `Hub cluster` too.
+
+The KubeDB Platform cluster can be a single-node k3s cluster for staging or development. Or a full-fledged multi-node cluster for prod.
+
+The installer page on the `selfhost-ui` on appscode.com provides instructions for quickly setting up a K3s cluster to get started immediately.
+
+### DBaaS
+DBaaS cluster is the main cluster for database users. This can be of two main type: spoke cluster, general imported cluster.
+While importing, if someone make it a spoke, then cluster-manager-spoke features will be installed by the Hub cluster.
+If you don't want to manage it from the hub, we can just import it as a general cluster. In that case, that auto-sync from hub will not happen.
+
+
+Both KubeDB Platform & DBaaS clusters can be of any vendors like AWS, Azure, Google Cloud etc. It can be an on-prem cluster too.
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/enable-features.md b/content/docs/platform/v2026.7.10/guides/get-started/enable-features.md
new file mode 100644
index 0000000000..85697d5c23
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/enable-features.md
@@ -0,0 +1,30 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start-features
+ name: Enable Features
+ parent: guide-start
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Enable Features
+
+
+Once your cluster is imported, you can enable or disable KubeDB Platform features based on your requirements.
+
+1. Navigate to your Cluster Overview page, selecting your imported cluster in the [Platform Console](https://console.appscode.com/).
+2. In the "Feature Sets" section, you'll find a list of FeatureSets associated with your cluster, along with their current status.
+3. Click on any FeatureSet in the list to go to the FeatureSet Management page.
+4. On the FeatureSet Management page, you can enable or disable specific features according to your needs.
+
+Managing features in the Platform Console is a straightforward process that allows you to tailor your Platform Console to meet your cluster's requirements. Feel free to explore the features and capabilities offered by KubeDB Platform.
+
+For more advanced configurations and detailed documentation, check out the [Features in Details](../../cluster-management/cluster-features.md).
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/images/architecture.png b/content/docs/platform/v2026.7.10/guides/get-started/images/architecture.png
new file mode 100644
index 0000000000..b8e74bbf16
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/get-started/images/architecture.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/images/selfhost.png b/content/docs/platform/v2026.7.10/guides/get-started/images/selfhost.png
new file mode 100644
index 0000000000..d8dfbddda9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/get-started/images/selfhost.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/manage-databases.md b/content/docs/platform/v2026.7.10/guides/get-started/manage-databases.md
new file mode 100644
index 0000000000..20049dcd76
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/manage-databases.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start-databases
+ name: Manage Databases
+ parent: guide-start
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Manage Databases
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/register-login.md b/content/docs/platform/v2026.7.10/guides/get-started/register-login.md
new file mode 100644
index 0000000000..5e99ddb159
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/register-login.md
@@ -0,0 +1,56 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-start-register
+ name: Get Started (Register & Login)
+ parent: guide-start
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Get Started with KubeDB Platform
+
+## Register and Login
+
+Welcome to KubeDB Platform! This is a new version Follow these quick steps to get started:
+
+### 1. Register for an Account
+
+1. Navigate to the [KubeDB Platform Registration Page](https://accounts.appscode.com/user/sign_up).
+2. Provide the following information:
+ - Username
+ - Email
+ - Password
+ - Complete any required captcha challenge.
+3. Click on the `Register Account` button.
+4. Optionally, you can sign up quickly using your existing accounts:
+ - Sign up with `Google`
+ - Sign up with `GitHub`
+
+
+### 2. Verify Your Email
+
+After registration, check your email inbox for a verification email from KubeDB Platform.
+
+1. Open the verification email.
+2. Click on the verification link to confirm your account.
+
+### 3. Log In to KubeDB Platform
+
+1. Once your account is verified, go to the [KubeDB Platform Login Page](https://accounts.appscode.com/user/login).
+2. Enter your registered `Username` or `Email Address` and `Password`.
+3. Click on the `Sign In` button.
+4. Optionally, you can sign in using your connected External accounts.
+
+### 4. Explore Platform Console
+
+You are now logged in to the Platform Console! Take a moment to explore the features and navigate through the dashboard.
+
+Congratulations! You have successfully registered, verified your email, and logged in to KubeDB Platform. If you encounter any issues or have questions, refer to the [KubeDB Platform Documentation](https://appscode.com/docs/) for detailed guidance.
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/guides/get-started/requirements.md b/content/docs/platform/v2026.7.10/guides/get-started/requirements.md
new file mode 100644
index 0000000000..2f0795eb2c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/get-started/requirements.md
@@ -0,0 +1,63 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: guide-ace-requirements
+ name: KubeDB Platform Requirements
+ parent: guide-start
+ weight: 14
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Requirements to deploy KubeDB Platform
+We will discuss the resources requirements. networking requirements & best practices for deploying your first KubeDB Platform & DBaaS cluster. It is highly recommended to read the [architecture](https://appscode.com/docs/en/guides/get-started/architecture.html) doc first before continuing.
+
+## Requirements for KubeDB Platform Cluster
+
+### 1. Resources
+**Minimum**: Single node with 4 cpu, 16 GB ram, 100 GB disk attached. A k3s cluster will be deployed on that VM. And then the ui-components will be installed.
+
+**HA Deployment**: 3 worker nodes, each with 4 cpu, 16 GB ram, PVC support (3000 iops, 200 GB disk across multiple pvcs) and LB service support. The Kubernetes control plane should be also HA.
+
+### 2. Networking
+If you want to run in an air-gapped environments (disconnected from internet), You will have to make sure that all images are cached locally. You can use Harbor or jfrog artifactory for this.
+
+We maintain a complete list of the [charts](https://github.com/appscode-cloud/installer/blob/master/catalog/copy-images.sh) & [images](https://github.com/appscode-cloud/installer/blob/master/catalog/ace.yaml).
+
+#### Connectivity
+These are the required connectivities to everything work correctly:
+- `DB pod to pod` communication using dns (k8s service discovery)
+- `operator to db-pods` for health checks
+- `db pods to kube-apiserver` for failover handling (update pod label when it becomes a primary replica)
+- `operator to kube-apiserver` for CRUD
+- `Backup pods to db pods` over network and on node level so they can access the shared disks.
+- `Backup pods to object storage` (s3 , minio etc.)
+
+#### Port Requirements
+1. 80 - Auto redirects to https
+2. 443 - Https Ingress port
+3. 4222 - NATS.io port
+4. 4224 - s3-proxy service port
+
+Here is a sample video on how you can setup KubeDB Platform:
+
+
+## Requirements for DBaaS Cluster
+### 1. Resources
+Depends on how many and what size of databases users are running.
+
+Minimum: Kubernetes cluster with 3 worker nodes, each with 8- 16GB ram, PVC support (3000 iops, 200 GB disk across multiple pvcs) and LB service support.
+
+Note that, The largest node must be able to fit the largest DB Pod(in terms of CPU, memory).
+
+### 2. Networking
+Literally all the Networking requirements described for KubeDB Platform are also applicable here, except the `Port Requiements` part.
+Only one additional requirement here is that the DBaaS cluster should be accessible from the management/KubeDB Platform cluster.
+
+You now have an overall idea on the requirements. So, [Login](https://appscode.com/docs/en/guides/get-started/register-login.html) into your account & get going with our [installer](https://appscode.com/selfhost/). Happy KubeDB Platform!
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/_index.md b/content/docs/platform/v2026.7.10/guides/integrations/_index.md
new file mode 100644
index 0000000000..2c045d3cf6
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/integrations/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: integrations
+ name: Integrations
+ parent: guides
+ description: Integrate KubeDB Platform into your Kubernetes platform
+ icon: https://img.icons8.com/?size=100&id=80695&format=png&color=000000
+ popular: true
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/ace-url.png b/content/docs/platform/v2026.7.10/guides/integrations/images/ace-url.png
new file mode 100644
index 0000000000..ca6ee30ba7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/ace-url.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/acer-proxy-installer.png b/content/docs/platform/v2026.7.10/guides/integrations/images/acer-proxy-installer.png
new file mode 100644
index 0000000000..e4789ee366
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/acer-proxy-installer.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/create-repo.png b/content/docs/platform/v2026.7.10/guides/integrations/images/create-repo.png
new file mode 100644
index 0000000000..8b2c8d11ac
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/create-repo.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/extensions.png b/content/docs/platform/v2026.7.10/guides/integrations/images/extensions.png
new file mode 100644
index 0000000000..edf0ab5bf4
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/extensions.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/install-ext.png b/content/docs/platform/v2026.7.10/guides/integrations/images/install-ext.png
new file mode 100644
index 0000000000..dcf06603a2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/install-ext.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-list.png b/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-list.png
new file mode 100644
index 0000000000..9daeff28e6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-list.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-rancher.png b/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-rancher.png
new file mode 100644
index 0000000000..3dd8c4bcdc
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/kubedb-in-rancher.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/manage-repo.png b/content/docs/platform/v2026.7.10/guides/integrations/images/manage-repo.png
new file mode 100644
index 0000000000..6a4a130bf6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/manage-repo.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/organization-create.png b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-create.png
new file mode 100644
index 0000000000..798a03294a
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-create.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-generate-installer.png b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-generate-installer.png
new file mode 100644
index 0000000000..cea3c80e1c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-generate-installer.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-sync-users.png b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-sync-users.png
new file mode 100644
index 0000000000..2bd1ceecf8
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings-sync-users.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings.png b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings.png
new file mode 100644
index 0000000000..856b641630
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/organization-settings.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/repo-info.png b/content/docs/platform/v2026.7.10/guides/integrations/images/repo-info.png
new file mode 100644
index 0000000000..b1bcb5579f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/repo-info.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/images/three-dot.png b/content/docs/platform/v2026.7.10/guides/integrations/images/three-dot.png
new file mode 100644
index 0000000000..9cd489e6c3
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/integrations/images/three-dot.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/integrations/rancher-extension.md b/content/docs/platform/v2026.7.10/guides/integrations/rancher-extension.md
new file mode 100644
index 0000000000..a19380603c
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/integrations/rancher-extension.md
@@ -0,0 +1,118 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: rancher-extension
+ name: KubeDB Rancher Extension
+ parent: integrations
+ weight: 50
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# KubeDB Rancher Extension
+
+The **KubeDB Rancher Extension** enables you to manage **KubeDB** resources directly from the Rancher UI. With this extension, you can **deploy**, **monitor**, and **manage** production-grade databases in your Kubernetes clusters without leaving the Rancher dashboard.
+
+This guide walks you through deploying and configuring the KubeDB Rancher Extension so you can start managing your databases seamlessly within Rancher.
+
+---
+
+## 1. Prerequisites
+
+Before proceeding, make sure you have:
+
+- A Rancher setup with access to the **Local** cluster.
+- An account on [appscode.com](https://appscode.com/).
+- The [KubeDB Platform](https://appscode.com/docs/en/selfhost-setup/) deployed on your Rancher cluster.
+
+---
+
+## 2. Deploying the KubeDB Rancher Extension
+
+### Step 1 – Deploy KubeDB Platform
+1. Create an account at [appscode.com](https://appscode.com/).
+2. Follow the [self-hosting KubeDB Platform guide](https://appscode.com/docs/en/selfhost-setup/) to deploy KubeDB Platform on your Rancher cluster.
+ You can also watch this video tutorial for step-by-step instructions: [Self-Hosting KubeDB Platform Video Guide](https://www.youtube.com/watch?v=1diG8qq73f4&list=PLoiT1Gv2KR1iqWFGkCozbLqYe31QMsQcX&index=2)
+
+
+---
+
+### Step 2 – Create a Rancher-Type Organization in KubeDB Platform
+1. Visit your KubeDB Platform URL and log in with your **admin account**. 
+2. Navigate to **Organizations** and create a new organization with the type set to **Rancher**.
+3. Provide a valid **Sync Token**.
+ > The Sync Token is used to synchronize Rancher users into the KubeDB Platform.
+
+
+
+---
+
+### Step 3 – Sync Rancher Users
+1. Go to **Organization Settings → Rancher Extension**. 
+2. Click **Sync User** to import Rancher users into KubeDB Platform. 
+
+---
+
+### Step 4 – Install the Rancher Proxy in Local Cluster
+1. Click **Generate Rancher Proxy Installer** to generate the Rancher proxy installation command. 
+2. First, Click the **Download** button to download the CA. We are passing it by --set-file in helm command. Then Copy the generated Helm installation command. 
+3. Open a terminal connected to your Rancher **Local** cluster.
+4. Run the copied Helm command to install the Rancher proxy.
+
+---
+
+### Step 5 – Verify Installation
+Run the following command in your **Local** cluster to confirm that the Rancher proxy pod is running:
+
+```bash
+kubectl get pods -n kubeops | grep acerproxy
+
+acerproxy-6cdcd88df-nts6w 1/1 Running 0 6d
+```
+
+## 3. Install KubeDB Extension from Rancher UI
+
+Follow these steps to install the KubeDB extension in Rancher:
+
+#### 1. Open Extensions Page
+ In your Rancher UI, click on **Extensions**.
+ 
+
+#### 2. Open Managed Repositories
+ In the list of available extensions, click the **three dots** menu (as shown below) and select **Managed Repositories**.
+ 
+ 
+
+#### 3. Create a New Repository
+ Click the **Create** button.
+ 
+
+#### 4. Enter Repository Details
+ Fill in the required fields as shown in the screenshot, then click **Create**.
+ 
+
+#### 5. Locate the KubeDB Extension
+ After adding the repository, you will see **KubeDB** in the list of available extensions.
+ 
+
+#### 6. Install the Extension
+ Click **Install** to add the KubeDB extension to Rancher.
+ 
+
+#### 7. Access KubeDB in a Cluster
+ Open any cluster in Rancher — you will now see a **KubeDB** dropdown in the sidebar.
+ From here, you can deploy, monitor, and manage your databases directly from the Rancher UI.
+ 
+
+---
+
+
+✅ Installation Complete!
+You can now deploy and manage your databases directly from the KubeDB menu in your cluster.
+NB: Import your Rancher cluster into the KubeDB Platform UI under the Rancher organization you created earlier before using the Rancher extension, or it won’t work.
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/_index.md b/content/docs/platform/v2026.7.10/guides/license-management/_index.md
new file mode 100644
index 0000000000..38067f76a5
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/license-management/_index.md
@@ -0,0 +1,20 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: license-management
+ name: License Management
+ parent: guides
+ description: License Management for AppsCode's products
+ icon: https://img.icons8.com/?size=100&id=80695&format=png&color=000000
+ popular: true
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/contract.md b/content/docs/platform/v2026.7.10/guides/license-management/contract.md
new file mode 100644
index 0000000000..5b0992399d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/license-management/contract.md
@@ -0,0 +1,95 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: license-management-contract
+ name: Contract
+ parent: license-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## Contract
+
+A contract is basically a digital agreement of the licensing relationship between AppsCode and its customers. Each contract represents a formal agreement for the use of
+specific KubeDB Platform products, such as KubeDB or platform-enterprise, with defined validity periods and feature sets.
+
+The contract management system within the Billing Console provides comprehensive tools for creating, modifying, and monitoring contracts. Administrators can specify
+product details, validity periods, and associated features, ensuring that customers have access to the appropriate resources for their needs.
+
+
+
+Key information typically contained within a contract includes:
+
+- **Product:** The specific KubeDB Platform product or bundle covered by the contract (e.g., `kubedb-enterprise`, `platform-enterprise` etc.).
+- **Org/User:** The organization or user account to which the contract is assigned.
+- **Status:** The current state of the contract (e.g., active, expired, revoked), managed by AppsCode administrators.
+- **Start Date:** The date from which the contract, and thus the license, becomes valid (not_before).
+- **End Date:** The date on which the contract, and the license, expires (not_after).
+
+
+Contracts ensure that product usage is aligned with the purchased entitlements, providing clarity for both the customer and AppsCode.
+
+### Managing Cluster Associations with Contracts
+
+For KubeDB Platform products to operate with a valid license on a Kubernetes cluster, customers must explicitly associate that cluster with one or more active contracts
+made available to them in the Billing Console. This capability is a key `self-service` feature, allowing customers to dynamically manage which of their Kubernetes
+environments are licensed under a given contract, within the overall terms and capacity of that agreement.
+
+### Adding Clusters to Contracts
+
+To add a Kubernetes cluster to a contract and enable license validation within that environment, customers need to perform the following steps:
+
+1. **Navigate to Contract Details:** Access the specific contract detail page within the Billing Console.
+2. **Initiate Cluster Addition:** Locate the `Cluster` section on the contract page and `click on` the `Add Cluster` button. 
+3. **Provide Cluster Information:** A dialog box will appear, prompting for cluster details. Customers need to provide:
+ - **Cluster ID:** The unique identifier of the Kubernetes cluster. This can be retrieved using the command: `kubectl get ns kube-system -o=jsonpath='{.metadata.uid}`.
+ - **Cluster Name (optional):** A descriptive name, such as `dev-us-east-1` or `prod-us-east-2`, for easy identification within the console. Customers can enter multiple `ClusterID` and `ClusterName` pairs, each on a new line, separated by a space. 
+4. **Preview and Confirm:** After entering the details, selecting `Preview` will display the entered cluster(s) for verification. Once confirmed, click `Add` to finalize the association. 
+5. **View Associated Clusters:** Upon successful addition, the cluster(s) will appear in the `Cluster` section of the contract's detail page, listed by their `Cluster ID` and `Name`. 
+
+### Removing Clusters from Contracts
+
+To remove a cluster's authorization to use licensed products under a specific contract:
+
+1. **Navigate to Contract Details:** Access the specific contract detail page within the Billing Console.
+2. **Locate and Remove:** In the `Cluster` section, find the cluster in the associated clusters list that needs to be removed.
+3. **Confirm Removal:** Select the `Remove` option (often represented by a `trash` icon) next to the cluster and confirm the action when prompted. 
+
+After removal, the cluster will no longer be authorized to use the licensed products associated with that contract. Any installed KubeDB Platform products on that cluster may revert to their community or limited functionality, depending on their licensing model.
+
+**Audit Trail:** The Billing Console maintains an audit trail of changes to cluster associations, logging which user performed the action and when. This feature is vital for tracking, security, and troubleshooting. 
+
+### Cluster Contract Relationship
+
+The AppsCode License Management System supports flexible relationships between clusters and contracts:
+1. **Many-to-One:** Multiple clusters can be associated with a single contract.
+2. **One-to-Many:** A single cluster can be associated with multiple contracts for different products.
+3. **Many-to-Many:** Multiple clusters can be associated with multiple contracts.
+
+This flexibility allows organizations to structure their licensing in a way that aligns with their operational needs and deployment architecture.
+
+### Contract Operational Modes: Online vs. Offline
+
+The operational mode of a contract (`online` or `offline`) is a critical setting configured by AppsCode administrators, usually at the time of contract creation or during major revisions, based on the customer's operational environment and requirements. This choice significantly impacts license validation:
+
+**Online Mode:**
+- This is the standard mode for contracts where clusters have internet access.
+- The `license-proxyserver` in the customer's cluster regularly connects to AppsCode's central licensing servers (e.g., `AppsCode.com`s) for license `validation` and `renewal`.
+- Licenses are typically issued for shorter durations (e.g., `7 days` by default) and are automatically rotated.
+- This mode facilitates dynamic license management and ensures continuous validation against the current contract status.
+
+**Offline Mode:**
+- Designed for environments without `internet access` (air-gapped) or with highly restricted outbound connectivity.
+- When a contract is configured as `offline` by AppsCode's administrators, the `license-proxyserver` installer generated by the customer will include licenses covering the contract's entire duration.
+- These licenses do not require periodic online `validation` or `rotation`.
+- Any changes to the contract term requires the customer to generate & deploy a new offline License Proxy Server installer.
+- In offline contract you can download the license file from the contract details page. 
+
+> The Billing Console enables customers to generate the appropriate License Proxy Server installer based on the mode of their contract.
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-button-rectangle.png b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-button-rectangle.png
new file mode 100644
index 0000000000..2eb5febc0f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-button-rectangle.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-confirm.png b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-confirm.png
new file mode 100644
index 0000000000..3f9fb1d069
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-confirm.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-information.png b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-information.png
new file mode 100644
index 0000000000..ca1107f729
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-information.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-preview.png b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-preview.png
new file mode 100644
index 0000000000..82ed64eb14
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/add-cluster-preview.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/audits.png b/content/docs/platform/v2026.7.10/guides/license-management/images/audits.png
new file mode 100644
index 0000000000..efd844e0f6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/audits.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/cluster-delete.png b/content/docs/platform/v2026.7.10/guides/license-management/images/cluster-delete.png
new file mode 100644
index 0000000000..853cc58066
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/cluster-delete.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/contract-details.png b/content/docs/platform/v2026.7.10/guides/license-management/images/contract-details.png
new file mode 100644
index 0000000000..2779ad86a9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/contract-details.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/download-offline-license.png b/content/docs/platform/v2026.7.10/guides/license-management/images/download-offline-license.png
new file mode 100644
index 0000000000..2fa0993044
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/download-offline-license.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/home-billing-console.png b/content/docs/platform/v2026.7.10/guides/license-management/images/home-billing-console.png
new file mode 100644
index 0000000000..2e0303f60f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/home-billing-console.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-apiservice-yaml-status.png b/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-apiservice-yaml-status.png
new file mode 100644
index 0000000000..fab9dc6ad2
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-apiservice-yaml-status.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-server-svc-check.png b/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-server-svc-check.png
new file mode 100644
index 0000000000..a04e1e388b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/license-proxy-server-svc-check.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-free-contract.png b/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-free-contract.png
new file mode 100644
index 0000000000..bab6329714
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-free-contract.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-paid-contract.png b/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-paid-contract.png
new file mode 100644
index 0000000000..fb0ce6e573
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/license-status-paid-contract.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-cluster-selection.png b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-cluster-selection.png
new file mode 100644
index 0000000000..79088606dd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-cluster-selection.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-contract-selection.png b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-contract-selection.png
new file mode 100644
index 0000000000..beb6138b17
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-contract-selection.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-scripts.png b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-scripts.png
new file mode 100644
index 0000000000..369d8ca3b4
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/offline-installer-scripts.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer-scripts.png b/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer-scripts.png
new file mode 100644
index 0000000000..e0919ec04b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer-scripts.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer.png b/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer.png
new file mode 100644
index 0000000000..1959f9154b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/guides/license-management/images/online-installer.png differ
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/license-proxyserver.md b/content/docs/platform/v2026.7.10/guides/license-management/license-proxyserver.md
new file mode 100644
index 0000000000..8fba64d6fb
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/license-management/license-proxyserver.md
@@ -0,0 +1,126 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: license-management-license-proxyserver
+ name: License Proxy Server
+ parent: license-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## The License Proxy Server
+
+The `license-proxyserver` is a critical component of the AppsCode License Management System, deployed within customer Kubernetes clusters to validate and apply licenses to KubeDB Platform products.
+### 1. Purpose and Architecture
+
+The primary purpose of the `license-proxyserver` is to:
+
+- **Serve Licenses:** Provide valid license tokens to KubeDB Platform products (e.g., KubeDB, KubeStash, KubeVault operators and provisioners) running within the same Kubernetes cluster.
+- **Validate Licenses:**
+ - In **Online Mode**, The `license-proxyserver` connects periodically to the Billing Server to validate and rotate licenses. This mode provides automatic license updates and ensures that changes to contract status are reflected promptly in the customer environment.
+ - In **Offline Mode**, The `license-proxyserver` operates without connecting to the Billing Server. Instead, it uses `pre-generated` licenses embedded in the installer until the embedded licenses are expired. This mode is ideal for `air-gapped` environments or scenarios where external connections are restricted.
+- **Centralized License Management within the Cluster:** Simplifies license management for multiple KubeDB Platform products within a single cluster by acting as a common point for license queries.
+
+#### Architectural Flow
+
+1. **KubeDB Platform Product Request:** When a KubeDB Platform product (e.g., KubeDB operator) starts or performs a licensed operation, it requests a license from the License Proxy Server running in its cluster.
+2. **License Proxy Server Response:**
+ - **Online Mode:** If the `license-proxyserver` has a valid, cached license, it provides it immediately. If the license is nearing its expiration, has already expired, or is otherwise invalid, the `license-proxyserver` attempts to contact AppsCode `Billing Backend` to fetch a new license. This new license is based on the active contracts associated with that specific cluster.
+ - **Offline Mode:** The `license-proxyserver` primarily uses the pre-generated licenses embedded in its installer. It operates without connecting to the Billing Console for routine validation. However, if all embedded licenses are found to be expired or have been revoked, the `license-proxyserver` will, as a fallback, attempt to fetch new licenses from the AppsCode billing backend. This means that even in air-gapped environments, a temporary or controlled outbound connection might be necessary for license renewal or recovery if the embedded licenses become invalid over time.
+ > Each mode offers distinct advantages and is suitable for different operational contexts.
+3. **Product Operation:** A valid license allows the product to operate with its full feature set, while an invalid or absent license may lead to reduced functionality or prevent the product from operating.
+
+> This architecture ensures that licensing checks are performed locally within the cluster, minimizing latency and dependency on external services for routine operations, especially after initial license acquisition.
+
+### 2. Generating the License Proxy Server Installer
+
+The AppsCode Billing Console provides a dedicated interface for generating the necessary deployment manifests (typically a `Helm chart` or `YAML files`) for the `license-proxyserver`. The generation process requires the administrator to choose the operational mode for which the installer is being created: `online` or `offline`.
+This choice dictates how the installer is packaged and how the deployed `license-proxyserver` will behave regarding license validation.
+
+#### Online Mode Deployment
+
+Online mode is suitable for clusters with reliable internet connectivity, allowing for dynamic license management and regular validation.
+
+##### Installer Generation for Online Mode
+
+When the `Online` option is selected for installer generation in the Billing Console, the system prepares a standard `license-proxyserver` installer. 
+This installer is typically provided as a `Helm` commands or `YAML files`, as seen in the `Scripts` pop-up. 
+
+The generated installer configures the license-proxyserver to communicate with the AppsCode licensing backend. The cluster where this `license-proxyserver` is installed must be `associated with one or more online contracts` in the Billing Console for successful license acquisition.
+Key configurations embedded in the installer include:
+
+- The base URL for the AppsCode licensing backend, explicitly set (e.g., `-set platform.baseURL=https://AppsCode.com`). This ensures the `license-proxyserver` knows where to connect for license validation and updates.
+- A platform token (e.g., `-set platform.token=dc823391fc8d6d9ca10f47a1ed07************`). This token is used by the `license-proxyserver` to authenticate itself with the AppsCode backend and identify which licenses it is eligible for.
+
+
+#### License Acquisition and Rotation
+
+- **Initial Acquisition:** Upon startup, the `license-proxyserver` contacts AppsCode.com, identifies its cluster (based on its configuration or a token provided during installation), and requests licenses for the products covered by any active online contracts associated with that cluster.
+- **Periodic Rotation:** Licenses issued in online mode have a finite, relatively short lifespan (e.g., the default is 7 days). Before a license expires, the `license-proxyserver` automatically attempts to renew it by contacting the AppsCode backend. This ensures continuous legal operation of the products.
+
+**Benefits:**
+- **Up-to-date Compliance:** Ensures the cluster is always checked against the latest contract status. If a contract is terminated or expires, new licenses will not be issued, maintaining compliance.
+- **Dynamic Updates:** Allows AppsCode to propagate updates to license terms or features if necessary, which would be picked up during a renewal cycle.
+
+> **Requirements:**
+> - The `license-proxyserver` must have consistent outbound `HTTPS` (typically port 443) connectivity to the AppsCode licensing endpoints.
+> - `Firewall` rules in the customer's environment must `permit` this communication.
+
+#### Offline Mode Deployment
+
+Offline mode caters to environments that are air-gapped or have stringent restrictions on external network communications. It is ideal for sectors like finance, government, or critical infrastructure, where Kubernetes cluster environments are completely offline.
+
+#### Enabling Offline Contracts
+The prerequisite for generating an offline `license-proxyserver` installer is that the relevant contract(s) in the AppsCode Billing Console must be explicitly
+designated as `offline` type by an [AppsCode administrators](https://AppsCode.com/contact/). This tells the system that licenses derived from this contract should be `long-lived` and not require `online renewal`.
+
+#### Installer Generation for Offline Mode
+Generating an installer for offline mode is a multi-step process, designed to embed specific licenses for a chosen cluster:
+
+1. **Select Offline Mode:** In the `License Proxy Server` section of the Billing Console, choose the `Offline` option.
+2. **Identify Target Cluster:** The console will then display a list of clusters that are associated with at least one `offline` contract, along with their `Name`, `UID`, and the `count` of Associated Contracts (e.g., `doc-preview` with `6 Contracts`, `prod-us-east-1` with `2 Contracts`). The administrator must select the specific cluster for which the offline installer is to be generated.  Click on the `Associated Contracts` button next to the desired cluster to embed the licenses against the selected contracts.
+3. **Select Contracts for Embedding:** Once a cluster is chosen, the `Billing Console` shows all offline contracts currently linked to the selected cluster, allowing the administrator to choose which of these contracts' licenses should be embedded into the `license-proxyserver` installer. This provides granular control, especially if a cluster is associated with multiple offline contracts for different products or terms.  After making the selections, click the `Generate License Proxy Installer` button within this pop-up to proceed.
+4. **Generate the Installer Bundle:** Upon clicking `Generate License Proxy Installer`, the Billing Console compiles the installer package. This package includes the `license-proxyserver` deployment manifests (typically `Helm` commands or `YAML` files) and the actual license data for the selected contracts. This license data is encoded (e.g., as a `Base64` string) and embedded directly within the configuration, as indicated by parameters like `-set encodeLicenses` in the generated scripts.  The generated installer is then ready for download and deployment to the target cluster.
+
+#### License Characteristics in Offline Mode
+
+- **Full Duration Licenses:** Offline licenses are valid for the entire contract term, e.g., June 1, 2025, to May 31, 2026.
+- **No Periodic Online Rotation (Initially):** Self-contained licenses don’t need AppsCode server contact until expiration.
+- **Fallback to Online Mode:** Expired offline licenses trigger the license-proxyserver to fetch new licenses online, mimicking online mode.
+- **Self-Contained Deployment:** Licensing data is embedded in the license-proxyserver, allowing disconnected operation while licenses are valid.
+- **Updates Require New Installer:** Contract extensions or expired licenses require a new installer from the Billing Console, which must be upgraded or reinstalled to maintain or restore offline functionality.
+
+
+### 3. Verifying Product License Status
+
+After the `license-proxyserver` is installed and KubeDB Platform products are deployed, administrators can verify the license status directly within the Kubernetes cluster using `kubectl`.
+
+#### Using kubectl for License Verification
+
+The `license-proxyserver` component functions as an `extended API server` within the Kubernetes cluster. This means it extends the Kubernetes API by exposing new endpoints, including those to check license status. Administrators can query these endpoints directly using the following command.
+
+```bash
+kubectl get licensestatus
+```
+
+This command will list the status of licenses being consumed by various KubeDB Platform products within the cluster.
+
+##### Interpreting licensestatus Output
+
+The output of `kubectl get licensestatus` provides several key pieces of information for each licensed component:
+
+- **ID:** A unique identifier for this specific license.
+- **PRODUCT:** The name of the KubeDB Platform product that this license status pertains to (e.g., `kubedb`, `kubestash`, `platform` etc.).
+- **REQUESTER:** The specific `component` or `service account` within the cluster that requested and is utilizing this license. This helps pinpoint which part of a KubeDB Platform product installation is covered by this license entry (e.g., `system:serviceaccount:kubedb:kubedb-kubedb-provisioner`).
+- **CONTRACT:** This field indicates the identifier of the AppsCode contract which is utilized providing the license. There are two scenarios on how this field is populated:
+ - If a cluster is not explicitly associated with any contract in the Billing Console, AppsCode automatically provides a `1-month (30-day)` free trial license. In such cases, the `CONTRACT` column in the `licensestatus` output will display `0`. This temporary license is particularly helpful for customers during initial testing and evaluation periods. Each cluster is eligible for this free trial only once. 
+ - Otherwise, if a cluster is associated with a specific contract, this column will display the actual `CONTRACT ID` from the Billing Console, allowing administrators to `cross-reference` the license with the detailed contract terms. 
+- **VALID:** This field indicates the remaining validity period for the current license instance.
+- **ROTATES:** This field indicates when the license is next scheduled for rotation or renewal.
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/overview.md b/content/docs/platform/v2026.7.10/guides/license-management/overview.md
new file mode 100644
index 0000000000..e4c8b8920f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/license-management/overview.md
@@ -0,0 +1,42 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: license-management-overview
+ name: Overview
+ parent: license-management
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## Overview
+
+The AppsCode License Management System simplifies managing product licenses for Kubernetes deployments. It offers a centralized billing console for efficient license administration and secure validation, supporting both online and offline modes to suit various needs.
+
+This guide explores the Billing Console, covering its key components, contract management, license-proxyserver deployment, and troubleshooting tips for common issues. By the end, you’ll know how to effectively manage licenses with this tool.
+
+**Target Audience:** This guide is intended for `administrators` and `personnel` responsible for managing KubeDB Platform product licenses.
+
+## AppsCode Billing Console
+
+A centralized web-based platform serving as the primary interface for licensing operations in the AppsCode ecosystem. Hosted on [AppsCode Billing Console](https://appscode.com/billing), this self-managed system allows customers to manage `contracts` by associating clusters, generating `license-proxyserver` installers and tracking clusters for which licenses are generated.
+
+While AppsCode administrators are responsible for the core lifecycle of contracts—including their `creation`, `modification`, `revocation`, and `extension`—customers retain the ability to perform specific operations pertinent to the licensing lifecycle. This includes `associating` and `disassociating` their Kubernetes clusters with allocated contracts, generating `installers` for the `license-proxyserver` through the console, and track the `clusters` for which licenses have been issued.
+
+
+
+### Key Components
+
+- **Contracts:** Digital agreements, typically established by [AppsCode administrators](https://appscode.com/contact/) within the Billing Console, that define the terms of AppsCode's product (e.g., KubeDB Platform, KubeDB, KubeStash, KubeVault etc.) usage. This includes the specific AppsCode products which can be licensed, the duration of the contract, applicable features, and the clusters authorized to use these licenses. Contracts ensure that usage aligns with legal and financial terms, providing a foundation for all subsequent actions in the console. Contracts can be configured for either online or offline license validation.
+
+- **Licensed cluster:** The `Licensed Cluster` section within the AppsCode Billing Console offers a comprehensive overview and detailed management capabilities for Kubernetes clusters that have been issued KubeDB Platform product licenses. This component is pivotal for administrators to monitor the cluster(s) `licences` and `events` of licensed products across their infrastructure.
+
+- **License Proxy Server:** A lightweight in-cluster component that validates licenses, either by connecting to AppsCode servers (online) or using preloaded licenses (offline). The console generates customized installers for deployment. Depending on the contract type (`online` or `offline`), it either periodically refreshes and validates licenses with AppsCode's central licensing servers or uses static preloaded licenses embedded during deployment for the full contract duration.
+
+These components work together to provide a seamless experience for license administrators, allowing them to efficiently manage the entire licensing `lifecycle` from a single interface. For instance, AppsCode's administrator creates a contract for KubeDB, and associates the contract to the target customer. Then from the customer panel, the customer can add a cluster to it, generates a customized installer for the `license-proxyserver`, deploys it to the cluster, and then monitors usage—all within the Billing Console. This integrated workflow eliminates the need for disparate tools or manual processes, saving time and reducing errors.
diff --git a/content/docs/platform/v2026.7.10/guides/license-management/troubleshoots.md b/content/docs/platform/v2026.7.10/guides/license-management/troubleshoots.md
new file mode 100644
index 0000000000..b6ae551f6b
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/guides/license-management/troubleshoots.md
@@ -0,0 +1,159 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: license-management-license-proxyserver-troubleshoot
+ name: Troubleshoot
+ parent: license-management
+ weight: 40
+menu_name: docsplatform_v2026.7.10
+section_menu_id: guides
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+## Troubleshooting License Proxy Server Issues
+The troubleshooting process involves verifying its API registration, service health, connectivity to the AppsCode backend etc.
+
+#### 1. Verify `APIService` Configuration
+First, confirm that the APIService for the license-proxyserver is correctly registered and available within the Kubernetes API aggregation layer.
+
+```bash
+kubectl get apiservice v1alpha1.proxyserver.licenses.AppsCode.com -o yaml
+```
+
+**Interpretation:**
+Examine the `status.conditions` section of the output. Look for a condition with `type: Available` and `status: "True"`. 
+This indicates that the Kubernetes API aggregation layer is properly configured to route requests to the `license-proxyserver`. If this condition is `"False"` or `missing`, it suggests an issue with the APIService registration or the `license-proxyserver's` readiness.
+
+
+#### 2. Check `API Resources`
+Next, verify that the custom API resources exposed by the `license-proxyserver` are recognized by the Kubernetes API.
+
+```bash
+kubectl api-resources | grep -i license
+```
+**Expected Output:**
+You should see entries similar to these, confirming the presence of license-related API resources:
+```text
+NAME SHORTNAMES APIVERSION NAMESPACED KIND
+addofflinelicenses offline.licenses.AppsCode.com/v1alpha1 false AddOfflineLicense
+offlinelicenses offline.licenses.AppsCode.com/v1alpha1 true OfflineLicense
+licenserequests proxyserver.licenses.AppsCode.com/v1alpha1 false LicenseRequest
+licensestatuses proxyserver.licenses.AppsCode.com/v1alpha1 false LicenseStatus
+```
+
+This output confirms that the Kubernetes API recognizes the custom resources provided by the `license-proxyserver`.
+
+You can also inspect the raw `API definition` exposed by the `license-proxyserver` to confirm its capabilities:
+```bash
+kubectl get --raw=/apis/proxyserver.licenses.AppsCode.com/v1alpha1/ | jq
+```
+**Expected Output (abbreviated):**
+```json
+{
+ "kind": "APIResourceList",
+ "apiVersion": "v1",
+ "groupVersion": "proxyserver.licenses.AppsCode.com/v1alpha1",
+ "resources": [
+ {
+ "name": "licenserequests",
+ "singularName": "licenserequest",
+ "namespaced": false,
+ "group": "proxyserver.licenses.AppsCode.com",
+ "version": "v1alpha1",
+ "kind": "LicenseRequest",
+ "verbs": [
+ "create"
+ ]
+ },
+ {
+ "name": "licensestatuses",
+ "singularName": "licensestatus",
+ "namespaced": false,
+ "group": "proxyserver.licenses.AppsCode.com",
+ "version": "v1alpha1",
+ "kind": "LicenseStatus",
+ "verbs": [
+ "get",
+ "list"
+ ]
+ }
+ ]
+}
+```
+
+**Interpretation:**
+This output confirms that the `license-proxyserver` API server is exposing `licenserequests` (with create verb) and `licensestatuses` (with `get`, `list` verbs) resources.
+This is crucial for the `kubectl get licensestatus` command to function correctly.
+
+#### 3. Verify `license-proxyserver` Service and Endpoints
+If the API registration appears correct, the next step is to ensure that the Kubernetes Service and Endpoints for the `license-proxyserver` are functioning properly, allowing internal cluster
+traffic to reach the pod.
+
+```bash
+kubectl get svc -n kubeops license-proxyserver
+kubectl get endpoints -n kubeops license-proxyserver
+```
+
+**Interpretation:**
+- For the `kubectl get svc -n kubeops license-proxyserver` command, verify that the service `TYPE is ClusterIP` and has a `cluster-IP`.
+```text
+NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
+license-proxyserver ClusterIP 10.43.189.38 443/TCP,8080/TCP 19h
+```
+
+- For the `kubectl get endpoints -n kubeops license-proxyserver` command, ensure that the endpoints list contains the IP address(es) of the `license-proxyserver` pod(s).
+ The IP(s) listed here should match the IP(s) of the actual `license-proxyserver` pod(s) in the `kubeops` namespace. If the endpoints are missing or incorrect,
+ it indicates a problem with the `service selector` or the `license-proxyserver` pod itself (e.g., pod not `running`, `crashlooping`).
+
+
+#### 4. Test AppsCode Backend Connectivity (for Online Mode/Fallback)
+If the `in-cluster` components of the `license-proxyserver` appear healthy, and you are operating in `Online Mode` or troubleshooting an `Offline Mode fallback` scenario, verify that the cluster can reach the AppsCode licensing backend.
+
+1. **Check Network Connectivity:** Ensure that the cluster has internet access and can reach the AppsCode licensing backend. This may involve checking `firewall rules`, `network policies`, or `proxy settings`.
+2. **Get Cluster ID:** Retrieve the unique identifier for your Kubernetes cluster:
+ ```bash
+ kubectl get ns kube-system -o=jsonpath='{.metadata.uid}'
+ ```
+ Copy the output, which will be your ``.
+3. **Get Platform Token:** Extract the platform token used by the `license-proxyserver` for authentication with the AppsCode backend:
+ ```bash
+ kubectl get secrets -n kubeops ace-licenseserver-cred -o=jsonpath='{.data.license-proxyserver\.yaml}' | base64 -d
+ ```
+ From the output, locate the token field under `platform:` (e.g., `token: ac9b9eeec181fb09j73ab1604bd0180a4361e859`). Copy this value as your ``.
+4. **Get License Using CURL:** Perform a `curl` request to the AppsCode Backend: Use `curl` from within a pod in your cluster (or a machine with network access to the cluster's outbound internet) to simulate a
+ license request to the AppsCode backend. Replace `` and `` with the values obtained in the previous steps. The features can be get from the Contract details page in AppsCode Billing Console
+ ```bash
+ curl -k -X 'POST' -d '{"cluster":"","features":["kubedb-enterprise"]}' \
+ -H 'Authorization: Bearer ' \
+ -H 'Content-Type: application/json' \
+ -H 'User-Agent: license-proxyserver/v0.0.22' \
+ 'https://api.AppsCode.com/api/v1/license/issue' --compressed
+```
+ **Expected curl Response Analysis:**
+ A successful response indicates that your cluster can communicate with the AppsCode backend and that the authentication token is valid. The response will contain `contract` and `license` sections:
+ ```json
+ {
+ "contract": {
+ "id": "1187",
+ "startTimestamp": "2025-05-21T00:00:00Z",
+ "expiryTimestamp": "2025-06-21T23:59:59Z"
+ },
+ "license": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUlaRENDQjB5Z0F3SUJBZ0lJUFY2NEVSL0o1aE13RFFZSktvWklodmNOQVFFTEJRQXdKVEVXTUJRR0ExVUUKQ2hNTlFYQndjME52WkdVZ1NXNWpMakVMTUFrR0ExVUVBeE1DWTJFd0hoY05NalV3TlRJek1EUTFNVE0xV2hjTgpNalV3TlRNd01EUTFNVE0xV2pDQ0JRUXhEekFOQmdOVkJBWVRCbXQxWW1Wa1lqRVRNQkVHQTFVRUNCTUtaVzUwClpYSndjbWx6WlRHQ0ErZ3dnZ1BrQmdOVkJBY01nZ1BiVW1WemRISnBZM1JwYjI1elBYc05DaUFnSWtSeWRXbGsKSWpvZ2V3MEtJQ0FnSUNKMlpYSnphVzl1UTI5dWMzUnlZV2x1ZENJNklDSXFJZzBLSUNCOUxBMEtJQ0FpUld4aApjM1JwWTNObFlYSmphQ0k2SUhzTkNpQWdJQ0FpZG1WeWMybHZia052Ym5OMGNtRnBiblFpT2lBaUtpSXNEUW9nCklDQWdJbVJwYzNSeWFXSjFkR2x2Ym5NaU9pQmJEUW9nSUNBZ0lDQWlUM0JsYmxObFlYSmphQ0lOQ2lBZ0lDQmQKRFFvZ0lIMHNEUW9nSUNKR1pYSnlaWFJFUWlJNklIc05DaUFnSUNBaWRtVnljMmx2YmtOdmJuTjBjbUZwYm5RaQpPaUFpS2lJTkNpQWdmU3dOQ2lBZ0lrdGhabXRoSWpvZ2V3MEtJQ0FnSUNKMlpYSnphVzl1UTI5dWMzUnlZV2x1CmRDSTZJQ0lxSWcwS0lDQjlMQTBLSUNBaVRXRnlhV0ZFUWlJNklIc05DaUFnSUNBaWRtVnljMmx2YmtOdmJuTjAKY21GcGJuUWlPaUFpS2lJTkNpQWdmU3dOQ2lBZ0lrMWxiV05oWTJobFpDSTZJSHNOQ2lBZ0lDQWlkbVZ5YzJsdgpia052Ym5OMGNtRnBiblFpT2lBaUtpSU5DaUFnZlN3TkNpQWdJazE1VTFGTUlqb2dldzBLSUNBZ0lDSjJaWEp6CmFXOXVRMjl1YzNSeVlXbHVkQ0k2SUNJcUlnMEtJQ0I5TEEwS0lDQWlVR1Z5WTI5dVlWaDBjbUZFUWlJNklIc04KQ2lBZ0lDQWlkbVZ5YzJsdmJrTnZibk4wY21GcGJuUWlPaUFpS2lJTkNpQWdmU3dOQ2lBZ0lsQm5RbTkxYm1ObApjaUk2SUhzTkNpQWdJQ0FpZG1WeWMybHZia052Ym5OMGNtRnBiblFpT2lBaUtpSU5DaUFnZlN3TkNpQWdJbEJuCmNHOXZiQ0k2SUhzTkNpQWdJQ0FpZG1WeWMybHZia052Ym5OMGNtRnBiblFpT2lBaUtpSU5DaUFnZlN3TkNpQWcKSWxCdmMzUm5jbVZ6SWpvZ2V3MEtJQ0FnSUNKMlpYSnphVzl1UTI5dWMzUnlZV2x1ZENJNklDSXFJaXdOQ2lBZwpJQ0FpWkdsemRISnBZblYwYVc5dWN5STZJRnNOQ2lBZ0lDQWdJQ0pQWm1acFkybGhiQ0lzRFFvZ0lDQWdJQ0FpClJHOWpkVzFsYm5SRVFpSU5DaUFnSUNCZERRb2dJSDBzRFFvZ0lDSlFjbTk0ZVZOUlRDSTZJSHNOQ2lBZ0lDQWkKZG1WeWMybHZia052Ym5OMGNtRnBiblFpT2lBaUtpSU5DaUFnZlN3TkNpQWdJbEpoWW1KcGRFMVJJam9nZXcwSwpJQ0FnSUNKMlpYSnphVzl1UTI5dWMzUnlZV2x1ZENJNklDSXFJZzBLSUNCOUxBMEtJQ0FpVW1Wa2FYTWlPaUI3CkRRb2dJQ0FnSW5abGNuTnBiMjVEYjI1emRISmhhVzUwSWpvZ0lqdzlJRGN1TkRBaURRb2dJSDBzRFFvZ0lDSlQKYjJ4eUlqb2dldzBLSUNBZ0lDSjJaWEp6YVc5dVEyOXVjM1J5WVdsdWRDSTZJQ0lxSWcwS0lDQjlMQTBLSUNBaQpXbTl2UzJWbGNHVnlJam9nZXcwS0lDQWdJQ0oyWlhKemFXOXVRMjl1YzNSeVlXbHVkQ0k2SUNJcUlnMEtJQ0I5CkRRcDlNWUdrTUJjR0ExVUVDaE1RYTNWaVpXUmlMV052YlcxMWJtbDBlVEFYQmdOVkJBb1RFR3QxWW1Wa1lpMWwKZUhRdGMzUmhjMmd3R0FZRFZRUUtFeEZyZFdKbFpHSXRZWFYwYjNOallXeGxjakFZQmdOVkJBb1RFV3QxWW1WawpZaTFsYm5SbGNuQnlhWE5sTUJ3R0ExVUVDaE1WY0dGdWIzQjBhV052YmkxbG5SbGNuQnlhWE5sTUJBNEdBMVVFCkNoTVhhM1ZpWldSaUxXMXZibWwwYjNKcGJtY3RZV2RsYm5ReEdqQVlCZ05WQkFzVEVXdDFZbVZrWWkxbGJuUmwKY25CeWFYTmxNUzB3S3dZRFZRUURFeVJsTlRjd1pqVXpNeTAwTmpSbExUUTNaVGd0WVdZMU9TMDJOek16TlRBMQpOVFpoWkRJd2dnRWlNQTBHQ1NxR1NJYjNEUUVCQVFVQUE0SUJEd0F3Z2dFS0FvSUJBUUNhVDZsdldiSFFsTVpZClphRjNNTStjQ0VPblM0cVJ2cWoyWTNaS2E3K1d1THNhd09xQ2MxdzlLMXpReGVXaGpPSktSL1lqSlNzdUpNV1MKVkY2cEFRZXFEUWgwdFNFUE42Z0pCdmZIVDlxOXliSTc3Q0kwcDFKMTFYL1BFSVhyZStUbWpWWEthcTV3WUNOcQpEdExwZ0tEUG5TajczdHNoSFBhV2Jqb0VLL01OTEw0ZVI0ZUtvRHNqWEN1TEZXeVl4THBZSHhBSVZHN0c1VDB3ClRaaVpSS2dvSGFHOU9FYmZWNmVxT3h3ODNJcGlnV1JvNlZ0ekcwMEpWMG5uM05oTXRmdk01eEUrV3ZndVd0czcKdkFZZTk4UXJ2TitHUVphTTB0RDVUZ1F5SXhIdjdHZEdDMUVUWlhUc2dMNVIrVFg5SXgzV21zQXFDM0VSQncrbgpMZEJvSGx3SkFnTUJBQUdqZ2JZd2diTXdEZ1lEVlIwUEFRSC9CQVFEQWdXZ01CTUdBMVVkSlFRTU1Bb0dDQ3NHCkFRVUZCd01DTUI4R0ExVWRJd1FZTUJhQUZOa3hFU1FnWHIwYmVyTXdJdEtiMFBPU3hLQjVNR3NHQTFVZEVRUmsKTUdLQ0pHVTFOekJtTlRNekxUUTJOR1V0TkRkbE9DMWhaalU1TFRZM016TTFNRFUxTm1Ga01vRWhiM0puTFhoNQplaUE4TXpNME5qRXlRR2xrTG1KNWRHVXVZblZwYkdSbGNuTStnUmN6TXpRMk1USkFhV1F1WW5sMFpTNWlkV2xzClpHVnljekFOQmdrcWhraUc5dzBCQVFzRkFBT0NBUUVBQWRUeXpWWE9SR09zS2FaUDFRZFQxT0lhUW5KWm9wOTgKdUd6R1l2clNlSmdVTnRPaVNka2U0N1VVTGEzTkE4SDhtViszNG1zcUFaUTRkYWppSVova001cm5DbFdDUWE3MgpGV3dJUU9xRm4rcEFReDhYeEVJOEs3OSt6SzBESlRPdHpCYTRoVWgyNlMxOFFMQWRuN1VYWUJ0S3JGTm9VVGoxCmF6ZVF3bDIwbW1IQkNPcVBKdE4wSjVtendOajVzVWhNWG05ZUY4djlhQW9KQ2xySlBuY3BHdWFoQ1JFOW1RbWMKMkw4YnZPYVAzODl4ZmF5VDFsYXBJcXA3QUZockc3RU5RZUF5QmpOUGlJZG1uNExmK0VVdFFwbEd4V0pSdVJ4NgpNdFo0M0lVLzJhM3lvTzRwSzBqNXdSM28xcWllWkN3Q2w0UEpXZFNuT1I2dkVoTmE3TTlwcUE9PQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg=="
+ }
+ ```
+ **Interpretation:**
+ - `contract.id:` This field is crucial. If it displays `0`, it indicates that the license issued is a `1-month (30-day)` free `trial` license, automatically provided by AppsCode because the cluster is not explicitly associated with any paid contract. This is useful for initial testing. Each cluster is eligible for this free trial only once.
+ - `contract.startTimestamp` and `contract.expiryTimestamp:` These fields define the validity period of the contract under which the license was issued.
+ - `license:` This is the actual `Base64-encoded` license token. A valid token here confirms that the AppsCode backend successfully issued a license.
+ If the curl command fails (e.g., `connection refused`, `timeout`, `authentication` error), it indicates a network or authentication issue preventing the `license-proxyserver` from reaching the AppsCode backend.
+
+#### 5. Conclusion
+The AppsCode License Management System delivers a `lightweight`, `in-cluster` authority for fast, reliable license validation in Kubernetes. Its `online` and `offline` modes accommodate both
+always-connected and isolated environments. It empowers customers with `self-service` capabilities for cluster association.
+
+For unresolved issues, email [support@appscode.com](mailto:support@appscode.com) or [platform-support@appscode.com](mailto:support@appscode.com), or file a ticket at [AppsCode Contact](https://appscode.com/contact).
\ No newline at end of file
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/README.md b/content/docs/platform/v2026.7.10/selfhost-setup/README.md
new file mode 100644
index 0000000000..2a2bc95377
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/README.md
@@ -0,0 +1,42 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-setup-readme
+ name: Selfhost Setup
+ parent: selfhost-setup
+ weight: -1
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+url: /docs/platform/v2026.7.10/selfhost-setup/
+aliases:
+- /docs/platform/v2026.7.10/selfhost-setup/README/
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Host KubeDB Platform as Your Own
+
+Welcome to KubeDB Platform's Self-Hosted deployment! Whether you're looking for a quick trial in "Self Hosted Demo" mode or gearing up for a production-ready environment (`Self Hosted Production`), you're in control.
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+
+
+
+
+
+
+Click on the `Create New Installer` button to get started. You can choose various deployment types including `Cloud Demo` or `Self Hosted Production`. Provide the required data and click `Done` button to generate the installer. Upon generation of the installer, you will get the documentation how to host KubeDB Platform Server on your own.
+
+
+
+
+To get detailed documentation on `Cloud Demo` installer, head over to [Demo Deployment](../selfhost-setup/install/cloud-demo).
+
+
+
+
+To get detailed documentation on `Self Hosted Production` installer, head over to [Production Deployment](../selfhost-setup/install/selfhosted-production).
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/_index.md b/content/docs/platform/v2026.7.10/selfhost-setup/_index.md
new file mode 100644
index 0000000000..70f0a87271
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/_index.md
@@ -0,0 +1,16 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-setup
+ name: Selfhost Setup
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/acaas-chart.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/acaas-chart.png
new file mode 100644
index 0000000000..ef1ef858c9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/acaas-chart.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-dashboard.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-dashboard.png
new file mode 100644
index 0000000000..bdf6a21213
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-dashboard.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-status.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-status.png
new file mode 100644
index 0000000000..e9d389c76b
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/ace-status.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/admin-setting.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/admin-setting.png
new file mode 100644
index 0000000000..6781a2e611
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/admin-setting.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep1.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep1.png
new file mode 100644
index 0000000000..af5971dd01
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep1.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep2.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep2.png
new file mode 100644
index 0000000000..67e967b720
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep2.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep3.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep3.png
new file mode 100644
index 0000000000..64394d19f0
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep3.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep4.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep4.png
new file mode 100644
index 0000000000..69bd8dc577
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep4.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep5.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep5.png
new file mode 100644
index 0000000000..0f8f737b96
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep5.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep7.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep7.png
new file mode 100644
index 0000000000..45dd7a2cdd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/awsStep7.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep1.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep1.png
new file mode 100644
index 0000000000..f15c264468
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep1.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep2.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep2.png
new file mode 100644
index 0000000000..d0ddf55614
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep2.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep3.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep3.png
new file mode 100644
index 0000000000..ace08742db
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep3.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep4.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep4.png
new file mode 100644
index 0000000000..dc75bc9793
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep4.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep5.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep5.png
new file mode 100644
index 0000000000..728b112a57
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/azureStep5.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/branding.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/branding.png
new file mode 100644
index 0000000000..dc667fffbd
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/branding.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/deployment-progress.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/deployment-progress.png
new file mode 100644
index 0000000000..251c749fa9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/deployment-progress.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/domain-whitelisting.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/domain-whitelisting.png
new file mode 100644
index 0000000000..e64ac68955
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/domain-whitelisting.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/features.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/features.png
new file mode 100644
index 0000000000..bc6d0e04e9
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/features.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/ingress-gateway.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/ingress-gateway.png
new file mode 100644
index 0000000000..10dc559f45
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/ingress-gateway.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/installer-home.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/installer-home.png
new file mode 100644
index 0000000000..3ed14406c1
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/installer-home.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/ip-reconfigure-openshift.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/ip-reconfigure-openshift.png
new file mode 100644
index 0000000000..2eb0545918
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/ip-reconfigure-openshift.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/managed-resources.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/managed-resources.png
new file mode 100644
index 0000000000..845687f70c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/managed-resources.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/monitoring-alertmanager.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/monitoring-alertmanager.png
new file mode 100644
index 0000000000..9031a62914
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/monitoring-alertmanager.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/nats.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/nats.png
new file mode 100644
index 0000000000..dd4da5e2f6
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/nats.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/offline-toggle.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/offline-toggle.png
new file mode 100644
index 0000000000..2cbd9a7f46
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/offline-toggle.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-1.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-1.png
new file mode 100644
index 0000000000..0b13417187
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-1.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-10.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-10.png
new file mode 100644
index 0000000000..393c158994
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-10.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-2.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-2.png
new file mode 100644
index 0000000000..d5a297e421
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-2.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-3.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-3.png
new file mode 100644
index 0000000000..144b2259a7
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-3.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-4.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-4.png
new file mode 100644
index 0000000000..412e479634
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-4.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-5.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-5.png
new file mode 100644
index 0000000000..57fbc65ade
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-5.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-7.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-7.png
new file mode 100644
index 0000000000..c0cf3a563f
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-7.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-8.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-8.png
new file mode 100644
index 0000000000..3377d69251
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-8.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-9.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-9.png
new file mode 100644
index 0000000000..16e8aec723
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/policy-9.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/resource-limit.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/resource-limit.png
new file mode 100644
index 0000000000..7a3f015543
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/resource-limit.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/selfhost-deployment-option.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/selfhost-deployment-option.png
new file mode 100644
index 0000000000..40b3afcf60
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/selfhost-deployment-option.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/images/tenant.png b/content/docs/platform/v2026.7.10/selfhost-setup/images/tenant.png
new file mode 100644
index 0000000000..a88f0b301c
Binary files /dev/null and b/content/docs/platform/v2026.7.10/selfhost-setup/images/tenant.png differ
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/_index.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/_index.md
new file mode 100644
index 0000000000..00235b8eb4
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/_index.md
@@ -0,0 +1,17 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhosted-installer
+ name: Self Hosted Installer
+ parent: selfhost-setup
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/aws-marketplace.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/aws-marketplace.md
new file mode 100644
index 0000000000..110b95af48
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/aws-marketplace.md
@@ -0,0 +1,526 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: aws-marketplace
+ name: AWS Marketplace
+ parent: selfhosted-installer
+ weight: 6
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform: AWS Marketplace
+
+Welcome to the KubeDB Platform's **AWS Marketplace** deployment! This guide will walk you through the deployment process via the **AWS Marketplace**, ensuring your environment is configured correctly for a seamless installation.
+
+To install **KubeDB Platform**, you need to have the permissions to manage **EC2**, **IAM**, **CloudFormation** etc.
+
+### Prerequisite
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+You have to create an `Access Key` and `Secret Key` with following policies attached. Check out similar [eksctl docs](https://eksctl.io/usage/minimum-iam-policies/) for reference.
+
+### For importing cluster to console:
+ImportClusterCustomAccess
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "eks:DescribeNodegroup",
+ "ec2:DescribeAvailabilityZones",
+ "ec2:DescribeRegions",
+ "eks:DescribeCluster",
+ "eks:ListClusters"
+ ],
+ "Resource": "*"
+ }
+ ]
+}
+```
+### For creating and managing the EKS Cluster and EC2 resources:
+
+AmazonEC2FullAccess (AWS Managed Policy)
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Action": "ec2:*",
+ "Effect": "Allow",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "elasticloadbalancing:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "cloudwatch:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "autoscaling:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "iam:CreateServiceLinkedRole",
+ "Resource": "*",
+ "Condition": {
+ "StringEquals": {
+ "iam:AWSServiceName": [
+ "autoscaling.amazonaws.com",
+ "ec2scheduled.amazonaws.com",
+ "elasticloadbalancing.amazonaws.com",
+ "spot.amazonaws.com",
+ "spotfleet.amazonaws.com",
+ "transitgateway.amazonaws.com"
+ ]
+ }
+ }
+ }
+ ]
+}
+```
+AWSCloudFormationFullAccess (AWS Managed Policy)
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "cloudformation:*"
+ ],
+ "Resource": "*"
+ }
+ ]
+}
+```
+EksAllAccess
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": "eks:*",
+ "Resource": "*"
+ },
+ {
+ "Action": [
+ "ssm:GetParameter",
+ "ssm:GetParameters"
+ ],
+ "Resource": [
+ "arn:aws:ssm:*::parameter/aws/*",
+ "arn:aws:ssm:*::parameter/aws/*"
+ ],
+ "Effect": "Allow"
+ },
+ {
+ "Action": [
+ "kms:CreateGrant",
+ "kms:DescribeKey"
+ ],
+ "Resource": "*",
+ "Effect": "Allow"
+ },
+ {
+ "Action": [
+ "logs:PutRetentionPolicy"
+ ],
+ "Resource": "*",
+ "Effect": "Allow"
+ }
+ ]
+}
+```
+IamLimitedAccess
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:CreateInstanceProfile",
+ "iam:DeleteInstanceProfile",
+ "iam:GetInstanceProfile",
+ "iam:RemoveRoleFromInstanceProfile",
+ "iam:GetRole",
+ "iam:CreateRole",
+ "iam:DeleteRole",
+ "iam:AttachRolePolicy",
+ "iam:PutRolePolicy",
+ "iam:UpdateAssumeRolePolicy",
+ "iam:AddRoleToInstanceProfile",
+ "iam:ListInstanceProfilesForRole",
+ "iam:PassRole",
+ "iam:DetachRolePolicy",
+ "iam:DeleteRolePolicy",
+ "iam:GetRolePolicy",
+ "iam:GetOpenIDConnectProvider",
+ "iam:CreateOpenIDConnectProvider",
+ "iam:DeleteOpenIDConnectProvider",
+ "iam:TagOpenIDConnectProvider",
+ "iam:ListAttachedRolePolicies",
+ "iam:TagRole",
+ "iam:UntagRole",
+ "iam:GetPolicy",
+ "iam:CreatePolicy",
+ "iam:DeletePolicy",
+ "iam:ListPolicyVersions"
+ ],
+ "Resource": [
+ "arn:aws:iam:::instance-profile/eksctl-*",
+ "arn:aws:iam:::role/eksctl-*",
+ "arn:aws:iam:::policy/eksctl-*",
+ "arn:aws:iam:::oidc-provider/*",
+ "arn:aws:iam:::role/aws-service-role/eks-nodegroup.amazonaws.com/AWSServiceRoleForAmazonEKSNodegroup",
+ "arn:aws:iam:::role/eksctl-managed-*"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:GetRole",
+ "iam:GetUser"
+ ],
+ "Resource": [
+ "arn:aws:iam:::role/*",
+ "arn:aws:iam:::user/*"
+ ]
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:CreateServiceLinkedRole"
+ ],
+ "Resource": "*",
+ "Condition": {
+ "StringEquals": {
+ "iam:AWSServiceName": [
+ "eks.amazonaws.com",
+ "eks-nodegroup.amazonaws.com",
+ "eks-fargate.amazonaws.com"
+ ]
+ }
+ }
+ }
+ ]
+}
+```
+
+### S3:FullAccess for storing cluster backups
+AmazonS3FullAccess (AWS Managed Policy)
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "s3:*",
+ "s3-object-lambda:*"
+ ],
+ "Resource": "*"
+ }
+ ]
+}
+```
+## Application Deployment
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Choose Deployment Mode And Environment
+
+Choose `Deployment Type` -> `AWS Marketplace` and give it a name in the installer name section.
+
+Before beginning the installation, identify your target infrastructure and cluster type.
+
+### 3. Global Administrative Settings
+These credentials define the primary super-user and the initial organizational structure.
+
+* **System Admin:** In this section, provide the administrator's following information.
+ - **Access Key ID:** AWS access key id.
+ - **Secret Access Key:** AWS secret access key, these credentials will be used to manage resources to your aws account, like create bucket or create cluster.
+ - **Admin Account Display Name:** The display name for the administrator account.
+ - **Admin Account Email:** The email address for the administrator account.
+ - **Admin Account Password:** The password for the administrator account.You may manually set a password or leave it blank to allow the system to **auto-generate** a secure administrative password.
+ - **Initial Organization Name:** You can choose what will be the initial organization name for your account
+
+For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint
+
+### 4. Registry
+See [Registry](../common-config/#registry) in the Common Configuration guide for Docker registry proxies, Helm repositories, credentials, certs, and image pull secrets.
+
+### 5. Monitoring
+
+See [Monitoring](../common-config/#monitoring) in the Common Configuration guide for Alertmanager email and webhook configuration.
+
+
+### 6. Settings
+
+#### Domain White List
+
+* You must specify the end users domains, the system will only allow users with those specified domains. You can Add multiple domain whitelists at the same time.
+* Put Login and Logout URL
+
+### 7. Self Management
+In this section you can enable or disable features. You can also create an initial `CAPI Cluster` from this section.
+
+
+### 8. Branding & UI Customization
+See [Branding & UI Customization](../common-config/#branding--ui-customization) in the Common Configuration guide to re-brand the platform interface.
+
+### 9. Generate Installer and Documentation
+
+Click the "Next" button to submit your information. KubeDB Platform will generate the installer and provide the necessary documentation and further installation guideline in details.
+
+You will find an `Installer URL` for this installer. You have to give this URL in the AWS Marketplace application.
+
+### 10. Deploy KubeDB Platform
+
+The expiry time for this installer is 2 hours. You will find in detail deployment guideline after creating the installer.
+
+### Set the IAM permission(optional).
+
+### Step 1: Create IAM policy
+
+ * Navigate to **IAM** -\> **Policy** -\> **Create policy**.
+ * Select the **JSON** input tab and paste your JSON configuration. Click **Next** to continue.
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Action": "ec2:*",
+ "Effect": "Allow",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "elasticloadbalancing:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "cloudwatch:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "autoscaling:*",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": "iam:CreateServiceLinkedRole",
+ "Resource": "*",
+ "Condition": {
+ "StringEquals": {
+ "iam:AWSServiceName": [
+ "autoscaling.amazonaws.com",
+ "ec2scheduled.amazonaws.com",
+ "elasticloadbalancing.amazonaws.com",
+ "spot.amazonaws.com",
+ "spotfleet.amazonaws.com",
+ "transitgateway.amazonaws.com"
+ ]
+ }
+ }
+ },
+ {
+ "Action": [
+ "aws-marketplace:MeterUsage"
+ ],
+ "Effect": "Allow",
+ "Resource": "*"
+ },
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:*",
+ "organizations:DescribeAccount",
+ "organizations:DescribeOrganization",
+ "organizations:DescribeOrganizationalUnit",
+ "organizations:DescribePolicy",
+ "organizations:ListChildren",
+ "organizations:ListParents",
+ "organizations:ListPoliciesForTarget",
+ "organizations:ListRoots",
+ "organizations:ListPolicies",
+ "organizations:ListTargetsForPolicy"
+ ],
+ "Resource": "*"
+ }
+ ]
+}
+```
+
+
+
+
+
+ * Give the policy the name **AWSMarketplacePolicyForCloudFormation** and click **Create Policy**.
+
+
+
+
+
+
+
+### Step 2: Create IAM role
+
+ * Navigate to **IAM** -\> **Roles** -\> **Create Role**.
+ * Select **Trusted entity** type: `AWS service`.
+ * Select **Use case**: `CloudFormation` and click **Next**.
+
+
+
+ * Search for and select the **AWSMarketplacePolicyForCloudFormation** policy you just created, then click **Next**.
+
+
+
+ * Name the role **AWSMarketplaceMeteringRoleForCloudFormation** and click **Create role**.
+
+
+
+
+
+### Step 3: PassRole Permission
+
+ * Copy the **Role ARN** of the role you just created: `arn:aws:iam::xxxxxxxx:role/AWSMarketplaceMeteringRoleForCloudFormation`.
+
+
+
+
+
+
+### Step 4: Role JSON
+
+ * Create another new policy.
+ * Paste the required JSON and **replace the resource value with the Role ARN** you copied in the previous step.
+
+```json
+{
+ "Version": "2012-10-17",
+ "Statement": [
+ {
+ "Effect": "Allow",
+ "Action": [
+ "iam:GetRole",
+ "iam:PassRole"
+ ],
+ "Resource": "arn:aws:iam::XXXXXXXXXXX:role/AWSMarketplaceMeteringRoleForCloudFormation"
+ }
+ ]
+}
+```
+
+
+
+
+
+
+
+### Step 5: Policy name
+
+ * Provide a name for this policy (e.g., **AllowPassingMeterUsageRoleToCloudFormation**) and click **Create policy**.
+
+
+
+
+
+
+
+### Step 6: Attach this policy to user or user group
+
+ * Go to the **User** or **Group** that requires these permissions.
+ * Click **Add permissions**.
+ * Select the **AllowPassingMeterUsageRoleToCloudFormation** policy you just created to attach it.
+
+
+
+
+
+Now follow the steps to configure the stack
+
+### Step 1: Go to AWS Marketplace
+
+ * Go to [AppsCode Cloud w/ Usage Billing](https://aws.amazon.com/marketplace/pp/prodview-izn7wxvkpbjuo) in the AWS Marketplace. Launch the application
+and subscribe to **AppsCode Cloud w/Usage Billing** product.
+ * Click on Continue To Configuration.
+
+
+
+
+
+### Step 2: Configuration
+
+ * Select the latest software version, and region for the Application and click on **Continue to Launch.**
+
+
+
+
+
+### Step 3: Create stack
+
+ * You will be forwarded to the Cloudformation selection page.
+ * Keep the default selected template and click on **Next.**
+
+
+
+
+
+### Step 4: Specify stack details
+
+ * **ApplicationAccessIpCIDR:** The IP CIDR range from which the application will be accessed. **x.x.x.x/32** will allow one specific IP; we recommend using **0.0.0.0/0** so that it is publicly available.
+ * **InstallerURL:** The URL that you have generated above.
+ * **InstanceType:** Select an instance type; the instance must have at least **4 core** CPUs and **16GiB** of Memory.
+ * **KeyPair:** Choose one of your existing KeyPairs. This KeyPair will be added as the known keys in the Instance for SSH.
+ * **SSHIpCIDR:** This CIDR range IPs will have access to SSH on the application instance. **x.x.x.x/32** will allow one specific IP and **0.0.0.0/0** will allow all IPs.
+ * Click **Next** and you will be forwarded to the **review and create page.**
+
+
+
+
+
+### Step 5: Attach role to CloudFormation (Optional)
+
+ * **Prerequisite:** You must have IAM roles for this.
+ * When applying the cloudformation template (CFT), attach **AWSMarketplaceMeteringRoleForCloudFormation** role to the template. This way the CFT will have all the necessary permission to deploy the resources.
+
+
+
+
+
+### Step 6: Review & Deployment
+
+ * Review the Cloudformation Template and click on **Submit** to start the application creation process.
+ * Wait for some time to create the Cloudformation template.
+ * Once the Cloudformation is created it will take **5-10min** to spin up the application.
+
+
+
+
+
+### 10. Explore the Deployed Platform
+
+Once deployed, access the **KubeDB Platform** using the specified domain. Log in with the admin account credentials provided during the creation process.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/azure-marketplace.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/azure-marketplace.md
new file mode 100644
index 0000000000..aa2202b271
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/azure-marketplace.md
@@ -0,0 +1,153 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: azure-marketplace
+ name: Azure Marketplace
+ parent: selfhosted-installer
+ weight: 7
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# 1. Deploying KubeDB Platform: Azure Marketplace
+
+Welcome to the KubeDB Platform's **Azure Marketplace** deployment! This guide will walk you through the deployment process via the Azure Marketplace, ensuring your environment is configured correctly for a seamless installation.
+
+### Prerequisites
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+## Getting Started
+
+The **Azure Marketplace** installation wizard will prompt you for specific configuration parameters. Having these details ready beforehand will streamline your setup.
+
+If you encounter any issues during the deployment, please refer to our Official Documentation or contact with us.
+
+### 2. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 3. Choose Deployment Mode And Environment
+
+Choose `Deployment Type` -> `Azure Marketplace` and give it a name in the installer name section.
+
+For deploying KubeDB Platform using azure marketplace, you usually need these four pieces of information to establish a secure connection. These represent the "Identity" of your application and the "Address" of your billing/directory structure.
+
+#### 1. Subscription ID
+The unique identifier for your **Azure Subscription**. This is where the actual billing for Marketplace services occurs. To get Subscription ID:
+ 1. Log in to the [Azure Portal](https://portal.azure.com).
+ 2. Search for **Subscriptions** in the top search bar.
+ 3. Select your active subscription.
+ 4. Copy the **Subscription ID** (e.g., `a1b2c3d4-5678-90ab-cdef-1234567890ab`).
+
+#### 2. Tenant ID
+The identifier for your **Microsoft Entra ID** (formerly Azure AD) instance. It represents your entire organization in the cloud. To get Tenant ID:
+ 1. In the Azure Portal, search for **Microsoft Entra ID**.
+ 2. On the **Overview** page, look for **Tenant ID**.
+ 3. Copy the GUID.
+
+#### 3. Client ID
+This is the "username" for your application. When you register an app in Azure to interact with the Marketplace API, it is assigned this ID. To get Client ID:
+ 1. Go to **Microsoft Entra ID** > **App registrations**.
+ 2. Select your application (if you haven't made one, click **New registration**).
+ 3. Copy the **Application (client) ID** from the Essentials section.
+Your application must have the necessary permissions to create deployment resources. It requires permissions to manage the cluster and blob storage, as well as to list regions. In this case, we have assigned the Contributor role.
+
+#### 4. Client Secret
+This is the "password" for your application. It allows the app to prove its identity to Azure. To get Client Secret:
+ 1. Inside your **App registration**, click **Certificates & secrets** in the left menu.
+ 2. Click **+ New client secret**.
+ 3. Add a description and expiry (e.g., 12 months).
+ 4. **CRITICAL:** Copy the **Value** (not the Secret ID) immediately. Once you leave the page, it will be hidden forever.
+
+Put **Subscription ID**, **Tenant ID**, **Client ID** and **Client Secret** in the respective field. For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint
+
+### 4. Global Administrative Settings
+
+See [Global Administrative Settings](../common-config/#global-administrative-settings) in the Common Configuration guide for the System Admin account fields (display name, email, password, and initial organization).
+
+For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint
+
+### 5. Registry
+
+See [Registry](../common-config/#registry) in the Common Configuration guide for Docker registry proxies, Helm repositories, credentials, certs, and image pull secrets.
+
+### 6. Monitoring
+
+See [Monitoring](../common-config/#monitoring) in the Common Configuration guide for Alertmanager email and webhook configuration.
+
+### 7. Settings
+
+#### Domain White List
+* Add domain one by one for whitelisting
+* Put Login and Logout URL
+
+
+
+
+
+### 8. Self Management
+
+In this section you can enable or disable features. You can also create an initial `CAPI Cluster` from this section.
+
+### 9. Branding & UI Customization
+
+See [Branding & UI Customization](../common-config/#branding--ui-customization) in the Common Configuration guide to re-brand the platform interface.
+
+### 10. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. KubeDB Platform will generate the installer and provide the necessary documentation.
+
+### 11. Deploy KubeDB Platform
+
+#### Step 1: Create Azure application
+Go to Azure Marketplace and select AppsCode Cloud w/ Usage Billing application. [AppsCode Cloud w/ Usage Billing from Marketplace](https://portal.azure.com/#create/appscode.ace_paygace-payg)
+
+
+
+
+
+#### Step 2: Basic Information
+Provide basic information for the Azure application. Put your resource group and application name.
+
+
+
+
+
+#### Step 3: Select VM
+Select a virtual machine for the Installer with at least 4 core CPU and 16GB of RAM.
+
+
+
+
+
+#### Step 4: Authentication Type
+By default Username user will be created to your Installer VM.
+You can use one of the Password or SSH Key Pair to authenticate into the VM.
+
+
+
+
+
+#### Step 5: Installer Information
+Provide the URL link you found from the instruction in the Installer Url field
+
+
+
+
+
+You can monitor the deployment progress through the **Managed Resource Group's** overview page and the **Activity Log**. Once the deployment is complete, the necessary resources will be provisioned within that managed resource group.
+
+
+
+
+### 12. Explore the Deployed Platform
+
+Once deployed, access the **KubeDB Platform** using the specified domain. Log in with the admin account credentials provided during the creation process.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/cloud-demo.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/cloud-demo.md
new file mode 100644
index 0000000000..63e55782e9
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/cloud-demo.md
@@ -0,0 +1,95 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-cloud-demo-deployment
+ name: Cloud Demo Deployment
+ parent: selfhosted-installer
+ weight: 2
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform: Cloud Demo
+
+Welcome to the KubeDB Platform's "Cloud Demo" deployment! Follow these steps to deploy the KubeDB Platform in Cloud Demo mode.
+
+### Prerequisites
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Choose Deployment Mode
+
+Choose `Deployment Type` -> `Cloud Demo` and give it a name in the installer name section.
+
+Before beginning the installation, identify your target infrastructure and cluster type.
+
+* **DNS & Connectivity:**
+ * **Enable DNS:** Toggle this to allow the installer to manage or integrate with your DNS provider.
+ * **Target IP:** Provide the static IP addresses for your cluster nodes or load balancer.
+* **Cluster Type:** Determine if you are installing on **AWS EKS Cluster** or **Red Hat OpenShift Cluster**.
+
+> For Red Hat OpenShift clusters, see the [Deploying KubeDB Platform in OpenShift Cluster](../openshift-cluster.md) guide.
+
+#### Additional configuration for EKS cluster
+
+See [Additional configuration for EKS cluster](../common-config/#additional-configuration-for-eks-cluster) in the Common Configuration guide for the EBS CSI / AWS Load Balancer Controller prerequisites and the commands to fetch the Kube API server endpoint, subnet IDs, and EIP allocation IDs.
+
+### 3. Global Administrative Settings
+See [Global Administrative Settings](../common-config/#global-administrative-settings) in the Common Configuration guide for the System Admin account fields (display name, email, password, and initial organization).
+
+### 4. Registry
+See [Registry](../common-config/#registry) in the Common Configuration guide for Docker registry proxies, Helm repositories, credentials, certs, and image pull secrets.
+
+### 5. Monitoring
+
+See [Monitoring](../common-config/#monitoring) in the Common Configuration guide for Alertmanager email and webhook configuration.
+
+
+### 6. Settings
+
+#### Domain White List and Proxy Servers
+
+See [Domain White List and Proxy Servers](../common-config/#domain-white-list-and-proxy-servers) in the Common Configuration guide for whitelisting domains, proxy servers, and login/logout URLs.
+
+### 7. Ingress & Gateway
+
+See [Ingress & Gateway](../common-config/#ingress--gateway) in the Common Configuration guide for exposing the platform via the Gateway API or standard Ingress.
+
+### 8. Self Management
+See [Self Management](../common-config/#self-management) in the Common Configuration guide to enable or disable platform features.
+
+### 9. Branding & UI Customization
+See [Branding & UI Customization](../common-config/#branding--ui-customization) in the Common Configuration guide to re-brand the platform interface.
+
+### 10. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. KubeDB Platform will generate the installer and provide the necessary documentation.
+
+### 11. Deploy KubeDB Platform
+
+Follow the documentation provided by AppsCode to deploy the KubeDB Platform on your system.
+
+### 12. Explore the Deployed Platform
+
+Once deployed, access the KubeDB Platform using the specified domain. Log in with the admin account credentials provided during the creation process.
+
+
+
+
+
+## Get Support
+
+If you encounter any challenges during the deployment or have questions, reach out to KubeDB Platform support for assistance.
+
+Congratulations! You have successfully deployed the KubeDB Platform in Cloud Demo mode. Explore the features and capabilities of the platform in your customized environment.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/common-config.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/common-config.md
new file mode 100644
index 0000000000..93b66acbb5
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/common-config.md
@@ -0,0 +1,179 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-common-config
+ name: Common Configurations
+ parent: selfhosted-installer
+ weight: 1
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Common Configuration Sections
+
+Several configuration sections of the installer wizard are identical across all
+Self-Hosted deployment modes. They are documented here once and referenced from
+each mode-specific guide. Use the links in those guides to jump to the relevant
+section below.
+
+## Registry
+
+KubeDB Platform requires access to various container registries and Helm repositories to pull necessary images and charts.
+
+**Docker Registry:** Go to the docker registry section first then look for the following settings
+* **Proxies:** Put registry name for Appscode `r.appscode.com` and other Public Registries like Docker Hub, GitHub Container Registry (`ghcr.io`), Kubernetes Registry, Microsoft (`mcr.microsoft.com`), and Quay.
+* **Helm Repositories:** In the helm repositories section put your helm repository url
+If using private or authenticated registries, provide:
+* **Credentials:** Username and Password.
+* **Certs:** Upload CA Cert, Client Cert, and Client Key if required for mutual TLS.
+* **Image Pull Secrets:** Define the secrets used by the cluster to authenticate with the registries. You can enable create namespace during helm install, allow nondistributable artifacts and insecure option for insecure registry
+
+## Monitoring
+
+Use the **Monitoring** section to configure Alertmanager notifications for platform alerts for the site admin.
+
+* **Alert Manager Email:** Enable email notifications for Alertmanager alerts.
+ * **Enable Email:** Turns email notifications on or off.
+ * **To:** The recipient email address. For Gmail, you can also use plus addressing such as `user+alerts@example.com`.
+ * **From:** The sender email address shown in the message. For Gmail, use the same address as **Auth Username** unless you have configured a verified alias.
+ * **Smarthost:** The SMTP server address. For Gmail, use `smtp.gmail.com:587`.
+ * **Auth Username:** The SMTP login username. For Gmail, this should be the real Gmail or Google Workspace mailbox used to authenticate.
+ * **Password:** The SMTP password. For Gmail, use an App Password generated from `https://myaccount.google.com/apppasswords`.
+ * **Require TLS:** Enables TLS for the SMTP connection. Leave this enabled for Gmail.
+ * **Send Resolved:** Sends a follow-up notification when an alert returns to a healthy state.
+* **Alert Manager Webhook:** Send alerts to an endpoint that accepts Alertmanager's generic webhook payload.
+ * **Enable Webhook:** Turns webhook delivery on or off.
+ * **URL:** The destination webhook URL. Some systems embed the secret directly in the URL.
+ * **Send Resolved:** Sends a follow-up notification when an alert returns to a healthy state.
+
+
+
+
+
+> **Tip:** For Google Chat, a supported workaround is to generate a space email address in Google Chat settings and use that address in the **To** field.
+
+## TLS
+
+Configure TLS certificates for secure communication. You can choose the Issuer type from the following list.
+ * **External**: Use this if you already have certificates from an external provider.
+ * CA CERT: Paste the Certificate Authority certificate.
+ * Certificate CERT: Paste the certificate issued for your domain.
+ * Certificate Key: Paste the private key associated with the certificate.
+
+ * **CA:** Use this if you want AppsCode to manage your certificates with its internal CA.
+ * CA CERT: Paste the internal CA certificate.
+ * CA Key: Paste the internal CA key.
+
+## NATS
+
+Configure NATS, which is used as the internal messaging system for the platform.
+
+**Expose Via:**
+ Choose how NATS will be exposed:
+
+ * **HostPort:** Exposes NATS directly on the node’s network interface.
+
+ * **Node Selector:** Specify the node label (Key and Value) to control where NATS will be scheduled.
+ * **Ingress:** Use this option to expose NATS externally via an ingress controller.
+**Replicas:** For production, ensure at least 1 replica is active (consider 3 for high availability).
+**Resources:** Configure CPU Requests, CPU Limits, Memory Request and Memory Limit
+
+
+
+
+
+## Branding & UI Customization
+
+Administrators can globally re-brand the KubeDB Platform interface to match corporate identity.
+
+* **App Name:** Changes the browser tab title.
+* **Primary Color:** Enter a Hex code (default: `#009948`).
+* **Assets:**
+ * **Logo:** Upload a 200x30px image (SVG/PNG recommended).
+ * **Favicon:** Upload a 20KB icon file.
+* **App Tag:** Toggle **"Show App Tag"** to display or hide the version/tagging info in the UI.
+
+
+
+
+
+
+## Prerequisites
+
+Before you begin, please ensure your Kubernetes cluster meets the following minimum system requirements:
+* **Worker Nodes**: At least one dedicated worker node.
+* **CPU**: 4–6 vCPUs.
+* **Memory**: 16 GB of RAM.
+* **Networking**: A routable IP address for external connectivity.
+
+You will get an instruction to deploy a k3s cluster in Ubuntu VM, or you can skip this step if you already have a cluster.
+
+## Global Administrative Settings
+
+These credentials define the primary super-user and the initial organizational structure.
+
+* **System Admin:** In this section, provide the administrator's following information.
+ - **Admin Account Display Name:** The display name for the administrator account.
+ - **Admin Account Email:** The email address for the administrator account.
+ - **Admin Account Password:** The password for the administrator account. You may manually set a password or leave it blank to allow the system to **auto-generate** a secure administrative password.
+ - **Initial Organization Name:** You can choose what will be the initial organization name for your account
+
+
+
+
+
+## Additional configuration for EKS cluster
+
+**Prerequisite:**
+* EBS CSI Driver must be installed
+* AWS Load Balancer Controller must be installed
+
+Run the following command to get the Kube API Server and put it in the API server field:
+
+```
+aws eks describe-cluster --name --region --query "cluster.endpoint" --output text
+```
+
+Run the following command to get the Subnet IDs and add them:
+
+```
+aws ec2 describe-subnets --filters "Name=vpc-id,Values=$(aws eks describe-cluster --name --region --query "cluster.resourcesVpcConfig.vpcId" --output text)" "Name=map-public-ip-on-launch,Values=true" --region --query "Subnets[*].SubnetId" --output text
+```
+
+**Subnet IDs:** Make sure you have added the allocation id of Target IP as well. Run the following command to create EIP Allocation IDs `aws ec2 allocate-address --region `
+
+**EIP Allocation IDs:** Give EIP allocation IDs for your public subnets.
+
+## Domain White List and Proxy Servers
+
+* Add domain one by one for whitelisting
+* **Proxy Servers:** If you have proxy servers then put **HTTP Proxy**, **HTTPS Proxy** and **No Proxy**
+* Put Login and Logout URL for your app
+
+
+
+
+
+## Ingress & Gateway
+
+Configure how the application is exposed to the internet or your internal network.
+
+* **Ingress & Gateway:** Enable either the **Gateway API** or standard **Ingress**.
+
+
+
+
+
+## Self Management
+
+In this section you can enable or disable features.
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/offline.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/offline.md
new file mode 100644
index 0000000000..49bb4613ff
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/offline.md
@@ -0,0 +1,107 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-offline-platform
+ name: Offline Platform
+ parent: selfhosted-installer
+ weight: 7
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform in Offline Mode
+
+This guide describes how to deploy the **KubeDB Platform** in an **offline (air-gapped)** environment. An offline deployment is only supported with the **Self Hosted Production** deployment type — no other deployment type can be installed offline.
+
+In offline mode, AppsCode never receives any of your KubeDB usage data. AppsCode is only involved once, to issue the license against your **Cluster ID** in the very first step. Everything else — including all billing-related functionality — runs entirely inside your own cluster through the **acaas** chart, which is deployed *only* in offline mode.
+
+### Prerequisites
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Choose the Self Hosted Production Deployment Type
+
+Offline mode is only available with the **Self Hosted Production** deployment type. Choose `Deployment Type` -> `Self Hosted Production` and give it a name in the installer name section.
+
+### 3. Enable Offline Installer and Set the Cluster ID
+
+This is the requirement that distinguishes an offline deployment from a standard production deployment.
+
+* Toggle on the **Offline Installer?** option.
+* Set the **Cluster ID** field. This ID is what AppsCode uses to issue the license for your offline cluster. This is the only piece of information AppsCode receives — it is used solely for license issuance.
+
+
+
+
+
+> [!NOTE]
+> Because the platform runs fully air-gapped, AppsCode has no visibility into your KubeDB usage data after the license is issued. All billing and usage accounting happens locally via the **acaas** chart.
+
+### 4. Complete the Remaining Configuration
+
+Aside from enabling the offline toggle and providing the Cluster ID, all other sections are identical to a standard Self Hosted Production deployment (Global Administrative Settings, Release, Registry, Settings, Monitoring, Infra, TLS, Ingress & Gateway, NATS, and more). For the complete field-by-field walkthrough, follow the [Self Hosted Production](../selfhosted-production.md) guide.
+
+### 5. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. AppsCode will generate the installer and provide the necessary documentation.
+
+### 6. Deploy KubeDB Platform
+
+Follow the documentation provided by AppsCode to deploy the KubeDB Platform. The generated instructions for an offline deployment include an extra step to install the **acaas** chart, which carries the billing-related frontend and backend deployments. This chart is deployed *only* in offline mode.
+
+```bash
+curl -fsSLO https://appscode.ninja/links/installer//offline//archive.tar.gz
+tar -xzvf archive.tar.gz
+
+# Install FluxCD
+# Install ACE
+# It may take up to 10 mins to get everything into a running state
+
+# Install acaas
+helm upgrade -i acaas \
+ oci://ghcr.io/appscode-charts/acaas \
+ --version v2026.6.19 \
+ --namespace ace --create-namespace \
+ --values=./acaas-values.yaml \
+ --wait --debug --burst-limit=10000
+```
+
+
+
+
+
+> [!IMPORTANT]
+> The **acaas** chart contains the billing-related frontend and backend deployments. It is what keeps all usage and billing data inside your cluster, so it is installed in offline mode only — no other deployment type installs this chart.
+
+### 7. Explore the Deployed Platform
+
+Once deployed, access the **KubeDB Platform** using the configured IP or domain. Log in with the admin account credentials provided during the creation process.
+
+
+
+
+
+### 8. Importing Additional DBaaS Clusters
+
+When importing other DBaaS clusters into an offline platform, the platform cannot reach AppsCode to obtain a license automatically. The platform admin must acquire the license for each new cluster manually and supply it during import:
+
+1. Obtain the license for the new cluster from the [AppsCode portal](https://appscode.com) yourself.
+2. Provide that license in the license field while importing the cluster.
+
+> [!NOTE]
+> This manual step applies only to offline mode. In online deployments the license is fetched automatically during import.
+
+## Get Support
+
+If you encounter any challenges during the deployment or have questions, reach out to AppsCode support for assistance.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/onprem-demo.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/onprem-demo.md
new file mode 100644
index 0000000000..c1489f0779
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/onprem-demo.md
@@ -0,0 +1,98 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-onprem-demo-deployment
+ name: Onprem Demo Deployment
+ parent: selfhosted-installer
+ weight: 3
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform: Onprem Demo
+
+Welcome to the KubeDB Platform's "Onprem Demo" deployment! Follow these steps to deploy the KubeDB Platform in Onprem Demo mode.
+
+### Prerequisites
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Choose Deployment Mode
+
+Choose `Deployment Type` -> `Onprem Demo` and give it a name in the installer name section.
+
+Before beginning the installation, identify your target infrastructure and cluster type.
+
+* **DNS & Connectivity:**
+ * **Enable DNS:** Toggle this to allow the installer to manage or integrate with your DNS provider.
+ * **Target IP:** Provide the static IP addresses for your cluster nodes or load balancer.
+* **Cluster Type:** Determine if you are installing on **Red Hat OpenShift Cluster**.
+
+> For Red Hat OpenShift clusters, see the [Deploying KubeDB Platform in OpenShift Cluster](../openshift-cluster.md) guide.
+
+### 3. Global Administrative Settings
+See [Global Administrative Settings](../common-config/#global-administrative-settings) in the Common Configuration guide for the System Admin account fields (display name, email, password, and initial organization).
+
+### 4. Registry
+See [Registry](../common-config/#registry) in the Common Configuration guide for Docker registry proxies, Helm repositories, credentials, certs, and image pull secrets.
+
+### 5. Monitoring
+
+See [Monitoring](../common-config/#monitoring) in the Common Configuration guide for Alertmanager email and webhook configuration.
+
+
+### 6. Settings
+
+#### Domain White List and Proxy Servers
+
+See [Domain White List and Proxy Servers](../common-config/#domain-white-list-and-proxy-servers) in the Common Configuration guide for whitelisting domains, proxy servers, and login/logout URLs.
+
+### 7. TLS
+See [TLS](../common-config/#tls) in the Common Configuration guide for configuring the certificate issuer (External or CA).
+
+### 8. Ingress & Gateway
+
+See [Ingress & Gateway](../common-config/#ingress--gateway) in the Common Configuration guide for exposing the platform via the Gateway API or standard Ingress.
+
+### 9. NATS
+
+See [NATS](../common-config/#nats) in the Common Configuration guide for configuring the internal messaging system (expose method, replicas, and resources).
+
+### 10. Self Management
+See [Self Management](../common-config/#self-management) in the Common Configuration guide to enable or disable platform features.
+
+### 11. Branding & UI Customization
+See [Branding & UI Customization](../common-config/#branding--ui-customization) in the Common Configuration guide to re-brand the platform interface.
+
+### 12. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. KubeDB Platform will generate the installer and provide the necessary documentation.
+
+### 13. Deploy KubeDB Platform
+
+Follow the documentation provided by AppsCode to deploy the KubeDB Platform on your system.
+
+### 14. Explore the Deployed Platform
+
+Once deployed, access the KubeDB Platform using the specified domain. Log in with the admin account credentials provided during the creation process.
+
+
+
+
+
+## Get Support
+
+If you encounter any challenges during the deployment or have questions, reach out to KubeDB Platform support for assistance.
+
+Congratulations! You have successfully deployed the KubeDB Platform in Onprem Demo mode. Explore the features and capabilities of the platform in your customized environment.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/openshift-cluster.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/openshift-cluster.md
new file mode 100644
index 0000000000..ca67d8392f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/openshift-cluster.md
@@ -0,0 +1,130 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-openshift-cluster
+ name: OpenShift Cluster
+ parent: selfhosted-installer
+ weight: 6
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform in OpenShift Cluster
+
+This guide describes how to deploy the **KubeDB Platform** on a **Red Hat OpenShift** cluster. The deployment types available to you depend on how you want to reach the platform:
+
+* **IP mode** — choose this when you want to access the platform over a **static IP**. Available deployment types: **Cloud Demo** and **Onprem Demo**.
+* **DNS mode** — choose this when you want to access the platform over a **DNS name**. Available deployment types: **Onprem Demo** and **Self Hosted Production**.
+
+Regardless of the mode, an OpenShift deployment always requires you to toggle the **Install on Red Hat OpenShift cluster?** option and provide the **Kube API Server** endpoint.
+
+### Prerequisites
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Enable OpenShift and Set the Kube API Server
+
+This is the common requirement for every OpenShift deployment, irrespective of the mode you chose above.
+
+* Toggle on the **Install on Red Hat OpenShift cluster?** option.
+* Set the **Kube API Server** field with your cluster's API server endpoint.
+
+Run the following command against your OpenShift cluster to fetch the API server endpoint:
+
+```bash
+oc whoami --show-server
+```
+
+You can also read it from your current kubeconfig context:
+
+```bash
+kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}'
+```
+
+Paste the returned URL (for example, `https://api..:6443`) into the **Kube API Server** field.
+
+### 3. Choose the Deployment Mode
+
+Pick the `Deployment Type` based on how you want to access the platform, and give it a name in the installer name section. The specifics for each mode are below.
+
+#### IP mode (IP preferred)
+
+Use this mode when you want to reach the platform through a static IP instead of a DNS name. In this mode you can choose either **Cloud Demo** or **Onprem Demo** as the deployment type.
+
+* **DNS & Connectivity:**
+ * **Enable DNS:** Leave this toggle **off** since access is over an IP.
+ * **Target IP:** At this point the load balancer does not exist yet, so just provide any random IP to proceed with creating the installer.
+
+> [!IMPORTANT]
+> The LoadBalancer IP is not known yet, so the random Target IP must be fixed later (see [Deploy KubeDB Platform](#5-deploy-kubedb-platform)).
+
+Once OpenShift is enabled and the Kube API Server is set, follow the standard configuration sections for the deployment type you picked. See the [Cloud Demo](../cloud-demo.md) or [Onprem Demo](../onprem-demo.md) guide for the full walkthrough of these sections.
+
+#### DNS mode (DNS preferred)
+
+Use this mode when you want to reach the platform through a DNS name. In this mode you can choose either **Onprem Demo** or **Self Hosted Production** as the deployment type, the latter being the recommended setup for production.
+
+* **DNS & Connectivity:**
+ * **Enable DNS:** Toggle this **on** so the installer can manage or integrate with your DNS provider.
+ * **Target IP:** At this point the load balancer does not exist yet, so just provide any random IP to proceed with creating the installer.
+
+> [!IMPORTANT]
+> The LoadBalancer IP is not known yet, so the random Target IP and the DNS `A` record must be fixed later (see [Deploy KubeDB Platform](#5-deploy-kubedb-platform)).
+
+Once OpenShift is enabled and the Kube API Server is set, follow the standard configuration sections for the deployment type you picked. See the [Onprem Demo](../onprem-demo.md) or [Self Hosted Production](../selfhosted-production.md) guide for the full walkthrough of these sections.
+
+> [!NOTE]
+> This guide only covers the fields that are **specific to an OpenShift deployment**. Each deployment type has many more configuration sections (Global Administrative Settings, Registry, Monitoring, TLS, Ingress & Gateway, NATS, and more). For the complete field-by-field walkthrough, follow the guide for the deployment type you choose:
+> * **[Cloud Demo](../cloud-demo.md)**
+> * **[Onprem Demo](../onprem-demo.md)**
+> * **[Self Hosted Production](../selfhosted-production.md)**
+
+### 4. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. AppsCode will generate the installer and provide the necessary documentation.
+
+### 5. Deploy KubeDB Platform
+
+Follow the documentation provided by AppsCode to deploy the KubeDB Platform on your OpenShift cluster. For an OpenShift deployment the generated instructions are ordered specifically, and you must pause partway through to fix the placeholder Target IP:
+
+1. **Create the LoadBalancer service.** The first part of the generated instructions creates the platform's LoadBalancer service in the `ace` namespace.
+2. **Wait for the external IP.** The LoadBalancer takes some time to get an external IP assigned. Run `kubectl get svc -n ace` until the `EXTERNAL-IP` column is populated, then copy that IP.
+3. **Reconfigure the installer.** Update the **Target IP** with the assigned LoadBalancer IP and regenerate the installer. For **DNS mode**, also create or update the DNS `A` record so your domain points to this IP.
+4. **Run the remaining install steps.** Continue with the rest of the generated instructions (flux install, `helm upgrade`, and the ACE install) using the reconfigured values.
+
+
+
+
+
+### 6. Explore the Deployed Platform
+
+Once deployed, access the **KubeDB Platform** using the configured IP (IP mode) or domain (DNS mode). Log in with the admin account credentials provided during the creation process.
+
+
+
+
+
+## Notes
+
+- The Prometheus node-exporter DaemonSet will not run on an OpenShift cluster unless it runs in privileged mode. Since this is not our chart, you need to grant the required permission yourself:
+
+ ```bash
+ oc adm policy add-scc-to-user privileged -z kube-prometheus-stack-prometheus-node-exporter -n monitoring
+ ```
+
+- We also run the cert-manager `csi-driver-cacerts` feature in privileged mode so that it can add CA certificates to the OS trusted certificate store. You don't need to do anything manually for this — it is handled automatically at the chart level.
+
+## Get Support
+
+If you encounter any challenges during the deployment or have questions, reach out to AppsCode support for assistance.
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/selfhosted-production.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/selfhosted-production.md
new file mode 100644
index 0000000000..91989d9a51
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/selfhosted-production.md
@@ -0,0 +1,258 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-prod-deployment
+ name: Production Deployment
+ parent: selfhosted-installer
+ weight: 5
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Deploying KubeDB Platform: Self Hosted Production
+
+Welcome to the **Self-Hosted Production** deployment guide for the **KubeDB Platform**. This installation mode is designed for environments requiring high levels of customization and granular control.
+
+By following this walkthrough, you can tailor the deployment to meet your specific production requirements while ensuring a stable and optimized installation.
+
+#### Why Choose Self-Hosted Production?
+
+The self-hosted model provides the flexibility to:
+* **Optimize Resources:** Tune performance parameters based on your specific workload.
+* **Custom Configurations:** Integrate with existing infrastructure and security policies.
+* **Production Readiness:** Implement the platform using best practices for high availability and reliability.
+
+
+#### Deployment Overview
+
+This guide provides a structured approach to deploying the platform manually. We will cover the prerequisite checks, configuration steps, and final verification to ensure your environment is ready for a seamless rollout.
+
+> **Note:** Ensure your infrastructure meets the minimum system requirements before proceeding to the configuration steps.
+
+See [Prerequisites](../common-config/#prerequisites) in the Common Configuration guide for the minimum cluster requirements and the optional k3s setup note.
+
+
+### 1. Visit the KubeDB Platform Self-Hosted Page
+
+Navigate to [KubeDB Platform Self-Hosted](https://appscode.com/selfhost). Here you will find your previously generated self-hosted installers.
+Click on the `Create New Installer` button to get started.
+
+### 2. Choose Deployment Mode And Environment
+
+Choose `Deployment Type` -> `Self Hosted Production` and give it a name in the installer name section.
+
+Before beginning the installation, identify your target infrastructure and cluster type.
+
+* **DNS & Connectivity:**
+ * **Enable DNS:** Toggle this to allow the installer to manage or integrate with your DNS provider.
+ * **Target IP:** Provide the static IP addresses for your cluster nodes or load balancer.
+* **Cluster Type:** Determine if you are installing on **AWS EKS Cluster** or **Red Hat OpenShift Cluster**. For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint. See the [Deploying KubeDB Platform in OpenShift Cluster](../openshift-cluster.md) guide.
+* **Credential-Less Mode:** Enable this if you are using IAM roles for service accounts (IRSA) to avoid manual secret management.
+
+
+
+
+### Additional configuration for EKS cluster
+
+See [Additional configuration for EKS cluster](../common-config/#additional-configuration-for-eks-cluster) in the Common Configuration guide for the EBS CSI / AWS Load Balancer Controller prerequisites and the commands to fetch the Kube API server endpoint, subnet IDs, and EIP allocation IDs.
+
+### Configuring AWS credentialless mode
+
+For Database backup process **KubeDB** uses **KubeStash** and KubeStash depends on Object storage for storing data. If you configure S3 in aws then by configuring credentialless mode you can avoid the hassle of using `Access Key` and `Secret Key`. You can configure credentialless mode for both EC2(K3s cluster VM) and EKS infrastucture.
+
+### EC2 Instance
+
+If you are managing credentialless mode in EC2 VM then you will get policy permission json file after clicking the deploy button. You need to attach this to EC2 instance profile. Follow the following steps for policy attachment
+
+#### 1. Create the IAM Policy
+First, create the policy in your AWS account.
+
+```bash
+aws iam create-policy \
+ --policy-name \
+ --policy-document file://iam-selfhost-permission.json
+```
+
+**Note:** Copy the `Arn` from the output; you will need it for the next step. It will look like: `arn:aws:iam::123456789012:policy/`.
+
+#### 2. Identify your IAM Role
+If you don't know the exact name of the role currently attached to your EC2 instance, use this command to list the role attached to your specific instance:
+
+```bash
+aws ec2 describe-instances \
+ --instance-id \
+ --query "Reservations[0].Instances[0].IamInstanceProfile.Arn" \
+ --output text
+```
+
+#### 3. Attach the Policy to the Role
+Once you have the role name, attach the newly created policy to it.
+
+```bash
+aws iam attach-role-policy \
+ --role-name \
+ --policy-arn arn:aws:iam::123456789012:policy/
+```
+#### Verifying the Setup
+After running the command, you can verify that the policy is attached to the role:
+
+```bash
+aws iam list-attached-role-policies --role-name
+```
+
+### EKS Cluster
+
+Use following steps to give necessary permission to the credential manager controller through service acccount.
+
+Here you have to give IRSA related information. Create Role for IRSA and get OIDC ID
+
+```
+export CLUSTER_NAME=
+export REGION=
+export ACCOUNT_ID=
+
+OIDC_ID=$(aws eks describe-cluster --name $CLUSTER_NAME --region $REGION --query "cluster.identity.oidc.issuer" --output text | cut -d '/' -f 5)
+echo $OIDC_ID
+
+#Verify the OIDC already created or not
+aws iam list-open-id-connect-providers | grep $OIDC_ID | cut -d "/" -f4
+
+#If the command doesn't return the oidc id then create one
+eksctl utils associate-iam-oidc-provider --cluster $CLUSTER_NAME --region $REGION --approve
+
+```
+
+Download Policy and trust-relationship files
+```
+for file in iam-ec2-permissions.json iam-eks-permissions.json template-trust-relationship; do
+ echo "http://cdn.appscode.com/files/products/appscode/aws-selfhost/$file"
+done | xargs -n 1 -P 4 curl -O
+```
+Create Policy using the downloaded files skip if the policy already exists, take note of the policy arn which will be attached to the role next
+
+```
+# grab the policy arn’s from the output
+aws iam create-policy --policy-name AceSelfhostInstallerEC2Policy --policy-document file://iam-ec2-permissions.json
+EC2_POLICY_ARN=$(aws iam list-policies --query "Policies[?PolicyName==’AceSelfhostInstallerEC2Policy’].Arn" --output text)
+aws iam create-policy --policy-name AceSelfhostInstallerEKSPolicy --policy-document file://iam-eks-permissions.json
+EKS_POLICY_ARN=$(aws iam list-policies --query "Policies[?PolicyName==’AceSelfhostInstallerEKSPolicy’].Arn" --output text)
+```
+Create Role using the downloaded trust-relationship file
+```
+sed -e "s/OIDC_ID/$OIDC_ID/g" -e "s/ACCOUNT_ID/$ACCOUNT_ID/g" -e "s/REGION/$REGION/g" -e "s/SA_NAMESPACE/"ace"/g" -e "s/SA_NAME/"ace"/g" template-trust-relationship > ace-trust-relationship.json
+aws iam create-role --role-name AceInstaller-$OIDC_ID --assume-role-policy-document file://ace-trust-relationship.json --description "A role to be used by KubeDB Platform selfhost installer"
+ROLE_ARN=$(aws iam get-role --role-name AceInstaller-$OIDC_ID --query "Role.Arn" --output text)
+# attach Policies to the Role
+aws iam attach-role-policy --role-name AceInstaller-$OIDC_ID --policy-arn=$EC2_POLICY_ARN
+aws iam attach-role-policy --role-name AceInstaller-$OIDC_ID --policy-arn=$EKS_POLICY_ARN
+
+```
+Create and associate access policy
+
+```
+# Create access entry
+aws eks create-access-entry \
+ --cluster-name $CLUSTER_NAME \
+ --region $REGION \
+ --principal-arn $ROLE_ARN \
+ --type STANDARD
+# Associate access policy
+aws eks associate-access-policy \
+ --cluster-name $CLUSTER_NAME \
+ --region $REGION \
+ --principal-arn $ROLE_ARN \
+ --policy-arn arn:aws:eks::aws:cluster-access-policy/AmazonEKSClusterAdminPolicy \
+ --access-scope type=cluster
+```
+
+Provide the output role arn as Ace Installer Role ARN `echo $ROLE_ARN`in the **Ace Installer Role ARN** field.
+
+### 3. Global Administrative Settings
+See [Global Administrative Settings](../common-config/#global-administrative-settings) in the Common Configuration guide for the System Admin account fields (display name, email, password, and initial organization).
+
+### 4. Release
+Define the specific Kubernetes namespace and release information for the KubeDB Platform components.
+
+* **Release Name:** Defaults to `ace`.
+* **Namespace:** Enter the target namespace (default: `ace`).
+* **Namespace Automation:** Toggle **"Create namespaces during Helm install"** if you want the installer to handle namespace lifecycle management.
+
+### 5. Registry
+See [Registry](../common-config/#registry) in the Common Configuration guide for Docker registry proxies, Helm repositories, credentials, certs, and image pull secrets.
+
+### 6. Settings
+This secton is for Persistence & Resource Allocation. Properly sizing your resources is critical for production stability. Configure CPU Requests, CPU Limits, Memory Request and Memory Limit for both cache and Database
+
+
+
+
+
+> [!IMPORTANT]
+> Ensure your cluster has a **Storage Class** defined to fulfill the PVC requests for both the Cache and the Database.
+
+#### Domain White List and Proxy Servers
+
+See [Domain White List and Proxy Servers](../common-config/#domain-white-list-and-proxy-servers) in the Common Configuration guide for whitelisting domains, proxy servers, and login/logout URLs.
+
+
+#### KubeStash
+KubeDB Platform uses **KubeStash** for automated backups and disaster recovery.
+
+* **Retention Policy:** Define how long backups are kept (e.g., `keep-1mo`).
+* **Schedule:** Set the backup frequency using Cron syntax (default: `0 */2 * * *` or every 2 hours).
+* **Storage Secret:** Select the secret containing credentials for your cloud provider.
+
+### 7. Monitoring
+
+See [Monitoring](../common-config/#monitoring) in the Common Configuration guide for Alertmanager email and webhook configuration.
+
+### 8. Infra
+
+* **Cloud Services:** Configure your **Provider** (e.g., AWS, GCP, Azure), **Bucket Name**, **Endpoint**, **Region** and **Prefix**. In the **Auth Section** put your `AWS Access Key ID`,`AWS Secret Access Key` and `CA CERT Data`
+* **StorageClass:** Select your StorageClass in this section
+* **TLS:** Configure TLS certificates for secure communication. You can choose the Issuer type from the following list.
+ * **External**: Use this if you already have certificates from an external provider.
+ * CA CERT: Paste the Certificate Authority certificate.
+ * Certificate CERT: Paste the certificate issued for your domain.
+ * Certificate Key: Paste the private key associated with the certificate.
+
+ * **CA:** Use this if you want AppsCode to manage your certificates with its internal CA.
+ * CA CERT: Paste the internal CA certificate.
+ * CA Key: Paste the internal CA key.
+ * **letsencrypt:** Use this for production environments to obtain globally trusted SSL/TLS certificates.
+ * **letsencrypt-staging:** Use this for testing your installation
+
+### 9. Ingress & Gateway
+See [Ingress & Gateway](../common-config/#ingress--gateway) in the Common Configuration guide for exposing the platform via the Gateway API or standard Ingress.
+
+### 10. NATS
+
+See [NATS](../common-config/#nats) in the Common Configuration guide for configuring the internal messaging system (expose method, replicas, and resources).
+
+### 11. Self Management
+See [Self Management](../common-config/#self-management) in the Common Configuration guide to enable or disable platform features.
+
+### 12. Branding & UI Customization
+See [Branding & UI Customization](../common-config/#branding--ui-customization) in the Common Configuration guide to re-brand the platform interface.
+
+### 13. Generate Installer and Documentation
+
+Click the "Deploy" button to submit your information. KubeDB Platform will generate the installer and provide the necessary documentation.
+
+### 14. Deploy KubeDB Platform
+
+Follow the documentation provided by AppsCode to deploy the KubeDB Platform on your system.
+
+### 15. Explore the Deployed Platform
+
+Once deployed, access the **KubeDB Platform** using the specified domain. Log in with the admin account credentials provided during the creation process.After the login process you will see the **KubeDB Platform dashboard** user interface
+
+
+
+
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/install/troubleshoot.md b/content/docs/platform/v2026.7.10/selfhost-setup/install/troubleshoot.md
new file mode 100644
index 0000000000..747e8e8e00
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/install/troubleshoot.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-setup-install-troubleshoot
+ name: Troubleshooting
+ parent: selfhosted-installer
+ weight: 10
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Troubleshooting Common Errors
diff --git a/content/docs/platform/v2026.7.10/selfhost-setup/uninstall.md b/content/docs/platform/v2026.7.10/selfhost-setup/uninstall.md
new file mode 100644
index 0000000000..2ea435816d
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/selfhost-setup/uninstall.md
@@ -0,0 +1,18 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: selfhost-setup-uninstall
+ name: Uninstall
+ parent: selfhost-setup
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: selfhost-setup
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Uninstall
diff --git a/content/docs/platform/v2026.7.10/support.md b/content/docs/platform/v2026.7.10/support.md
new file mode 100644
index 0000000000..71ad5e954f
--- /dev/null
+++ b/content/docs/platform/v2026.7.10/support.md
@@ -0,0 +1,22 @@
+---
+layout: docs
+menu:
+ docsplatform_v2026.7.10:
+ identifier: platform-support
+ name: Support
+ parent: welcome
+ weight: 20
+menu_name: docsplatform_v2026.7.10
+section_menu_id: welcome
+info:
+ kubedb-installer: v2026.7.10
+ kubeops-installer: v2026.7.10
+ product: kubedbplatform
+ version: v2026.7.10
+---
+
+# Support
+
+To speak with us, please leave a message on our [website](https://appscode.com/contact/). To receive product announcements, follow us on [Twitter](https://twitter.com/AppsCodeHQ).
+
+If you have found a bug with KubeDB or want to request for new features, please file an issue.
diff --git a/data/products/kubedbplatform.json b/data/products/kubedbplatform.json
index 40e225a87c..e76db5fff5 100644
--- a/data/products/kubedbplatform.json
+++ b/data/products/kubedbplatform.json
@@ -156,6 +156,15 @@
"hostDocs": false,
"show": true
},
+ {
+ "version": "v2026.7.10",
+ "hostDocs": true,
+ "show": true,
+ "info": {
+ "kubedb-installer": "v2026.7.10",
+ "kubeops-installer": "v2026.7.10"
+ }
+ },
{
"version": "v2026.6.19",
"hostDocs": true,
@@ -176,7 +185,7 @@
"show": true
}
],
- "latestVersion": "v2026.6.19",
+ "latestVersion": "v2026.7.10",
"socialLinks": {
"facebook": "https://facebook.com/appscode",
"github": "https://github.com/kubedb",
diff --git a/firebase.json b/firebase.json
index 098e3efa2f..1e0507eca3 100644
--- a/firebase.json
+++ b/firebase.json
@@ -44,17 +44,17 @@
"redirects": [
{
"source": "/docs/platform/latest/",
- "destination": "/docs/platform/v2026.6.19/",
+ "destination": "/docs/platform/v2026.7.10+akp/",
"type": 302
},
{
"source": "/docs/platform/latest/:rest*",
- "destination": "/docs/platform/v2026.6.19/:rest",
+ "destination": "/docs/platform/v2026.7.10+akp/:rest",
"type": 302
},
{
"source": "/docs/platform",
- "destination": "/docs/platform/v2026.6.19/",
+ "destination": "/docs/platform/v2026.7.10+akp/",
"type": 302
},
{