ArchiMate-to-code vs modeling-only vs codegen-only
| Factor | EA tools (LeanIX, Ardoq, Sparx EA) | AI scaffolders (v0, Bolt, Lovable) | Archiet | |---|---|---|---| | ArchiMate 3.2 layer fidelity | Full modeling, viewpoints, relationships | None — prompt-driven UI/code | Genome maps Business / Application / Technology layers | | Traceability model → code | Manual export, often lost in translation | None — no formal model | Traceability matrix: user story → FR → entity → route → test → ADR | | Multi-stack output | None (documentation only) | Usually one stack per session | Same genome → Flask, FastAPI, Django, NestJS, Laravel, Go, Java, Rails, .NET, Tauri, SAP, Salesforce, Dynamics | | Compliance alongside code | Governance reports (separate from delivery) | Rarely included | SOC 2, ISO 27001, GDPR, HIPAA, PCI-DSS, DORA, NIS2 docs generated from the same model | | Production scaffold depth | N/A | Frontend-heavy or thin backend | Auth (httpOnly cookies), multi-tenant filters, Alembic migrations, Docker, CI/CD, OpenAPI | | Reproducibility | Model versioning in EA tool | Non-deterministic per prompt | Same PRD/genome → same ZIP (deterministic lowering pipeline) |
The honest split: keep LeanIX or Sparx EA if portfolio management and stakeholder viewpoints are the job. Use Archiet when the architecture model must become deployable software — with evidence an auditor or new engineer can follow.
How Archiet converts an ArchiMate model to code
Archiet does not flatten ArchiMate into CRUD. The pipeline preserves architectural intent through a stack-agnostic genome — an intermediate representation compiled from your model or PRD, then lowered deterministically to each target stack.
Step 1 — Capture the architecture. Upload a PRD, paste requirements, or describe the system in the Blueprint Wizard. ArchiMate element types (Business Process, Application Component, Technology Node, and standard relationship types) are validated against the ArchiMate 3.2 metamodel — not invented ad hoc.
Step 2 — Compile to genome. Business capabilities become entities and services. Application components map to API boundaries and integration adapters. Technology nodes inform deployment topology, runtime services, and infrastructure templates. Material decisions become ADRs in MADR v4 format.
Step 3 — Render and gate. render_genome emits the target stack (you choose Flask + Next.js, NestJS, FastAPI, etc.). delivery_gate blocks shipment if quality is below threshold, placeholder secrets leak, or tenant-isolation patterns are missing.
Representative output tree:
app/ or src/ # Stack-native backend (Flask, FastAPI, NestJS, …)
frontend/ # Next.js + shadcn (when web UI is in scope)
mobile/ # Expo React Native (when mobile is in scope)
migrations/ or alembic/ # One revision per schema change — never db.create_all()
docs/
├── decisions/ # ADR per material choice (DB, auth, ORM, billing, …)
├── traceability/matrix.md # ArchiMate element → requirement → code mapping
├── compliance/ # DPIA, HIPAA, PCI scope — when overlays are enabled
└── security/posture.md # Attack surface + control table
docker-compose.yml # Boot-ready local stack
openapi.yaml # Authoritative API contract
ARCHITECTURE.md # Headline architecture doc (consulting-grade gate)
What ArchiMate practitioners should verify
Before trusting any architecture-to-code tool, check these against the ArchiMate 3.2 specification:
- Layer separation — Business, Application, and Technology concerns must not collapse into a single "Entity" table.
- Relationship direction — Serving, Realization, Assignment, and Aggregation used semantically (not inverted for convenience).
- Viewpoints — Deployment and cooperation views must inform generated infra, not just decorate a PDF.
- Traceability — Every generated route or service should trace back to a source architectural element.
Archiet's model-review UI surfaces the proposed formal model for confirmation before lowering — ambiguity stays in the PRD-parsing zone, not silently guessed during codegen.
Who this is for
- Enterprise architects exporting from ArchiMate tooling who need engineering to receive more than a diagram PDF.
- Solution architects on fixed-bid builds who must hand off a production scaffold plus ADRs, not a slide deck.
- CTOs who want one architecture description to render across multiple stacks when vendors or teams differ.
Free tools to try first
- Architecture score — paste a description, get a scored blueprint in 2 minutes
- Audit my architecture — upload docs, get procurement-grade traceability %
- ROI calculator — justify architecture-to-code to finance
CTA
Describe your system — Archiet builds the ArchiMate-aligned blueprint and generates production-ready code in minutes.
Free plan, no credit card. Start at archiet.com/register.
FAQ
Can I import an ArchiMate file from Sparx EA or LeanIX?
Today the primary intake is PRD and structured requirements via the Blueprint Wizard; ArchiMate fidelity is enforced in the genome schema and model-review step. Export your model's elements and relationships into the wizard, or paste architecture documentation — the pipeline validates against ArchiMate 3.2 types. Native EA tool import connectors are on the roadmap; the genome IR is the stable contract either way.
Which stacks can Archiet generate from the same ArchiMate model?
Fifteen backends including Flask, FastAPI, Django, NestJS, Laravel, Go (chi), Java Spring Boot, Rails, .NET Core, Tauri + Rust, SAP CAP, Salesforce Apex, and Dynamics 365 — plus Next.js web and Expo mobile from the same genome.
Does generated code include architecture documentation?
Yes. Every ZIP ships ADRs, a traceability matrix, security posture notes, and a headline ARCHITECTURE.md — consulting-grade gated before delivery.
How is this different from GitHub Copilot or Cursor?
Copilot and Cursor accelerate writing code inside an existing repository. Archiet generates the repository from the architecture model — entities, auth, billing, migrations, tests, Docker, and docs — before day-to-day IDE assistance begins.
How long does generation take?
Typically 60–120 seconds for a complete blueprint render, depending on stack and compliance overlays.