Loading…
Loading…
Archi and every other ArchiMate tool stops at the diagram. Archiet is the code generation layer: your ArchiMate 3.2 model compiles to backend, frontend, database migrations, CI/CD, and compliance documentation — across 9 web stacks (Flask+Next.js production-ready; FastAPI, Django, NestJS and more in active beta).
Import from Archi · Sparx EA · Visual Paradigm · any ArchiMate Exchange Format export
Flask · FastAPI · Django · NestJS · Laravel · Go · Java · Rails · .NET · Tauri+Rust
Enterprise architects draw ArchiMate models. They document business processes, application components, technology nodes, compliance drivers, and implementation plateaus. Then the model is handed off to a development team — and the translation from model to code begins again from scratch.
Archi is the reference implementation of ArchiMate: excellent for modeling, widely used, genuinely open source. But it does not generate application code. Sparx Enterprise Architect and Visual Paradigm generate UML-style class stubs — not full-stack applications with authentication, multi-tenancy, compliance controls, and deployment configuration.
Archiet fills the gap. The Architectural Genome is an intermediate representation derived from your ArchiMate model that drives deterministic code generation across nine web stacks and Tauri+Rust for desktop. Same model, any stack, same compliance controls.
Each ArchiMate layer maps to a set of generated artifacts. The mapping is deterministic — the same model always produces the same output.
| ArchiMate Layer | ArchiMate elements | Generated by Archiet |
|---|---|---|
| Business Layer | Business processes, roles, actors, services, interfaces | Workflow scaffolding, user roles, RBAC, business-logic endpoints |
| Application Layer | Application components, data objects, interfaces, services | API routes, service classes, DTOs, database entities, migrations |
| Technology Layer | Infrastructure nodes, communication paths, artefacts | Docker, docker-compose, CI/CD, Kubernetes manifests, environment config |
| Motivation Extension | Goals, requirements, constraints, drivers, assessments | ADRs, compliance flags, architecture documentation, Annex IV trace |
| Implementation Extension | Work packages, deliverables, gaps, plateaus | Project milestones, delivery roadmap, phased implementation guide |
Export from Archi, Sparx EA, Visual Paradigm, or any ArchiMate tool — or paste your model as text. You can also describe your architecture in plain English and Archiet will produce the Genome.
Archiet maps each ArchiMate element to the Genome IR — entities, services, compliance requirements, technology choices. You review and confirm the spec before generation.
Generate Flask + Next.js, FastAPI, Django, NestJS, Laravel, Go chi, Java Spring Boot, Rails, .NET, or Tauri+Rust. Same Genome, any stack.
The ZIP ships backend, frontend, database migrations, Docker, CI/CD, ArchiMate-grounded ADRs, and compliance documentation. Zero manual wiring.
Every generated archive is a complete, runnable application. No manual wiring.
Archiet accepts ArchiMate exports from Archi (the reference open-source implementation), Sparx Enterprise Architect, Visual Paradigm, BiZZdesign Horizzon, BOC ADOIT, and any tool that exports to ArchiMate Exchange Format (the Open Exchange standard). You can also paste your architecture as text — a markdown description, a C4 model, or a plain English summary — and Archiet's PRD extractor produces the Genome.
All five ArchiMate 3.2 structure aspects — Business, Application, Technology, and the Motivation and Implementation extensions — map to Genome fields. The Strategy extension (Capability, Value Stream, Course of Action) maps to the genome's capabilities block and drives RBAC and workflow scaffolding. Physical elements (physical infrastructure) do not generate code but are preserved in the documentation.
The Architectural Genome is Archiet's intermediate representation — a YAML spec derived from your ArchiMate model that encodes entities, services, compliance requirements, and technology choices in a form the code generator can process deterministically. It is the formal model that sits between your architecture diagram and the generated code. You can inspect, diff, and version-control it in git.
No. The most common entry point is a plain-English PRD or product description. Archiet's extraction pipeline produces the Genome from natural language. An existing ArchiMate model — from Archi, Sparx EA, or any tool — is the highest-fidelity input because the formal model already encodes the architectural decisions precisely. But the workflow works from a description too.
Yes, and this is one of the key advantages over diagram-only ArchiMate tools. When your model — or your Genome spec — includes compliance requirements (HIPAA, SOC 2, GDPR, DORA, EU AI Act, etc.), the generated code carries the corresponding controls: encryption, audit logging, access scoping, data minimisation, documentation. The compliance controls are structural properties of the generated system, not documentation added after the fact.
jArchi (Archi's JavaScript plugin) lets you script the Archi tool — generate reports, validate models, export data. It does not generate application code. Archiet takes the ArchiMate model as input and produces a full production application: backend, frontend, database, CI/CD, and compliance documentation. The code generator is deterministic; the same Genome always produces the same output.
Import your existing ArchiMate model or describe your architecture — Archiet produces the Genome, you review it, and the code generation run ships the full application. Free plan available.
Related: spec-driven development · compliance by construction · architecture glossary