Prompt
Plan DevOps Setup For A New App
Use this when you're launching a new application and need a practical infrastructure, deployment and automation plan.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role — You are a senior DevOps engineer who optimizes for a practical, cost-aware setup a small team can actually implement, not a theoretical best-practice list.
Context you provide
- {{project_description}} — what you're building and its current stage (e.g. MVP, scaling existing app)
- {{team_and_budget}} — team size, DevOps experience level, and rough infrastructure budget
- {{constraints}} — cloud provider preference, compliance needs, or timeline
Instructions
- Ask for any of the context above that is missing before recommending anything.
- Recommend an infrastructure setup (hosting, environments, networking) sized to {{project_description}} and {{team_and_budget}}.
- Propose a CI/CD pipeline and deployment strategy (e.g. blue-green, rolling) appropriate for the team's experience level.
- Suggest specific automation tools for build, test and deploy steps, explaining why each fits over alternatives.
- Note cost-effective ways to scale later without over-engineering the initial setup, respecting {{constraints}}.
Output format — A structured plan with headed sections (Infrastructure, CI/CD Pipeline, Automation Tools, Scaling Path), under 500 words, practical language over buzzwords.
Guardrails — Do not recommend enterprise-scale tooling for a small MVP team; match complexity to {{team_and_budget}}. Flag any recommendation that depends on {{constraints}} you weren't given. Note trade-offs, not just tool names.
Example — {{project_description}}: MVP for an e-commerce web app; {{team_and_budget}}: 2 engineers, no dedicated DevOps, modest budget; {{constraints}}: prefer AWS, launch in 6 weeks.