# How do I deploy self-hosted software safely in production?

Canonical page: https://launchinyourcloud.com/questions/production-deployment/

Prepare the account or project, guardrails, budgets and logging first. Review the deployment artifact, use least-privilege identities, and test monitoring and restoration. Assign owners for upgrades, incidents and exit before exposing the production service.

Answer page: https://launchinyourcloud.com/questions/production-deployment/
Answer reviewed: 2026-11-21

- [Follow the production launch checklist](/guide/launch-checklist/)
- [Download the launch evaluation toolkit](/guide/toolkit/)


## Use a staged acceptance plan

Before installation, establish the selected account or project, available access controls, network boundary, logging and budgets. Review the installer and runtime identities separately. Keep the supported artifact version and configuration under change control, with secrets handled through the chosen environment’s secret-management process.

## Prove operation before go-live

Deploy a representative non-production workload. Test failure detection, backup restoration, access removal and a supported upgrade. Verify outbound connections and compare actual resource usage with the sizing assumptions. Do not infer production recovery from a successful initial installation.

Record named owners for daily operation, security fixes, incident response and support escalation. Write down the export and removal procedure as well. The launch checklist is intended to turn these decisions into evidence you can review before production traffic depends on the service.

