Rebrand AppsCode Platform / ACE to KubeDB Platform

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

Author: tamalsaha

docs/platform/guides/account-management/kubernetes/credentials.md

@@ -29,7 +29,7 @@ Supported Credential Types include:
 - [Scaleway](#scaleway)
 - [Vultr](#vultr)
 
-Visit https://home.appscode.com/user/settings/credentials to manage credential.
+Visit https://appscode.com/id/{user}/user/settings/credentials to manage credential.
 
 
 ## AWS
@@ -261,7 +261,7 @@ Details:
     aws iam create-access-key --user-name "eks-cluster"
     ```
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create) you got from previous step.
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from previous step.
 
 <img  width="50%" src="images/aws-cred.png">
 
@@ -281,7 +281,7 @@ To configure Azure credentials for accessing and managing Azure Kubernetes Servi
 - Save Credentials <br>
 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://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 
 <img align="right" width="50%" src="images/do-cred.png">
@@ -292,7 +292,7 @@ To access Digital Ocean Managed clusters, you need to create a API token from Di
 Ref: [How to Create a Personal Access Token](https://docs.digitalocean.com/reference/api/create-personal-access-token/)
 
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create) you got from Digital Ocean.
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from Digital Ocean.
 
 <br><br><br><br>
 
@@ -322,14 +322,14 @@ To access GKE clusters, you need to create a GCP service account with with conta
     --iam-account $GKE_SA_EMAIL
     ```
 
-Then add the service account credentials [here](https://home.appscode.com/user/settings/credentials/create).
+Then add the service account credentials [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <img align="right" width="50%" src="images/gcp-oauth.png">
 
 ## Google OAuth
 
 Simplest way to access GKE clusters is through creating `Google OAuth` type credential. <br>
-Just head over [here](https://home.appscode.com/user/settings/credentials/create) and
+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`
@@ -349,15 +349,15 @@ To access LKE clusters, you need to create a API token from Linode with the foll
 Ref: [Manage Linode Personal Access Tokens](https://www.linode.com/docs/products/tools/api/guides/manage-api-tokens/)
 
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create) you got from Linode.
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create) you got from Linode.
 
 <br><br><br>
 
 <img align="right" width="50%" src="images/rancher-cred.png">
 
 ## Rancher
 
-To access Rancher clusters through AppsCode, you need to create an API token in your Rancher system. Follow these steps:
+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`.
@@ -369,7 +369,7 @@ Reference: [Rancher API Keys](https://ranchermanager.docs.rancher.com/reference-
 
 Copy the generated access key, secret key, and API endpoint from the `Account & API Keys` overview page.
 
-Next, add these credentials to the [AppsCode user settings credentials page](https://home.appscode.com/user/settings/credentials/create).
+Next, add these credentials to the [KubeDB Platform user settings credentials page](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <img align="right" width="50%" src="../images/credentials/azureStorage.png">
 
@@ -380,7 +380,7 @@ To access Azure Blob Storage, you need your Storage Account name and one of its
 - **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://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <br><br><br><br>
 
@@ -393,7 +393,7 @@ To access Cloudflare R2 Object Storage, you need your Account ID and an R2 API t
 - **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://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <br><br><br><br>
 
@@ -408,7 +408,7 @@ To access Hetzner Cloud resources, you need an API token and an SSH key.
 
 Ref: [Hetzner Cloud API Tokens](https://docs.hetzner.com/cloud/api/getting-started/generating-api-token/)
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <br><br><br>
 
@@ -423,7 +423,7 @@ To access Scaleway resources, you need your Organization ID and an API secret ke
 
 Ref: [Scaleway API Keys](https://www.scaleway.com/en/docs/iam/api-keys/)
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).
 
 <br><br><br>
 
@@ -437,4 +437,4 @@ To access Vultr resources, you need a Vultr API key.
 
 Ref: [Vultr API](https://www.vultr.com/api/)
 
-Then add the credential [here](https://home.appscode.com/user/settings/credentials/create).
+Then add the credential [here](https://appscode.com/id/{user}/user/settings/credentials/create).

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 KubeDB Platform 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/billing-and-usage-guide/overview.md

@@ -18,7 +18,7 @@ This document provides a detailed overview of the **Usage** section within our b
 
 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.
+This section focuses on the **Usage** dashboard, which shows the resources consumed by downstream KubeDB Platform services like KubeDB running in your clusters.
 
 ![usage-dashboard](../images/usage-section-home.png)
 

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/_index.md

@@ -5,7 +5,7 @@ menu:
     identifier: guide-start
     name: Get Started
     parent: guides
-    description: Basic information and instructions for first-time users of AppsCode
+    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

docs/platform/guides/get-started/add-cluster.md

@@ -13,7 +13,7 @@ section_menu_id: guides
 
 # Add a Kubernetes Cluster
 
-With your credentials in place, it's time to connect your Kubernetes cluster to the Platform Console. This step allows AppsCode to seamlessly manage and provide insights into your 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:
 

docs/platform/guides/get-started/add-credential.md

@@ -13,11 +13,11 @@ section_menu_id: guides
 
 # 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 AppsCode to seamlessly manage your clusters.
+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://home.appscode.com/user/settings/credentials/create).
+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.
 

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.