infra-architect

To design hosting infrastructure from project requirements, you input structured needs covering scale, budget, and geography. The system processes these drivers to output a complete hosting architecture, platform-ready configuration files, and an INFRA_DECISIONS.md document explaining every choice in plain English.

A complete cloud infrastructure architecture blueprint includes app hosting, database, file storage, CDN, auth, email, monitoring, CI/CD, and scheduled background tasks. It also provides explicit migration paths, cost projections, and a security checklist.

You generate CI/CD and monitoring configuration files by feeding structured infrastructure requirements into an architecture generator. It applies opinionated decision trees optimized for small teams to produce platform-ready configs alongside an INFRA_DECISIONS.md document with cost projections.

The best way to choose a cloud platform for a small team is using decision trees that prioritize simplicity and practical scaling. This approach evaluates your specific reliability, complexity, and budget drivers to select an opinionated stack like Vercel, Neon, and R2 with clear migration paths.

Yes, you need a requirements file before generating an infrastructure deployment plan. The system requires reading a structured `.planning/infra-requirements.md` file to extract scale, geography, budget, and existing stack drivers needed to produce accurate hosting configurations.

You should not use an automated infrastructure architecture generator if your project lacks defined requirements or involves highly custom, non-standard platform dependencies. The tool relies on structured input and opinionated decision trees tailored for typical app hosting, database, and CI/CD scaling scenarios.