Managed Nomad Hosting — production-ready from $11 a month
Flexible workload scheduler for containers, binaries, and batch jobs across clusters. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Nomad, no lock-in.
Nomad on ManageStacks is a workload scheduler and orchestrator from HashiCorp, deployed to your own AWS, Azure, or GCP region with flat per-app pricing from $11 a month ($25 on the Standard production plan). Platform teams use it to run containers, plain executables, and batch jobs on a cluster, as a simpler alternative to managed Kubernetes services such as Amazon EKS.
What does Nomad do, and why do teams deploy it?
Nomad is a scheduler written in Go that decides where jobs run across a pool of machines. Jobs are described in a declarative file and can use different drivers, so containers, Java applications, and ordinary binaries can share one cluster. Servers keep cluster state and elect a leader, while client agents run the workloads. It handles long-running services, scheduled batch work, and system jobs that must run on every node. It integrates with other HashiCorp tools for service discovery and secrets, and has a built-in web interface for inspecting jobs.
- Declarative job files for services, batch, and system jobs
- Task drivers for containers, executables, and Java applications
- Built-in web interface for inspecting jobs and allocations
- Rolling updates and canary deployments for services
- Server cluster with leader election for cluster state
- Parameterized and periodic jobs for batch workloads
Flexible workload scheduler for containers, binaries, and batch jobs across clusters
Nomad as a self-hosted alternative to Amazon EKS and Azure Kubernetes Service
Instead of paying per-seat fees to a SaaS vendor, teams self-host Nomad to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Nomad hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Nomad the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Nomad at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Nomad run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Nomad in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Nomad on ManageStacks
What is Nomad on ManageStacks?
Nomad is a workload orchestrator that schedules jobs onto a cluster of machines. ManageStacks runs the Nomad server in your own cloud account with SSL and backups, and your client nodes join it to receive work.
How does Nomad compare to Amazon EKS?
Amazon EKS is a managed Kubernetes control plane. Nomad is a different, generally smaller scheduler that handles containers and non-container workloads with job files rather than Kubernetes manifests. Pick it when you want simpler operations and are not tied to the Kubernetes ecosystem.
Can Nomad run things other than containers?
Yes. Task drivers let Nomad run Docker containers, Java applications, and raw executables on the same cluster. That is useful when you are migrating gradually, or when some workloads have never been containerized.
Can I move existing Nomad jobs to ManageStacks?
Job files are plain text, so they carry across to a new cluster once clients are joined and drivers are available. You keep full ownership of your job definitions and cluster state, and you can store the files in version control as you see fit.
How do I run periodic batch work in Nomad?
Define a job with the batch type and a periodic block containing a schedule. Nomad then launches new runs on that schedule and records each one, which you can review in the web interface or through the command line.
Other devtools tools on ManageStacks
WordPress
Open-source publishing platform for websites, blogs, and online applications
GitLab
Single DevOps platform for Git hosting, CI/CD pipelines, code review, and security scanning
Drupal
Open-source content management platform for structured, multi-author websites
Joomla
Open-source content management system for websites and online applications
Run Nomad without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $11/mo.