Compute and cost
ScaleBop picks a compute target when it generates the deployment plan. You can override that choice under Advanced: compute preference. The change is saved immediately and applied the next time architecture is generated. It does not redeploy by itself.
Choices
Section titled “Choices”| Preference | When it fits |
|---|---|
| Auto | Default. Beanstalk for an Express or Node app without Docker when the environment is Lambda-safe; Fargate when a Dockerfile exists or environment variables exceed 4KB; Lambda for a serverless-native stack. |
| Elastic Beanstalk | A zip deployed with npm start on the Node.js platform. Lower always-on floor than Fargate with a load balancer. |
| Lambda + API Gateway | Small environment (under 4KB), a stateless API, or spiky traffic. Not offered when the known environment already exceeds 4KB. |
| ECS Fargate + ALB | Containers, streaming, a large environment, or native dependencies. Needs a Dockerfile, or ScaleBop generates a placeholder one. |
If the plan marks Fargate as recommended, that is because of the environment size or something analysis found in the repo. Auto will follow that signal unless you override it.
What the monthly range means
Section titled “What the monthly range means”The deployment plan and the cost hints show a rough monthly range for low or dev traffic in a typical US region. AWS bills that usage on your account. The range is not a quote. It does not include data transfer spikes, and it does not include ScaleBop’s own plan.
For a number you would budget against, use the AWS Pricing Calculator with the services listed on the plan.