As of 13 August 2026, AI cannot deploy your business app to the cloud.

What to actually do

1. Hand it to a person

   The route this page recommends

   Someone with a licence or accountable authority has to sign this before it counts.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface gets you a draft, but you cannot verify it yourself. That is the catch.

   How to actually do it

   1. Open the app repository and the documentation for the chosen cloud provider, then record the framework, runtime version, database, storage, domain, environments and data types without copying secrets.
   2. Create a separate staging project or environment and gather the app configuration, dependency files, build command, start command, database migration steps and required environment-variable names.
   3. Paste that information into the prompt and ask the model for the architecture, missing information, deployment files and commands, keeping passwords, API keys and private keys out of the chat.
   4. Have a developer or cloud administrator compare the proposed resources, permissions, network rules, secret storage, database settings, backups and costs with the provider documentation before running anything.
   5. Apply the reviewed configuration to staging, deploy the app there, run the model's tests and record the logs, errors, authentication results, authorisation results and database migration outcome.
   6. Ask the model to update the rollback and go-live checklist using the staging results, then have the reviewer inspect the resulting changes and confirm that a tested restore and rollback path exists.
   7. Deploy to production only after the reviewer approves the change, then check the domain, TLS, monitoring, logs, backups, access controls and a real user journey before sending the app to staff or customers.

   Prompt

   Act as a deployment assistant, not an operator. I need to deploy this business app to [cloud provider or hosting platform] for [business purpose]. The app uses [language and framework], stores data in [database or storage], and currently runs at [local or existing hosting setup]. Its expected users are [user group], and it handles [types of data]. The required domain is [domain or none], and the required environments are [staging and production, or other].
   
   Using only the information I provide, produce:
   1. A deployment architecture in plain English.
   2. A pre-deployment checklist covering dependencies, environment variables, database migrations, backups, access control, secrets, TLS, logging, monitoring, rollback and data protection.
   3. The exact files, settings and commands I need, clearly separated for staging and production.
   4. A list of missing information and assumptions. Do not invent cloud resources, IP addresses, credentials, domains, permissions or configuration values.
   5. A safe test plan, including a rollback plan and checks for authentication, authorisation, data isolation, error handling and performance.
   6. A final go-live checklist.
   
   Never ask me to paste passwords, API keys, private keys or personal data. Mark every step that needs a cloud administrator or qualified developer. Do not claim that the app is deployed or secure. Do not recommend production release until the tests, logs, backups, permissions and rollback procedure have been checked by a person with relevant cloud and application security experience.
   
   Here is the available project information:
   [PASTE CODE STRUCTURE, CONFIGURATION WITH SECRETS REMOVED, LOGS, CURRENT HOSTING DETAILS AND REQUIREMENTS HERE]

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.