Upsun vs AWS Fargate: when you want container orchestration without running Kubernetes yourself

"Container orchestration without running Kubernetes yourself" sounds like a single, well-defined ask. In practice, it covers two very different outcomes. One removes server management but leaves you configuring an orchestrator. The other removes the orchestrator itself. 

AWS Fargate is the first. Upsun is the second. Confusing the two is how teams end up disappointed with a platform that was never trying to solve their actual problem.

This piece breaks down what Fargate actually removes from your plate, what it still leaves on it, how Upsun's model differs, and which one fits which team.

What is Fargate?

Fargate is a serverless compute engine for containers. It is not an orchestrator on its own. It runs on top of either Amazon ECS or Amazon EKS, which handle the actual orchestration, scheduling, and networking decisions. Fargate's job is narrower: it removes the need to provision and manage the EC2 instances that would otherwise host your containers.

This distinction matters more than it sounds like it should, because it changes what "avoiding Kubernetes" means depending on which path you take:

• Fargate with EKS still means running Kubernetes. You write Kubernetes manifests, define Deployments and Services, and think in pods and namespaces. What Fargate removes is managing the worker nodes underneath. The orchestration layer, and its concepts, are still yours to learn and operate.
• Fargate with ECS avoids Kubernetes concepts entirely. Instead, you define ECS task definitions, services, and clusters, which is AWS's own orchestration model. You've swapped Kubernetes for a different, AWS-proprietary set of primitives, not removed the need for an orchestration layer altogether.

Either way, Fargate answers "who manages the servers," not "who manages the orchestration."

What Upsun removes that Fargate doesn't

Upsun's model skips the orchestration layer as a concept the developer needs to touch at all. There's no cluster, no task definition, no service definition, and no manifest. A single configuration file (.upsun/config.yaml) describes the application, its runtimes, and the services it depends on. The platform handles scheduling, networking, scaling, and failover underneath that file.

To make this concrete, here's what a standard containerized web application with a database typically requires to run in production on Fargate, compared to Upsun:

• Task or service definitions. Fargate: yes, including CPU/memory allocation, container image, ports, and IAM roles per task. Upsun: not exposed, defined once in the app config.
• Networking (VPC, subnets, security groups). Fargate: configured manually. Upsun: handled by the platform.
• Load balancing (ALB, target groups). Fargate: wired manually to each service. Upsun: handled by the platform.
• Orchestration objects (Deployments, Services, HPA, if running EKS). Fargate: yes, if Kubernetes is underneath. Upsun: not applicable, there's no orchestration layer exposed.
• Environment and staging parity. Fargate: built manually, typically with custom scripts and data sanitization pipelines. Upsun: every branch is a full clone of code, config, and data by default.
• Cluster and runtime upgrades. Fargate: your responsibility (EKS control plane, or ECS agent and runtime patching). Upsun: managed by the platform.

None of this means Fargate is poorly designed. It means "serverless" describes the compute layer, not the configuration work required around it.

Side-by-side comparison

Fargate's strengths

Fargate is a legitimate, common choice, and it's worth being direct about why:

• Fine-grained AWS integration. IAM roles, VPC networking, CloudWatch monitoring, and security groups all plug in natively, which matters for teams that need that level of control over networking and permissions.
• Hybrid flexibility within EKS. You can run some pods on Fargate and others on EC2-backed nodes in the same cluster, isolating variable or sensitive workloads without standing up a separate cluster.
• Per-second, per-task billing. You pay for the CPU and memory a task actually consumes, without paying for idle EC2 capacity.
• Compliance inheritance. Because Fargate runs on AWS's own infrastructure, it benefits from AWS's existing compliance programs, which can simplify parts of an audit for regulated workloads already committed to AWS. 
   

Fargate's trade-offs

• Configuration surface. Removing server management doesn't remove the rest of the wiring. Task definitions, services, target groups, load balancers, security groups, and IAM roles are all still yours to build and maintain, even though no one is provisioning EC2 instances by hand.
• Stateful workloads. Fargate supports both EFS and EBS, but EBS volumes attach to one task at a time and add setup overhead (snapshots, volume lifecycle, IAM for volume provisioning). Most teams still pair Fargate with a separate managed database service like RDS rather than running a database directly on an attached volume.
• Provider lock-in. Fargate only runs on AWS. If a customer contract, a cost renegotiation, or a compliance requirement means moving to a different cloud provider, Fargate has no path for that. The application and its orchestration configuration are tied to AWS specifically.

Upsun's model

Upsun's approach is to standardize the primitives that Fargate (and the orchestrator underneath it) leaves exposed, and remove them from the developer's day-to-day work entirely:

• One configuration file defines the application, its runtimes, and its services (databases, caches, search), and how they connect. No task definitions, no manifests, no cluster to reason about.
• Environment parity by default. Every branch gets a full clone of code, configuration, and sanitized production data, rather than a simplified staging approximation built by hand.
• Day 2 operations are the platform's job. Cluster upgrades, runtime patching, and provider API compatibility are managed by Upsun, not by your own engineers on call.
• Broad language support. Upsun runs containerized applications across supported runtimes including PHP, Python, Node.js, Java, Go, Ruby, and .NET.
• Compliance applied consistently. ISO/IEC 27001, SOC 2 Type 2, PCI DSS Level 1, HIPAA, and TX-RAMP apply the same way across every environment, not just production.

Upsun's trade-offs

• Infrastructure control. Upsun's abstraction is the same thing that makes it simple: it also means less granular control over networking topology, instance types, or low-level orchestration behavior. Teams that need to hand-tune those details, or that need GPU-backed instances for specialized workloads, are trading away control they might actually want.
• Not Kubernetes-native. If your organization has standardized on Kubernetes tooling, such as Helm charts, custom operators, or CNCF-ecosystem integrations, Upsun doesn't give you that layer to plug into. It replaces it rather than wrapping it.

Choosing between Fargate and Upsun

Choose Fargate if you're already committed to AWS, you have a platform team that wants and can own IAM, VPC, and networking configuration directly, and you're running workloads that benefit from fine-grained AWS-native control.

Choose Upsun if you want to deploy containerized applications without owning the orchestration layer at all, whether that's Kubernetes manifests or ECS task definitions, and you want environment parity and compliance handled consistently without building that tooling yourself.

If cloud provider flexibility matters as much as avoiding Kubernetes does, that's a related but separate question. See our comparison of Upsun, Fly.io, and Render on multi-cloud deployment for how each handles running the same application across different providers.

Frequently Asked Questions (FAQs)

Is AWS Fargate a Kubernetes alternative?  
Not exactly. Fargate is a compute layer that runs underneath ECS or EKS. If you use it with EKS, you're still running Kubernetes, just without managing the worker nodes. It replaces server management, not orchestration.

What does Upsun remove that Fargate doesn't?  
Task definitions, service definitions, load balancer wiring, security groups, and IAM roles per service. Upsun's application is described in one configuration file, and the platform handles the rest.

Can Fargate run a database directly?  
It supports both EFS and EBS now, but running a database directly still means managing volume attachment and lifecycle yourself. Most teams run Fargate alongside a separate managed database service like RDS instead.

Does Upsun support multiple cloud providers the way Fargate doesn't?  
Yes. Fargate only runs on AWS. Upsun deploys the same application configuration to AWS, Azure, Google Cloud, IBM Cloud, or OVHcloud, depending on what a given project needs.

Which platform gives more low-level infrastructure control?  
Fargate, by design. It exposes IAM, VPC, and networking configuration directly. Upsun trades that control for a smaller configuration surface and less operational ownership.