Running a handful of containers is easy. Running hundreds of them across dozens of servers, restarting the ones that crash, routing traffic to healthy instances, and rolling out updates without downtime is not — that’s the job of a container orchestrator. Three tools dominate this space in 2026: Kubernetes, the open-source standard; Amazon ECS, AWS’s own simpler alternative; and HashiCorp Nomad, the lightweight scheduler that handles containers and non-container workloads alike. They are not interchangeable, and the right pick depends heavily on how much operational complexity a team is willing to take on.
At a Glance
| Tool | License / Cost Model | Control Plane Cost | Best For | Learning Curve |
|---|---|---|---|---|
| Kubernetes | Open source (self-hosted) or managed via a cloud provider | Free self-hosted; $0.10/cluster/hour on Amazon EKS (standard support) | Large, multi-cloud or portable workloads with complex scaling needs | Steep |
| Amazon ECS | AWS proprietary service | Free — no orchestration fee at all | Teams already committed to AWS who want less operational overhead | Low to moderate |
| HashiCorp Nomad | Business Source License 1.1 (not OSI-approved open source since 2023) | Free (Community edition); Enterprise is quote-based, not publicly priced | Mixed fleets running containers alongside VMs, batch jobs, or raw binaries | Low to moderate |
Short Verdict
Kubernetes wins on ecosystem and portability but costs the most in engineering time to run well. Amazon ECS is the pragmatic choice if a team is AWS-only and wants orchestration without the Kubernetes tax — it genuinely has no control-plane fee. Nomad is the dark horse: a single lightweight binary that schedules containers, Java apps, and raw executables side by side, but it’s worth knowing upfront that it is no longer open source in the traditional sense, and its Enterprise pricing is not public.
What Each Tool Actually Is
Kubernetes is a Cloud Native Computing Foundation (CNCF) graduated project that automates deployment, scaling, and management of containerized applications. It’s cloud-agnostic by design — the same YAML manifests can, in principle, run on Amazon EKS, Google GKE, Azure AKS, or a self-managed cluster on bare metal. That portability comes with genuine operational weight: etcd, control-plane upgrades, networking plugins (CNI), and a sprawling ecosystem of add-ons that most teams end up needing (ingress controllers, service meshes, autoscalers).
Amazon ECS (Elastic Container Service) is AWS’s own orchestrator, tightly integrated with IAM, VPC networking, Application Load Balancer, and CloudWatch. It supports two launch types: the EC2 launch type, where you manage the underlying instances yourself, and Fargate, a serverless mode where AWS manages the servers and you simply specify how much vCPU and memory each task needs. ECS deliberately trades portability for simplicity — it only runs on AWS, but there’s no cluster software to patch or upgrade.
HashiCorp Nomad is a single-binary scheduler that treats containers as just one of several supported “task drivers” — it can also run raw executables, Java applications, QEMU virtual machines, and more, all from one tool. It has no etcd-equivalent dependency and is often praised for being easier to operate at small-to-mid scale than Kubernetes. Since August 2023, Nomad (along with most of HashiCorp’s products) has shipped under the Business Source License 1.1 rather than the Mozilla Public License it previously used — the source is visible on GitHub, but BUSL restricts competing commercial use, so it is not an OSI-approved open-source license. HashiCorp itself was acquired by IBM, which closed in 2025, and Nomad is now sold and supported as part of IBM’s HashiCorp product line.
Pricing Breakdown
| Tool | What You Actually Pay |
|---|---|
| Kubernetes (self-hosted) | $0 in licensing; you pay only for the servers it runs on. Operational/engineering-time cost is the real expense. |
| Amazon EKS (managed Kubernetes) | $0.10 per cluster per hour under standard support (first ~14 months after a Kubernetes version’s release), rising to $0.60 per cluster per hour once that version enters extended support — plus the cost of the EC2/Fargate capacity the pods run on, per AWS’s EKS pricing page. |
| Amazon ECS | No orchestration fee on either launch type. EC2 launch type: standard EC2/EBS rates only. Fargate launch type: billed per second (one-minute minimum) at roughly $0.000011244 per vCPU-second and $0.000001235 per GB-second in US East (N. Virginia), per AWS’s ECS pricing page — AWS does not publish a simple flat hourly rate, only these per-second figures. |
| Nomad Community | Free, self-hosted, under BUSL-1.1. |
| Nomad Enterprise / HCP Nomad | Not publicly priced. HashiCorp’s and IBM’s own pricing pages list rates for Terraform, Vault, Packer, and Boundary but do not list a Nomad Enterprise figure — it is sold through a sales quote. |
Pros and Cons
Kubernetes
- Pros: Enormous ecosystem (Helm, operators, service meshes); runs identically across any cloud or on-premises; the de facto industry standard, so hiring and documentation are easiest here.
- Cons: Steep learning curve; managed control planes still cost money per cluster; teams frequently need a dedicated platform engineer just to keep it healthy.
Amazon ECS
- Pros: Genuinely no orchestration fee; deep native integration with IAM, ALB, and CloudWatch; Fargate removes server management entirely.
- Cons: AWS-only — no portability to other clouds; smaller ecosystem of third-party tooling than Kubernetes; less flexible for teams with complex, custom scheduling needs.
HashiCorp Nomad
- Pros: Single lightweight binary, simple operational model; can schedule non-container workloads (VMs, batch jobs, raw binaries) alongside containers; lower overhead than Kubernetes at small-to-mid scale.
- Cons: No longer OSI-approved open source (BUSL-1.1 since 2023); much smaller ecosystem and community than Kubernetes; Enterprise pricing is opaque and quote-only.
Who It’s a Good Fit For
Choose Kubernetes if the team needs multi-cloud portability, already has (or is building) platform-engineering expertise, or needs the breadth of the CNCF ecosystem. Choose Amazon ECS if the organization is AWS-only, wants orchestration with the least possible operational burden, and doesn’t need to run outside AWS. Choose Nomad if the workload mix includes more than just containers — batch jobs, VMs, or legacy binaries — and the team wants a simpler single-binary tool, while accepting that its licensing is more restrictive than classic open source and that enterprise support pricing isn’t public.
Who Should Look Elsewhere
Small teams running a handful of services should think twice before adopting full Kubernetes — the operational overhead often outweighs the benefit at that scale, and a simpler option (ECS Fargate, or even a PaaS) usually gets the job done faster. Teams that need a strictly open-source (OSI-approved) license with no commercial-use restrictions should be cautious with Nomad given its BUSL-1.1 terms, and should confirm current licensing directly with HashiCorp/IBM before committing.
Bottom Line
There’s no universally “best” orchestrator — only the one that matches a team’s cloud strategy and appetite for operational complexity. Kubernetes remains the safest long-term bet for portability and hiring; Amazon ECS is the lowest-friction choice for AWS-committed teams; and Nomad is worth a serious look for mixed workloads, as long as its current licensing terms are acceptable for the use case.
FAQ
Is Kubernetes free?
The Kubernetes software itself is free and open source (CNCF project). What costs money is either the servers you run it on yourself, or a managed control plane like Amazon EKS, which charges $0.10–$0.60 per cluster per hour depending on Kubernetes version support status.
Does Amazon ECS really have no extra fee?
Correct — AWS’s own ECS pricing page states there is no additional charge for ECS orchestration on either the EC2 or Fargate launch type. You only pay standard rates for the compute, storage, and networking resources the tasks use.
Is HashiCorp Nomad still open source?
Its source code is publicly visible on GitHub, but since August 2023 it has been licensed under the Business Source License 1.1, not the Mozilla Public License it used before. BUSL is not an OSI-approved open-source license because it restricts certain competing commercial uses, even though the Community edition remains free to use for most purposes.
Can Nomad really run things other than containers?
Yes — Nomad’s “task driver” model supports Docker containers, raw executables (exec driver), Java applications, and QEMU virtual machines, among others, all managed by the same scheduler.
Sources
- Amazon ECS Pricing — AWS
- Amazon EKS Pricing — AWS
- Kubernetes — Production-Grade Container Orchestration (kubernetes.io)
- hashicorp/nomad on GitHub (license: BUSL-1.1)
- Nomad Pricing — HashiCorp
- IBM HashiCorp Pricing
Discover more from Software Online Review
Subscribe to get the latest posts sent to your email.
