
# HashiCorp Nomad Enterprise

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

Canonical page: https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## HashiCorp Nomad Enterprise

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

- Listing: https://launchinyourcloud.com/directory/hashicorp-nomad-enterprise/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Nomad Enterprise license required for the selected edition; Community Edition uses separate source-available terms.
- Licensing model: commercial-only
- Installation: HashiCorp Validated Design Terraform modules where available or manual package and binary installation
- Architecture: Customer-operated Nomad server quorum and client nodes with persistent state, networking and workload drivers.
- Operations: Customer manages servers and clients, TLS, gossip encryption, ACLs, snapshots, networking, workload drivers, upgrades and availability.
- Product website: https://www.hashicorp.com/en/products/nomad
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

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.

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

Production Nomad uses persistent server nodes for consensus and state plus client nodes that execute workloads on customer virtual machines.


### 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.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (checked 2026-11-17). 


### Cloud deployment evidence

- Nomad Enterprise validated cloud deployment on AWS, Azure and Google Cloud (aws, azure, gcp): https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment
  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.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Nomad validated cloud deployment: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment

- Nomad pricing and editions: https://www.hashicorp.com/en/products/nomad/pricing

- HCSEC-2026-51: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929

- HCSEC-2026-52: https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930

- HCSEC-2026-53: https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931

### Licensing sources

- https://www.hashicorp.com/en/products/nomad/pricing

### Infrastructure sources

- https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment


### Buyer diligence


Research coverage: 12/12 fields (100%); 6 documented, 6 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The Enterprise pricing and deployment material establishes licensed self-management, but not a current Nomad Enterprise-specific Marketplace offer. HCP/Vault offers were excluded. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Nomad Enterprise pricing did not establish offer-specific eligible charges against the buyer cloud agreement; infrastructure discounts are separate. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Single sign-on: Documented. 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. Scope: Self-managed Nomad Enterprise identity design. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- SCIM provisioning: Sources checked — unresolved. 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. Scope: Reviewed public evidence for HashiCorp Nomad Enterprise; unresolved within this edition/deployment. Source: https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. 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. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Security controls: Documented. 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. Scope: Nomad customer-managed cluster controls Fixed in Nomad Enterprise 2.1.0, 1.11.12, and 1.10.18.. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929 (reviewed 2026-11-18). Supporting source: Identity and access management — https://developer.hashicorp.com/validated-designs/nomad/administration-guide/identity-access-management. Supporting source: Prior security-controls source — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.

- Air-gapped operation: Sources checked — unresolved. 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. Scope: Self-managed Nomad Enterprise reporting; not blanket isolation of integrations. Source: https://developer.hashicorp.com/nomad/docs/enterprise/license/utilization-reporting (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. 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. Scope: Self-managed Enterprise validated cloud design. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- Minimum footprint / sizing: Documented. 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. Scope: Nomad cluster topology versus workload capacity. Source: https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment (reviewed 2026-11-17).

- License pricing: Documented. Nomad Enterprise is proprietary commercial software. Nomad Community Edition is separately distributed under source-available terms and does not grant Enterprise features or support. Scope: HashiCorp Nomad Enterprise: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.hashicorp.com/en/products/nomad/pricing (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. 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. Scope: 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: https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json (reviewed 2026-11-17). Supporting source: Product topology/sizing basis — https://developer.hashicorp.com/validated-designs/nomad/installation-guide/cloud-deployment. Supporting source: Current AWS documentation: us-east-1 gp3 capacity example — https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/cost.html. Supporting source: EBS performance and charging qualifications — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 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. Scope: Enterprise-filtered release API snapshot; community and HCP releases excluded. Source: https://api.releases.hashicorp.com/v1/releases/nomad/latest?license_class=enterprise (reviewed 2026-11-17). Supporting source: Versioned Enterprise binaries and checksums — https://releases.hashicorp.com/nomad/2.1.1+ent/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- HashiCorp Nomad Enterprise October 2026 security updates (security-advisory): 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. Conditions: 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. Source: https://discuss.hashicorp.com/t/hcsec-2026-51-nomad-vulnerable-to-cross-namespace-information-disclosure-in-multiple-endpoints/77929; reviewed 2026-11-18. Supporting source: HCSEC-2026-52 — https://discuss.hashicorp.com/t/hcsec-2026-52-nomad-dispatch-payload-writes-can-escape-the-allocation-directory-through-symlinks/77930. Supporting source: HCSEC-2026-53 — https://discuss.hashicorp.com/t/hcsec-2026-53-nomad-allocation-data-migration-may-allow-host-directory-permission-modification-via-symlink-following/77931.



