Skip to content

Deploying

ScaleBop deploys your application into your AWS account. It does not host your app on shared infrastructure — it writes deployment files into your GitHub repository and runs them from your GitHub account.

  • infra/ — an AWS CDK project defining the infrastructure for your application.
  • .github/workflows/deploy.yml — the GitHub Actions workflow that runs the deployment.

ScaleBop opens these as a pull request, so you can review what will run before a deployment starts.

  1. Builds your application.
  2. Deploys the infrastructure with AWS CDK into your AWS account. For container apps, this step also pushes your Docker image and rolls the service out to it, rolling back automatically if the new version never becomes healthy.
  3. For static sites, publishes your built files to AWS.
  4. Runs a health check and confirms the deployed URL is serving your real application.

The workflow runs in your GitHub account and deploys with a short-lived role in your AWS account, assumed via OpenID Connect (OIDC). No long-lived AWS credentials live in the repository.

  • First launch: after the workflow files are merged, ScaleBop starts the first deployment from your default branch. You can also use Run deploy on your project hub.
  • After launch: the workflow deploys whatever is on the production branch. Use Ship changes on your project hub to move production up to your default branch. Commits to your default branch don’t go live until you ship them, unless you turn on Auto-ship.
  • Redeploy: Redeploy production on your project hub reruns the deployment for the commit already on production, for example after you change configuration.
  • From GitHub: run the workflow from the Actions tab.

If you build with an AI tool, see Keep building with your AI tool.


The pages in this section cover deploying your application with ScaleBop. Operational detail about ScaleBop’s own platform (how the ScaleBop product itself is hosted and run) is internal to ScaleBop and is not published here.