Rebrand AppsCode Platform / ACE to KubeDB Platform

Signed-off-by: Tamal Saha <tamal@appscode.com>

Author: tamalsaha

docs/platform/guides/account-management/site-administration/ace-upgrade.md

@@ -3,17 +3,17 @@ layout: docs
 menu:
   docsplatform_{{.version}}:
     identifier: account-management-siteadmin-ace-upgrade
-    name: ACE Upgrade
+    name: KubeDB Platform Upgrade
     parent: account-management-siteadmin
     weight: 60
 menu_name: docsplatform_{{.version}}
 section_menu_id: guides
 ---
 
 
-# ACE Upgrade
+# KubeDB Platform Upgrade
 
-Site administrators can upgrade the AppsCode Enterprise (ACE) management cluster directly from the platform UI by uploading a configuration file downloaded from the AppsCode portal.
+Site administrators can upgrade the KubeDB Platform management cluster directly from the platform UI by uploading a configuration file downloaded from the AppsCode portal.
 
 ---
 
@@ -27,21 +27,21 @@ Before starting the upgrade, download the required values file from the AppsCode
 
 ---
 
-## Step 1 — Open ACE Upgrade
+## Step 1 — Open KubeDB Platform Upgrade
 
-![ACE Version Page](../images/upgrade-version-1.png)
+![KubeDB Platform Version Page](../images/upgrade-version-1.png)
 
-Go to **SITE ADMINISTRATION > ACE Upgrade** from the left-hand menu.
+Go to **SITE ADMINISTRATION > KubeDB Platform Upgrade** from the left-hand menu.
 
-The page displays the current ACE version and the upgrade status of all platform components. Click the **Upgrade Version** button at the top right to begin.
+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
 
 ![Upload Values File](../images/upgrade-version-2.png)
 
-On the **Upgrade ACE** screen:
+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.

docs/platform/guides/cluster-management/cluster-features.md

@@ -37,7 +37,7 @@ The Feature Sets grid on the Cluster Overview page shows all available product m
 | **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 ACE. |
+| **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. |

docs/platform/guides/cluster-management/cluster-overview.md

@@ -88,7 +88,7 @@ Scroll down past the **Basic** section to see the **Feature Sets** grid. Each ca
 | **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 ACE |
+| **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 |

docs/platform/guides/cluster-management/cluster-upgrade.md

@@ -11,12 +11,12 @@ section_menu_id: guides
 ---
 
 
-# Upgrading Your ACE Platform: Management, Imported, and Spoke Clusters
+# Upgrading Your KubeDB Platform: Management, Imported, and Spoke Clusters
 
 ## Overview
 
