From cebbd905918d1e4f89eab423f62c5f8c2af2d314 Mon Sep 17 00:00:00 2001 From: ktroller Date: Fri, 28 Aug 2026 16:08:56 -0300 Subject: [PATCH] W-23997997: Clarify why on-premises is omitted from the control-plane matrix. Unregistered Mule is not a Runtime Manager deploy target. Registering the agent makes that instance Hybrid Standalone. --- hosting-home/modules/ROOT/pages/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hosting-home/modules/ROOT/pages/index.adoc b/hosting-home/modules/ROOT/pages/index.adoc index b57f0bae..986a7b46 100644 --- a/hosting-home/modules/ROOT/pages/index.adoc +++ b/hosting-home/modules/ROOT/pages/index.adoc @@ -115,7 +115,7 @@ For CloudHub 2.0 regions, identifiers, and DNS records, see xref:cloudhub-2::ch2 [[support-matrix-control-plane]] == Control Plane and Runtime Plane Compatibility -This matrix shows which runtime plane options are supported in each control plane. On-premises Mule does not require a control plane. If you register the Runtime Manager agent, that instance is Hybrid Standalone. +This matrix shows which runtime plane options you can deploy to from each control plane. On-premises runtimes aren't listed because they don't require a control plane. You install Mule and deploy applications to that instance. If you register the Runtime Manager agent so Anypoint Platform can manage that instance, it becomes a Hybrid Standalone runtime. See xref:mule-runtime::mule-standalone.adoc[Run Mule Runtime Engine On-Premises]. [%header%autowidth.spread] |===