Why Merlin?
Your cloud foundation should fit your business — not the other way around.
When other tool hands you a Fortune 500 blueprint and says "good luck simplifying it." Merlin asks who you are first.
THE PROBLEM
Enterprise tools work for enterprises — but small and medium companies need something right-sized.
Today's GCP landing zone tools — Google's Cloud Foundation Fabric FAST and Ollion's Landing Zone Accelerator — share the same philosophy. They start with a reference architecture built for the largest, most complex enterprises. Then they hand it to you.
"You shouldn't need to build a system designed for a big bank just to run 15 virtual machines in the cloud."
— The reality for most organizations adopting GCP
If you're an industrial company with a couple of dozen VMs in a datacenter, do you really need 8 top-level folders, a multi-tier hub-and-spoke network, dedicated security and networking projects, and 50 pages of IAM policy? These tools don't know your answer. They assume the worst case and build for that. The result: over-engineered environments that are expensive to operate, hard to understand, and fragile to change.
And if you are an experienced cloud architect building landing zones for a large enterprise? You're looking at a month of hard work — and that's before rapidly changing compliance requirements collide with even more rapidly changing customer demands. Every framework update, every new business unit, every regulatory shift means going back into the code, tracing dependencies, and re-validating the whole structure. It's not a design problem anymore — it's a maintenance treadmill that never stops.
Merlin turns that treadmill into a design loop. It monitors 11 compliance frameworks and Google best practices recommendations out of the box — so when a framework changes or a new regulation kicks in, you see the impact immediately rather than discovering it during an audit. And when business requirements drift — new teams, new workloads, shifting priorities — you adjust inputs in the wizard, regenerate, and get an updated architecture with code, documentation, and diagrams that all stay in sync. The month of manual rework becomes an afternoon of informed decisions.
Enterprise scale or nothing — most choose nothing
When the only path to a proper cloud foundation looks like a six-month enterprise project with a consulting firm, most companies choose the other option — skip it entirely. They create GCP projects by hand, assign permissions ad hoc, skip the resource hierarchy, and move straight to workloads. It works on day one. Then the bill arrives.
Security Gaps
Overly broad IAM roles, no org policies, no audit logging. Every project is a standalone island with its own attack surface. You don't find out until the breach — or the audit.
Cost Surprises
No budget alerts, no billing export, no cost allocation. Spending is invisible until the monthly invoice arrives 30% higher than expected — and nobody can explain which project caused it.
Operational Drift
Each team configures things differently. Naming conventions diverge. Network ranges overlap. When it's time to connect environments or onboard a new team, the cleanup takes longer than doing it right would have.
Compliance Debt
No centralized logging means no audit trail. No resource hierarchy means no policy inheritance. When SOC 2 or ISO 27001 becomes a business requirement, retrofitting a flat environment costs three times more than designing it right from the start.
The real cost of "nothing" is paid later — in emergency security remediation, in wasted cloud spend nobody can trace, in the six-week project to restructure everything before the auditor arrives. Merlin exists so that "doing it right" doesn't have to mean "doing it like a Fortune 500."
HOW WE'RE DIFFERENT
Template vs. Design Studio
Existing tools are templates — fixed starting points you subtract from. Merlin is a design process — it builds up from your requirements to the right architecture.
| Aspect | Traditional Approach | Merlin ✦ |
|---|---|---|
| Approach | SUBTRACT — Start with an enterprise reference architecture. Strip away what you don't need — if you know what that is. | BUILD UP — Start with discovery questions about your business. Generate exactly the architecture your situation requires. |
| Complexity Fit | One complexity level — enterprise. A 15-VM shop gets the same structure as a bank with 200 teams. | Three profiles — Simple, Standard, Advanced — each with calibrated defaults for hierarchy, IAM, networking, security, and observability. |
| Hierarchy | Typically 6–8 top-level folders regardless of org size. | Simple: 2 folders. Standard: 5. Advanced: 8+ with nesting. Structure matches organizational reality. |
| Configuration | Edit YAML/HCL files. Understand module internals. Comment out what you don't need. Hope nothing breaks. | Guided wizard — Express (accept smart defaults), Guided (review with explanations), Expert (full control). No raw code editing. |
| Iteration | Modify code, re-plan Terraform, debug. Each change is a manual development cycle. | Save your design. Bring it to the stakeholder meeting. Adjust inputs. Regenerate. Decisions stay in context — code follows automatically. |
| Output | Pre-built Terraform modules you fork and maintain yourself. | Production-ready Terraform (FAST-compatible), JSON specification, architecture documentation, and diagrams — generated from your inputs. |
| Expertise Required | HIGH — Must understand GCP resource hierarchy, IAM inheritance, VPC design, org policies, and Terraform fluently. | GUIDED — Contextual explanations at every step. Best practices embedded. Professional judgment still required — but you're not starting from scratch. |
Approach
SUBTRACT — Start with an enterprise reference architecture. Strip away what you don't need — if you know what that is.
BUILD UP — Start with discovery questions about your business. Generate exactly the architecture your situation requires.
Complexity Fit
One complexity level — enterprise. A 15-VM shop gets the same structure as a bank with 200 teams.
Three profiles — Simple, Standard, Advanced — each with calibrated defaults for hierarchy, IAM, networking, security, and observability.
Hierarchy
Typically 6–8 top-level folders regardless of org size.
Simple: 2 folders. Standard: 5. Advanced: 8+ with nesting. Structure matches organizational reality.
Configuration
Edit YAML/HCL files. Understand module internals. Comment out what you don't need. Hope nothing breaks.
Guided wizard — Express (accept smart defaults), Guided (review with explanations), Expert (full control). No raw code editing.
Iteration
Modify code, re-plan Terraform, debug. Each change is a manual development cycle.
Save your design. Bring it to the stakeholder meeting. Adjust inputs. Regenerate. Decisions stay in context — code follows automatically.
Output
Pre-built Terraform modules you fork and maintain yourself.
Production-ready Terraform (FAST-compatible), JSON specification, architecture documentation, and diagrams — generated from your inputs.
Expertise Required
HIGH — Must understand GCP resource hierarchy, IAM inheritance, VPC design, org policies, and Terraform fluently.
GUIDED — Contextual explanations at every step. Best practices embedded. Professional judgment still required — but you're not starting from scratch.
Right-Sized Architecture
Same tool. Different output. Because the input is different.
Merlin's discovery process understands your organization — team count, compliance requirements, workload types, connectivity needs — and calibrates every section of the design accordingly.
Industrial company, 15 VMs, single team
Migrating from an on-premise datacenter. One IT team. No compliance frameworks. Just needs a clean, secure GCP environment that makes sense.
SaaS company, 3 teams, SOC 2 preparation
Growing product company. Engineering, platform, and data teams. SOC 2 audit in six months. Production SLAs. Needs proper separation without over-engineering.
Financial services, multi-region, HIPAA + PCI
Regulated enterprise. Multiple business units across regions. Strict compliance. Hybrid connectivity to on-premises. This is where you actually need the full FAST-scale architecture.
DESIGN PRINCIPLES
What makes Merlin different under the hood
Discovery-Driven Design
Before any configuration begins, Merlin's discovery phase profiles your organization — industry, team structure, compliance, workloads, connectivity. Everything downstream is calibrated by these answers, not by assumptions.
Iterative by Nature
Cloud foundation design is not a one-shot exercise. Merlin saves your current state, lets you bring it to stakeholder meetings, incorporate feedback, adjust decisions, and regenerate — without starting over or manually editing code.
Best Practices, Not Mandates
Every recommendation is backed by Google's FAST patterns and real-world engineering practice. But Merlin explains the rationale and lets you override. Your professional judgment is the final authority — Merlin supports it, doesn't replace it.
Complete, Deployable Output
Not just a diagram. Not just a checklist. Merlin generates the full package — production-ready Terraform code, a machine-readable JSON specification, architecture documentation, and visual diagrams — all consistent with each other, all from a single design session.