Google Cloud · Open source · No account required

Google Cloud architecture diagrams as code.

Describe Cloud Run, GKE, Pub/Sub, BigQuery and the rest of your Google Cloud architecture in plain text. ArchLex checks it against a 189-service GCP catalog and renders SVG with official Google Cloud icons.

Try it in the playground Google Cloud reference

GCP VPC Network Architecture.

Cloud Load Balancing routing to Compute Engine and Memorystore inside a regional VPC with subnets.

provider gcp
direction LR
validation normal

account production {
  region us-central1 {
    vpc main-vpc {
      subnet app-subnet {
        app: compute-engine
        cache: memorystore
      }
    }
  }
}

lb: cloud-load-balancing
lb -[routes]-> app
app -[caches]-> cache
app -[writes]-> cloud-storage

See this example in the gallery

Why write Google Cloud diagrams as code?

Organization, region and VPC scopes. An account models an organization or folder, region models regional placement, and vpc with subnet models network containment, so resources sit where they run.
Rules written for Google Cloud. Checks cover subnet containment, network placement, Cloud SQL connectivity, Workflows and Eventarc targets, IAP backends, storage and analytics placement, and GKE Autopilot configuration.
Typed relationships, not loose arrows. Relationship kinds declare allowed sources and targets. An edge that breaks them returns GCP-RELATIONSHIP-INVALID-ENDPOINT-001 with a fix, instead of silently drawing.
Official Google Cloud artwork. Icons come from pinned official Google Cloud archives and are sanitized before rendering.

More Google Cloud architecture examples.

Each example passes ArchLex provider checks and opens in the playground. Browse all examples.

Let your AI agent draw it.

Install the ArchLex skill or connect the MCP server, then ask Claude, Cursor, or Codex to diagram your Google Cloud setup. The agent writes the source, ArchLex validates it, and you get back an SVG.

Agent skill install

npx skills add baires/archlex

Prefer MCP? Follow the MCP server guide.

Render from the command line.

Save the source as a .arch file and render it with the CLI, or call @archlex/core from Node.js or the browser.

npx @archlex/cli render gcp-vpc-architecture.arch --output gcp-vpc-architecture.svg

Google Cloud diagram questions.

Which Google Cloud services are supported?

The GCP catalog has 189 entries across networking, compute, storage, databases, security, observability, integration, analytics, AI, developer tools, containers, hybrid, healthcare, retail, maps and management. Unknown kinds render as generic nodes and report GCP-CATALOG-UNKNOWN-RESOURCE-001.

Does ArchLex read my GCP project?

No. It validates the diagram source only. Rules use facts in the graph and do not infer firewall contents, IAM policy, peering or service configuration.

Can I combine Google Cloud with AWS, Cloudflare or Kubernetes?

Yes. Register several providers and use qualified kinds such as gcp.cloud-run or gcp.pubsub next to aws.lambda, cloudflare.workers or k8s.deployment in one diagram. Each provider validates its own nodes.

Can an AI agent draw Google Cloud diagrams with ArchLex?

Yes. Install the agent skill with npx skills add baires/archlex, or connect the free hosted MCP server at https://mcp.archlex.dev/mcp. Claude Code, Cursor, Codex and other MCP clients can look up Google Cloud resources, validate the source, render SVG and return an editable playground link. No API key or account is required.

Google Cloud service architecture diagrams.

Focused pages for high-search services, each with validated ArchLex source and SVG.

Other clouds.

Mix providers in one diagram when your architecture does.

Open source · MIT licensed

Diagram your Google Cloud architecture.

Open playground Get started