The Problem
Every GCP engagement starts the same way. Discovery call, spreadsheet
of requirements, weeks of manual Terraform, IAM wiring, VPC design,
org policies, budget alerts. Then a review cycle to catch what was
missed. Then another.
For a process that happens at the start of every cloud project,
it's remarkably unautomated.
What a Landing Zone Actually Requires
A production-ready GCP landing zone typically includes:
- Organization hierarchy and folder structure
- VPC and shared networking
- IAM roles and service accounts
- Org policies and constraints
- Budget alerts and billing controls
- Security baselines
- FAST-compatible configuration
Getting all of this right manually takes 2-3 weeks minimum.
A New Approach: Merlin
Merlin is a GCP landing zone generator. Answer an architecture
questionnaire — org structure, environments, compliance, networking
— and it outputs a complete production-ready landing zone.
What comes out:
- FAST-compatible Terraform files
- Architecture and security scorecards
- Mermaid diagrams
- Validation warnings
See the Real Output
Published openly on GitHub — no signup required:
Includes Simple, Standard, and Advanced profile examples.
Top comments (0)