The deployment lifecycle
Each deployment is a complete attempt to turn one repository revision into a running application. Infrastry records the revision, build output, resulting runtime, and final health state together.
- Queued means the launch is waiting to begin.
- Building means Infrastry is preparing the application artifact.
- Deploying means the new runtime is being created and connected.
- Healthy means the application answered its health check and is available.
Deploy a change
Use Deploy on the application page to launch the latest selected branch. When a connected GitHub repository is configured for deploys on push, changes to that branch can also start a new deployment.
- Check Settings before deploying if the repository or branch changed.
- Use Builds to compare the source revision and artifacts for each attempt.
- Wait for health verification before treating the new version as ready.
Note: A redeploy creates a new attempt. It does not rewrite the history of the previous deployment.
Cancel a deployment
Cancel an in-progress deployment when you selected the wrong revision or no longer want the launch to continue. Infrastry stops the active work and removes partial resources created by that attempt.
- The cancelled attempt remains visible in deployment history.
- An earlier healthy version remains available when the cancellation happened before it was replaced.
- Start a fresh deployment after correcting the repository or configuration.
Stop an application
Stopping removes the running application while keeping its configuration, deployment history, and retained persistent data. Use it when the application should no longer serve traffic but may be launched again later.
- Open Settings and review the stop action before confirming it.
- A stopped application does not have an active live URL.
- Deploy again when you are ready to recreate the runtime.