Taking an app live involves more than its first successful deployment. Refer to this checklist as you prepare your project, verify the result, and plan for future updates.

Before, during, and after deployment

Before you deploy

Make sure the app and its supporting systems are ready:

• Compare the project with the current Webflow Cloud app requirements, then run the app and its production build locally.
• Verify the GitHub repository, app root, and branch containing the version you want to deploy.
• Decide whether the app belongs alongside a Webflow site or on its own domain. Check that its mount path won't conflict with an existing page.
• Identify where the app's data is managed and how updates will reach the experience.
• Keep private credentials out of the code and repository, and confirm who can maintain the app after launch.

While you deploy

Check both the deployment and the experience it produces:

• Confirm that Cloud is using the intended repository, branch, app root, and environment.
• Review the build status. If it fails, start with the first useful error in the build log.
• Open the live app at its expected domain or mount path and test its routes, links, assets, and main features.
• Test successful, empty, and failed data states where they apply.
• Confirm that private credentials don't appear in browser-delivered code or requests.

Publishing the Webflow site and deploying the Cloud app are separate workflows. Check both when the live experience includes a Webflow site and an app mounted alongside it.

After launch

Plan for the updates that may follow:

• Check the live experience after each deployment, especially its routes and data connections.
• When an environment tracks a GitHub branch, push app changes to that branch to trigger a new deployment.
• Export DevLink components again when their Webflow source changes, then test and deploy the updated app code.
• Review Cloud usage and the limits of connected APIs or services.
• Keep credentials, dependencies, and access current.
• Name a primary owner and a backup who can investigate problems and deploy an update.

The right level of planning depends on the app. A public calculator may need fewer controls than a signed-in customer portal, but neither should depend on technical information that only one person knows.

Additional resources

Check out these resources for more details on important decisions and workflows for deploying an app with Webflow Cloud.

• Bring your own app — current requirements for preparing and deploying an existing app
• Webflow Cloud environments — branches, mount paths, environment variables, and secrets
• Webflow Cloud deployments — deployment history, build logs, runtime logs, and rollback guidance
• Storing data in Webflow Cloud — the available storage options and how they connect to an app
• Webflow Cloud usage and limits — usage monitoring, with current resource limits available in the limits reference

That's a wrap

Click the Complete course button in the progress box on the right, then head back to the Webflow University Courses page to start your next course.