{"kind":"guide","markdown":"# Deployment pitfalls and mitigations\n\nCanonical page: https://launchinyourcloud.com/guide/pitfalls/\n\n[Guide](/guide/) › Deployment pitfalls and mitigations\n\n\n\n\nPitfall | What happens | Mitigation | \n\n\n\nOver‑broad permissions | Templates request administrator or wildcard access. | Require documented permissions, cloud-specific access guardrails, and reviewed audit logs. | \n\n\nUnclear responsibility | Nobody owns patching, on‑call or key rotation. | Agree a responsibility matrix (section 4) with named owners and response times. | \n\n\nUpgrade drift | Installs fall many versions behind and become hard to support. | Automate upgrades through the pipeline; agree a maximum version lag. | \n\n\nUnexpected infrastructure cost | Default sizing, idle environments or data transfer inflate the bill. | Request a cost model at your scale; set budgets and alerts; tag from day one. | \n\n\nUndisclosed data egress | Telemetry or licence checks send more than expected. | Restrict egress to documented endpoints and inspect traffic during the trial. | \n\n\nSkills gap | The team that bought the software cannot operate it. | Prefer managed cloud services in the stack, ask for runbooks, or choose a BYOC model. | \n\n\n\n\n\n\n\n\n\n\nNext: [browse the directory](/directory/) · See also: [where each model runs](/#where)\n\n\n\n## Further reading\n\nUse the official infrastructure documentation linked in the [cloud provider guide](/clouds/) and the product-specific sources on every directory entry. The responsibility matrix above is a planning example; agree actual ownership with your vendor.\n\nEditorial review: November 10, 2026.\n\n\n\n[Complete guide](/guide/) · [Download evaluation templates](/guide/toolkit/)\n\n\n\n## Related questions\n\n- [How do I know if self-hosted software sends data back to the vendor?](https://launchinyourcloud.com/questions/outbound-data/)\n- [How do I avoid unexpected cloud bills from self-hosted apps?](https://launchinyourcloud.com/questions/unexpected-cloud-bills/)\n- [How do I keep self-hosted software up to date?](https://launchinyourcloud.com/questions/software-upgrades/)\n- [What mistakes should I plan for when self-hosting vendor software?](https://launchinyourcloud.com/questions/self-hosting-mistakes/)\n\n","questions":[],"relatedQuestions":[{"id":"outbound-data","json":"https://launchinyourcloud.com/api/v1/questions/outbound-data.json","markdown":"https://launchinyourcloud.com/questions/outbound-data/index.md","question":"How do I know if self-hosted software sends data back to the vendor?","url":"https://launchinyourcloud.com/questions/outbound-data/"},{"id":"unexpected-cloud-bills","json":"https://launchinyourcloud.com/api/v1/questions/unexpected-cloud-bills.json","markdown":"https://launchinyourcloud.com/questions/unexpected-cloud-bills/index.md","question":"How do I avoid unexpected cloud bills from self-hosted apps?","url":"https://launchinyourcloud.com/questions/unexpected-cloud-bills/"},{"id":"software-upgrades","json":"https://launchinyourcloud.com/api/v1/questions/software-upgrades.json","markdown":"https://launchinyourcloud.com/questions/software-upgrades/index.md","question":"How do I keep self-hosted software up to date?","url":"https://launchinyourcloud.com/questions/software-upgrades/"},{"id":"self-hosting-mistakes","json":"https://launchinyourcloud.com/api/v1/questions/self-hosting-mistakes.json","markdown":"https://launchinyourcloud.com/questions/self-hosting-mistakes/index.md","question":"What mistakes should I plan for when self-hosting vendor software?","url":"https://launchinyourcloud.com/questions/self-hosting-mistakes/"}],"schemaVersion":1,"title":"Deployment pitfalls and mitigations","url":"https://launchinyourcloud.com/guide/pitfalls/"}