-This guide walks through upgrading an **AppsCode Container Engine (ACE)** deployment
-across all cluster tiers — the base management cluster, the AC cluster, general imported
+This guide walks through upgrading 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`.
 
@@ -25,17 +25,17 @@ clusters, and spoke clusters. The example below upgrades from release `2025.5.16
 ## Architecture
 
 ```
-                    ┌─────────────────────────┐
-                    │   Management Cluster     │
-                    │   (ACE control plane)    │
-                    └────────────┬────────────┘
-                                 │
-              ┌──────────────────┼──────────────────┐
-              │                  │                  │
-   ┌──────────▼──────┐  ┌────────▼────────┐   ┌─────▼──────────┐
-   │  ACE Cluster    │  │ Imported Cluster │  │ Spoke Cluster  │
-   │ (management)    │  │ (generic import) │  │ (generic import│
-   └─────────────────┘  └─────────────────┘   └────────────────┘
+                    ┌─────────────────────────────────┐
+                    │       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.
@@ -104,10 +104,10 @@ Once the job completes, verify the op-center feature set reflects the new versio
 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 → ACE**.
+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 ACE Resources → Update Version → Yes**.
+4. Click **Update KubeDB Platform Resources → Update Version → Yes**.
 
 ![Upgrade](images/upgrade/upgrade_1.png)
 
@@ -144,7 +144,7 @@ visible immediately.
 
 After **all** individual clusters are on the new version:
 
-1. In the Console, go to **Your Organization → Hub Cluster → ACE**.
+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**.
 
@@ -194,7 +194,7 @@ appscode.com → Download val file
        ↓
 Platform UI → Update Version (Management / Platform cluster)
        ↓
-Console → Generic DBaaS → Update AC Resources (each spoke)
+Console → Generic DBaaS → Update KubeDB Platform Resources (each spoke)
        ↓
 Console → Generic DBaaS → Update Cluster Set
        ↓

docs/platform/guides/get-started/architecture.md

@@ -15,14 +15,14 @@ Let's first discuss some basic terminologies, those will be repeated many times
 
 ![architecture](../images/architecture.png)
 
-### ACE
-ACE 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. 
+### 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. 
-ACE is used as the hub of OCM mode. Thats why we call this `Hub cluster` too.
+KubeDB Platform is used as the hub of OCM mode. Thats why we call this `Hub cluster` too.
 
-The ACE cluster can be a single-node k3s cluster for staging or development. Or a full-fledged multi-node cluster for prod.
+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.
 
@@ -32,4 +32,4 @@ While importing, if someone make it a spoke, then cluster-manager-spoke features
 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 ACE & DBaaS clusters can be of any vendors like AWS, Azure, Google Cloud etc. It can be an on-prem cluster too.
+Both KubeDB Platform & DBaaS clusters can be of any vendors like AWS, Azure, Google Cloud etc. It can be an on-prem cluster too.

docs/platform/guides/get-started/requirements.md

@@ -3,17 +3,17 @@ layout: docs
 menu:
   docsplatform_{{.version}}:
     identifier: guide-ace-requirements
-    name: ACE Requirements
+    name: KubeDB Platform Requirements
     parent: guide-start
     weight: 14
 menu_name: docsplatform_{{.version}}
 section_menu_id: guides
 ---
 
-# Requirements to deploy ACE
-We will discuss the resources requirements. networking requirements & best practices for deploying your first ACE & 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 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 ACE Cluster
+## 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.
@@ -40,7 +40,7 @@ These are the required connectivities to everything work correctly:
 3. 4222  -  NATS.io port
 4. 4224  -  s3-proxy service port
 
-Here is a sample video on how you can setup ACE:
+Here is a sample video on how you can setup KubeDB Platform:
 <iframe width="560" height="315" src="https://www.youtube.com/embed/1diG8qq73f4?si=pisqA3gOrfO1wxlx" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
 
 ## Requirements for DBaaS Cluster
@@ -52,7 +52,7 @@ Minimum: Kubernetes cluster with 3 worker nodes, each with 8- 16GB ram, PVC supp
 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 ACE 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/ACE cluster.
+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 ACE!
+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!

docs/platform/guides/integrations/_index.md

@@ -5,7 +5,7 @@ menu:
     identifier: integrations
     name: Integrations
     parent: guides
-    description: Integrate ACE into your Kubernetes platform
+    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

docs/platform/guides/integrations/rancher-extension.md

@@ -24,33 +24,33 @@ Before proceeding, make sure you have:
 
 - A Rancher setup with access to the **Local** cluster.
 - An account on [appscode.com](https://appscode.com/).
-- The [ACE](https://appscode.com/docs/en/selfhost-setup/) platform deployed on your Rancher cluster.
+- The [KubeDB Platform](https://appscode.com/docs/en/selfhost-setup/) deployed on your Rancher cluster.
 
 ---
 
 ## 2. Deploying the KubeDB Rancher Extension
 
-### Step 1 – Deploy ACE
+### Step 1 – Deploy KubeDB Platform
 1. Create an account at [appscode.com](https://appscode.com/).
-2. Follow the [self-hosting ACE guide](https://appscode.com/docs/en/selfhost-setup/) to deploy ACE on your Rancher cluster.  
-   You can also watch this video tutorial for step-by-step instructions: [Self-Hosting ACE Video Guide](https://www.youtube.com/watch?v=1diG8qq73f4&list=PLoiT1Gv2KR1iqWFGkCozbLqYe31QMsQcX&index=2)
+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 ACE
-1. Visit your ACE URL and log in with your **admin account**. ![ACE URL](../images/ace-url.png)
+### Step 2 – Create a Rancher-Type Organization in KubeDB Platform
+1. Visit your KubeDB Platform URL and log in with your **admin account**. ![KubeDB Platform URL](../images/ace-url.png)
 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 ACE platform.
+   > The Sync Token is used to synchronize Rancher users into the KubeDB Platform.
 
 ![Create Organization](../images/organization-create.png)
 
 ---
 
 ### Step 3 – Sync Rancher Users 
 1. Go to **Organization Settings → Rancher Extension**. ![Organization Settings](../images/organization-settings.png)
-2. Click **Sync User** to import Rancher users into ACE. ![Sync User](../images/organization-settings-sync-users.png)
+2. Click **Sync User** to import Rancher users into KubeDB Platform. ![Sync User](../images/organization-settings-sync-users.png)
 
 ---
 
@@ -110,4 +110,4 @@ Follow these steps to install the KubeDB extension in Rancher:
 
 ✅ 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 ACE UI under the Rancher organization you created earlier before using the Rancher extension, or it won’t work.
+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.

docs/platform/guides/license-management/overview.md

@@ -29,7 +29,7 @@ While AppsCode administrators are responsible for the core lifecycle of contract
 
 ### 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., ACE, 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.
+- **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.
 <br> <br>
 - **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 AppsCode product licenses. This component is pivotal for administrators to monitor the cluster(s) `licences` and `events` of licensed products across their infrastructure.
 <br> <br>

docs/platform/selfhost-setup/install/aws-marketplace.md

@@ -14,7 +14,7 @@ section_menu_id: selfhost-setup
 
 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 **ACE**, you need to have the permissions to manage **EC2**, **IAM**, **CloudFormation** etc.
+To install **KubeDB Platform**, you need to have the permissions to manage **EC2**, **IAM**, **CloudFormation** etc.
 
 ### Prerequisite
 
@@ -267,7 +267,7 @@ These credentials define the primary super-user and the initial organizational s
 For openshift cluster toggle Red Hat OpenShift cluster and give Kube API Server endpoint 
 
 ### 4. Registry
-Ace requires access to various container registries and Helm repositories to pull necessary images and charts.
+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.
@@ -313,7 +313,7 @@ In this section you can enable or disable features. You can also create an initi
 
 
 ### 8. Branding & UI Customization
-Administrators can globally re-brand the Ace interface to match corporate identity.
+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`).