ArchLex
ArchLex is an open-source cloud architecture diagramming tool that generates validated diagrams from natural language or DSL input, integrating directly with Claude, Cursor, and Codex via MCP server. It validates architectures against AWS, GCP, and Kubernetes rules before rendering official-icon SVG output, preventing hallucinated resources and ensuring compliance with platform best practices. Diagrams are stored as text-based source code, making them reviewable and versionable in Git alongside application code. Agencies can embed diagram rendering in client portals via npm packages or use ArchLex internally to accelerate architecture design during code review. As open-source software, ArchLex has no per-client licensing cost and no vendor lock-in, but requires self-hosted deployment and in-house engineering support.
ArchLex is an open-source cloud architecture diagramming tool, integrating with Claude, Cursor, Codex, and VS Code. InnovaAI scores it 5.3/10 for agency resale.
Agency Audit
ArchLex generates validated cloud architecture diagrams from natural language or its own DSL, integrating directly with Claude and Cursor to embed diagram generation into AI coding workflows. It validates against AWS, GCP, and Kubernetes rules before rendering official-icon SVG output, making architectures reviewable as text-based code diffs. Best suited for cloud infrastructure agencies and DevOps consultancies that bill clients for architecture design or need to embed diagrams in client portals via npm packages. As an open-source tool, ArchLex has no vendor lock-in but also no SaaS support tier, making it a fit for technically mature teams rather than agencies seeking managed services.
5.3/10
Depends on volume
2d 1-2 days
- Your agency delivers cloud architecture consulting to DevOps teams and needs to embed diagrams in client reports or dashboards using npm packages.
- You work with Claude or Cursor daily and want architecture diagrams generated inline during code review without context-switching to Lucidchart or Visio.
- You bill clients for architecture validation against AWS, GCP, or Kubernetes compliance rules and need a tool that prevents hallucinated resources.
- Your clients use primarily Azure, Oracle Cloud, or on-premises infrastructure that falls outside AWS, GCP, and Kubernetes validation scope.
- You need a fully managed SaaS with vendor support and do not have engineering capacity to deploy and maintain ArchLex infrastructure.
- Your agency resells architecture tools as a white-label retainer and requires branded client-facing portals with support escalation.
Profit Path
Estimate available after setup inputs
$1K–$3K/project
Monthly Recurring
Planning benchmark at United States price levels. Not a measured market survey.
Platform Features
Core capabilities of ArchLex
Natural language to diagram generation
Describe cloud architectures in plain English or ArchLex DSL, and the tool generates validated diagrams with official cloud provider icons. Eliminates manual diagramming and reduces time from architecture concept to reviewable output.
Architecture validation against cloud rules
Validates diagrams against AWS, GCP, and Kubernetes compliance rules before rendering, catching invalid resource configurations and preventing hallucinated components. Ensures client architectures meet platform best practices without manual review.
MCP server integration with coding agents
Connects directly to Claude, Cursor, and Codex via MCP server, allowing architects to generate and refine diagrams without leaving their IDE. Embeds diagram generation into existing AI-assisted code review workflows.
Text-based diagram source for code review
Diagrams are defined as readable text-based DSL, making them diffable and versionable in Git. Enables architecture changes to be reviewed like code, with full audit trail and rollback capability.
SVG rendering with official icons
Outputs diagrams as official-icon SVG files compatible with web applications and documentation. Supports embedding in client portals via npm packages for self-service architecture visualization.
Open-source deployment model
Available as open-source software with no vendor lock-in, allowing agencies to self-host and customize validation rules. Reduces per-client licensing costs for high-volume architecture consulting practices.
What Makes ArchLex Different
Unique advantages vs similar tools in this niche
Validates diagrams against cloud provider rules
vs Generic diagramming tools that only draw shapesArchLex understands cloud resources and relationships, preventing invalid architectures.
Integrates with AI agents via MCP
vs Manual diagram creation or separate AI toolsAgents can generate and validate diagrams directly in the coding workflow.
Text-based source for easy code review
vs Binary or proprietary diagram formatsThe DSL source is concise and diffable, making reviews consistent.
Value Equation
Outcome-likelihood-time-effort assessment for ArchLex
Value math requires real pricing
The Value Equation (dream outcome × likelihood ÷ time × effort) feeds directly into ROI math. ArchLex has no published pricing, so we hold this section until real numbers are available.
Contact ArchLexPricing
Platform cost for ArchLex
Custom pricing
ArchLex uses custom/enterprise pricing: rates aren't published publicly. Contact their team directly for a quote.
Contact ArchLexMarket Intelligence
Offer + scale economics for ArchLex
Offer economics require real pricing
Offer economics, scale projections, and margin potential all depend on ArchLex's actual platform cost. Once pricing is published or shared with your agency, we'll compute the full breakdown here.
Contact ArchLexInvestment Decision Framework
Strategic vetting analysis for ArchLex
Consider
Favorable fit, worth a closer look
Buy If
4Your agency delivers cloud architecture consulting to DevOps teams and needs to embed diagrams in client reports or dashboards using npm packages.
You work with Claude or Cursor daily and want architecture diagrams generated inline during code review without context-switching to Lucidchart or Visio.
You bill clients for architecture validation against AWS, GCP, or Kubernetes compliance rules and need a tool that prevents hallucinated resources.
Your team is comfortable managing open-source deployments and does not require vendor SLA support.
Skip If
4You work with non-technical stakeholders who cannot read DSL syntax or text-based diagram source code in pull requests.
Your clients use primarily Azure, Oracle Cloud, or on-premises infrastructure that falls outside AWS, GCP, and Kubernetes validation scope.
You need a fully managed SaaS with vendor support and do not have engineering capacity to deploy and maintain ArchLex infrastructure.
Your agency resells architecture tools as a white-label retainer and requires branded client-facing portals with support escalation.
Bottom Line
ArchLex generates validated cloud architecture diagrams from natural language or its own DSL, integrating directly with Claude and Cursor to embed diagram generation into AI coding workflows. It validates against AWS, GCP, and Kubernetes rules before rendering official-icon SVG output, making architectures reviewable as text-based code diffs. Best suited for cloud infrastructure agencies and DevOps consultancies that bill clients for architecture design or need to embed diagrams in client portals via npm packages. As an open-source tool, ArchLex has no vendor lock-in but also no SaaS support tier, making it a fit for technically mature teams rather than agencies seeking managed services.
Reality Check
ArchLex is open-source with no commercial support tier, so agencies adopting it must maintain their own deployment and troubleshoot integration issues without vendor escalation. Validation rules are limited to AWS, GCP, and Kubernetes, so multi-cloud or on-premises architectures outside those platforms cannot be validated.
Low effort: self-service setup with guided onboarding
Academy for ArchLex
Work through it in order: the course for this service first, then the modules behind it.
No Academy modules are published for this service yet. Browse the full Academy
Why this category matters
The commercial case before the tooling.
Core concepts
The mental model you need to price and scope the work.
- Scaffold, Don't SubstituteConcept
Scaffold, Don't Substitute is a framework for agencies adopting AI code tools: use them to generate scaffolding and handle maintenance, but never as a replacement for human architectural oversight. The strategic insight from the category description warns that over-reliance risks code quality inconsistency and vendor lock-in. For example, an agency might use Verdent to rapidly prototype a full-stack app from a natural language brief, then have senior engineers review and refactor the generated code before delivery. Similarly, Ripple can auto-fix consumer code when APIs break, but a human must verify the changes align with client contracts. This framework helps agencies capture speed advantages while protecting quality and client trust. It also aligns with recent market data showing that AI agent loops can run 100x cheaper via simulation, but accuracy tradeoffs demand human judgment for high-stakes tasks.
- Human Checkpoint RatioConcept
The Human Checkpoint Ratio is the proportion of AI-generated code that passes through human review before delivery. Agencies adopting AI code tools often see speed gains, but unchecked automation can introduce subtle bugs and architectural drift. The framework holds that the optimal ratio depends on task risk: scaffolding and boilerplate can run nearly autonomous, while core business logic and client-facing features demand human sign-off. For example, HumanLayer structures workflows with six phases, each requiring human checkpoints, ensuring alignment and early error catching. Similarly, Ripple automates API break fixes but relies on developers to review generated pull requests. Agencies should define explicit checkpoints per task type, balancing speed with quality. A 100x cost reduction in simulation-based agents, as reported by Marktechpost, suggests that high-volume, low-stakes tasks can tolerate lower ratios, freeing human oversight for critical paths.
- Maintenance Over BuildConcept
AI code tools shift agency value from greenfield builds to ongoing maintenance. Platforms like Ripple auto-fix breaking API changes across repos, while Verdent generates full-stack apps from prompts, making initial builds cheap and commoditized. The durable margin lies in keeping client systems healthy: dependency updates, security patches, and refactors. Agencies that sell maintenance retainers, not just launch fees, convert a one-off project into recurring revenue. A 100x cost reduction in agent loops, as reported in simulation research, makes automated upkeep affordable at scale. The framework: use AI for scaffolding and repairs, but anchor the commercial model on continuous care, where human oversight prevents the quality drift that pure automation introduces.
Decision and risk
How to judge the fit, and the ways it goes wrong.
- AI Code Tools Rule: Scaffold Fast, Architect SlowEvaluation Rule
Use AI code tools for scaffolding and maintenance tasks, but keep human architectural oversight for production decisions.
- AI Code Tools Rule: When Delivery Speed Is the Bottleneck, Automate Maintenance Before Greenfield BuildsEvaluation Rule
Use AI code tools for scaffolding and maintenance automation first, and reserve human architects for greenfield design and final review.
- The Scaffolding-Only Trap: Why AI Code Tools Stall in Agency DeliveryFailure Pattern
- The Unreviewed Merge Trap: Why AI Code Tools Fail in Agency DeliveryFailure Pattern
8 modules selected for ArchLex
Frequently Asked Questions
Answers about pricing, setup, implementation, and more
ArchLex generates cloud architecture diagrams from natural language descriptions or its own DSL, validates them against AWS, GCP, and Kubernetes rules, and renders official-icon SVG output. It integrates with Claude, Cursor, and Codex via MCP server, allowing architects to generate diagrams inline during code review. Diagrams are stored as text-based source code, making them reviewable and versionable in Git.
ArchLex is open-source software with no commercial pricing. Agencies deploy it on their own infrastructure and pay only for hosting and compute resources.
No verified white-label program. ArchLex is an open-source tool that agencies deploy internally; client-facing surfaces depend on how the agency integrates diagram output into their own portals or reports. Agencies can embed SVG diagrams in branded client dashboards via npm packages, but ArchLex itself does not provide a branded SaaS interface.
Yes. ArchLex provides an MCP server that integrates natively with Claude, Cursor, and Codex, allowing architects to generate and refine diagrams directly within their coding environment without switching tools.
Setup time depends on your deployment model. If you self-host ArchLex, initial infrastructure setup takes 30-60 minutes; per-client onboarding is minimal once the parent deployment is running. If you embed diagrams in a client portal via npm packages, integration time is 15-30 minutes per client.
Cloud infrastructure agencies serving DevOps teams, SaaS startups designing multi-region AWS or GCP deployments, and Kubernetes consultancies validating cluster architectures. Also fits agencies that embed architecture diagrams in client portals or technical documentation.
ArchLex validation rules are limited to AWS, GCP, and Kubernetes. Multi-cloud or on-premises architectures outside those platforms can still be diagrammed, but validation will not catch platform-specific compliance issues.
ArchLex is open-source with no commercial support tier. Agencies rely on community documentation, GitHub issues, and their own engineering capacity for troubleshooting and customization. There is no vendor SLA or escalation path.