diff --git a/docs/content/en/docs/fleet-manager/application.md b/docs/content/en/docs/fleet-manager/application.md
index fc42e5222..f248f61b0 100644
--- a/docs/content/en/docs/fleet-manager/application.md
+++ b/docs/content/en/docs/fleet-manager/application.md
@@ -247,6 +247,10 @@ kubectl get po -A --kubeconfig=/root/.kube/kurator-member2.config
 
 Upon examining the respective clusters, you'll find that applications originating from the same source configuration have been distributed to different clusters based on their respective policy selector labels.
 
+## Playgroud
+
+Kurator uses killercoda to provide [applications demo](https://killercoda.com/965010e0-4f60-4a28-bf27-597d3kurator/scenario/application-example), allowing users to experience hands-on operations.
+
 ## CleanUp
 
 Use the following command to clean up the `gitrepo-kustomization-demo` application and related resources, like `gitRepository`, `kustomization`, `helmRelease`, etc.
diff --git a/docs/content/en/docs/setup/insatll-kurator.md b/docs/content/en/docs/setup/insatll-kurator.md
index 661d8e446..8d53c44d0 100644
--- a/docs/content/en/docs/setup/insatll-kurator.md
+++ b/docs/content/en/docs/setup/insatll-kurator.md
@@ -55,3 +55,7 @@ You should see output resembling:
   "platform": "linux/amd64"
 }
 ```
+
+## Playground
+
+Kurator uses killercoda to provide [Kurator install demo](https://killercoda.com/965010e0-4f60-4a28-bf27-597d3kurator/scenario/install-kurator), allowing users to experience hands-on operations.