HashiCorp Nomad Enterprise

Commercial workload scheduler and orchestrator deployed as a multi-node cluster on customer cloud virtual machines.

5 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 Nomad Enterprise October 2026 security updates

HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths.

Scope: Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.

Namespace permissions, dispatch payload writes, allocation migration, and symlink handling determine exposure.

Action: Upgrade the installed maintained Enterprise branch to the listed fixed or later build.

Primary source · HCSEC-2026-52 · HCSEC-2026-53 · Reviewed 2026-11-18

What lands where

  1. Supplied by

    Vendor or project

    HashiCorp Validated Design Terraform modules where available or manual package and binary installation

  2. Operated by

    Your team

    Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades 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 where available or manual package and binary installation
InfrastructureServers / containers
Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.
Licensing modelCommercial Only
Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.
LicenseCommercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.

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 Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded.

Reviewed public evidence for HashiCorp Nomad 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

Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate.

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

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

Nomad documents OIDC SSO through external IdPs with ACL policies, roles and binding rules. Human and machine authentication are different flows; short-lived ACL tokens replace distributing static tokens.

Self-managed Nomad Enterprise identity design · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

Nomad OIDC maps identity claims to short-lived ACL tokens. A Nomad Enterprise SCIM lifecycle service was not established; HCP Terraform SCIM is a different product.

Reviewed public evidence for HashiCorp Nomad 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 Nomad 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 validated identity design requires appropriate ACL policies and mapped roles. Protect management tokens, configure TLS/gossip and snapshot recovery, and isolate workload client permissions from server administration. Current advisory review: HCSEC-2026-51 through 53 cover cross-namespace information disclosure and two symlink-based host or allocation escalation paths. Upgrade the installed maintained Enterprise branch to the listed fixed or later build.

Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18. · Source ↗ · Identity and access management ↗ · Prior security-controls source ↗ · HCSEC-2026-52 ↗ · HCSEC-2026-53 ↗ · 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 Nomad 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 documents customer-cloud Nomad installation on AWS, Azure and Google Cloud with servers, clients, networking and enterprise licensing. Review the design and pin the chosen deployment tooling before applying it.

Self-managed Enterprise validated cloud design · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

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

The cloud design separates voting/non-voting servers from workload clients across availability zones. Server count alone does not size user jobs, 1 TB application data, storage plugins or client failover capacity.

Nomad cluster topology versus workload capacity · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support.

HashiCorp Nomad 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

Illustrative priced infrastructure subtotal: USD 864.96/month. Six 4-vCPU/16-GiB server VMs follow the validated three-voting/three-non-voting design, with 50 GB gp3 each. This prices the control plane only; workload clients and their 1 TB data are unpriced. This is not a complete operating-cost estimate or a validated capacity/SLA claim.

Nomad Enterprise server control-plane subtotal; 100 identities do not size jobs, task concurrency or workload clients. Price applications and replicated workload storage separately. · Source ↗ · Product topology/sizing basis ↗ · Current AWS documentation: us-east-1 gp3 capacity example ↗ · EBS performance and charging qualifications ↗ · 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.1+ent as a supported, non-prerelease Enterprise build. Its record was created 2026-10-29. 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 scopes Nomad Enterprise rather than the separately licensed Community Edition. HashiCorp's validated cloud design requires a production multi-node topology, enterprise license, TLS and gossip encryption, protected snapshots and provider-specific infrastructure. Confirm the current validated module release and supported operating systems before deployment. HCSEC-2026-51, 52, and 53 cover cross-namespace information disclosure plus symlink-based allocation-directory escape and host permission modification. Fixed Enterprise builds are 2.1.0, 1.11.12, and 1.10.18.

Category fit

DevOps
Schedules and operates application, batch and system workloads across customer infrastructure.
Workflow orchestration
Coordinates long-running services, batch jobs and parameterized workload execution through declarative job specifications.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

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

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.

    • Nomad Enterprise validated cloud deployment 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's Validated Design documents production Nomad deployment on customer AWS, Azure and Google Cloud infrastructure. The operator supplies the Enterprise license and manages the resulting cluster.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory