OPEN SOURCE AWS + GCP

Write the architecture. We’ll check it.

Turn concise cloud text into a validated, accessible diagram—right in your browser.

✓ AWS + GCP
✓ Semantic checks
✓ Deterministic SVG
✓ No sign-up

ARCHLEX / PLAYGROUND READY · VALID

01 SOURCE

direction LR
provider aws
validation normal

account global-core {
  region us-east-1 {
    vpc primary-vpc {
      subnet app-subnet-1 {
        app_primary: ecs
        db_primary: rds
      }
    }
  }
}

Multi-region AWS architecture rendered by ArchLex — Provider-aware layout · deterministic SVG

NOT JUST BOXES THE MODEL IS THE PRODUCT

Your diagrams should understand what they describe.

Drawing tools see shapes. ArchLex sees cloud resources, boundaries, and typed relationships—so the diagram can tell you when the architecture does not add up.

DRAWING TOOL

Everything is a rectangle. Every connection is accepted.

NO SEMANTIC CONTEXT

ARCHLEX

API GATEWAYinvokes →LAMBDAwrites →DYNAMODB

Provider rules validate containment and relationship compatibility.

✓ ARCHITECTURE VALID

Built for infrastructure engineers.

Every feature exists to keep architecture legible, reviewable, and honest.

DIAGNOSTICS

Actionable diagnostics, never a dead end.

Invalid source produces precise messages and the best partial diagram possible. Fix the system without losing the system.

AL-SEM-REL-003 relationship incompatible

OUTPUT

Stable output built for engineering workflows.

Deterministic ordering, stable IDs, and accessible SVG make diagrams useful in docs, review, version control, and tooling.

<svg role="img" data-archlex-version="1">

PROVIDERS

Cloud-aware from the first token.

AWS and GCP catalogs bring official service imagery, aliases, containment rules, and provider-specific semantic checks.

provider aws · provider gcp

ONE SOURCE TWO KINDS OF CLARITY

Write the intent. Inspect the system.

Concise source stays readable in review. The render gives every stakeholder the same architecture at a glance.

Try this example →

ARCHLEX / PLAYGROUND READY · VALID

01 SOURCE

direction LR
provider aws
validation normal

ingress_api: api-gateway
ingest_fn: lambda
events_bus: eventbridge
notification_topic: sns
buffer_queue: sqs
processor_fn: lambda
lake: s3
nosql_store: dynamodb

ingress_api -[invokes]-> ingest_fn
ingest_fn -[publishes]-> notification_topic
notification_topic -[forwards]-> buffer_queue
events_bus -[triggers]-> buffer_queue
buffer_queue -[batch_invokes]-> processor_fn
processor_fn -[persists]-> nosql_store
processor_fn -[archives]-> lake

AWS event pipeline architecture rendered by ArchLex — Provider-aware layout · deterministic SVG

OSS / ESM BROWSER + NODE.JS

From install to architecture in one small API.

Use the core renderer directly, embed the SVG in your own interface, or start in the playground and learn the language by editing real examples.

Read getting started → API reference

01 INSTALL

npm install @archlex/core @archlex/aws @archlex/gcp

02 RENDER

import { createArchLex, awsProvider, gcpProvider } from '@archlex/core';

const archlex = createArchLex({
  providers: [awsProvider(), gcpProvider()]
});

const result = await archlex.render(source);
document.querySelector('#diagram').innerHTML = result.svg;

READY WHEN YOU ARE NO ACCOUNT REQUIRED

Your architecture already lives in code. Diagram it there too.

Open playground → Explore the docs