App Runner vs Fargate cost: managed simplicity or container control

Quick answer

App Runner is a fully managed container service that handles build, deploy, load balancing, and scaling for you, billing for provisioned compute and memory plus active request handling, with a lower-cost provisioned (idle) state when no requests arrive. Fargate runs containers on ECS or EKS with more control, billing per vCPU-hour and GB-hour continuously while tasks run, and can drop to zero tasks between uses. App Runner tends to cost more per unit of compute in exchange for bundling the operational layer, so it is cheaper in total for small teams valuing simplicity, while Fargate is cheaper at scale and for spiky workloads that can scale to zero. The choice is operational simplicity versus finer cost control.

App Runner and Fargate both let you run containers without provisioning servers, and teams often weigh them for the same web service or API. The difference is how much of the surrounding operational layer, build, deployment, load balancing, and scaling, each one bundles, and that bundling shows up in the price. Neither is universally cheaper; it depends on scale and how much you value the managed layer.

How each one bills

Factor	App Runner	Fargate
Compute billing	Provisioned vCPU/GB, plus active request compute	Per vCPU-hour and GB-hour while running
Idle state	Lower-cost provisioned (warm) rate	Scale to zero tasks between uses
Bundled operations	Build, deploy, load balancer, autoscaling	You configure via ECS/EKS
Control	Less, opinionated	More, granular

App Runner charges for the compute and memory you provision, with a reduced rate when the service is warm but idle (no active requests), plus the compute used to handle requests. It bundles the load balancer, deployment pipeline, and autoscaling into that price. Fargate charges per vCPU-hour (about $0.04048) and GB-hour (about $0.004445) for every task while it runs, and you add and pay separately for a load balancer and configure scaling yourself.

Where App Runner is cheaper in total

App Runner's per-unit compute is not the cheapest, but its bundling can make the total cheaper for small services. You avoid running and paying for a separate Application Load Balancer (roughly $16 or more per month plus data processing), you skip the engineering time to wire up ECS, and the idle provisioned rate keeps a low-traffic service inexpensive between requests. For a small team running a handful of web services, the all-in simplicity often wins on total cost of ownership.

Where Fargate is cheaper

At scale, Fargate's finer control pays off. You can right-size tasks precisely, use Fargate Spot for up to 70 percent off interruptible capacity, cover the steady baseline with a Compute Savings Plan, and scale to zero tasks for spiky workloads. None of those deeper levers are as available on App Runner. For a larger or spikier workload, the raw compute savings from Spot and right-sizing outweigh the value of App Runner's bundling, echoing the Fargate versus EC2 tradeoff one level down.

The load balancer factor

A hidden part of the comparison is the load balancer. App Runner includes request routing in its price, while a Fargate service typically sits behind an ALB you pay for separately. For a single small service, that ALB cost can tip the total toward App Runner. For many services sharing one ALB, the per-service load balancer cost shrinks and Fargate's advantage returns. Count the load balancer in the comparison, one of the line items easy to forget.

Choosing on cost

For small, low-traffic services where simplicity and a low idle rate matter and you would otherwise run a dedicated load balancer, App Runner is often cheaper in total. For larger, spikier, or cost-sensitive workloads where Spot, Savings Plans, right-sizing, and scale-to-zero matter, Fargate is cheaper. Estimate your traffic pattern, service count, and whether you need the deeper cost levers, then price both against the resource catalog so the total, load balancer included, is clear before you deploy.

FAQ

Is App Runner or Fargate cheaper?

It depends on scale. App Runner bundles build, deployment, load balancing, and autoscaling into its price and offers a low idle rate, so it is often cheaper in total for small, low-traffic services that would otherwise need a dedicated load balancer. Fargate gives finer control, including Fargate Spot, Savings Plans, and scale-to-zero, so it is cheaper for larger or spikier workloads where those deeper cost levers matter.

How does App Runner pricing work?

App Runner charges for the compute and memory you provision, with a reduced rate when the service is warm but idle (no active requests), plus the compute used to handle requests. That price bundles the load balancer, deployment pipeline, and autoscaling, so you do not pay for or configure those separately. The per-unit compute is not the cheapest, but the bundling can make the total lower for small services.

When is Fargate cheaper than App Runner?

At scale and for spiky workloads. Fargate lets you right-size tasks precisely, use Fargate Spot for up to 70 percent off interruptible capacity, cover the baseline with a Compute Savings Plan, and scale to zero tasks between uses, deeper cost levers that App Runner does not expose as fully. For a larger or cost-sensitive workload, those savings outweigh the value of App Runner's bundled simplicity.

Does the load balancer affect the App Runner versus Fargate comparison?

Yes, significantly. App Runner includes request routing in its price, while a Fargate service typically sits behind an Application Load Balancer costing roughly $16 or more per month plus data processing. For a single small service, that separate ALB cost can tip the total toward App Runner. For many services sharing one ALB, the per-service load balancer cost shrinks and Fargate's advantage returns.

How does C3X help compare App Runner and Fargate?

C3X prices both an App Runner and a Fargate configuration from Terraform against a live catalog, including the load balancer a Fargate service needs, so you can compare the total cost for your traffic pattern before you deploy. That surfaces where App Runner's bundling wins for small services and where Fargate's Spot and right-sizing win at scale, as concrete monthly numbers in the pull request.

What to do next

Compare managed container options on total cost. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.