HCP Consul Pricing

  • Development

    Starting At
    $0.027/hr*

    *Regional costs may vary

    Get Started
    Included:OSS and Enterprise featuresSingle-node clusterDesigned for Testing and small POCsRecommended for up to 50 service instancesTiers:Extra-Small (2vCPU, 1 GiB RAM) - $0.027/hrSupport:Email support

  • Standard

    Starting At
    $0.069/hr*

    *Price scales with active service instances

    Get Started
    Included:OSS and Enterprise FeaturesProduction Ready EnvironmentFlexible Deployment Sizing Packages AvailableTiers:Small (2vCPU, 8 GiB RAM) - $0.069/hr plus $0.02/hr per service instanceMedium (4vCPU, 16 GiB RAM) - $0.173/hr plus $0.015/hr per service instanceLarge (8vCPU, 32 GiB RAM) - $0.345/hr plus $0.0125/hr per service instanceSupport:Cloud SLA and support

  • Enterprise

    Annual and multi-year agreements

    Discounts available

    Contact Sales
    Included:Everything in Standard, plus:Dedicated Support OptionsEnterprise Use CasesTiers:Contact sales for more detailsSupport:Premium support and services
Have a question or need a custom solution?

Frequently Asked Questions

A service is a logical representation of an application or microservice that is registered in Consul. Service instances refers to one or more running versions of a given service, each tracked as a distinct provider of the service by Consul’s service registry. Multiple instances of a service are typically created to address scale and/or redundancy requirements from organizations.
HCP Consul offers the functionality of Consul OSS without the users also being responsible for maintaining, monitoring, and scaling their Consul deployment. Consul OSS does give users some greater controls for crafting a more custom implementation, where HCP Consul aims to simplify the deployment and management process while still enabling the desired capabilities and providing some additional enterprise capabilities.

While HCS on Azure and HCP Consul are both part of HashiCorp’s Cloud offerings, they have different models of consumption. HCS on Azure was designed to live within the Azure Marketplace as a native offering within Microsoft Azure. The backend infrastructure is still managed by HashiCorp, however the underlying billing is through the customers Azure account.

HashiCorp Cloud Platform (HCP) is a platform that was built by HashiCorp for both deploying and managing HashiCorp products natively in the cloud. Users are tenants on the HCP platform and the deployed products are run within the HashiCorp AWS environment. Customers deploy workloads into their AWS accounts/VPC’s and peer those workloads with the HCP Virtual Network (HVN) where their HCP workloads live. They are not responsible for the underlying AWS infrastructure that the cluster is running on.

Both solutions are designed to support organizations that plan on backing large, business critical applications with Consul’s networking capabilities. HCP Consul provides a quicker and simplified starting path, flexibility for organizations to start with smaller implementations and scale as needed, and the ability to offload the operational burden of maintaining a deployment.

Consul is a private installation and designed to give enterprises greater customization capabilities over the architecture and networking policies. This is critical for organizations with strict regulatory or security compliance policies not supported by hosted solutions.

Currently, yes. As we continue to evolve the platform more cloud options will become available.