diff --git a/hosted_control_planes/index.adoc b/hosted_control_planes/index.adoc
index 2113559ae3..81514befe8 100644
--- a/hosted_control_planes/index.adoc
+++ b/hosted_control_planes/index.adoc
@@ -9,6 +9,7 @@ You can deploy {product-title} clusters by using two different control plane con
 toc::[]
 
 include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
+include::modules/hcp-mce-acm-relationship-intro.adoc[leveloffset=+1]
 include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
@@ -17,4 +18,4 @@ include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]
 * xref:../scalability_and_performance/using-node-tuning-operator.adoc#node-tuning-hosted-cluster_node-tuning-operator[Configuring node tuning in a hosted cluster]
 * xref:../scalability_and_performance/using-node-tuning-operator.adoc#advanced-node-tuning-hosted-cluster_node-tuning-operator[Advanced node tuning for hosted clusters by setting kernel boot parameters]
 
-include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
\ No newline at end of file
+include::modules/hosted-control-planes-concepts-personas.adoc[leveloffset=+1]
diff --git a/images/acm-mce-intro-diagram.png b/images/acm-mce-intro-diagram.png
new file mode 100644
index 0000000000..1217d941f0
Binary files /dev/null and b/images/acm-mce-intro-diagram.png differ
diff --git a/images/rhacm-flow.png b/images/rhacm-flow.png
new file mode 100644
index 0000000000..07cd886d65
Binary files /dev/null and b/images/rhacm-flow.png differ
diff --git a/modules/hcp-mce-acm-relationship-intro.adoc b/modules/hcp-mce-acm-relationship-intro.adoc
new file mode 100644
index 0000000000..6c32b4d04b
--- /dev/null
+++ b/modules/hcp-mce-acm-relationship-intro.adoc
@@ -0,0 +1,26 @@
+// Module included in the following assemblies:
+//
+// * hosted_control_planes/index.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="hcp-mce-acm-relationship-intro_{context}"]
+= Relationship between {hcp}, {mce-short}, and {rh-rhacm}
+
+You can configure {hcp} by using the {mce}. The multicluster engine is an integral part of {rh-rhacm-first} and is enabled by default with {rh-rhacm}. The {mce-short} cluster lifecycle defines the process of creating, importing, managing, and destroying Kubernetes clusters across various infrastructure cloud providers, private clouds, and on-premises data centers.
+
+The {mce-short} is the cluster lifecycle Operator that provides cluster management capabilities for {product-title} and {rh-rhacm} hub clusters. The {mce-short} enhances cluster fleet management and supports {product-title} cluster lifecycle management across clouds and data centers.
+
+.Cluster life cycle and foundation
+image::acm-mce-intro-diagram.png[Cluster life cycle and foundation]
+
+You can use the {mce-short} with {product-title} as a standalone cluster manager or as part of a {rh-rhacm} hub cluster.
+
+[TIP]
+====
+A management cluster is also known as the hosting cluster.
+====
+
+You can deploy {product-title} clusters by using two different control plane configurations: standalone or hosted control planes. The standalone configuration uses dedicated virtual machines or physical machines to host the control plane. With {hcp} for {product-title}, you create control planes as pods on a management cluster without the need for dedicated virtual or physical machines for each control plane.
+
+.{rh-rhacm} and the {mce-short} introduction diagram
+image::rhacm-flow.png[{rh-rhacm} and the {mce-short} introduction diagram]