hashicorp · boruszak · Nov 6, 2025 · Nov 6, 2025 · Nov 6, 2025 · Nov 6, 2025
@@ -145,7 +145,6 @@ Consul dataplanes on Kubernetes supports the following features:
 - Running Consul service mesh in AWS Fargate and GKE Autopilot is supported.
 - xDS load balancing is supported.
 - Servers running in Kubernetes and servers external to Kubernetes are both supported.
-- HCP Consul Dedicated is supported.
 - Consul API Gateway
 
 Consul dataplanes on ECS support the following features:
@@ -154,7 +153,7 @@ Consul dataplanes on ECS support the following features:
 - Mesh gateways
 - Running Consul service mesh in AWS Fargate and EC2
 - xDS load balancing
-- Self-managed Enterprise and HCP Consul Dedicated servers
+- Self-managed Enterprise servers
 
 ## Technical constraints and limitations
 

@@ -64,8 +64,4 @@ Platform-specific guidance is also available:
 ### AWS ECS
 
 - [Deploy Consul to ECS using the Terraform module](/consul/docs/deploy/server/ecs)
-- [Deploy Consul to ECS manually](/consul/docs/deploy/server/ecs/manual)
-
-### HCP Consul Dedicated
-
-To learn about how to deploy HCP Consul Dedicated servers, refer to [Deploy servers on HCP Consul](/consul/docs/deploy/server/hcp). You can access the UI workflow to deploy Dedicated clusters from [the HCP portal](https://portal.cloud.hashicorp.com).
+- [Deploy Consul to ECS manually](/consul/docs/deploy/server/ecs/manual)
@@ -43,11 +43,4 @@ The process to deploy a Consul client agent depends on your runtime:
 The process to deploy a Consul dataplane depends on your runtime:
 
 - [Deploy Consul dataplanes on Kubernetes](/consul/docs/deploy/workload/dataplane/k8s)
-- [Deploy Consul dataplanes on AWS ECS](/consul/docs/deploy/workload/dataplane/ecs)
-
-### HCP Consul Dedicated 
-
-When you use HCP Consul Dedicated clusters, you must deploy Consul alongside your workloads. Refer to the following pages in the [HCP Consul Dedicated documentation](/hcp/docs/consul):
-
-- [Deploy Consul clients](/hcp/docs/consul/dedicated/clients)
-- [Deploy Consul dataplanes](/hcp/docs/consul/dedicated/dataplanes)
+- [Deploy Consul dataplanes on AWS ECS](/consul/docs/deploy/workload/dataplane/ecs)
@@ -29,7 +29,7 @@ Refer to the following documentation and tutorials for additional guidance.
 
 ### Tutorials
 
-- [Integrate your AWS ECS services into Consul service mesh](/consul/tutorials/cloud-integrations/consul-ecs): Shows how to use Terraform to run Consul service mesh applications on ECS with self-managed Enterprise or HCP Consul Dedicated.
+- [Integrate your AWS ECS services into Consul service mesh](/consul/tutorials/cloud-integrations/consul-ecs): Shows how to use Terraform to run Consul service mesh applications on ECS with Consul Enterprise.
 
 You can also refer to the following example configurations:
 

@@ -67,14 +67,6 @@ The following features are [available in several forms of Consul Enterprise](#co
 The method of accessing Consul Enterprise and its features depends on the whether using
 HashiCorp Cloud Platform or self-managed Consul Enterprise.
 
-### HCP Consul Dedicated
-
-No action is required to access Consul Enterprise in a
-[HashiCorp Cloud Platform](https://cloud.hashicorp.com/products/consul) installation.
-
-You can try out HCP Consul Dedicated for free. Refer to the
-[HCP Consul Dedicated product page](https://cloud.hashicorp.com/products/consul) for more details.
-
 ### Self-managed Consul Enterprise
 
 To access Consul Enterprise in a self-managed installation,

@@ -20,8 +20,6 @@ To get a trial license for CTS, you can sign-up for the [trial license for Consu
 ## Automatic License Retrieval
 CTS automatically retrieves a license from Consul on startup and then attempts to retrieve a new license once a day. If the current license is reaching its expiration date, CTS attempts to retrieve a license with increased frequency, as defined by the [License Expiration Date Handling](/consul/docs/nia/enterprise/license#license-expiration-handling).
 
-~> Enabling automatic license retrieval is recommended when using HCP Consul Dedicated, as HCP Consul Dedicated licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
-
 ## Setting the License Manually
 
 If a license needs to be manually set, choose one of the following methods (in order of precedence) to set the license:

@@ -120,10 +120,6 @@ Contact your organization's [HashiCorp account team](https://www.hashicorp.com/e
 
 The license files are not locked to a specific cluster or cluster node. The above changes apply to all nodes in a cluster.
 
-## Q: Will this impact HCP Consul?
-
-This will not impact HCP Consul.
-
 ## Q: Does this need to happen every time a node restarts, or is this a one-time check?
 
 Consul Enterprise binaries starting with 1.10.0+ent, will be subject to EULA check. Release 1.10.0+ent introduces the EULA check for trial licenses (non-trial licenses already go through EULA check during contractual agreement).

@@ -32,12 +32,6 @@ To run Consul Enterprise, you must configure Consul agents with an Enterprise li
 
 To learn more about Consul Enterprise and its features, refer to [Consul Enterprise](/consul/docs/enterprise).
 
-## HCP Consul Dedicated
-
-HCP Consul Dedicated is the networking software as a service (SaaS) product available through the HashiCorp Cloud Platform (HCP). This service provides simplified workflows for common Consul tasks and the option to have HashiCorp set up and manage your Consul servers for you.
-
-On November 12, 2025, HashiCorp will end operations and support for HCP Consul Dedicated clusters. After this date, you will no longer be able to deploy new Dedicated clusters, nor will you be able to access, update, or manage existing Dedicated clusters. Refer to [Migrate Consul Dedicated cluster to self-managed Enterprise](/hcp/docs/consul/migrate) for more information.
-
 ### Additional tool binaries and maintained repositories
 
 We make several additional Consul CLI tools available as separate binary releases. These tools can simplify operations and processes for certain runtimes, cloud providers, or complex network requirements.
@@ -59,11 +53,6 @@ The following is a current list of Consul releases with active support:
 | `consul-template`           | Consul Template                          | Use templates to update Consul configurations dynamically using Go syntax.                                                                |
 | `consul-terraform-sync`     | Consul-Terraform-Sync (CTS)              | Dynamically manage network infrastructure, nearly in real-time.                                                                           |
 
-The following is a list of Consul tools that were used by previous versions of Consul. Some tools may be useful when performing Consul updates with especially large release gaps, while others were deprecated entirely.
-
-- `consul-api-gateway`. This feature was fully integrated into the `consul` package in v1.16.
-- `consul-telemetry-collector`. This tool was developed to support [HCP Consul Central](/hcp/docs/consul/concepts/consul-central).
-
 Consul also supports integrations with tools developed by our community. Refer to [Community tools](/consul/docs/integrate/consul-tools) for more information.
 
 ## Next steps

@@ -17,7 +17,7 @@ The program is intended to be largely self-service with links to resources, code
 
 ## Categories of Consul Integrations
 
-By leveraging Consul's RESTful HTTP API system, prospective partners are able to build extensible integrations at the data plane, platform, and the infrastructure layer to extend Consul's functionalities. These integrations can be performed both with the community edition of Consul, Consul Enterprise, and HCP Consul.
+By leveraging Consul's RESTful HTTP API system, prospective partners are able to build extensible integrations at the data plane, platform, and the infrastructure layer to extend Consul's functionalities. These integrations can be performed both with the community edition of Consul and Consul Enterprise.
 
 **The Consul ecosystem of integrations:**
 
@@ -37,26 +37,17 @@ By leveraging Consul's RESTful HTTP API system, prospective partners are able to
 
 -> **Network Infrastructure Automation (NIA)***: These integrations leverage Consul's service catalog to seamlessly integrate with Consul-Terraform-Sync (CTS) to automate changes in network infrastructure via a publisher-subscriber method. Refer to the [NIA documentation](/consul/docs/integrate/nia) for details.
 
-**HCP Consul**: HCP Consul is secure by default and offers an out-of-the-box service mesh solution to streamline operations without the hassle of managing Consul servers. [Sign up for a free HCP Consul account](https://cloud.hashicorp.com/products/consul).
-
-@include 'alerts/hcp-dedicated-eol.mdx'
-
-**Consul integration verification badges**: Partners will be issued the Consul Enterprise badge for integrations that work with [Consul Enterprise features](/consul/docs/enterprise) such as namespaces. Partners will be issued the HCP Consul badge for integrations validated to work with [HCP Consul](/hcp/docs/consul#features). Each badge would be displayed on HashiCorp's partner page as well as be available for posting on the partner's own website to provide better visibility and differentiation of the integration for joint customers.
+**Consul integration verification badges**: Partners will be issued the Consul Enterprise badge for integrations that work with [Consul Enterprise features](/consul/docs/enterprise) such as namespaces. Each badge would be displayed on HashiCorp's partner page as well as be available for posting on the partner's own website to provide better visibility and differentiation of the integration for joint customers.
 
 <span style={{display:'block', textAlign:'center'}}>
 <ImageConfig inline height={192} width={192}>
 
 ![Consul Enterprise Badge](/img/consul_enterprise_partner_badge.png)
 
-</ImageConfig>
-<ImageConfig inline height={192} width={192}>
-
-![HCP Consul](/img/HCPc_badge.png)
-
 </ImageConfig>
 </span>
 
-Developing a valid integration with either Consul Enterprise or HCP Consul also qualifies the partner for the Premier tier of the HashiCorp Technology Partners program. The process for verification of these integrations is detailed below.
+Developing a valid integration with Consul Enterprise also qualifies the partner for the Premier tier of the HashiCorp Technology Partners program. The process for verification of these integrations is detailed below.
 
 ## Development Process
 
@@ -89,8 +80,6 @@ Here are links to resources, documentation, examples and best practices to guide
 
 - [Consul Telemetry Documentation](/consul/docs/reference/agent/telemetry)
 - [Monitoring Consul with Datadog APM](https://www.datadoghq.com/blog/consul-datadog/)
-- [Monitor HCP Consul with New Relic Instant Observability](https://github.com/newrelic-experimental/hashicorp-quickstart-annex/blob/main/hcp-consul/README.md)
-- [HCP Consul and CloudFabrix AIOps Integration](https://bot-docs.cloudfabrix.io/Bots/consul/?h=consul)
 - [Consul and SnappyFlow Full Stack Observability](https://docs.snappyflow.io/docs/Integrations/hcp_consul)
 
 **Network Performance Monitoring (NPM)**
@@ -169,21 +158,6 @@ Here are links to resources, documentation, examples and best practices to guide
 
 The only knowledge necessary to write a plugin is basic command-line skills and knowledge of the [Go programming language](http://www.golang.org). Use the plugin interface to develop your integration. All integrations should contain unit and acceptance testing.
 
-**HCP Consul**:  As a managed service, minimal configuration is required to deploy HCP Consul server clusters. You only need to install Consul client agents. Furthermore, HashiCorp provides all new users an initial credit, which provides approximately two months worth of [development cluster](https://cloud.hashicorp.com/products/consul/pricing) access. When deployed with AWS or Azure free tier services, there should be no cost beyond the time spent by the designated tester. Refer to the [Deploy HCP Consul tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy) for details on getting started.
-
-HCP Consul is currently only deployed on AWS and Microsoft Azure, so your application can be deployed to or run in AWS or Azure. 
-
-#### HCP Consul Resource Links:
-
-@include 'alerts/hcp-dedicated-eol.mdx'
-
-- [Getting Started with HCP Consul](/consul/tutorials/get-started-hcp/hcp-gs-deploy)
-- [HCP Consul End-to-End Deployment](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-overview)
-- [Deploy HCP Consul with EKS using Terraform](/consul/tutorials/cloud-deploy-automation/consul-end-to-end-eks)
-- [HCP Consul Deployment Automation](/consul/tutorials/cloud-deploy-automation)
-- [HCP Consul documentation](/hcp/docs/consul/usage)
-
-**Consul Enterprise**: An integration qualifies for Consul Enterprise when it is tested and compatible with Consul Enterprise Namespaces.
 
 ### 4. Review and Approval
 

@@ -12,7 +12,6 @@ HashiCorp Consul is a service networking solution that enables teams to manage s
 > **Hands-on**: Complete the Getting Started tutorials to learn how to deploy Consul:
 - [Get Started on Kubernetes](/consul/tutorials/get-started-kubernetes)
 - [Get Started on VMs](/consul/tutorials/get-started-vms)
-- [HashiCorp Cloud Platform (HCP) Consul Dedicated](/consul/tutorials/get-started-hcp)
 
 ## How does Consul work?
 
@@ -76,16 +75,10 @@ Rolling out changes can be risky, especially in complex network environments. Up
 
 HashiCorp offers core Consul functionality for free in the community edition, which is ideal for smaller businesses and teams that want to pilot Consul within their organizations. As your business grows, you can upgrade to Consul Enterprise, which offers additional capabilities designed to address organizational complexities of collaboration, operations, scale, and governance.
 
-### HCP Consul Dedicated
-
-@include 'alerts/hcp-dedicated-eol.mdx'
-
-HashiCorp Cloud Platform (HCP) Consul is our SaaS that delivers Consul Enterprise capabilities and shifts the burden of managing the control plane to us. Create an HCP organization and leverage our expertise to simplify control plane maintenance and configuration. Learn more at [HashiCorp Cloud Platform](https://cloud.hashicorp.com/products/consul). 
-
 ## Community
 
 We welcome questions, suggestions, and contributions from the community.
 
 - Ask questions in [HashiCorp Discuss](https://discuss.hashicorp.com/c/consul/29).
-- Read our [contributing guide](https://github.com/hashicorp/consul/blob/main/.github/CONTRIBUTING.md).
+- [Contribute to our documentation](https://github.com/hashicorp/web-unified-docs).
 - [Submit a Github issue](https://github.com/hashicorp/consul/issues/new/choose) for feature requests and bug reports.
@@ -77,13 +77,10 @@ Consul server agents are an important part of Consul’s architecture. This sect
 
 Consul servers can be deployed on a few different runtimes:
 
-- **HashiCorp Cloud Platform (HCP) Consul (Managed)**. These Consul servers are deployed in a hosted environment managed by HCP. To get started with HCP Consul servers in Kubernetes or VM deployments, refer to the [Deploy HCP Consul tutorial](/consul/tutorials/get-started-hcp/hcp-gs-deploy).
 - **VMs or bare metal servers (Self-managed)**. To get started with Consul on VMs or bare metal servers, refer to the [Deploy Consul server tutorial](/consul/tutorials/get-started-vms/virtual-machine-gs-deploy). For a full list of configuration options, refer to [Agents Overview](/consul/docs/fundamentals/agent).
 - **Kubernetes (Self-managed)**. To get started with Consul on Kubernetes, refer to the [Deploy Consul on Kubernetes tutorial](/consul/tutorials/get-started-kubernetes/kubernetes-gs-deploy).
 - **Other container environments, including Docker, Rancher, and Mesos (Self-managed)**.
 
-@include 'alerts/hcp-dedicated-eol.mdx'
-
 When operating Consul at scale, self-managed VM or bare metal server deployments offer the most flexibility. Some Consul Enterprise features that can enhance fault tolerance and read scalability, such as [redundancy zones](/consul/docs/manage/scale/redundancy-zone) and [read replicas](/consul/docs/manage/scale/read-replica), are not available to server agents on Kubernetes runtimes. To learn more, refer to [Consul Enterprise feature availability by runtime](/consul/docs/enterprise#feature-availability-by-runtime).
 
 ### Number of Consul servers