Introduction
Last updated 18/02/2026
The documentation contained in this folder explains how to deploy your application to the web and highlights the key differences in the deployment process depending on your plan.
Deployment behavior varies across plans, including how environments are managed, when changes go live, and whether upgrades occur automatically, or require manual action. Understanding these differences is important to ensure your application is deployed safely, predictably, and in the right environment. And when the time is right upgrades are handled in the correct environment and time frame.
By the end of this guide, you'll know which deployment steps apply to your plan and how to confidently move your application into the production phase.
For each plan, you will learn the following:
- How to deploy your application
- How to apply application upgrades
- How to apply image upgrades
Plans:
Development Deployment Reset for Production Release
When transitioning an application from development to production ready status, the existing development deployment must be removed and redeployed for changes to take effect.
This step ensures:
- The updated application form configuration is properly compiled and packaged
- All environment-specific settings are correctly applied
- Cached or previously deployed assets do not override new changes
- The production environment reflects the latest validated build
Failure to remove and redeploy the development instance may result in outdated form structures, validation rules, or configuration settings persisting in the live environment.
To guarantee that all updates to the application form are correctly applied, a clean redeployment is required as part of the production release process.