HashiCorp Consul Enterprise

Commercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.

4 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

HashiCorp Consul authorization-bypass updates

HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses.

Scope: Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Health-check registration permissions and Kubernetes component ACL binding rules determine exposure.

Action: Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds.

Primary source · HCSEC-2026-50 · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    HashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud

  2. Operated by

    Your team

    Customer manages cluster nodes, TLS, ACLs, gossip keys, secret handling, snapshots, upgrades, service integrations and availability.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodHashiCorp Validated Design Terraform modules for AWS, Azure or Google Cloud
InfrastructureServers / containers
Consul Enterprise runs persistent server and client agents on customer infrastructure with consensus state, snapshots and network dependencies.
Licensing modelCommercial Only
Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.
LicenseCommercial Consul Enterprise license required for the selected validated design.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 6 documented · 6 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

The reviewed Enterprise pricing and Terraform deployment establish the licensed product, but not a current Consul Enterprise-specific Marketplace offer. HCP procurement is separate.

Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

Consul Enterprise price/edition material did not establish qualifying Marketplace charges and commitment treatment for the buyer agreement.

Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The OIDC authentication method requires self-managed Consul Enterprise 1.8.0+. It supports browser-based UI/CLI login through a configured IdP, with ACL tokens and claim mappings.

Self-managed Consul Enterprise, not HCP account SSO · Source ↗ · Reviewed 2026-11-17

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

Enterprise OIDC exchanges claims for ACL tokens; it does not establish a SCIM user/group lifecycle endpoint. HCP account SCIM was excluded.

Reviewed public evidence for HashiCorp Consul Enterprise; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed HashiCorp Consul Enterprise material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The Enterprise Terraform workflow configures cluster secrets and cloud permissions. Apply ACL, TLS/gossip, backup and key-management requirements rather than treating provisioning completion as a security review. Current advisory review: HCSEC-2026-49 and 50 cover health-check registration and consul-k8s cross-namespace authorization bypasses. Upgrade Consul Enterprise and consul-k8s to the applicable fixed or later builds.

Consul Enterprise deployment controls Fixed in Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18. · Source ↗ · Prior security-controls source ↗ · HCSEC-2026-50 ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The Enterprise licence-reporting guide explicitly allows manual utilization reporting for isolated installations. This resolves the reporting dependency, but the complete offline licence-renewal, identity, package and upgrade procedure for the selected deployment still needs confirmation.

Self-managed Consul Enterprise reporting; not blanket isolation of integrations · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The validated design provides provider-specific Terraform deployment for Consul Enterprise on AWS, Azure and Google Cloud. Configure the licence, secrets, network access and snapshot storage before production use.

Self-managed Enterprise validated Terraform deployment · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The design deploys a fault-tolerant Consul server cluster; service count, agent placement, traffic, mesh gateways and availability requirements determine total capacity. Human-user count does not size the service mesh.

Consul topology and workload boundary · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Consul Enterprise is proprietary commercial software. The separate Community Edition and HCP service do not determine this entry's entitlement.

HashiCorp Consul Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Specify service/agent count, mesh traffic, gateways and Enterprise server topology. Human users and 1 TB application data do not size a Consul service mesh. A complete monthly operating estimate is not established.

Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The vendor release API identifies 2.1.0+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-22. This is the API record-creation date, not a separately established publication date; verify the licensed release/support path before upgrading.

Enterprise-filtered release API snapshot; community and HCP releases excluded · Source ↗ · Versioned Enterprise binaries and checksums ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Scope & considerations

This entry covers Consul Enterprise, not HCP Consul and not the separately licensed Community Edition. The validated designs require a commercial license and production security material, including TLS certificates, ACL configuration and gossip encryption. Protect bootstrap tokens and snapshot storage and validate the selected module release before deployment. HCSEC-2026-49 and 50 cover a health-check registration authorization bypass and a consul-k8s cross-namespace ACL binding-rule bypass. Fixed builds are Consul Enterprise 2.1.0 or 1.21.19 and consul-k8s 2.1.0 or 1.8.18.

Category fit

Backend platforms
Provides service discovery, configuration, connectivity and service-mesh control for distributed application platforms.
DevOps
Automates service networking, health discovery and policy across deployment environments.

Compare within Backend platforms

  • Appwrite Self-HostedSelf-hosted backend services for authentication, databases, storage, functions and messaging.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
    • Northflank
    Customer-operated · Open Source / Open Core
  • Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Heroku
    Customer-operated · Open Source / Open Core
  • Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
    • AWS
    • Azure
    • Google Cloud
    • Alibaba Cloud
    • IBM Cloud
    Customer-operated · Commercial Only

Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Consul Enterprise Terraform deployments on AWS, Azure and Google Cloud ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      HashiCorp provides validated Terraform deployment paths for Consul Enterprise in customer AWS, Azure and Google Cloud environments. Customers manage the deployed cluster, security material and backups.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory