> Index of every page on this site: [llms.txt](https://docs.a-line.cloud/llms.txt)

# Builds and deploys

> How a change becomes a running app.

## Builds

An app that runs from a Git repository is built by the platform. A build
checks out the configured GitHub repository and branch and builds an image,
either from your Dockerfile (path and build context are configurable) or from
a build preset for frameworks such as Next.js, Remix, SvelteKit and Nuxt.

Builds start on their own when the app's auto-deploy trigger fires: a `push`
to the branch, a `release` or `prerelease`, or a `tag` matching a pattern.
With `manual`, you start them yourself. Build logs can be read while the build runs and afterwards.

### Refused builds

A build needs compute, so it only starts while the organization can pay for
it. When a push, tag or release arrives while the billing account is out of
credit, or the monthly Actions spend cap is reached, no build starts. The
app's build history shows a `refused` entry instead, with the same reason a
manually started build would get and a link to fix it: top up the billing
account, or raise the spend cap. Further pushes while the app stays refused
update that one entry and count how many were refused, so the history does
not fill up. The organization's owners and admins also get one billing email
when automatic builds start being refused (it follows the billing
notification preference in **Settings > Notifications**). Once the organization can pay again, push again
or start the build by hand: refused builds are not retried on their own. See
[when credit runs out](/billing#low-balance).

## Deploys

A deploy rolls an app out to a new image or configuration. Its status moves
through `pending`, `building` (for Git apps), `deploying`, and ends as
`succeeded`, `failed` or `cancelled`.

Strategies:

- `rolling` (the default): new replicas replace old ones a few at a time.
- `recreate`: old replicas stop before new ones start.

A running deploy can be cancelled, and a past deploy can be rolled back to.
See [deploys in the API reference](/api/reference/apps#deploy-the-apps-current-image-again).
