[Critical] GCP/Azure: Finish or remove from marketing

[jessfortemnaturae8717]

Problem

Website and docs claim multi-cloud support, but GCP/Azure handlers are stubs:

• AWS: 97 resource types with full handlers
• GCP: ~6 types — basic patterns only
• Azure: ~6 types — basic patterns only

// src/resources/gcp/*.ts — mostly TODO comments
// src/resources/azure/*.ts — mostly TODO comments

Risk

• Misleading marketing → customer complaints
• Enterprise customers expecting GCP/Azure parity will churn
• Credibility damage

Options

Option A: Finish GCP/Azure (4-6 weeks)

Add deterministic handlers for top 50 GCP/Azure resource types:

GCP Priority:

• google_compute_instance
• google_sql_database_instance
• google_storage_bucket
• google_container_cluster
• google_bigquery_dataset
• ... (50 total)

Azure Priority:

• azurerm_virtual_machine
• azurerm_sql_database
• azurerm_storage_account
• azurerm_kubernetes_cluster
• ... (50 total)

Option B: Remove from marketing (1 day)

1. Update website to say "AWS support (GCP/Azure coming soon)"
2. Add "beta" badge to GCP/Azure in docs
3. Remove multi-cloud from pricing page claims

Recommendation

Option B now, Option A for v2.

Don't sell what doesn't work. Be honest about AWS-first, add GCP/Azure when ready.

Tasks (Option B)

• Update website hero/copy to focus on AWS
• Add "Coming Soon" badge to GCP/Azure on integrations section
• Update docs to mark GCP/Azure as experimental
• Remove multi-cloud claims from any sales materials
• Create roadmap issue for GCP/Azure v2

---

Priority: P0 — Must fix before monetization